The organisation that thinks it consults communities but actually just informs them

There is a phrase that appears in almost every NGO project plan: "community consultation." It appears in programme budgets, in donor reports, in implementation timelines. It is cited as evidence of community ownership, of participatory design, of ethical practice. It almost never means what it says.

What it usually means is this: the project plan is already written. The budget has been submitted. The donor has approved. The implementation timeline has been fixed. And then — at some point before the project actually begins — a meeting is held in the community. People attend. Questions are asked. Notes are taken. Sometimes a "community consultation report" is filed. The project then proceeds exactly as designed.

That is not consultation. That is notification with extra steps.

The test for real consultation

The simplest test of whether a consultation process is genuine is this: did it change anything? Not the framing. Not the language used to describe the project to the community. The design itself — the timeline, the priorities, the approach, or in the most significant cases, the decision to proceed at all.

If your consultation process has never resulted in a fundamental change to the project design — you are not consulting. You are informing. These are different activities. They carry different names for a reason.

I have sat in those rooms. The ones where the flipchart is already filled in when participants arrive. Where the questions are a formality and the answers are a courtesy. Where the real meeting — the one where priorities were set and decisions were made — happened months earlier in an office in Nairobi or London or Geneva. The community did not attend that meeting. But the outcomes of that meeting were brought to them as though they were the beginning of a conversation, rather than the end of one.

What the room tells you

The room often tells you before anyone speaks. The schedule has no white space — no time allowed for the conversation going somewhere unexpected. When questions are asked, they are noted down. But there is a quality to the note-taking. In a genuine consultation, the person writing occasionally pauses, because what was just said is worth considering. In a performed one, the pen keeps moving at the same pace throughout. Everything is received equally. Because nothing is changing anything.

Why communities always know

Communities are not naive about this. They have often been through this process before — with the previous project, with the previous organisation, with the previous funding cycle. They know the difference between a meeting where their input is genuinely sought and a meeting where their presence is required to complete a document. They know which questions have real answers attached and which are being asked because the form needs to be filled in.

The result of repeated performed consultation is not simply a missed opportunity for better project design. It is accumulated distrust. Every project that runs a consultation process without genuinely allowing community input to change it makes the next organisation's genuine consultation harder. Communities learn, rationally, that participation is symbolic — and they engage with it symbolically. The trust that genuine participation requires has to be rebuilt from scratch each time.

The honest language

I am not arguing for perfect consultation. Genuine community participation in project design is difficult, slow, and sometimes produces outcomes that are harder to fund and harder to implement. I understand the pressures. I am arguing for honest language about what actually happened.

If you informed the community about a decision that had already been made — say so. That is a legitimate thing to do, and naming it accurately does not require pretending it is something else. If you consulted and the community's input shaped the design — say so, and show how. If you consulted and nothing changed — that is the most important thing to name, because it is the conversation that can produce genuine change in practice.

The gap between the language and the practice is not primarily a communication problem. It is a trust problem. And trust, unlike a project plan, cannot be revised in the next funding cycle. It compounds — in both directions — with every project.

What the other direction looks like is quieter than people expect. It is a community that asks harder questions the next time — because last time, the questions changed something. It is a project that works better than anyone planned — because the people who would live inside it helped build it.

That is what honest language makes possible. Not perfect practice. Just the conditions under which practice can actually get better.