Always/Never Audit · worked example

The safeguards, audited

IFC's Performance Standards, read the way a lender's E&S desk or a CAO complaint reads them: for enforcement, not intent. Every quote below is checked against the 2012 source, character for character.

The finding

Three gold-standard safeguards. Not one of them lets the person they were written to protect enforce a single line.

The IFC Performance Standards are the closest thing project finance has to a constitution, and every Equator Principles lender treats them as the floor. Read them for what a client should intend and they are humane and complete. Read them the way a complaint reads them, hunting for the word that turns a requirement into a preference, and a pattern surfaces on the first pass: the obligation is stated in binding language, and then, at the exact moment it might stop a project, a softener reopens the question.

This is a worked example of the Safeguard Defensibility Read, run on the standards themselves rather than on a document that answers to them.

The two reads

One document, two readings

Read for intent

A duty of care, generously drawn

Avoid harm, consult communities, compensate fairly, restore livelihoods. Written in the future indicative: the client will.

Read for enforcement

A duty that returns itself to the client

Where feasible. Commensurate with. Should. To the extent permitted by the agency. Each phrase hands the judgement back to the party being judged.

Method

Six hostile readers at one table

The standards were put to the six seats a safeguards document actually faces. The council supplies breadth; it does not supply verified quotes, so every quotation here was checked back against the sourced 2012 text by hand. The garbles the room produced, including one clause that does not exist, were struck.

The Lender

project-finance due diligence

Reads the E&S covenant for what it can actually be enforced to deliver, and what it cannot.

The CAO / Inspection Panel

the complaint it invites

Reads for the floor an affected community was promised and then quietly denied.

The Affected Person

the household it is about

Reads one question: when it matters, does “consent” mean they can say no?

The Regulator

the standard it implies

Reads for the binding requirement sitting behind the word, if there is one.

The Auditor

is it verifiable

Reads for the traceable evidence a claim of compliance is supposed to rest on.

Counsel

the legal exposure

Reads for the softener that turns a duty into a discretion nobody can be held to.

Audit summary

The grade grid

Four dimensions, because the audit keeps surfacing the same four questions and they do not collapse into one. Transparency and enforceability are kept apart on purpose: a document can disclose everything and still leave no one outside the institution able to act on it.

Dimension	PS1Assessment & Management	PS5Land Acquisition & Resettlement	PS7Indigenous Peoples
Binding force of the core duty	partial Core duties are “will,” but scope and effort ride on “commensurate” and “should” (¶22, ¶25, ¶30).	partial “Full replacement cost” is firm; land-for-land is only “where feasible” (¶8, ¶9).	partial “Will obtain the FPIC,” but only “in the circumstances described in paragraphs 13–17” (¶11, ¶12).
Hard floora line the project cannot cross	weak No “will not proceed” anywhere; residual harm is offset “wherever technically and financially feasible” (¶14).	weak “To avoid forced eviction” is an Objective; the requirement permits it “except in accordance with law” (¶24).	partial “Will not proceed … unless FPIC has been obtained,” once the client judges relocation “unavoidable” (¶15).
Evidence and traceability	partial Documented monitoring; external verifiers “for projects with significant impacts,” a threshold the client sets (¶22).	partial Completion audits and records exist; “adequate” and “where feasible” stay self-declared (¶9, ¶22).	weak FPIC needs “evidence of agreement,” but agreement “does not necessarily require unanimity” (¶12).
External enforceability	weak Every duty runs to IFC by contract; the grievance mechanism “should not impede” courts, which is not the same as opening them (¶35).	weak Grievance “consistent with” PS1; in state-run resettlement the client acts only “to the extent permitted by the agency.”	weak “To the extent feasible and permitted by the agency” (¶21); GN32 lets the client proceed where government runs land acquisition.

Read the bottom row. No document earns a strong grade anywhere, and all three bottom out on the same dimension: the floor that would let an outsider enforce any of it does not exist.

strong absolute floor, checkable from outside IFCpartial real duty, gated or internally verifiedweak discretionary, self-certified, or absent

The teardowns

Three documents, read to the seam

PS1 · Assessment and Management of E&S Risks and Impacts

The management system that manages itself

Binding duties, discretion hidden in the sizing

PS1 is the spine: an ESMS, monitoring, stakeholder engagement, and a grievance mechanism, all in binding will language. The discretion lives in how much of any of it is required, and that dial is held by the client. Independent eyes are promised, then rationed to whichever projects the client itself classes as significant.

“The extent of monitoring should be commensurate with the project's environmental and social risks and impacts”
PS1 ¶22 · verified

“The mechanism should not impede access to judicial or administrative remedies”
PS1 ¶35 · verified. Not impeding the courthouse is a long way from opening it.

PS5 · Land Acquisition and Involuntary Resettlement

The eviction it tells you it will avoid

An Objective the operative clause takes back

PS5 states the cleanest prohibition in the set as an Objective, “To avoid forced eviction,” and then the requirement returns most of it, relocating the whole question into national law. That is precisely the terrain a lender's standard exists to backstop when national law is thin. The livelihood protection that matters most, land for lost land, arrives already conditional.

“Forced evictions will not be carried out except in accordance with law and the requirements of this Performance Standard”
PS5 ¶24 · verified

“the client will, where feasible, offer the displaced land-based compensation”
PS5 ¶9 · verified. Cash is the fallback, and cash “is frequently insufficient to restore livelihoods” (¶28).

PS7 · Indigenous Peoples

Consent, redefined until it cannot refuse

The set's one real floor, and the word it rests on

