IFC evidence: what a document proves — and what it does not

Short answer and objective

Evidence is useful when it answers a bounded claim. Permits, declarations, studies, engagement records and measurements serve different purposes; no single document demonstrates comprehensive conformity with IFC standards. This guide teaches a reviewable chain: question, evidence, limitation, conclusion and action.

Official reference: PS1 connects assessment, management programs, capacity and monitoring, and addresses stakeholder engagement and communications. IFC-PS:system IFC-PS:engagement The worksheet below is an original Enverium proposal, not an IFC-mandated form.

What each record can support

This reading is Enverium interpretation. Check authenticity, version, scope and competence before deciding a record’s evidential weight. An authentic document can be outdated; a current document can cover the wrong facility.

Original evidence worksheet

Use one row per testable claim, not per file. One file can support several rows, and one row can require several records.

Workflow for the credit analyst

Start with the conclusion you would need to support. If the question concerns community exposure to traffic, do not automatically accept a corporate policy as the answer. Look for the connection between route, frequency, exposed people, controls and follow-up.

Record discrepancies without erasing earlier evidence. If two teams supply different numbers, preserve units, periods and perimeters before requesting reconciliation. Decide who is competent to assess the material; do not turn format validation into technical review.

IFC’s intermediary note addresses action-plan diligence and monitoring. IFC-FI:diligence IFC-FI:monitoring This proposed workflow adds document traceability, not a new IFC requirement.

Workflow for the evidence supplier

Supply a readable index with owners, versions and limitations. When an answer depends on third-party data, explain how it was obtained and what was checked. Separate public information from confidential material; use controlled references instead of attaching unnecessary personal data.

An adequate response is specific: “measurement M-14 covers three operating days on line 1; line 2 was stopped; the next campaign is planned.” An inadequate response would be: “we monitor everything and are compliant.” The first lets the analyst evaluate coverage; the second does not bound what has been demonstrated.

Fictional case: valid permit, unanswered question

Horizonte supplies a valid permit and factory noise report. The bank’s request, however, concerns nighttime traffic from an expansion. Fictional example: the analyst records the permit as authentic and relevant to the existing operation, but does not conclude that it answers the new access-road question.

The company explains that the report excluded traffic, identifies the design version and proposes a focused study. The worksheet conclusion is “does not resolve this question,” not “invalid document” or “noncompliant company.” A technical owner must assess the new material; the bank retains the transaction decision within its own governance.

This case shows why document quality and evidential sufficiency are separate dimensions. Better file organization does not eliminate a substantive gap.

Review checklist

• Does the question define the facility, period and activity?
• Can the source, version and locator be retrieved?
• Does the conclusion respect the method’s limitations?
• Do records contradict each other, or the narrative?
• Are future plans separated from observed results?
• Does the person concluding have competence and authority?
• Is there an explicit trigger for reopening the assessment?

Limitations: absence, confidence and confidentiality

Missing evidence should not automatically become compliance, zero impact or a proven violation. “Not identified” also requires an explanation of where and how the search was conducted. The proposed classification concerns sufficiency for a question, not an official IFC score.

The worksheet does not authorize public disclosure of customer records. Preserve access controls, confidentiality and data minimization. Publish educational cases using fictional data or appropriately assessed authorization and anonymization, without claiming independent verification that did not occur.

Further reading

Return to IFC scope or the intermediary workflow. For aggregated disclosure data, see GRSAC evidence and PCAF, each with its own methods and purposes.