The stakeholder engagement plan behind a resettlement

Consultation is the requirement projects are most confident they satisfied and least able to evidence. Meetings were held; people attended; the team recalls them clearly. Three years later a reviewer asks which households were present at the meeting where the cut-off date was announced, and the answer is a photograph and an attendance sheet with forty illegible signatures.

The stakeholder engagement plan exists to convert good intentions into a record that can be tested. It is worth writing on that basis rather than as a narrative of goodwill.

Engagement in resettlement is not general consultation

A project-wide SEP addresses many audiences: authorities, civil society, workers, neighbouring communities. Resettlement engagement is narrower and harder, because it concerns individually identifiable people who are losing specific assets and who need particular information at particular moments.[1]

That distinction has a practical consequence. General consultation can be evidenced at the level of the meeting. Resettlement engagement has to be evidenced at the level of the household, because entitlement decisions attach to households and each of them is entitled to have understood what was decided about them.

The moments that have to be covered

1. Before enumeration. What the survey is for, that it is not itself a promise of compensation, and what the cut-off date will mean.
2. At the cut-off. Declared, dated, disclosed in the settlements affected and in the local language, with the record of that disclosure retained.[2]
3. On the entitlement framework. What each category of loss attracts and on what basis — before individual offers, not with them.
4. At individual disclosure. Each household shown its own recorded assets and its own calculated entitlement, with time to dispute before signature.
5. Before possession. Dates, logistics, what happens to standing crops, where to go with a problem.
6. Through implementation. Progress, delays, and what remains outstanding — the phase where engagement usually stops and grievances start.

The individual disclosure step is the one most often compressed into the payment event. A household seeing its valuation for the first time on the day it is asked to sign has not been consulted; it has been informed.

Who is in the room, and who is not

Attendance at open meetings skews predictably: toward men, toward those with standing in the community, toward the physically mobile, and away from tenants who do not consider themselves entitled to attend. If the engagement record is built solely from open meetings, the plan will reflect the views of the people most able to attend them.[3]

The correctives are known and cost little: separate sessions for women held at a time and place they can reach; direct approaches to tenants and employees rather than reliance on landlords to pass on information; scheduling around the agricultural calendar rather than around the mission calendar; and recording attendance in a way that can be disaggregated afterwards, which means capturing identity and category, not just a signature.

What the file has to show

An engagement record that satisfies a reviewer answers four questions for each event: what was communicated, to whom, in what language and by what means, and what was said in response. The fourth is the one that separates a genuine record from an attendance archive.

Issues raised should be logged with an identifier, routed, answered, and the answer traceable back to the person who raised it. Where an issue changed the plan — a rate revised, a site rejected, an access track added — the record should say so, because demonstrable influence on the outcome is the strongest available evidence that consultation was meaningful rather than ceremonial.[4]

The relationship to the grievance mechanism

Engagement and grievance are usually run as separate systems and should share one record. A question asked at a meeting and not answered becomes a grievance; a grievance answered well becomes engagement. Keeping two logs guarantees that issues raised in meetings vanish, since nobody owns them.

A single register with a source field — meeting, field visit, grievance desk, phone line — costs nothing to implement and closes the most common gap between what a community raised and what the project can show it addressed.

Budget it as an operating cost

Engagement is usually costed as a preparation activity and consumed during preparation, leaving implementation — the longer and more contentious period — with a community liaison team of two and no transport budget. Since the majority of engagement events fall after the plan is approved, the majority of the engagement budget should too.