Develop a common vision
In the app: Project → Charter · Project → Team → Charter
PMP ECO · People (33%) · Task P1. Create a shared, compelling picture of why the project exists and what "done" looks like — and get the team and stakeholders behind it.
What it is
A vision is the north star: a concise statement of the project's purpose, the outcome it delivers, and the criteria by which success will be judged. In PMBOK® 8e it lives in two artefacts — the project charter (purpose, measurable objectives, success criteria, high-level scope) and the team charter (the shared values and ways of working the team commits to). Vision is not a slogan; it is the reference the project manager returns to whenever priorities compete.
Why it matters
- Alignment. Every later decision — scope trade-offs, risk responses, change requests — cascades from the vision. Without it, each stakeholder optimises for their own goal.
- Motivation. Teams commit to purpose, not tasks. A clear "why" sustains effort through the hard middle of a project.
- Authority. The charter formally authorises the project and the PM. It is the document you point to when someone tries to bolt on unfunded scope.
Where you do it in VanillaPM
Open the project's Charter and complete the purpose / objective and success criteria sections, then the Team → Charter tab for the team's values and working agreements. Both are governed documents — versioned, and the source that later plans inherit from.
Free downloads: Project charter template (Word, Markdown) · Assumption log template (Excel, CSV).
Walked example — Coral Ridge Resort
The Coral Ridge charter states the vision plainly:
"Design and build Coral Ridge Resort — a 10-storey, 220-key five-star hotel on the Cox's Bazar coast, with sea-facing rooms over the beach and hill-facing rooms over the ridge — delivered to brand standard, on budget, and opening in time for the winter tourist season."
That single sentence encodes the measurable success criteria the team returns to: Corvane brand standard, a $48M budget with reserves, and an opening before winter 2028. The team charter adds the values a coastal five-star build demands — safety-first (piling and high-rise work over a storm-exposed site), quality to five-star finish, and community respect (beach access is a live issue).
The artefact — the nine sections, one at a time
PMBOK® 8e asks a charter to carry nine required sections, plus two optional ones worth writing anyway. Below is each one: what belongs in it, the theory behind it where there is one, what the real Coral Ridge charter put there, and the mistake to avoid.
Every screenshot is the actual sample project — not a mock-up. Run
python manage.py seed_tutorial and you can open these yourself.
1 · Purpose & justification
What goes here. Why this project exists — the business problem or opportunity, and the rationale for spending money on it. Not what you'll build; why anyone should care.
The theory: it inherits from the business case. The charter doesn't invent the justification — it cites one. The business case (prepared before the project) carries the options considered, the cost–benefit analysis, and the payback. The charter summarises its conclusion. This is why "purpose" is section 1: everything downstream is justified by it.

Reading the screenshot: notice it leads with the investment logic — "investing in a 220-key five-star resort… to capture rising demand for premium coastal tourism" — then names the operator and the room mix. An investor could read this paragraph alone and understand the bet.
✅ Do state the problem or opportunity in business terms, and name the expected benefit.
❌ Avoid writing purpose before a business case exists. You'll invent the justification,
and every downstream decision inherits the invention.
2 · Measurable objectives
What goes here. What "done" looks like, stated so that someone who wasn't in the room can verify it.
The theory: SMART. The section is called measurable for a reason.
| The question it forces | ||
|---|---|---|
| S | Specific | What exactly, where, how much? Could a stranger picture it? |
| M | Measurable | Is there a number or a testable standard? Who checks, against what? |
| A | Achievable | Possible with the resources and constraints you actually have |
| R | Relevant | Does it trace back to the business case? |
| T | Time-bound | A date. Not "soon", not a season |
An objective failing any one of these can't be verified — and what you can't verify, you can't deliver, because nobody can agree when you're finished.

