Designing a grievance redress mechanism that a lender will accept

Resettlement generates more complaints than any other safeguard issue. The Compliance Advisor/Ombudsman, which handles complaints about IFC and MIGA projects, reports that social impacts relating to resettlement or cultural disruption feature in around 52 percent of the complaints it receives, and that land acquisition and involuntary resettlement specifically has been raised in roughly 22 percent over two decades.[2][3]

That is the context for a project-level grievance redress mechanism. A complaint reaching an international accountability body is, almost always, a complaint the project-level mechanism failed to resolve — or failed to receive.

What a GRM is required to be

Both PS-5 and ESS-5 require a grievance mechanism, and the requirements are consistent: accessible to affected people, at no cost to them, without retribution, and without prejudicing access to judicial or administrative remedy.[1][4]

That last clause is frequently misread. A GRM is not an alternative to courts and it cannot require people to waive legal rights as a condition of using it. A mechanism whose intake form includes a settlement waiver is non-compliant on its face.

The difference between a mechanism and a logbook

Most projects have something they call a GRM. Far fewer have one that works. The distinguishing features are unglamorous:

Multiple intake channels, at least one of which is not the project

If the only route is a desk at the project office, the mechanism will not hear from the people most likely to be harmed. Complaints about a resettlement officer are not brought to that officer. Working mechanisms offer several entry points — community-level committees, local leadership, a phone line, and field staff who can log a grievance on the spot — with at least one route that does not pass through the person being complained about.

Acknowledgement, not just receipt

A complainant who hears nothing assumes nothing happened. Acknowledgement within a defined period, with a reference the person can quote back, is what distinguishes a process from a void. It also produces the first timestamp in the record.

Defined timeframes, and a record of whether they were met

A GRM without service standards has no failure condition. A GRM with standards but no measurement of them has a failure condition nobody checks. The useful metric is not how many grievances were received — it is the distribution of time-to-resolution, and the count of cases that breached the standard.

Escalation that goes somewhere

Every mechanism needs a route for cases the first tier cannot resolve, and the escalation tier must have authority the first tier lacks. Escalating a valuation dispute to a committee with no power to revise a valuation converts a grievance into a delay.

What the data should tell you

A grievance log is a monitoring instrument, not a filing cabinet. Read properly it is the earliest available signal that something upstream is wrong. Some patterns worth watching:

• Clustering by location — a spike from one section usually means an enumeration or disclosure problem there, not fifteen unrelated disputes.
• Clustering by category — a run of tree valuation complaints is a rate problem, and re-litigating each case individually treats the symptom.
• Clustering by enumerator or valuer — uncomfortable, and the reason attribution needs to be in the record.
• Silence — an affected area generating no grievances is far more likely to indicate an unreachable mechanism than universal satisfaction.

A GRM that receives no complaints is not evidence of a project without problems. It is evidence of a mechanism nobody can reach.

What the record must show

For each grievance, a reviewer will expect to trace: who raised it and when; what it concerned; who handled it; what was decided and on what basis; when the complainant was informed; whether they accepted the outcome; and if escalated, where it went and what happened.[5]

Each of those is a timestamped, attributed event. Which is why grievance handling maintained in a shared spreadsheet fails at audit even when the underlying handling was diligent — the spreadsheet holds the current state, not the history, and the history is the thing being examined.

Anonymous complaints

A mechanism that cannot receive an anonymous complaint will not receive certain categories of complaint at all — allegations against project staff, and anything touching gender-based harm most of all. These are precisely the cases whose escalation is most damaging to a project and most harmful to the person involved.

Anonymous intake creates a genuine tension with verification, and the resolution is not to refuse it but to handle it differently: log it, investigate what can be investigated, and record the constraint. A mechanism that only accepts complaints it can conveniently verify is selecting for the complaints that were least urgent.

Why this is a system problem

A grievance about a compensation amount is only answerable if the compensation record it disputes can be retrieved: what was measured, by whom, valued on what basis, revised when and why. A GRM disconnected from the entitlement and payment records cannot resolve the majority of grievances it receives — it can only forward them.

Which is the practical case for holding the census, the entitlement matrix, the payment record and the grievance log in one system rather than four. Not for elegance. Because the answer to most grievances lives in a different file from the grievance.