What’s New — September and October 2026
Two months with one theme: carrying the strategy on the canvas all the way into the work. Engagement phases now behave the same everywhere, a mapping workflow makes the stakeholder decision deliberate, and two betas take the plan into survey design and onto the map.
Engagement phases, made consistent
The objective. A project with two rounds of engagement should read as two phases everywhere — on the canvas, in Delivery, in Tasks, in the plan, in Results and in the report — without a Playbook and without anyone re-entering dates.
What changes for you. One vocabulary runs through the product: project, engagement phase, step, task. Add a second phase from the Timeline or from Delivery and the canvas, tasks, plan and EVA all follow, with phases named consistently (Phase 1 — Gather input) rather than numbered twice. Edit phase in Delivery renames a phase or fixes its window in one place. Rescheduling follows one rule on every path: drag a milestone and the tasks timed from it move with it, unless they are complete or you set their dates yourself.
And when you report. Results can be filtered to one phase, and a multi-phase project gets a What we heard report for each phase alongside the whole-project report, so you can close the loop after every round rather than only at the end. Phases in Delivery · A report for each phase · Milestones on the Timeline
The stakeholder mapping workflow
The objective. Most stakeholder lists are the last project’s list with a name changed. They miss the people who bear the consequences and over-weight the people who are easy to reach, and nobody notices until the report is challenged. The mapping workflow makes who needs to be heard a decision you can show your working for.
What changes for you. From the Stakeholders section, the workflow walks five steps — List, Refine, Map, Reach, Review. Every group is placed by stake in the decision and influence over it (stake replaces the earlier impact axis: a committee that decides the matter has a high stake without living with the effects). A directly affected marker is recorded separately so the coverage review can always see the people who bear the consequences. Flagging a group for deliberate outreach turns a gap into a commitment with a stated reason. Get suggestions asks EVA to propose placements on the page; nothing is written until you apply a row. Every route ends at the same coverage review, which names what is missing while it can still be fixed.
Enabled per organization. Placing groups on the map
Beta: design your survey from the plan, host it wherever you already do
The objective. A survey is only as good as the plan behind it. The platform you host on knows how to collect answers; it has no awareness of the decision, what the plan promised participants, which stakeholder groups the survey must reach, or which objective each question serves. That knowledge lives in your plan, and CE Canvas is the one place a survey can be designed against it. Where the survey is hosted is a separate choice — most organizations already collect input on Social Pinpoint, EngagementHQ or SurveyMonkey, and that does not need to change.
What changes for you. The survey builder starts from the plan, and keeps it in view. Plan alignment beside the builder shows the purpose, the audience and the participant experience the plan promises; the needs list is your plan’s key questions and objectives, each marked until a question serves it. EVA drafts one to three questions per need from the same project context, for you to accept or edit, and you choose which stakeholder groups see which questions. Share shows exactly what is left before the survey can open. Then choose Hosted in another platform, name it and paste the participant link; when the survey closes, import that platform’s export and the responses read against the questions you designed, into Results, the Outcomes Report and Close & Learn’s evidence by objective. If you would rather CE Canvas host it — public link, QR code, consent, paper-form recording — that is there too.
Enabled per organization. Building a survey
Beta: say where your project is
The objective. “The community” should mean the people who live with this decision, not whoever turns up. Saying where the project is lets every later step be specific about place.
What changes for you. Search for a place, draw a boundary, drop a site with a catchment, trace a corridor or upload a file. The area then shows on the project home, in EVA’s advice, on activities (Show on the map places a venue against it), in the Engagement Plan and on any map a survey uses. Australian and Canadian organizations can add Community context: official census figures for the area, shown as honest ranges rather than a single invented total, with a view of which groups a broad average would miss. The Scopomap integration lets a partner send boundaries and community measures straight into a project, where you choose whether to adopt them.
Enabled per organization. Project Area · Scopomap integration
Smaller changes
- Digests arrive at your time. The daily and weekly task digests send at the hour you choose, in your organization’s timezone. New projects no longer seed an automatic “Add project context” task. Notification settings
- Template status. Organization document templates are draft, published or archived; only published templates are offered when a plan or report is created. A template with no documents can be deleted; one that has been used is archived instead. Document templates
- Start a plan again. A plan created from the wrong template can be started again from the template choice; the canvas is untouched. Starting again
- My feedback. Send feedback now has View my feedback, showing the status of anything you have reported and any replies from the team. Sending feedback
- Google Drive, per person. Where Google Drive is enabled, everyone connects their own Google account, and a shared folder can be connected once for the whole organization. Google Drive
- Partner API. Integrators can send documents, boundaries and measures into a project with a credential you control. Partner API
Also since August
- Review EVA’s whole draft before you apply it. Field-level drafts now show the full proposed text in the field it is destined for, and a draft that spans several fields previews every one of them. Saved content, unsaved edits and a pending draft are visibly different states. Working with EVA