PS7 contains the strongest floor anywhere in the three, the only will not proceed in the set, and then its Guidance Note quietly hollows the word that floor stands on. The floor triggers only once the client judges relocation “unavoidable,” a judgement it makes about its own project. And “Consent” has been defined so that it cannot be withheld.

“If such relocation is unavoidable the client will not proceed with the project unless FPIC has been obtained”
PS7 ¶15 · verified

“FPIC does not necessarily require unanimity and may be achieved even when individuals or groups within the community explicitly disagree”
PS7 ¶12 · verified

“focusing on achieving agreement while not conferring veto rights to individuals or sub-groups”
Guidance Note 7, GN22 · verified. Consent that cannot be withheld is consultation wearing a stronger word.

How the grades are reached

Each cell, traced to source

Hard floor

Is there an absolute line the project cannot cross, stated in binding language?

PS1

weak

The mitigation hierarchy … will favor the avoidance of impacts over minimization, and, where residual impacts remain, compensation/offset, wherever technically and financially feasible (¶14). Feasibility is assessed by the party paying for it.

PS5

weak

Forced evictions will not be carried out except in accordance with law (¶24). The “never” is only an Objective; the requirement carries the carve-out.

PS7

partial

the client will not proceed with the project unless FPIC has been obtained (¶15), gated by the client's own reading of “unavoidable.”

External enforceability

Can anyone outside IFC, an affected community, a court, a panel, compel compliance?

PS1

weak

Every duty runs to IFC by private contract. The grievance mechanism is client-run and should not impede access to judicial or administrative remedies (¶35).

PS5

weak

Grievance “consistent with” PS1; under state-run resettlement the client acts to the extent permitted by the agency.

PS7

weak

to the extent feasible and permitted by the agency (¶21); GN32: it may not be possible for the client to achieve all elements of this Performance Standard, including the requirement of FPIC.

The shared absence

The one hard floor none of the three contains

All three standards are built from a single template: state the duty in binding language, then attach a discretionary trigger that returns the judgement to the client. Each softener was written for a human reviewer weighing a real project against a real community in good faith. The standard is only ever as strong as that assumption.

Proceeding is never made conditional on verification by anyone outside IFC. The closest approach, PS7’s “will not proceed … unless FPIC has been obtained,” is gated by the client’s own “unavoidable” and enforced, if at all, through a contract the protected community will never see. Disclosure is abundant. An external veto does not exist.

Fullness on transparency tells you nothing about accountability. These documents are the proof.

The next reader is not human

What happens when AI moves into the workflow

Every softener is a delegation of judgement to a human who could be argued with, appealed to, or held to account. Move that judgement into a system that drafts, screens, monitors, or synthesises, and the discretion does not disappear. It hardens into a parameter, applied at scale and dressed as documentation, and it runs its verdict before anyone affected is in the room.

“commensurate with the project's risks”PS1 ¶22, ¶25

Whatever scaling the model has internalised becomes the de facto standard. A word chosen to invite proportionality freezes into a threshold no reviewer sees and no community can contest.

“where feasible”PS5 ¶9 · PS7 ¶14

Feasibility becomes a cost-and-logistics computation, and land-for-land, the thing that actually restores a livelihood, becomes the option the optimiser declines. “Feasible” resolves to “cheapest defensible.”

“if such relocation is unavoidable”PS7 ¶15

The hinge the whole FPIC floor swings on is exactly the determination a screening model makes early, quietly, from design constraints, and in the project's favour. The one stop-condition can be switched off upstream.

“evidence of agreement” without unanimityPS7 ¶12

FPIC becomes a document-classification task. Feed in the transcripts, ask whether agreement was reached, and dissent is compressed into a minority footnote while the file records consent.

grievance “should not impede … remedies”PS1 ¶35

The mechanism becomes an intake queue optimised for closure rate, where “resolved promptly” is the metric and a remedy is not. Excellent numbers, and the courthouse stays exactly as far away.

These standards were drafted for human reviewers, and their softeners are the seams where human judgement was meant to enter. Automate the seams and the discretion the standard was always carrying becomes invisible, instant, and impossible to appeal, and it produces its own paper trail. The document will still say a person considered it. Somewhere in the workflow, that will stop being true.

Try it live

Convene the council on one claim

The grid above is the method run on the standards. Point it at your own document by starting with a single line. Type one always / never claim a safeguards document might make, and a six-seat council of its hardest readers will try to break it in real time.

Type an always / never safeguards claim

Six hostile readers. One claim. About fifteen seconds.

Read your own document

This is what the Safeguard Defensibility Read does to your document.

The grid above took the gold-standard documents and found where each one hands its hardest promise back to the party being judged. Your resettlement plan, ESIA chapter, grievance procedure, or conformance mapping carries the same seams, and a lender’s desk or an inspection panel will read for them whether or not you have. Better that the first hostile read is one you commissioned.

The Safeguard Defensibility Read →The Always/Never Audit method →

Provenance

Performance Standards 1, 5, 7: 2012 edition, each dated January 1, 2012. Current; supersedes the 2006 edition. Sourced from ifc.org.
Guidance Notes: January 1, 2012, updated June 14, 2021. Non-binding by their own terms. Sourced from ifc.org.
Method: a six-role adversarial council on the operative text, then every carried quote verified against the source PDFs, character for character.

Documents read as published, retrieved from ifc.org on 4 July 2026. The Performance Standards are read as written; this is an audit of the text, not a claim about any institution’s or client’s conduct, and it is not legal advice.

Back to the Always/Never Audit or all advisory offerings.