Reading the screenshot — and this one isn't perfect. Score it yourself:
| Verdict | Why | |
|---|---|---|
| S | ✅ | 10-storey, 220-key, five-star, Cox's Bazar, sea/hill orientation |
| M | ⚠️ | "220-key" is measurable. "To brand standard" and "on budget" are not — whose standard, which budget? |
| A | ⚠️ | Not addressed here; achievability lives in the constraints (section 11) |
| R | ✅ | Traces to the purpose above |
| T | ❌ | "The winter tourist season" is not a date. The baseline says 31 August 2028 |
Sharpened:
"…to the Corvane commissioning standard, within the sanctioned $48M budget plus approved reserves, achieving practical completion by 31 August 2028 so the hotel opens before the 2028–29 winter season."
"Open before winter" can be argued about in December. "By 31 August 2028" cannot.
✅ Do read each objective back and ask "who checks this, and what do they measure?"
❌ Avoid adjectives doing the work of numbers — "high-quality", "world-class", "on budget".
3 · High-level requirements
What goes here. The conditions the result must satisfy — at charter altitude. Boundaries, not a backlog.
The theory: requirements ≠ scope. Requirements are what the product must do or be; scope is the work needed to deliver them. The charter holds requirements; the WBS holds scope. Prioritisation (MoSCoW — Must / Should / Could / Won't) belongs later, in the requirements documentation — but the "Won't" conversation starts here, in section 10.

Reading the screenshot: four bullets, each a constraint on the result — key count and stacking, the Corvane operating standard, regulatory compliance (building code, ECA clearance, fire and life safety), and salt-air-resistant construction. That last one is a genuine coastal-build requirement that drives material choices for the whole project.
✅ Do keep each bullet testable, and include regulatory requirements — they're
non-negotiable and shape the schedule.
❌ Avoid decomposing into tasks. If a line starts with a verb like "build" or "install",
it's scope, and it belongs in the WBS.
4 · High-level risks & opportunities
What goes here. The handful of uncertainties that could materially change the outcome — in either direction.
The theory, and an 8e change worth knowing. A risk is a future, uncertain event; an issue is one that has already happened. Risks are scored probability × impact, which is why they carry a number. And PMBOK treats opportunities as risks too — uncertainty with an upside. Most charters list only threats, which quietly trains a team to see risk as bad news only.

Reading the screenshot: five entries with scores — cyclone/storm-surge damage (15), ECA clearance delay (12), imported facade and lifts stuck at customs (12), monsoon overrun (12) — and then the one most charters omit: "early-open in peak tourist season boosts ADR" (12), an opportunity. Same register, same scoring, deliberately pursued rather than merely avoided.
✅ Do include at least one opportunity. If you can't name one, you probably haven't
looked.
❌ Avoid listing twenty risks. This is the high-level section — the ones that could
stop or transform the project. The full register comes later.
5 · Summary milestone schedule
What goes here. The externally-binding dates. The ones that cost money or reputation if missed.
The theory: a milestone has zero duration. It's a moment, not a piece of work — "clearance granted", "structure complete", "commissioning signed off". If it takes three weeks, it's an activity, not a milestone. And at charter stage you're doing rolling-wave planning: near-term detail, far-term summary. The charter holds the summary.

Reading the screenshot — and here's a weakness to learn from. It shows start, planned finish, and the baseline start/finish (2026-02-01 → 2028-08-31). The baseline distinction matters enormously — it's what makes "are we late?" a measurable question. But as a milestone list this is thin: it gives the envelope, not the gates. A stronger version would name the four or five moments the project actually turns on — ECA clearance, structure complete, operator commissioning, opening.
✅ Do list the dates that bind you to someone outside the project.
❌ Avoid copying the project plan in here. Hundreds of dates belong in the schedule; four
belong in the charter.
6 · Pre-approved financial resources
What goes here. How much money is authorised, and what's held back.
The theory — this is a favourite exam topic. Three distinct pots:
| What it covers | Who releases it | |
|---|---|---|
| Budget / cost baseline | The planned work | The PM, against the baseline |
| Contingency reserve | Known unknowns — identified risks that may occur | The PM, within the baseline |
| Management reserve | Unknown unknowns — what nobody foresaw | The sponsor, outside the baseline |
Contingency sits inside the cost baseline; management reserve sits outside it. Mixing them up is how a project quietly spends its last safety margin without anyone noticing.

Reading the screenshot: $48,000,000 planned, $2,400,000 contingency (5%),
$1,200,000 management reserve (2.5%). Three separate lines — which is the point. A single
"$51.6M budget" would hide the fact that two of those pots have different owners and
different release rules.
✅ Do write the figure, and separate the reserves. Percentages are a starting point, not
a rule.
❌ Avoid a budget agreed only in conversation. If it isn't written, it wasn't agreed —
and memories diverge in proportion to the money involved.
7 · Key stakeholder list
What goes here. Who matters, and how much — early, before anyone is surprised.
The theory: the Power/Interest grid. Usually credited to Mendelow, it plots each stakeholder on influence (can they affect the outcome?) against interest (do they care?), giving four strategies:
| Low interest | High interest | |
|---|---|---|
| High influence | Keep satisfied | Manage closely |
| Low influence | Monitor | Keep informed |

Reading the screenshot: every entry carries influence and interest out of 5 — that's the grid, as data. The sponsor sits at 5/5 (manage closely). The municipality is 5/3 — high influence, moderate interest — the classic keep satisfied quadrant, and exactly the party that can stop a build with a permit. Corvane at 5/4 shapes the standard the whole project is measured against.
✅ Do record influence and interest separately. The quadrant tells you how often to
communicate and in what depth.
❌ Avoid confusing a loud stakeholder with a powerful one. Interest is not influence —
and the quiet regulator at 5/2 will matter more than the vocal enthusiast at 2/5.
8 · Project manager assignment & authority
What goes here. Who the PM is and — the part everyone skips — what they may decide alone.
The theory: authority comes from structure, and must be written. In a functional organisation the PM has little formal authority; in a projectised one they have most; a matrix sits between, which is where most of us work and why the limits must be explicit. Responsibility without authority is the most common structural failure in project management — and the charter is the only document that can fix it.

Reading the screenshot: the PMs are named, then four explicit limits — change approval,
schedule movement, supplier commitment, and an escalation path with a response time. The
[bracketed] figures are deliberately blank: VanillaPM can autopopulate who the PM is, but
it cannot know what they're allowed to approve. That's the sponsor's decision, and the
blank exists to force the conversation.
Compare the version most charters ship with:
"The project manager has authority to manage the project and its resources."
That's the governance equivalent of a permissions file that says "the user can do user things." It settles nothing, so every decision escalates by default.
✅ Do write thresholds as numbers. If the sponsor won't commit to one, that's useful
information — in week two rather than month three.
❌ Avoid "has authority to…" phrasing. It reads as complete, which is why nobody ever
goes back and fills it in.
9 · Sponsor authorisation
What goes here. The named person who accepts accountability and formally starts the project.
The theory: authorisation is an act, not a field. A charter becomes authoritative by being approved, and the approval must attach to a specific version. Otherwise a later edit silently inherits the sponsor's sign-off — which is how a document people trusted stops deserving it.

Reading the screenshot: it names the sponsor, then says the authorisation is "recorded
through the governed approval workflow". In VanillaPM the charter is a governed document:
draft → submit → an ordered chain of approvers each record a decision, with state
(pending → approved / rejected) bound to the version approved. Change the charter
materially and it goes round again.
A signature on a document that can be edited afterwards isn't an authorisation; it's a formality.
✅ Do name an individual. Accountability doesn't divide — a committee cannot be
accountable.
❌ Avoid treating sign-off as a one-off. Re-approve at phase gates; a two-year project's
context moves underneath its charter.
The two optional sections (write them anyway)
10 · Out of scope. The approval gate doesn't demand it. Write it regardless — what you exclude is what gets argued about later.

Coral Ridge excludes post-handover hotel operations, off-site infrastructure beyond the plot boundary, guest-experience programming, and any phase-2 wing. Each of those is something a stakeholder could reasonably have assumed was included — which is precisely why it's listed.
11 · Assumptions & constraints. An assumption is something you're treating as true without proof; a constraint is a limit you cannot move. Assumptions are risks wearing a disguise — when one proves false, it becomes an issue.

Note they're tagged. "Piling reaches competent strata by −22 m" is an assumption — if the boreholes disagree, the foundation design and budget both move. "ECA clearance granted before superstructure" is a constraint — it isn't negotiable, it's a gate.
Five ways charters fail in practice
- Vague objectives. "A great hotel" can't be verified, so it can't be delivered. Numbers and dates, always.
- No authority written down. Every small decision escalates, and the project crawls while people wait for you to wait for someone else.
- Budget by conversation. If it isn't written, it wasn't agreed — and memories diverge in direct proportion to how much money is involved.
- Written once, never reopened. A charter not re-read at phase gates is decoration. On a two-year build the context shifts underneath it.
- Skipping the inputs. Writing purpose before a business case exists means inventing the justification, and everything downstream inherits the invention.
Four of those five are failures of specificity, not of effort. The charters were written. They just weren't written to be used.
On the PMP exam
Vision sits in the People domain and leans on servant leadership. Expect situational questions where a team is drifting or stakeholders pull in different directions — the best answer usually re-anchors everyone on the charter's purpose and success criteria rather than adding process. Remember the charter is what authorises the PM and the project.