This guide is the overview of planning practice: the sequence of judgments that sit behind a credible engagement plan and why the order matters. If you want the step-by-step document, with a downloadable template, start with how to write a community engagement plan. Read this page for the thinking, and that one for the write-up.
The sequence below starts with the decision, not the methods. Each step produces something the next step needs, which is why skipping one rarely saves time. It usually moves the cost to the middle of the engagement, where it is hardest to fix.
Where should community engagement planning start?
Planning should start with the decision and its decision space: what is being decided, what is genuinely open to influence, who holds authority and when the choice will be made. Everything else in the plan, from stakeholders to methods to dates, depends on those answers.
The decision space has three dimensions. Scope is the specific choices community input will inform, such as design, location, timing or how something is delivered, rather than the project in general. Authority is who decides each choice and how input reaches them. Timing is when each decision closes, which is often earlier than the formal approval date because funding agreements, business cases and preferred options presented to decision-makers narrow what can change. Mapping the decision space walks through the three questions and a one-page worksheet.
Write down what is fixed as carefully as what is open. Legislation, prior commitments, budget and technical limits all belong in the plan before engagement opens. A constraint that surfaces halfway through costs more trust than one stated at the start, a point made in the smallest undisclosed constraint.
Ask this first
Not "how do we engage?" but "is there still something meaningful to engage about, and until when?"
Is this an engagement project at all?
Not every project that touches the public is an engagement project, and planning should classify the work before designing a process for it. If no choices remain open, explain the decision through communication or notification. If consultation is legally required, establish what input can still influence and say so.
Calling an information campaign "engagement" is a problem when it implies influence that is not on offer, because people then expect influence they will not get. Running open-ended engagement on a fixed decision produces the same result at greater cost. Not every project is an engagement project sets out the distinction, and the free project assessment tool walks a project through it. When the window is narrow but not shut, the better move is to engage on the parts that are still open and say plainly what is not. Honest consultation on a small decision space is worth more than collaboration on one that has quietly closed.
What makes a good engagement objective?
A good engagement objective names what you need to understand from the community, which groups you need it from and what you will do with it. It describes the input that will change the decision, not the activities you plan to run.
"Engage the community on the park upgrade" is not an objective. "Understand which user groups have the least access to the park today, so the budget can be prioritized for them" is. The second tells you who must be reached, what to ask and whether the process succeeded. Keep objectives few, focused and proportionate to the decisions being informed. A long list usually means the decision has not been framed tightly enough.
Objectives also guard against a common failure: rich input that does not answer the question the decision-maker actually has. Teams often discover this only when analysis begins. Setting clear engagement objectives covers the drafting steps and the pitfalls, including vague goals and objectives copied from the last project.
How do you choose the level of engagement?
Choose the level of engagement as a promise about influence that the decision space, your objectives and your organization can actually support. The level is not a signal of how much you respect the community.
The IAP2 Spectrum of Public Participation is the usual reference. It describes five levels, each with a promise to the public:
- Inform: provide balanced information so people can understand the problem and the options, and keep them informed. Inform commits to keeping people informed; it does not offer influence over the decision.
- Consult: keep people informed, listen to and acknowledge their concerns and aspirations, and provide feedback on how their input influenced the decision.
- Involve: work with people to ensure their concerns and aspirations are directly reflected in the alternatives developed, and provide feedback on how their input influenced the decision.
- Collaborate: look to the public for advice and innovation in formulating solutions, and incorporate their advice and recommendations into decisions to the maximum extent possible.
- Empower: place the final decision in the hands of the public and implement what they decide.
Overclaiming is the more damaging mistake. Teams pick Collaborate because a project is significant, run co-design workshops, and then announce an option shaped by constraints nobody disclosed. Participants conclude the process was theatre, and they are right. Underclaiming has a cost too: defaulting to Consult signals limited influence before anyone has tested what more is possible. Choosing the level of engagement gives three questions to ask in order: what is open, what you need, and what you can deliver.
IAP2 is currently reviewing the spectrum. The recommendations before its board would rename the levels, move Inform out of the row as a foundation that carries no influence, and replace "promise" with "commitment". No final decision has been made. The IAP2 spectrum, explained tracks what has been proposed and what it would mean for plans and policies that use the current labels.
How should you map stakeholders for an engagement plan?
Map stakeholders against the open decision, by how much it matters to each group (stake) and how much each group can change the outcome today (influence). A map built before the decision space is settled tends to send good outreach toward choices that are not actually on the table.
Start broad. List directly affected people, people who avoid a place or service because of the issue, neighbors, rights-holders, regulators, internal teams and delivery partners. Then refine each group until you could find and contact it: "residents" becomes "renters within half a mile of the site", and "families" becomes "parents at a named primary school". Rights-holders keep their standing wherever they sit on the map.
When you place groups, mark which ones live with the effects as directly affected. Do not lower a group's stake because it is quiet, small or hard to reach. Reserve high influence for those who can change or block the outcome. The groups that need the most planning effort are usually the directly affected ones with low influence: they have the most at stake and the least say, and they are least likely to arrive without deliberate effort. Placing them is also a check on the level you chose. If the people most affected cannot be offered the influence the level implies, revisit the level now.
Stakeholder mapping and analysis explains why mapping belongs after the decision foundations. To do it on screen, use the free stakeholder mapping tool; for a document, the stakeholder engagement plan template follows the same list, refine, map, reach and review steps. Treat the map as a current judgment. Groups organize, options get shortlisted, and influence shifts, so plan points in the project where you will reassess it.
How do you plan outreach to people standard engagement misses?
Plan deliberate outreach by naming, for each group you flag, what gets in the way of taking part and what you will do about it. A flag without a barrier and a response is a good intention, not a plan.
Seven barriers cover most situations:
- Access: location, physical accessibility, childcare, transport or timing of sessions.
- Language: the process runs in a language the group does not use comfortably.
- Trust: past experience makes the group doubt the process or the organization.
- Time: work shifts and caring responsibilities leave little room to take part.
- Awareness: the group does not know the project exists or what it involves.
- Relevance: the group does not see how the decision affects them.
- Digital access: limited connection, devices or comfort with online tools.
Flagging a group is a commitment to resource it. Prioritize extra outreach by barriers and coverage gaps, not by influence alone. Spending follows the people who would otherwise go unheard.
How do you choose engagement methods?
Choose methods group by group, starting from the barriers each group faces, and pick the methods that remove those barriers. Familiarity, budget and what worked last time are real constraints, but they are poor starting points.
The familiar set of an online survey, information sessions, a project page and an email newsletter works for people who already know about the project, have time and are comfortable online. Used by default, it produces the same participation gaps project after project, which then get read as disinterest. A barrier-first plan looks different: a printed form and a drop-in for residents without internet access, a conversation hosted by a trusted community organization for a group with low trust, an evening or weekend session for shift workers. Online engagement tools still have a place, alongside the methods that reach the groups they miss. Choosing engagement methods by barrier, not habit sets out the approach.
Check coverage before you finalize. Every group in the register should appear against at least one activity. A group with no activity is a gap to fix, or to explain on the record.
How do you build an engagement timeline and resource it?
Build the timeline backward from the decision windows: find the latest date input must be in hand to shape each decision, then schedule analysis, approvals and activities before it. A timeline built forward from when the team is ready tends to run after the decision has narrowed.
Schedule the work between activities, not only the activities. Teams most often forget briefings and internal sign-off before launch, lead time for translation, venues, accessibility and materials, analysis time between phases so the next round can respond, and drafting time for the report back. Community rhythms matter as much as internal ones: school holidays, seasonal work, religious observance and local events all change who can take part. Planning a community engagement timeline covers each of these.
Resourcing follows the same logic. Budget for staff time, venues, translation, accessibility, communications and the analysis and reporting that happen after engagement closes. Deliberate outreach costs more per participant than a survey link, and the plan should say so rather than leave it to whatever is left over. If the resources cannot support the level you chose, lower the promise or find the resources before launch.
How do you turn an engagement plan into tasks and milestones?
Turn each activity into tasks with an owner, a start date, a due date and any dependency, and mark the milestones decision-makers care about: plan approval, engagement opens, engagement closes, the what we heard report and the decision itself. A plan without owners and dates is the first thing to slip when time runs short, and deliberate outreach usually slips first.
One line in a plan, such as "two drop-in sessions to test design options", becomes several tasks: book an accessible venue, prepare the display material once options are approved, promote through channels each group uses, prepare a printed form for people offline, run the sessions, and record what was heard. Keep the reason for each task visible. The outreach task exists because of a decision in the stakeholder plan, and anyone looking at it should be able to see why. Plan the report back now as well, since closing the loop is where participants judge whether the promise was kept. See closing the loop for that stage, and community engagement strategy for the organizational framework that sits above individual plans.
How does CE Canvas support engagement planning?
CE Canvas keeps the planning decisions in one project record. The engagement canvas and plan hold the decision, what is open and fixed, the stakeholders and the level of engagement on one page, so later work can be checked against them.
The stakeholder workshop follows the steps in this guide: list, refine, map, reach and review. The CE Canvas AI assistant can suggest groups you may have missed and review placements against practice, and your team makes the final calls.
A community engagement playbook builds each project's phases, milestones and dated tasks from your organization's practice, timed against when engagement opens and closes and the decision date. The team reviews everything before it is created. See how it works, or build your organization's framework first so every plan starts from the same practice.
Last reviewed October 19, 2026 by the CE Canvas practice team.