Project Context
Project Context is where you establish the decision frame before designing any engagement. It answers the questions every later surface depends on: what kind of project is this, what decision is being made, what is genuinely open to influence, and what is already fixed.
This is Steps 1–3 of the engagement sequence. The quality of what you capture here directly determines how useful the Canvas, the Engagement Plan, and EVA’s suggestions are downstream — a specific context produces specific guidance; a vague one produces plausible-sounding filler.
If you skip this: engagement gets designed around assumptions instead of the actual decision. Constraints surface mid-engagement, communities discover the thing they came to influence was never open, and trust is spent that took years to build.
What kind of project this is — concluded here, not asked first
Whether a project is engagement (people can influence a decision) or communications-led (the decision is settled and people need to understand it) is a conclusion Project Context reaches, not a question it asks at the door. The answer lives in two of its own fields — what decisions can stakeholders affect? and what is genuinely open to influence? — so Context draws it from them and shows it in the Project approach block at the end of the page.
- Say whether something is open, nothing is open to influence (with a short reason — the scope is fixed, there is no decision to make), or not sure yet. Blank and not sure are different things; a request can suggest an approach but never settles it.
- Confirm approach records it on the project and puts the canvas in the matching mode. If engagement is required, or the request asked for people’s input, yet nothing is recorded as open, Context asks you to resolve that before confirming — it never routes a project to communications silently.
- If the decision, who decides or what is open changes later, the block shows Needs review until you re-confirm. Nothing is cleared.
- A communications-led project keeps the shared facts here — what is happening, what has been decided, who decided it — so the classification can always be checked against them.
Why the order matters: calling a communications project an “engagement” invites the community to influence a decision that is already made. Deciding that before reading the brief is how it goes wrong; deciding it from the brief’s own answers is how it stays honest.
The Project Context workspace
Project Context opens as a workspace.
Getting started (right-hand rail) — three ways to give EVA something to work from: Upload materials, Discover with EVA (researches your organization’s public web presence), and Extract context with EVA (reads uploaded materials and drafts context fields). Put the note away once you’re moving; the actions stay, and Show brings the note back.
Before you start — the opening screen sets out what the step covers: the seven questions you’ll be asked (choose What will I be asked? to read them in full), what to have ready, and who to have in the room. Answer these with the project lead and the engagement lead together — the project lead knows what is fixed and who signs off, the engagement lead knows what participants will ask. Answers made without both tend to be revised later.
About this project — one line from the project description, for orientation. Edit changes it in place, with Draft with EVA support. Whether people can shape a decision is not asked here; the Project approach block at the end of the page concludes it.
Engagement Context — the decision-frame fields, confirmed one by one:
- The actions or decisions stakeholders can affect
- What is genuinely open to community influence
- What’s fixed and non-negotiable
- Decision-making authority
- Constraints and realities
- Key dates and project stages
- Additional context
An optional Risks & Sensitivities field captures historical context, equity gaps, or community trauma the strategy needs to navigate — surface it when it applies.
Each field shows its status: Needs input, Partial when something is written but the step’s own judgment says it could say more (Add detail opens it), or confirmed. The progress panel and the Planning hub’s Project Context pill count only confirmed fields, so a Partial answer never reads as ready; you can still continue with one outstanding. the Sources used panel lists which uploaded materials EVA is drawing from.
Guidance while you answer — each question carries a Practice note at the top of the step explaining why the decision frame matters, and a Guidance note beneath the field with a worked example, why the question is asked, and the trap people fall into. Choose Read more to expand either, or Got it to fold it to a single line once you know it — it is remembered for you across projects and devices, and View brings it back.
In guided setup, use Bold, Italic, Bullet List, and Numbered List to format longer answers. Put separate constraints or considerations on separate lines. Formatting is retained when you save, reopen, review earlier answers, and export to PDF or Word.
EVA follows your organization’s language setting for English spelling and prose dates: for example, September 7, 2026 for US English and 7 September 2026 for UK/Australian English. Your personal language is used when the organization has no setting or you work in another language. Defined source names and terminology retain their original wording.
When the context is in good shape, the completion card offers an Export menu — download the Project Context as a branded PDF or Word document to share outside CE Canvas.
Recommended workflow
- Upload project materials first if documents exist — project briefs, council reports, prior engagement findings, policies, stakeholder research. Go to Project Materials in the sidebar, or use Upload materials in the rail. EVA processes each document in the background.
- Extract context with EVA — EVA reads the processed materials and drafts each context field with sources attached. You review, edit, and confirm; you’re editing rather than writing from scratch.
- Confirm field by field — guided setup steps through each field. Accept the draft, edit it, write your own, or skip and return later. If you’ve asked EVA for a draft on the current field, apply or discard it before moving on — Save and next waits until you decide.
- Continue to the Canvas once the foundations hold — the brief doesn’t need to be complete, but the decision space and what’s-open/what’s-fixed fields should be honest before you design anything.
Historical materials
A plan or report from a previous engagement or project is still worth knowing: what happened, what was learned, what was promised, who was missed. But it describes what happened before, not what this project should do now, and its objectives, stakeholders and dates should not be drafted in as if they were this project’s.
Each project material has a Treat as setting with two values:
- Current — the default. EVA treats the material as evidence about this project, however old the document is.
- Historical — from a previous engagement or project. EVA reads it as what happened before: it draws on the lessons, commitments and gaps, and does not carry the earlier objectives, stakeholder list, promise, methods or dates into your Context, Canvas or document drafts. Ask EVA what happened last time and it answers from these files, saying the work was earlier.
Set it in the Treat as field when you upload, or later from a file’s More actions menu with Mark as historical. When you add a file, EVA reads its opening and compares it with your project. When the file clearly comes from a previous engagement or a different project, CE Canvas asks on the file’s row and names what it thinks the file is — for example, Looks like the 2019 engagement plan for the Foreshore upgrade. Treat as historical? Choose Treat as historical or It’s current. It only asks when the signs are clear, and it never changes the setting for you. Choosing It’s current tells EVA the file is this project’s, whatever its date.
Historical files are gathered in a Historical group at the end of the project’s materials, so you can see at a glance what EVA reads as what happened before. Your project’s own plan and outcomes report always count as current.
Finished work can still be current. Findings from an earlier phase of this project, and policies, strategies or studies that still apply, stay Current — EVA uses them as evidence, and does not repeat objectives a phase has already met.
Practitioner’s rule: if you can’t write one sentence for “what is genuinely open to community influence”, you are not ready to choose engagement methods. That sentence is the anchor for everything in the Canvas.
Re-entering and maintaining context
Context is not a form you fill once. Return to it when:
- A decision is made mid-project that changes what’s open to influence — update the field and tell the community if the change affects what they were told
- New materials arrive — upload them and re-run extraction; EVA updates its suggestions
- The project’s nature changes — the Project approach block shows Needs review when the decision, who decides or what is open changes; re-confirm it (an engagement project that loses its decision space should become communications-led, honestly)
Good practice
- Mark plans and reports from previous engagements or projects as Historical, so EVA learns from them without repeating them
- Upload materials before drafting — EVA’s extraction with sources beats memory-based entry, and every claim stays traceable
- Write the fixed and non-negotiable field as if the community will read it — one day they might
- Keep Key dates and project stages current. It records the project’s own stages and fixed dates — design, approvals, the decision — not its engagement phases, which you design on the Engagement Canvas. EVA reads it when it drafts your timing
- Revisit context whenever the project moves to a new stage
Next steps
- Engagement Canvas — turn the decision frame into an engagement strategy
- Engagement Planning — the Planning hub showing all three planning surfaces
- Responsible Use of AI — how EVA’s drafting and extraction work