Digital engagement platforms have changed community engagement for the better.
They have made it easier for organisations to create accessible project spaces, share information, collect feedback, run surveys, invite ideas and keep communities informed. For many engagement teams, they are now an essential part of how participation happens.
But the platform is where participation happens. It is not where engagement begins or ends.
Increasingly, we see engagement processes that follow a familiar pattern. A project page is created. A survey is developed. The opportunity is promoted. Responses are collected. Perhaps an open house or two is added. At the end, the organisation publishes a What We Heard report summarising what people said.
On the surface, all the components of an engagement process are there.
The problem is that sometimes the engagement design underneath them isn't.
A well designed project page cannot compensate for an unclear decision. A survey cannot fix weak engagement objectives. An open house does not automatically make a process inclusive. And a What We Heard report cannot demonstrate community influence if nobody tracked how community input was considered as decisions were being made.
Technology can make engagement easier to deliver. But that also means it can make poorly designed engagement easier to deliver at scale.
The opportunity is not to move away from digital engagement platforms. It is to think more carefully about the engagement practice that needs to surround them.
Start with the decision, not the topic
One of the most important distinctions in community engagement planning is between a topic and a decision.
Organisations frequently describe engagement in broad terms:
"We're engaging the community about the Downtown Master Plan."
"We want to hear what residents think about transportation."
"We're seeking feedback about the future of our parks."
These are topics. They do not tell participants what is actually being decided.
Before determining how to engage, the project team needs to understand the decision space. What specific decisions are still open? What has already been decided? What constraints exist? Who has the authority to make the decision? And when does community input need to be received in order to meaningfully influence it?
That decision space becomes the anchor for the entire community engagement process.
Without it, an organisation can run a technically excellent engagement process that is disconnected from the decisions it is supposed to inform.
It also creates a trust problem. If people are invited to comment broadly on a topic only to discover later that many of the things they commented on were never open to influence, the organisation may have unintentionally created expectations it cannot meet.
The first question therefore shouldn't be, "How should we engage?" It should be, "What are we asking people to influence?"
The survey shouldn't come next
Once the decision is clear, it can be tempting to move straight into writing questions.
But there is another step first.
Before asking what questions should go into a survey, workshop or interview, the project team needs to define its engagement objectives.
What do we need to understand from the community to make a better decision?
From whom do we need that understanding?
How will we use what we learn?
Those questions sound simple, but they fundamentally change the design of an engagement process.
Instead of:
Topic → Survey → Responses
the process becomes:
Decision → Engagement objectives → Stakeholders → Questions → Methods
That difference matters, and it is the logic behind the 10-step order of operations we use to sequence an engagement process.
When objectives are unclear, engagement can generate enormous amounts of input without necessarily producing the information the project team needs. Hundreds or thousands of survey responses may create the appearance of successful participation, only for the team to reach the analysis stage and discover that the questions didn't actually help resolve the choices facing decision makers.
Good engagement doesn't start by asking, "What questions should we ask?" It starts by asking, "What do we need to learn, from whom, to inform this decision?"
Reach is not the same as reaching the right people
Digital engagement platforms are very good at generating measurable activity.
Page visits. Registrations. Survey responses. Comments. Contributions.
Those metrics are useful, but they can also become proxies for engagement quality.
A project receives 1,500 survey responses and is described as highly successful. Another receives 300 and is considered less successful.
But what if the 300 responses came from the stakeholder groups most affected by the decision, while significant segments of the community were missing from the 1,500?
The more important questions are not simply about how many people participated.
Who needed to participate? Who actually participated? Who was missing? What barriers may have prevented their participation? And did we hear enough from the people affected by the decision to understand their perspectives?
This changes how we evaluate community engagement.
Participation numbers measure activity. They don't necessarily measure quality, representation or influence.
A large response rate can be valuable. But volume alone tells us very little about whether the engagement process reached the right segments of the community or whether their participation ultimately mattered.
In person engagement should have a purpose too
The same problem can happen offline.
Organisations sometimes complement an online survey with an open house because providing an in person option feels like good engagement practice.
It may be.
But the decision to hold an open house should be made for the same reason as any other engagement method: because it is appropriate for the people you need to reach and what you need to learn from them.
If a stakeholder group faces language barriers, transportation challenges, accessibility issues, limited digital access, low trust in government or simply has little reason to seek out a municipal project page, an open house at City Hall may do very little to address those barriers.
A different approach might be required.
Perhaps the team needs to go to an existing community event. Perhaps it needs small group conversations, stakeholder interviews, pop ups, facilitated workshops, translated materials or partnerships with trusted community organisations.
Perhaps an online survey really is the best method.
The point is that the method should follow the objective, stakeholder and barrier, rather than organisational habit.
The question shouldn't be, "Should we also offer an in person option?" It should be, "Who do we need to reach, what might prevent them from participating and what method gives us the best opportunity to involve them meaningfully?"
That is a very different way of designing engagement.
Good planning still needs to survive delivery
Even a well designed community engagement plan can break down once delivery begins.
This is where capacity becomes important.
Many organisations have strong community engagement frameworks and capable engagement practitioners. The challenge is applying that practice consistently across dozens, sometimes hundreds, of projects.
A central engagement team may be supporting multiple departments simultaneously. Project managers have competing responsibilities. Communications teams have deadlines. Consultants may be involved in some activities but not others. Engagement plans can become static documents that are completed at the beginning of a project and rarely revisited.
Under those conditions, the easiest form of engagement often wins.
Create the project page.
Launch the survey.
Promote it.
Collect the responses.
Move on.
Digital engagement platforms can inadvertently amplify this problem because they make these activities relatively easy to deliver.
The issue isn't the technology. The issue is what happens when the technology becomes a substitute for engagement practice rather than a tool for delivering it.
The answer to limited capacity cannot simply be doing more engagement faster. It needs to be finding ways to help teams apply good engagement practice more consistently.
Keep the engagement plan connected to delivery
A community engagement plan shouldn't be something that gets approved and then filed away.
It should remain a working part of delivery.
For every engagement activity, the team should still be able to answer:
Why are we doing this?
Which engagement objective does it support?
Who are we trying to reach?
What barriers are we trying to address?
What did we learn?
Which decision does that learning inform?
That creates a thread from the original decision through planning, participation and ultimately reporting.
Without that thread, engagement information quickly becomes fragmented.
The engagement plan is in one document. The stakeholder list is somewhere else. Survey responses sit in the digital engagement platform. Workshop notes are stored in Word documents. Emails contain important stakeholder conversations. Consultants produce separate reports. Project teams discuss trade offs in meetings.
Then, months later, someone is asked to prepare the What We Heard report.
And the organisation discovers just how difficult it is to reconstruct what happened.
You can't fix weak planning with a good What We Heard report
This is one of the most overlooked parts of community engagement reporting.
The quality of the final report is largely determined before engagement begins.
If the decision wasn't clear, it becomes difficult to explain what community members were actually influencing.
If engagement objectives weren't established, it becomes difficult to explain whether the process learned what it needed to learn.
If stakeholders weren't identified, it becomes difficult to evaluate whether the right people participated.
If methods weren't connected to objectives and barriers, it becomes difficult to explain why particular activities were undertaken.
And if the relationship between community input and project decisions wasn't documented during delivery, it can be almost impossible to reconstruct that relationship afterward.
The result is often a perfectly competent What We Heard report.
It summarises the number of participants. It describes the activities undertaken. It identifies major themes. It may include charts, quotes and demographic information.
But it stops at what we heard.
The question communities ultimately care about is: what happened because you heard us?
That requires more than analysis. It requires traceability.
As engagement progresses, organisations need to maintain the connection between what communities are saying, what the project team is learning and the decisions being made.
Because once that thread is lost, it is extremely difficult to recreate.
From participation metrics to engagement quality
This also requires us to rethink how engagement success is evaluated.
Participation still matters. If very few people know about an opportunity or take part, that deserves attention.
But evaluation shouldn't end there.
Instead of simply asking how many people participated, we should also ask:
Did we reach the stakeholder groups we identified as important to the decision?
Did we understand and address barriers that could prevent participation?
Did participants understand what they could and couldn't influence?
Did our methods generate the information our engagement objectives said we needed?
Did the project team receive that information while decisions were still open?
Can we demonstrate where community input influenced the decision?
Where community preferences weren't reflected in the final decision, can we explain why?
These are harder things to measure than page views or survey responses.
They are also much closer to what meaningful community engagement is supposed to achieve.
Before, during and after participation
This is why community engagement needs to extend beyond the platform.
Before participation, teams need to define the decision space, understand constraints, establish engagement objectives, identify stakeholders, understand barriers and select appropriate methods.
During participation, they need to deliver against that plan, monitor who is and isn't being reached, adapt where necessary, analyse what they are learning and maintain the connection between community input and emerging decisions.
After participation, they need to close the feedback loop by showing what they heard, what they learned, what was decided and how community input influenced the outcome.
The online participation platform is an important part of that ecosystem.
But it is one part.
Technology should strengthen engagement practice, not replace it
The next evolution of technology in community engagement shouldn't simply be about creating better surveys, prettier project pages or faster analysis.
It should be about helping organisations apply good engagement practice more consistently from beginning to end.
That is the gap CE Canvas was designed to address.
Digital engagement platforms provide places for communities to participate online. CE Canvas works around that participation, helping teams plan engagement before it begins, support the work while it is being delivered and maintain the evidence needed to demonstrate how participation influenced decisions afterward.
The two serve different but complementary purposes.
Because ultimately, the goal isn't to generate more participation. It is to support better decisions through meaningful participation.
A thousand survey responses may look impressive on a dashboard. But the more important measure of success is whether we reached the people we needed to reach, learned what we needed to learn and can demonstrate how their participation mattered.
The platform is where participation happens. Good engagement is everything that connects that participation to the decision.