Choosing your level of engagement — and honouring it
Choosing a level of engagement before you’re clear on your objectives, constraints, and decision-making authority isn’t aspirational. It’s a commitment you’re making to your community before you know whether you can keep it.
The level of engagement is not a preference. It is a promise — a commitment about the degree of influence communities will have over the decision.
A familiar conversation.
A project team is briefed on a new neighbourhood plan. The engagement manager asks what level of engagement they’re running. Someone suggests Collaborate — it’s a major project and it feels like the right signal to send.
Nobody asks whether the organisation has the mandate to co-design outcomes. Nobody asks which decisions are actually open to community influence. The level is chosen because it feels respectful, not because it reflects what the organisation can deliver.
Six months later, community members who participated in co-design workshops are frustrated that their preferred options weren’t on the shortlist. They weren’t told the shortlist had already been set. Nobody intended to mislead them. The level was chosen before anyone checked what the process could actually honour.
The IAP2 spectrum — Consult, Involve, Collaborate — is one of the most widely referenced frameworks in community engagement practice. It is also one of the most frequently misapplied. Not because practitioners don’t understand what each level means, but because the level is often chosen before the conditions that should determine it have been established.
The right level of engagement is the one you can honestly honour — not the one that signals the most respect.
What each level actually means
The IAP2 Spectrum of Public Participation provides the clearest shared language here, distinguishing different promises of influence from informing through to empowering.
Consult
Seek community feedback on analyses, options, or decisions.
Promise: We will listen, acknowledge what we heard, and explain how it influenced the decision.
Involve
Work directly with stakeholders throughout the process.
Promise: Your perspectives will shape the development of options and alternatives.
Collaborate
Partner with stakeholders to develop alternatives and identify preferred solutions.
Promise: Community input will significantly influence the preferred option.
The practical difference between levels is the degree of influence the process can honestly deliver.
Sequence dependency
As discussed in the previous step on defining engagement objectives, the engagement level should match the type of input the project actually requires.
The engagement level cannot be chosen responsibly until earlier steps are complete.
mapped the decision space (Step 1)
established scope and constraints (Step 2)
defined engagement objectives (Step 3)
Until these are clear, you do not yet know what influence the community can realistically have. Choosing the level earlier is choosing a promise before you know whether it can be kept.
The overclaiming problem
Overclaiming happens when the engagement level promises more influence than the process can realistically deliver. It is the most common and most damaging sequencing error in community engagement practice.
Overclaiming — choosing Involve or Collaborate when the process can only honestly deliver Consult — is the more common and more damaging of the two failure modes. It happens for understandable reasons: it signals respect, it feels more inclusive, and it is rarely challenged at the outset.
The damage surfaces later. When community members who participated in co-design processes find their recommendations not reflected in outcomes, they feel misled — not because the organisation acted in bad faith, but because the implicit promise of the engagement level was not kept. The gap between what the level implied and what the process delivered is experienced as a breach of trust, regardless of intent.
Overclaiming is also self-defeating from an organisational standpoint. It creates expectations that require more resource to manage than honest Consult would have required, while producing the same decision-making outcome.
Overclaiming pattern: The team selects Collaborate because the project is significant and the community has strong views. Co-design workshops are run. The community develops preferred options. The final decision reflects the organisation’s original preferred option, constrained by budget and prior commitments that were never disclosed. Community members feel the co-design process was theatre. They are right.
Many engagement teams now use structured planning templates to align engagement level with objectives and constraints before engagement begins.
Download the Choosing Your Engagement Level
Get the one-page field reference and use it in your next engagement project.
The underclaiming problem
Underclaiming — defaulting to Consult when Involve or Collaborate would be more honest — is less discussed but equally problematic. It often happens when organisations have had difficult experiences with community engagement and have retreated to the minimum commitment to manage expectations and reduce risk.
The cost is different from overclaiming but significant. Underclaiming signals to communities that their input will have limited influence before the process has tested what meaningful involvement is possible.
Professional practice principle
Honest Consult is more valuable than dishonest Collaborate. Communities respond better to clear expectations than to promises that cannot be kept.
How to choose the level honestly
Choosing the level honestly
Ask three questions in order:
First: What decisions are genuinely open to community influence? If the decision space is narrow — constrained by legislation, budget, or prior commitment — be honest about that before choosing a level that implies otherwise.
Second: What do we actually need from the community? Clarifying your engagement objectives (Step 3 in the sequence) will tell you whether you need feedback, collaborative input, or partnership in solution design. The level should match what you genuinely need, not what sounds most progressive.
Third: What can we organisationally deliver? The right level requires the right infrastructure — decision-making flexibility, time, skilled facilitation, and a genuine willingness to act on input. If those conditions are not in place, choose the level you can actually honour, and make a plan to build toward higher levels on future projects.
Once the level is chosen, communicate it explicitly
Tell communities at the outset: here is the level of engagement we are running, here is what that means for the influence your input will have, and here is how we will tell you what happened with your contribution. Stating this clearly at the beginning is the single most effective way to prevent trust damage later.
Can AI help with this process and how?
Where AI helps: Generate level options from known constraints and decision openness, then test where promise-risk is highest.
What stays human: Set the final engagement level and own the promise to communities about real influence.
Governance check: Document why the level was chosen, what changed, and who approved any shift during delivery.
Bottom line: AI can support level selection, but trust depends on people honouring the promise.
This post is part of a series on the sequence that drives effective community engagement. Read the full framework in our pillar post: Order of Operations — Why community engagement fails before the first session runs.