The Project Charter, Explained: One Page That Gets Everyone Pointed the Same Way
If you have ever joined a project where three people held three different ideas of what it was for, you already understand why a charter exists. A project charter is a short document — often a single page — that formally authorizes the project, names the person responsible, and states in plain language what the project will and won't do. It is the first artifact of a project, written before the detailed plan, and its job is to get everyone pointed in the same direction before anyone spends real money.
In early 2021, with teams split across home offices and timelines wobbling under supply delays, that shared starting point mattered more than usual. When people couldn't lean over a desk to ask "wait, what are we actually doing?", the charter became the answer they could all read.
What goes in a charter
A charter is deliberately brief. It captures the decisions that frame everything else, not the details that come later in planning. A useful one covers:
Purpose and business case — why this project, why now, and the problem it solves
Objectives and success measures — what "done well" looks like, stated so you could measure it
Scope boundaries — a short list of what is in, and just as importantly, what is out
Key deliverables and a high-level milestone or two
The sponsor and the project manager, with the manager's authority stated explicitly
Major stakeholders, assumptions, constraints and the biggest known risks
A rough budget range and timeline — order of magnitude, not a detailed estimate
Why it aligns people
The charter aligns a team because writing it forces the hard conversations to happen early, while they are cheap. Three moves do most of the work.
Name what's out of scope. Scope creep usually starts as a reasonable-sounding request. A charter that lists exclusions gives you a calm reference point: "that's worth doing, but it isn't in this project."
State the project manager's authority. A charter that says who can make decisions, commit resources and resolve disputes prevents the slow stall where everyone waits for someone else to act.
Get the sponsor to sign. The sponsor's signature is the point. It turns a wish into an authorized commitment of money and people, and signals to the organization that this work is real.
A charter is not a contract and not a plan; it doesn't lock you into a schedule or a design. It is the agreement on intent that everything else hangs from. Keep it to a page or two, write it in language a new team member could read in five minutes, and revisit it if the purpose genuinely changes. When a disagreement flares three months in, the team that has a clear charter settles it by re-reading; the team without one re-argues it from scratch.
If you are standing up a project and want it framed clearly from day one, XNM's program & project delivery advisory helps you write a charter that genuinely aligns sponsors, stakeholders and the delivery team.