Framework Overview
Use this as a quick map: each step creates prerequisites for the next.
Why community engagement fails before the first session runs
How to use this guide: Start with this pillar, then move step-by-step through each linked article. Each step depends on the one before it, and the companion reference card gives you a field-ready summary.
Before Step 1, confirm that the work is genuinely an engagement project at all. If the decision space is already closed, the right process may be statutory consultation, exhibition, communication, or notification rather than open-ended engagement. See Not Every Project Is an Engagement Project for the distinction.
This sequencing discipline aligns with principles embedded in the IAP2 Core Values of Public Participation, including clarity of influence, transparency about decision boundaries, and closing the feedback loop with participants.
Most community engagement failures don't happen in the sessions. They happen months earlier — in the sequence of decisions made while designing the engagement.
The 10-Step Community Engagement Sequence
Build your evaluation framework before implementation begins
Track the connection between input and decisions in real time
Sequence by phase
Decision foundations: Decision space, scope and constraints, engagement objectives, and engagement level.
Engagement design: Stakeholders, questions and content, methods.
Accountability: Evaluation, input-to-decision tracking, feedback loop.
Each step in the sequence depends on the one before it. Skipping or reordering steps doesn't save time — it introduces failure modes that are far more expensive to address once engagement is underway.
Sequence in community engagement is not just logistics. It is logic. Each step creates the conditions the next step requires. Most of the failures described in this guide are not failures of skill or effort — they are failures of sequence. They happen when capable, well-intentioned teams skip or reorder steps without understanding what depends on what.
Core Values and Ethics in Practice
This sequence is grounded in professional participation ethics: clarity of purpose, honesty about influence, inclusive access, and accountability for decisions. These principles align with the IAP2 Core Values of Public Participation.
In practice, values are only credible when they are operational: declared early, visible in design choices, and upheld when trade-offs emerge under delivery pressure.
Who this guide is for
Engagement practitioners in local government, state agencies, and the private sector
Project managers who lead engagement teams or commission engagement work
Community development professionals who sit at the interface between organisations and communities
What follows is the sequence that works — and an honest account of what goes wrong when it is skipped.
The ten-step sequence
International guidance such as the OECD Guidelines for Citizen Participation Processes reinforces this point: the quality of public participation depends not just on methods but on the clarity of decision context, stakeholder identification, and follow-through accountability.
STEP 1Map the decision space — before anything else
Project context baseline: In Step 1, establish project history, project objectives, project budget/funding constraints, and prior commitments before framing what is genuinely open to influence. See Before You Design Anything: What Is Actually on the Table?.
Why it matters
Before designing your engagement, understand what decisions are actually being made, who holds authority over them, and when the window for community influence opens and closes. Without this anchor, engagement design defaults to process for its own sake.
When skipped
Engagement is designed around internal project schedules rather than decision milestones. Communities participate after key decisions have already been made. Input cannot influence outcomes because the window has already closed.
STEP 2Establish scope and constraints honestly
Why it matters
What is genuinely open for community influence? What is fixed by legislation, prior commitment, or technical constraints? Documenting both — honestly, before engagement begins — sets accurate expectations and prevents the trust collapse that follows when hidden constraints emerge mid-process.
When skipped
Constraints that were not disclosed upfront emerge during or after the engagement. Communities feel misled. Trust erodes. Future engagement credibility is damaged.
→ Go deeper: The Smallest Undisclosed Constraint
STEP 3Define engagement objectives — not questions, objectives
Why it matters
Engagement objectives answer a different question to engagement activities. They ask: what do we need to understand from the community that we cannot understand without them? Not: what will we do in the sessions?
When skipped
Methods are chosen by habit rather than purpose. Teams reach for familiar tools without asking whether those tools will actually produce the information the project needs. The result is data-rich but insight-poor engagement.
→ Go deeper: Before You Write a Question, Answer This One
STEP 4Choose the level of engagement — and honour it as a commitment
Why it matters
Consult, Involve, Collaborate. These are not points on a scale from lesser to better. They are promises about the degree of influence communities will have. Choosing Collaborate when the decision space only supports Consult is not aspirational — it is a commitment you haven't checked you can keep.
When skipped
Teams choose Involve or Collaborate because it feels more respectful, without the earlier analysis to support it. Communities experience a gap between what the level implied and what the process delivered. That gap is experienced as broken trust.
→ Go deeper: A Promise, Not a Preference — Choosing your level of engagement and honouring it
STEP 5Map your stakeholders — before designing any content
Why it matters
Stakeholder mapping does three things that are prerequisites for almost everything that follows: it identifies who must be heard, it surfaces barriers to participation for each group, and it creates documented commitments about who the organisation will invest in reaching.
When skipped
Engagement design defaults to who is easiest to reach. Questions are written for general audiences. The communities most affected — and most likely to hold views different from those already captured — are systematically underrepresented.
A stakeholder map built before the decision space is defined is a map to somewhere you're not actually going.
→ Go deeper: Stakeholder Mapping: Who Needs to Be in the Room?
STEP 6Design questions and content by stakeholder group
Many practitioners keep this sequence as a quick reference when designing engagement plans.
Why it matters
Once you know who your stakeholders are and what barriers they face, you can design your engagement questions and content to address those barriers directly. Different groups need different framing, different depth, and different entry points to the same set of issues.
When skipped
One-size-fits-all engagement tools are used because they are efficient. The result is data that reflects the views of the most engaged and most accessible participants, not the full range of affected communities.
→ Go deeper: One Instrument, One Audience
STEP 7Select tools and methods through the lens of barriers
Why it matters
For each stakeholder group, tool selection should start with one question: what barriers does this group face in participating? The answer determines method choices — not budget, not familiarity, not what worked on the last project.
When skipped
The same groups are systematically under-reached across multiple projects. Teams notice the pattern but attribute it to community disinterest. The actual cause is method selection that was never designed to overcome their specific participation barriers.
→ Go deeper: Stop Choosing Engagement Methods By Habit — The barrier-first approach
STEP 8Build your evaluation framework before implementation begins
Why it matters
Define what success looks like before the first session runs. Process measures: did we reach the right people? Outcome measures: did community input influence the decision? Without pre-defined criteria, evaluation becomes post-rationalisation — selecting metrics that fit the outcomes achieved rather than the outcomes intended.
When skipped
Post-process evaluations measure what is easy to count: sessions held, participants, responses received. Nobody asks whether the engagement improved the decision. Because nobody agreed on what improvement would look like before it started.
STEP 9Track the connection between input and decisions in real time
Why it matters
As engagement runs, the thread connecting what communities say to what decisions are made must be maintained actively. This is not a documentation task — it is a governance task. It is the mechanism that makes closing the feedback loop possible.
When skipped
Teams reach the end of an engagement process knowing broadly what they heard but unable to demonstrate specifically how it shaped decisions. Closing the feedback loop becomes reconstruction rather than reporting. Communities receive summaries that describe input but cannot show influence.
→ Go deeper: The Thread You Can't Reconstruct
STEP 10Close the feedback loop — always, specifically, and on time
Why it matters
After decisions are made, go back to the communities who participated: this is what we heard from you, this is how it shaped what we decided, and this is why some of what you raised was not acted on. That last part is the most important and the most consistently avoided.
When skipped
The organisation moves to implementation without communicating back. Community members who invested time and knowledge never learn what happened to their contribution. They participate less in the next process — or not at all.
→ Go deeper: The Step That Determines Whether Communities Trust You Next Time — Closing the feedback loop
→ Go deeper: The Slow Erosion — What happens when feedback loops are never closed
Sequence is strategy
None of the failures described above require bad intentions, inadequate resources, or poor facilitation to occur. They require only that the sequence is not followed — that steps are reordered, skipped, or run before their prerequisites are in place.
The practitioners who consistently run high-quality engagement have internalised this sequence. They do not think of it as a framework or a compliance checklist. They think of it as the logic of the work — the order of operations that makes genuine community influence possible.
This is why experienced engagement teams increasingly move toward structured engagement design tools: not because structure constrains good practice, but because structure is what makes good practice consistent, auditable, and improvable.
That thinking is at the heart of CE Canvas.
Sequence is not a constraint on good engagement practice. It is the precondition for it.
Can AI help with this process and how?
Artificial intelligence can support engagement teams in maintaining sequence discipline — flagging when steps are out of order, surfacing constraints from project documents, and tracking the connection between community input and decisions. But AI cannot replace the human judgements at the heart of each step: what is genuinely open to influence, which communities must be heard, what engagement level the process can honestly deliver, and whether the feedback loop was closed with the specificity it requires.
Where AI helps: Maintain sequence discipline, surface constraints, and track input-to-decision threads across long engagement processes.
What stays human: Confirm what is genuinely open to influence, which communities must be heard, and whether the process can honestly deliver what it promises.
Governance check: Require source-linked outputs, human approval at each step, and a complete audit trail of sequence decisions and rationale.
Bottom line: AI can improve the consistency of engagement process design, but quality depends on the human judgements it supports, not replaces.
In This Series
Decision foundations
Before You Design Anything: What Is Actually on the Table? — Decision space mapping
The Smallest Undisclosed Constraint — Scope and constraints
Before You Write a Question, Answer This One — Engagement objectives
A Promise, Not a Preference — Choosing the engagement level
Engagement design
One Instrument, One Audience — Questions and content design
Stop Choosing Engagement Methods By Habit — Method selection
Accountability
Why Your Engagement Evaluation Is Probably Post-Rationalisation
The Thread You Can't Reconstruct — Input-to-decision tracking
The Step That Determines Whether Communities Trust You Next Time — Closing the feedback loop