Engagement Plan
The Engagement Plan is the formal document — for council approval, executive sign-off, compliance, or publication. It expands the strategy your team agreed on the Engagement Canvas into a full written plan, generated and refined with EVA.
From the project sidebar, go to Planning → Plan, or open it from the third card on the Planning hub.
If you skip this: the strategy stays in the team’s heads and on the canvas. The people who approve, fund, or audit the engagement never see the reasoning, and when the approach is challenged there is nothing on record to show it was deliberate. The plan is where the canvas becomes a commitment others can hold you to — and a plan that drifts from the project it describes is worse than none, which is why Refresh from project exists.
The canvas leads, the document follows. Not every project needs the formal plan — for many, the canvas is the plan. Generate the document when an audience outside the team requires it, and treat the canvas as the source of truth the document expresses. A plan generated before the canvas is settled documents a strategy you haven’t agreed yet.
The plan editor
The groups and sections come from your organization’s active Engagement Plan template, so exact names can differ. The default template organizes the document into four section groups — work them in order, because later sections depend on earlier decisions:
| Group | Covers |
|---|---|
| Foundation & Planning | Introduction, Engagement Objectives, Negotiables / Non-Negotiables, Engagement Decision Context |
| Scoping & Assessment | The stakeholder landscape, participation barriers, and groups needing deliberate outreach |
| Engagement Design | Methods, channels, accessibility, timeline, participant experience, and resourcing |
| Evaluation & Closure | How success is measured and how the feedback loop will be closed |
The Introduction section opens with an Engagement need field: the sizing from Assess needs in a few sentences. It covers the effort and your organization’s name for it, people’s role and the phases, the minimum notice and response periods with where each comes from (a statutory period is named as one), who leads, and the commitment on how people’s input will be used. It is prefilled when the plan is created; Refresh from project brings it up to date after the sizing is confirmed again. Edit it like any other field.
The Introduction section also carries a Project area field. It is prefilled from the project area when one is set — your own descriptions of the areas, their names and the size — and Refresh from project on the section brings it up to date after the area changes. With no area the field stays empty for you to write.
The Engagement Timeline section’s two tables are live: Key Milestones and Steps mirror the project’s Timeframe rather than being drafted, and refresh while the plan is a draft. Steps are listed in the same order and with the same dates as the Timeline — a step without its own dates shows the period its dated tasks and activities cover. When the project runs more than one engagement phase, each step also names its phase (Preparation · Phase 1 — Gather input). Once the plan is approved or published, its tables keep what was approved.
Templates vary. Groups and sections follow the template your organization has adopted — some rename the first group (for example, Project Foundations) or add sections beyond the default. Manage templates in Organization Settings.
For each section:
- Field guidance describes what to capture, with word counts against a minimum target
- Draft with EVA generates content from your context, canvas, and project materials. On a plan that is partly drafted it selects only the empty fields, so running it again carries on where it stopped; tick filled fields to redraft them
- Mark as Ready signals the section is reviewed and final — the section locks against accidental edits until you click Edit, and the progress card counts it (progress is sections marked Ready over included sections, so excluding a section removes it from the denominator and an all-Ready document reads 100%)
- Exclude Section removes sections that don’t apply to this project
Content saves automatically. Use Preview to see the formatted document and export it when the sections are ready. Headings, numbered lists, links and tables that EVA writes render the same way in the editor’s read view, in Preview and in the exported PDF or Word file.
What deserves human attention
EVA can draft every section — but four of them carry the commitments that make or break the engagement, and they must reflect decisions only your team can make:
- Negotiables / Non-Negotiables — the document’s honesty test. If this section is vague, every promise in the rest of the plan is built on sand
- Engagement Decision Context — must match the Project Context decision space, not a more comfortable retelling of it
- The engagement level — the plan must promise the level the canvas committed to (Level & Promise), not upgrade it for a better-reading document
- Evaluation & Closure — dates and channels for closing the loop, specific enough that someone could check whether you did it
Keeping the plan current
When context or canvas changes — a constraint added, a milestone moved, a method swapped — the affected plan sections need revisiting. Apart from those live tables while the plan is a draft, the document doesn’t auto-update: that’s deliberate, because an approved plan changing silently is worse than one that’s explicitly revised. Re-draft the affected sections with EVA, review, and re-mark them ready.
Approval and sign-off
When the plan is complete, Send for approval (in the ⋯ menu) puts it in review. To have named people sign it off first — for example a Director, a Development Director and two Executive General Managers — open Sign-off, choose them from the people on the project and Ask for sign-off. Each gets a task, “Review and sign off”, that opens the plan, so the request arrives through their email, My Tasks and the digest. They sign off from the same Sign-off button, with an optional note, or by completing that task. If someone can no longer sign — they have left the project, say — use Change reviewers: the people who stay keep their sign-offs, and anyone taken off no longer holds up approval.
Approve waits until every reviewer has signed (Waiting for sign-off (1/3)). Approving freezes the version, files a PDF with the approval and records who approved it. Project Home shows where the plan stands: Plan sign-off 1/3, then Plan approved, version 2.
A sign-off belongs to the content it was given on. Editing the plan, changing its sections or fields, or choosing Reopen returns it to draft and closes the request (a change of color theme does not); outstanding review tasks are put away and the earlier sign-offs stay on record. Send it for approval again to ask again. Without named reviewers, a project manager approves the plan directly, as before.
Starting again from a different template
A plan keeps the template it was created with. To move it to a different template, choose Start again in the plan toolbar. This deletes the plan’s content, comments and version history, then returns you to the template choice; your canvas is not affected, so Draft with EVA can rebuild the plan from it. An approved plan can’t be started again — reopen it first.
Next steps
- Engagement Planning — the hub showing all three planning surfaces
- Engagement Canvas — the strategy the plan expresses
- Delivery — where the plan becomes scheduled work