Community engagement has no shortage of frameworks, training courses, models, principles and best-practice guidance.
Organizations such as the International Association for Public Participation (IAP2) have played an important role in professionalizing the practice. Thousands of practitioners have learned concepts such as the IAP2 Spectrum of Public Participation, engagement planning, stakeholder identification and the importance of being clear about the influence communities have over decisions.
That knowledge matters.
But there is a growing challenge facing the profession that training alone cannot solve.
What happens on Monday morning, when the practitioner has to actually do the work?
There is an enormous gap between learning community engagement best practice and consistently applying it across real projects, teams and organizations.
We call this the community engagement implementation gap.
And closing it may be one of the biggest opportunities facing the profession today.
What is the community engagement implementation gap?
The community engagement implementation gap is the distance between knowing what good engagement practice requires and being able to apply it consistently in day-to-day work.
Professional development traditionally works by transferring knowledge.
A practitioner attends training, learns a framework, works through examples and returns to their organization better equipped to design and deliver engagement.
But the environment they return to hasn't necessarily changed.
Projects still arrive late.
Decision-makers may not have clearly defined what communities can influence.
Project teams want a survey launched next week.
Stakeholder knowledge sits across spreadsheets and people's heads.
Different departments interpret the organization's engagement framework differently.
Previous engagement plans are buried in shared drives.
Lessons from one project rarely make their way systematically into the next.
The practitioner may know exactly what good engagement looks like. The challenge is applying that knowledge consistently within the realities of everyday organizational work.
Training builds capability. Practice requires infrastructure.
A framework is only as valuable as its use
Many governments and organizations have invested significant time developing community engagement policies and frameworks.
They establish principles, define expectations and create a common language for how the organization intends to engage.
But publishing a framework doesn't automatically change practice.
The harder question is how the framework influences the hundreds of decisions practitioners and project teams make while planning and delivering engagement.
That means translating organizational principles into practical questions:
What decision are we actually engaging people about?
What is genuinely open to influence?
What constraints already exist?
What are our engagement objectives?
What level of participation can we honestly promise?
Who needs to participate?
What questions should we ask?
Which methods fit those audiences and objectives?
How will input be documented and connected to the eventual decision?
How will we report back?
These aren't theoretical questions. They are everyday project decisions.
As we explored in The Hard Part Comes After the Engagement Framework Is Finished, the real test of a framework isn't whether an organization has one. It is whether practitioners can consistently apply it.
The same principle applies to training: knowledge creates value when it changes what happens during the work.
Good engagement is a sequence, not a checklist
The implementation problem also appears at project level.
Our 10-step order of operations starts with the decision itself, not the survey, workshop, open house or digital engagement platform.
The sequence moves from defining the decision space and constraints through objectives, engagement level, stakeholders, questions, methods, evaluation, decision tracking and finally closing the feedback loop.
The order matters.
If a team selects methods before establishing objectives, it risks designing activity rather than engagement.
If it identifies stakeholders before understanding the decision space, it may not know whose interests are actually affected.
If reporting is considered only after engagement finishes, it becomes much harder to demonstrate how community input influenced the decision.
Experienced practitioners understand these relationships.
The challenge is making sure they happen every time, across every project, regardless of who is leading the work.
That requires something beyond knowledge. It requires infrastructure for practice.
From training to practice enablement
This is where we believe the next evolution of the profession may happen.
Training will continue to matter. Professional standards will continue to matter. Frameworks will continue to matter.
But practitioners increasingly need support while they're doing the work, not only before they do it.
Imagine if the guidance in training manuals, organizational frameworks, previous project experience and professional standards was available inside the workflow of an actual engagement project.
Instead of asking practitioners to remember every principle they have learned, the process itself could help them apply those principles.
Instead of a framework sitting in a PDF, it could actively guide project planning.
Instead of starting every engagement plan from a blank document, practitioners could work through a structured process grounded in established practice.
Instead of organizational knowledge disappearing when staff change roles, lessons could accumulate across projects.
And instead of AI simply generating engagement plans or summarizing comments, it could help practitioners interrogate their thinking while leaving professional judgment with the practitioner.
That is a different role for technology.
What is a practice layer for community engagement?
We think of this as the practice layer for community engagement.
A practice layer connects professional standards, organizational frameworks and practitioner knowledge to the everyday workflow of planning, delivering, evaluating and reporting on engagement.
It sits between knowing what good engagement looks like and actually doing it.
A practice layer should help an organization:
establish what communities can genuinely influence;
translate engagement policies and frameworks into project-level decisions;
maintain a consistent planning process;
apply professional standards across teams and departments;
preserve evidence and rationale throughout a project;
connect community input to decisions;
evaluate engagement quality and outcomes;
close the feedback loop; and
carry organizational learning from one project into the next.
This isn't about replacing professional judgment with a checklist.
It's about creating the conditions in which good judgment can be applied more consistently.
Technology shouldn't replace practitioners
The arrival of AI makes this distinction particularly important.
It is increasingly easy to ask a generic AI tool to create a stakeholder list, write survey questions or draft an engagement plan.
But producing content isn't the same as practicing community engagement.
Good engagement requires judgment:
Should this project involve engagement at all?
What can people genuinely influence?
Are we making a promise to Consult, Involve or Collaborate that the organization can actually honor?
Which voices might be missing?
Are the questions we're asking connected to a real decision?
Can we trace community input through to what ultimately happened?
Technology should help practitioners ask better questions and maintain that discipline throughout a project.
It shouldn't make those decisions for them.
That's why our approach to responsible AI in community engagement focuses on AI supporting structured thinking and human judgment rather than replacing it.
Community engagement isn't a content-generation problem. It is a practice and judgment problem.
The opportunity for IAP2 and the profession
IAP2 has helped establish a common language for public participation around the world. IAP2 International develops and owns the core training curriculum, and its Spectrum and practice resources have influenced generations of practitioners. It remains the premier training organization for engagement practitioners across Canada, the United States, Australia and New Zealand.
Around it, a wider ecosystem now supports engagement capability.
United States. The Institute for Local Government in Sacramento works with California local governments and has its own TIERS Public Engagement Framework and associated training. Pepperdine's Davenport Institute for Public Engagement and Civic Leadership trains local-government staff and elected officials in public engagement. The National Coalition for Dialogue & Deliberation offers training, events and a substantial resource library on dialogue, deliberation and facilitation.
Canada. The Tamarack Institute runs a Learning Centre of workshops, cohorts, courses and communities of practice in community engagement, collaboration and community change. Dialogue Partners delivers IAP2 training alongside its own curriculum in dialogue, facilitation and high-stakes engagement.
Australia. The Engagement Institute, known as IAP2 Australasia until its 2025 rebrand, remains part of the international IAP2 network. MosaicLab offers practice-based training in engagement, facilitation and deliberation. The UTS Centre for Local Government runs a professional-development course in community consultation and engagement.
Between them, these organizations have built a strong foundation of knowledge. That foundation raises an interesting question about what comes next.
If the first era of professionalizing community engagement was about teaching the practice, perhaps the next is about helping practitioners apply it continuously.
Training might happen several times in a practitioner's career.
Practice happens every day.
That creates an opportunity for professional bodies, technology providers, governments and practitioners to think differently about how the profession is supported.
The future doesn't need to be training or technology. It can be:
training connected to practice;
professional standards connected to workflows;
organizational frameworks connected to projects;
project decisions connected to evidence;
community input connected to decisions; and
technology connected to human judgment.
The organizations that help make those connections will create enormous value for practitioners, and may redefine how professional practice is supported.
From frameworks to everyday decisions
Consider something as fundamental as the IAP2 Spectrum.
Knowing the difference between Consult, Involve and Collaborate is important.
Applying that knowledge requires something more.
Before selecting an engagement level, a practitioner needs to understand the decision, identify what is genuinely open to influence, document constraints, establish objectives and determine what level of influence the organization can realistically honor.
That's why we describe an engagement level as a promise, not a preference.
The same applies throughout the engagement process.
Stakeholder mapping becomes valuable when it changes who participates.
Evaluation becomes valuable when it influences how the process is designed.
Reporting becomes valuable when organizations can show how community input influenced decisions.
Frameworks and training provide the principles.
Practice is where those principles become consequential.
The practice layer, in practice
This is the problem we set out to solve at CE Canvas.
Our ambition was never simply to digitize an engagement plan or add AI to community engagement.
We have built a practice layer for community engagement: a place where practitioners apply established engagement principles while they're actually doing the work. It is already in use with communications and engagement leaders at organizations such as Landcom in New South Wales and the City of Delta in British Columbia.
It connects organizational context, engagement frameworks, project decisions, planning, delivery, evidence, evaluation and reporting in one continuous workflow.
It helps organizations move from learning good practice, to applying it, to demonstrating it, to learning from it.
And over time, organizational engagement capability grows stronger with every project, rather than disappearing when the project finishes or people leave.
From knowing to doing
Community engagement doesn't suffer from a lack of principles.
We know a great deal about what good engagement looks like.
The bigger challenge is turning that knowledge into consistent practice across hundreds of projects, thousands of decisions and organizations with very different levels of capability.
Training helps practitioners understand what good looks like.
Frameworks establish expectations.
Professional standards create a common foundation.
The missing layer is what helps practitioners put all three into practice every day, while keeping judgment and accountability with the practitioner.
The question for the next phase of the profession may be less about how we teach better community engagement, and more about how we help people practice it better, every day.
That's the gap worth solving.