Engagement as an evidentiary record: what ESS10 requires a project to be able to show

1. The gap between holding a meeting and having consulted

Every large project consults. Teams travel to villages, sit with local leaders, hold public meetings, explain the project and answer questions. The activity is real and often extensive. Yet consultation is among the most frequent subjects of adverse findings, and the finding is rarely that consultation did not occur. [10] It is that the project cannot demonstrate what was communicated, to whom, when, in what language, or what was done with what people said.

The distinction is easy to dismiss as bureaucratic and is not. A standard that required only that meetings happen would be unenforceable, because every project would assert compliance and no external party could test the assertion. What makes the requirement operative is the record, and the record is therefore the requirement in practice, whatever the text says about process. [1][9]

This has an uncomfortable implication that project teams resist: engagement that genuinely occurred but was not documented is, for compliance purposes, engagement that did not occur. The team knows it happened and experiences the finding as unjust. The auditor cannot distinguish an undocumented meeting from an imagined one, and is not entitled to take the project's word for it — which is the whole point of external review.

2. What a meeting record must contain

A record adequate to support a compliance position captures more than attendance. It establishes what information was presented, in what form and language; who was present, with enough identification to link attendance to affected-person records; what was asked and asserted by participants, in their terms rather than summarised into agreement; what the project undertook in response; and what subsequently happened to those undertakings.

The last two elements are the ones most often missing and the ones that carry the most weight. A record showing that a project presented information and that attendees listened evidences disclosure. A record showing that participants raised a concern, that the project responded specifically, and that the response changed something evidences consultation. The standards' language about meaningful consultation and about engagement informing decisions is, in evidentiary terms, a requirement to show that second pattern. [1][5][6]

Attendance lists deserve particular attention because they are the field's most common failure. A list of signatures and thumbprints without printed names, without a link to household identifiers, and without a stated purpose demonstrates that people attended something. It does not demonstrate which households were reached, which is the question that matters when a project must show that a specific affected person was informed before a cut-off date.

3. Language, literacy and the limits of the written record

Engagement obligations are expressed in terms of accessibility: information in a form, manner and language that is understandable to affected people. [8] On most resettlement projects this means oral communication in a local language to participants with varying literacy, which sits awkwardly with a documentation regime built around written artefacts.

The awkwardness produces a specific failure mode. A project meets its accessibility obligation by explaining a resettlement entitlement orally and in the local language, and meets its documentation obligation by filing an English-language written summary prepared afterwards by a consultant. Both obligations are addressed and the record does not evidence the thing that actually happened, because it is not a record of the oral explanation but a parallel construction.

Practices that close this gap are known and unevenly applied: recording the language of delivery explicitly; retaining the visual or simplified materials actually used rather than only the technical document they were derived from; capturing audio or photographic evidence of the session; and having the record attested by a participant or independent observer rather than only by project staff. None is onerous. Their absence is usually a matter of nobody having specified them, rather than of cost.

It is worth noting that this ground was covered in detail well before the current standards were written. IFC's stakeholder engagement handbook, published in 2007, sets out documentation practice, differentiated engagement and grievance handling at a level of operational specificity the standards themselves do not attempt. [2] Much of what projects discover painfully through an adverse finding is described there, which suggests the field's difficulty is not an absence of guidance.

4. Engagement with people who are hard to reach

Aggregate engagement statistics conceal distributional failure. A project can hold many meetings with high attendance and systematically miss the categories of people whose interests most need protecting: women in contexts where public meetings are attended by male household heads; tenants and labourers who have no recognised standing in a land discussion; pastoralists absent during a seasonal movement; people with disabilities for whom the venue is inaccessible; and absentee owners working elsewhere.

The standards address this through requirements for differentiated engagement and attention to disadvantaged groups. [3][4] Operationally the requirement is that a project know who it has not reached, which requires a denominator — a census against which attendance can be compared — rather than a count of meetings held.

Projects that examine attendance against their own census records frequently discover that a substantial minority of affected households have never attended anything, and that the non-attenders are not randomly distributed. That finding is uncomfortable and is precisely the finding the requirement exists to generate. A project unable to produce it is not demonstrating good engagement; it is demonstrating that it has not looked.

5. Conclusion

Engagement is the safeguard obligation with the widest gap between effort expended and compliance demonstrated. Projects invest heavily in consultation and capture it in a form that cannot support the claims they will later need to make, then experience the resulting findings as a failure of understanding by reviewers rather than as a failure of record.

IFC's handbook treats a documented, denominator-based engagement record as a routine element of programme management, not a special measure. [7] The corrective is not more consultation. It is capturing what already happens in a form that links a person, a date, a communication and a response — which is a design decision about instruments and information systems, taken before the meetings begin, and almost impossible to retrofit once they are over.