Every infrastructure project financed by a DFI must establish a mechanism enabling affected communities to submit concerns and grievances, have them registered and addressed, and receive a response within a reasonable timeframe. The requirement is set out in IFC Performance Standard 1 (paragraph 35) for grievances external to workers, and in Performance Standard 2 for the worker component. AfDB Operational Safeguard 1 and World Bank Environmental and Social Standard 10 reproduce this requirement, the latter elevating it to a stand-alone standard.
On paper, the requirement is simple. In practice, few systems actually function after six months. The most frequent gaps do not stem from lack of good faith, but from design errors made at the outset, which compromise trust before the mechanism has even had time to prove itself.
This article presents the eight design principles which, taken together, produce an accessible and credible system. None is revolutionary, but their simultaneous application separates mechanisms that live from mechanisms that remain lines in the ESMP.
Principle 1: Accessibility Requires a Plurality of Channels
A mechanism that offers only a single submission channel structurally excludes some of the people concerned. A telephone number is useless to communities without reliable network coverage. A physical box installed only at project headquarters is not accessible to remote hamlets. An online form presupposes unequal digital literacy.
Robust practice consists of offering at least three complementary channels: a physical box in a neutral community location (community house, village chief, school), an identified human contact (project community liaison officer, regular visits), and a formal written channel (post, email, form) for grievances requiring a trail. Each channel must be the subject of regular communication on its operation and on the existence of the other channels.
Principle 2: Confidentiality is Guaranteed by Organisational Separation
A grievance filed by a worker against their team leader loses all value if it is handled by that team leader or by their direct superior. A community grievance about the negotiation conditions of a RAP cannot be handled by the RAP manager.
Confidentiality is not a slogan; it is built through separation of functions. Grievance handling must be entrusted to a team distinct from the operational management line, with reporting to E&S management or to a joint committee that includes independent representatives. For high-risk projects, the involvement of an external mediator for certain types of grievances (GBV, discrimination, harassment) strengthens the credibility of the system.
Principle 3: Community Anchoring Prefigures Legitimacy
A mechanism imported from outside, designed in an office and deployed as is, struggles to take root. Communities do not take ownership of a system they have not helped to shape.
Good practice consists of opening the design of the mechanism to prior consultation with community representatives: what type of channels? Where to place the boxes? Who would be a trusted interlocutor to serve as liaison officer? Which languages to use? These choices, made through consultation, weigh heavily on the subsequent uptake of the system.
Principle 4: The Register is the Keystone of Traceability
A mechanism without a centralised register, even if it receives grievances, does not produce the traceability required by lenders. The register is not a simple notebook; it is the tool that enables one to demonstrate, six months later, how many grievances were received, by which channel, on what subject, within what timeframe they were addressed, and with what satisfaction rate.
The register must contain, for each grievance, a unique identifier, the date and channel of submission, a summary description, the category (environment, social, labour, GBV, other), the name of the complainant if they agree or an anonymised code otherwise, the person responsible for handling, the actions taken, the closure date and the complainant's final assessment.
This information must be entered within 24 to 48 hours following submission, on a secure digital medium, with regular backup. Simply maintaining a paper notebook in the project office no longer meets current lender expectations.
Principle 5: Response Timeframes are Committed and Honoured
A mechanism must commit to public response timeframes adapted to the severity level of the grievance. Current practice distinguishes three levels.
Simple grievances or requests for information, which call for a response within a few days. An objective of ten to fifteen working days is reasonable.
Grievances that require investigation, between two weeks and one month. They presuppose a documented inquiry, sometimes a site visit, cross-consultation.
Complex, sensitive or high-stakes grievances (GBV, serious accidents, unresolved land disputes), which may take several months. They call for separate handling with a dedicated team and close monitoring.
In all cases, an acknowledgement of receipt must be provided within 48 to 72 hours and a progress update at regular intervals. Prolonged silence is the primary cause of discrediting a mechanism.
Principle 6: External Escalation is an Essential Safety Valve
A complainant who is not satisfied with the handling received by the project mechanism must have an external recourse channel. This channel can take several forms: an independent national ombudsman when one exists, lenders' own procedures (IFC Compliance Advisor Ombudsman, World Bank Inspection Panel, AfDB Independent Review Mechanism), conventional judicial recourse.
The project mechanism cannot substitute for these channels, nor discourage them. Its role is on the contrary to explain them, to make them visible and accessible, so that confidence in the internal system is built on knowledge of the alternatives.
Principle 7: Specific Systems for Sensitive Issues
Not all grievances can be handled by the same procedure. Three categories call for separate systems.
Grievances related to gender-based violence (GBV) require a confidential channel, a trained team, referral to specialised support services (medical, psychological, legal), and an investigation procedure that protects the complainant. These systems are now standardised in DFI projects following international recommendations adopted since 2018.
Grievances related to workers' working conditions fall under the PS2 or OS5 mechanism, which is separate from the community mechanism. The two systems may share common infrastructure but their procedures, handling teams and timeframes are adapted to the specificities of each public.
Sensitive land grievances, particularly those challenging a perceived compensation or the complainant's categorisation in the RAP, require a dedicated legal and social team, with an extended response timeframe and an internal appeal procedure before external recourse.
Principle 8: Public Reporting Nurtures Trust
A mechanism that functions in isolation ends up being perceived as opaque. The periodic publication, quarterly or half-yearly, of an aggregated report on the system (number of grievances received, distribution by category, average response timeframes, amicable resolution rate) nurtures trust and strengthens legitimacy.
This reporting must respect complainants' confidentiality (no names, no details enabling identification), but it must be sufficiently substantive for the community to understand that the mechanism is being used and that it produces results. Publication in the form of posters in community locations, oral presentation in assembly, or as an appendix to monitoring reports to the lender, are three complementary media.
The quality of a grievance mechanism is not measured by the sophistication of its architecture, but by the trust it manages to build over time. This trust is built through simple repeated actions: a prompt acknowledgement of receipt, a honoured timeframe, a reasoned response, a published report, a visible external recourse.
For a project owner, the operational challenge is to establish these actions as a project discipline, not as a regulatory obligation to be formally fulfilled. The difference can be read in the figures six months after commissioning: a mechanism that receives, handles and reports absorbs the majority of tensions before they degenerate. A façade mechanism produces exactly the opposite.
Comments
Be the first to react to this article.