The seven fields that matter
Purpose: the business outcome, in one sentence a non-specialist can repeat. Definition of done: the observable state that ends the project, not a feeling of completeness. Owner and sponsor: who runs it and who pays for it, one name each. Scope boundary: two or three things this project deliberately does not include. Budget and people: what it may consume before returning to the gate. Milestones: three to six dated commitments. Top risks: the two or three ways this most plausibly fails.
Anything beyond these seven earns its place only if someone will act on it. Approach essays, org charts and glossaries move to appendices or die.
What the charter is actually for
The charter is not documentation, it is a forcing function. Writing the definition of done exposes disagreements while they are still cheap: three stakeholders who would have discovered in month three that they wanted different outcomes discover it in the kickoff instead. The scope boundary gives the project owner a polite way to say no for the life of the project. And the named sponsor means that when priorities collide, there is a person, not a meeting, who resolves them.
The pattern across post-mortems is remarkably stable: projects that fail expensively usually had no written answer to what done means, and everyone involved would have answered differently.
Failure patterns and fixes
The novel: ten pages nobody reads. Fix: hard one page limit. The wish list: a definition of done that is really a backlog. Fix: one observable end state, everything else is scope for future projects. The ghost sponsor: a sponsor named for politics who never engages. Fix: the sponsor signs the gate decisions, so engagement is structural. The stale charter: reality moved, the paper did not. Fix: the charter is a living record reviewed at every gate, and changes to it are decisions, logged like any other.
Charters that write themselves and stay alive
On the PMO Desk, the charter is a structured record, not a file: seven fields, one page, attached to the project from gate one. Velora drafts it from a plain language description and flags the fields that are vague, then the charter travels with the project, updating through gate decisions instead of rotting in a folder.
The same record feeds milestone plans, risk registers and steering packs, so the thirty minutes spent chartering keeps paying for the life of the project. From the $19 Plus membership, with the rest of the workspace included.
Frequently asked questions
How long should a project charter be?
One page. The charter is a decision tool, and decision tools get read. Supporting detail can live in appendices that nobody is required to read to approve the project.
Who writes the charter?
The project owner drafts it, the sponsor approves it at the commitment gate. Writing it together in one sitting is the fastest way to surface disagreements early.
Do internal projects need charters too?
Anything that crosses a team boundary or consumes meaningful money deserves the one page. Truly small tasks do not; the charter threshold is a governance decision worth writing down once.