Engagement Playbooks
A Playbook is your organization’s engagement practice, encoded: applying one generates the engagement phases, steps, milestones, tasks, and suggested activities appropriate to a type of project. A new project gets a proven operational skeleton in minutes — which your team then makes specific.
If you skip this: every project rebuilds the same structure from scratch, and quality depends on who happens to be running it. Playbooks are how good practice stops being tribal knowledge.
Applying a Playbook
On Project Home, the Playbook menu shows what this project is using. In an organization with its own Playbook, a new project starts on intake (Project Context, then Assess) and the menu reads Project type not chosen until you pick one — usually from the end of Assess, which offers the project types that fit (Use Consult, for example). Confirming the intake decision with a project type chosen sets the Playbook up straight away: its steps, gates, suggested activities and tasks appear on Project Home. If no engagement window has dates yet, they arrive undated and take their dates when the window is dated on the Timeline. Use Review / Change later to adjust the setup below. The card names the project type in use and whether it has been applied.
Setup (from Review or Change, or when a project already has a different project type) has two steps.
Step 1 — Configure
Choose the Playbook and the project type within it — the type is what tunes the suggestions, and it sets how long an engagement window can run. Then answer when the public can have their say — the date it opens and how many days it stays open. This is the engagement window: it sets the opens and closes milestones, every task in the play is timed to them, and the decision date follows the close, so the page shows the close and decision dates as you type.
Re-opening setup on a project that already has a Playbook applied starts from the project’s own dates, not the template defaults — so reviewing the configuration never quietly reschedules anything. If you do change any window’s start date or length, in any phase, setup asks you to confirm before it moves the tasks scheduled against it.
Projects with more than one engagement phase
An engagement phase is a distinct period of community engagement with its own purpose, steps and report — Phase 1 — Gather input, then, after a draft, Phase 2 — Confirm direction. Inside each phase, the engagement window is the few weeks the community can contribute; the phase itself may span months of preparation, analysis and reporting around it. The steps (Preparation, Engage, Analyze, Report back) are the periods of work that hold the tasks.
Most project types have one engagement phase, and you never see the structure — just the steps. A type with several asks for one engagement window per phase, each named after its phase.
Only the first window is required. A later phase’s dates usually aren’t known at setup — they depend on how long the draft takes and when Council next sits. Each window’s length must fall within the project type’s range. Leave a later window blank, and:
- its tasks are still created, undated, so nothing is forgotten;
- its steps take their dates from those tasks rather than being given invented ones;
- the Decision Date stays undated. It is set after the last engagement window, so it waits until every window has dates — the review step says so.
When you know the dates, re-open setup, fill that phase in and apply again. Its tasks schedule themselves, the Decision Date is set after the last window, and nothing is duplicated.
Step 2 — Review & apply
Nothing is created until you press Apply playbook. Before that, review it across two tabs — activities first, because some tasks belong to them:
- Suggested activities — the engagement activities this type suggests, grouped by engagement phase when there’s more than one. Decline what you won’t run.
- Tasks — every task the Playbook proposes, grouped by step (and by engagement phase), each timed relative to a milestone (-14d · Engagement opens, or -49d · Phase 1 opens when there are several phases). Program tasks stand on their own. A task that belongs to an activity is marked with Let’s Talk Delta project and follows that activity: decline the activity and its tasks are set aside with it. Recommended tasks are pre-selected; deselect what doesn’t apply.
A summary bar keeps the consequences in view: project type, level, task count, activity count, and when the engagement window closes. Re-applying doesn’t duplicate what’s already there.
Once applied: tasks land in Tasks; the milestones (Engagement Opens, Engagement Closes, and Decision Date) and the steps appear in Delivery and the Timeline; and the activities you selected are added to the Engagement Canvas, scheduled across the engagement window. The Engage step of each phase takes that phase’s window as its period, so the plan reads with real dates from the first minute.
A project type with several engagement phases gets a milestone pair per phase instead, each named after it — Phase 1 — Gather input opens / closes — plus the one Decision Date at the end. Moving a phase’s opening milestone on the Timeline drags its closing milestone with it, so the window keeps its length.
Available Playbooks
A starter Playbook, Engagement Essentials, ships as a general-purpose framework suitable for most community engagement projects. Its project types are Community Vision & Strategy, Major Development, Policy & Service Changes, Project Delivery, Routine Engagement and Information & Awareness, each with one engagement phase, plus Major Engagement — Two Phases, which runs Phase 1 Gather input and then Phase 2 Confirm direction for major projects that size at two phases. Organizations maintain their own Playbooks in Organization Settings → Playbook: each project type’s Details tab lists its engagement activities, its task templates (grouped by step, each timed against a milestone), and its steps — add or rename steps right there. A step is either an engagement step, which defines an engagement phase of the Playbook (add two and the Playbook runs two phases, each with its own window), or an internal step (preparation, analysis, reporting back) that holds tasks and, when there are several phases, can be filed under one of them or left for the whole project.
Steps can belong to particular project types. Each project type shows only its own steps — exactly the ones a project of that type gets — so a one-phase type never shows a second phase’s steps. A step you add while a project type is selected belongs to that type when the Playbook already gives that type its own steps; otherwise it applies to every type.
A task template is timed against one of its project type’s milestones: the opening or closing of each engagement window (Phase 1 — Gather Input opens, or Engagement opens for a one-phase type) or the Decision Date. The Timeline tab previews everything the Playbook adds: each window in turn at the type’s minimum length, eight weeks apart, with the Decision Date after the last one.
Custom Playbooks — sector-specific workflows, compliance frameworks, or your organization’s signature methodology can be encoded as custom Playbooks. Contact CE Canvas to discuss.
Export, import and versions
Import/Export on the Playbook settings page downloads the current Playbook as a JSON file (a backup, or the file you hand to CE Canvas when a revision is being prepared) and imports one. Importing a file whose name matches your current Playbook offers Replace the current playbook: the current version is archived, projects already set up from it keep their steps and tasks, and new projects use the imported version. Without that option an import must use a different name and becomes a second Playbook, offered alongside the first when a project is set up.
An import goes live all at once, or not at all: until every step, project type, activity and task is in, projects keep using the current version, and a failed import leaves it untouched. The dialog stays open on what was imported, so you can check the counts against the file before setting up a project.
Approval gates. A step can end with a gate: the milestone its approvals lead to, such as Plan approved or Council direction. A gate is dated a set number of days from an engagement window or the Decision Date, and tasks can be timed from it. On a project the gate follows its window until someone moves it on the Timeline; from then on the date is theirs, and the tasks timed from it follow the gate. Gates are set in the file, as gate on a step (key, label, relative_to, offset_days); ask CE Canvas to add them to your Playbook.
What each project type is for. A project type can declare the needs it serves (Light, Standard, Major) and the project stage it belongs to, so Assess needs can tell apart types that share a participation level: a two-phase Medium need and a High need type, or a rezoning and a development application. It can also set its own suggested advance notice and response period, which Assess needs then shows in place of the CE Canvas defaults. Set these on the project type’s Details tab, or in the file as need_levels, stage_key with stage_label, notice_days and response_days. All are optional; a type that declares nothing is treated as suitable for any need and stage.
A play that covers the practice itself. Some work is too small for a plan, results and a report: a single notice, say. Tick This type covers the CE Canvas steps itself on the project type’s Details tab (or set covers_practice in the file) and projects of that type get only the Context and Assess tasks beside the play’s own.
Worth a second look. An import never fails over a level, but it flags a project type levelled Inform whose required activities ask people for input, such as a feedback form. If people can influence the outcome, level it Consult. If the input is a service, such as an enquiries line, Inform stands.
Sample files. sample-playbook.json is a complete playbook in the import format: three plays (a communications update, a standard one-phase engagement and a major two-phase engagement) with phases, step roles, methods and 60 task templates, each timed to a window and, where it has one, naming the CE Canvas screen it opens. sample-intake-form.json is a request form file with two sections of your own questions. Both are walked through in Three Worked Examples.
After applying
- Tasks are scheduled relative to your milestones, so moving a milestone on the Timeline moves the work that hangs off it
- Review the generated set within the first week: delete what doesn’t apply, add what’s missing, assign owners
- Re-open setup from Review on Project Home to check or change the configuration
- Re-applying with new dates re-schedules the generated tasks to match the moved milestones — except tasks whose dates you’ve edited yourself, which keep your dates. Nothing is ever duplicated.
Removing a Playbook
Changed your mind, or applied to the wrong project? Remove on the Playbook card takes out what the Playbook added — and tells you exactly what that means before it happens.
Removal deletes the untouched generated tasks and the milestones the Playbook created — its engagement window milestones and the Decision Date — in one atomic step. Everything you’ve invested in stays:
- tasks you’ve edited, started, or completed
- the project’s steps and any engagement phases you built yourself on the Canvas, with their windows (and anything linked to them)
- the activities on the Canvas and in Delivery
- any milestones you or EVA added
You can re-apply the Playbook later without creating duplicates.
Selecting No Playbook in Project Settings asks the same question — remove playbook items, or unlink only (keep everything, just detach the Playbook association).
Next steps
- Delivery — where the generated steps and activities are prepared
- Tasks — triage and assign the generated tasks
- Project Team — add the people the work belongs to