Your first project charter

A project charter does three things: it formally authorises the project, it appoints the project manager, and it captures the shared understanding between the sponsor and the PM before planning begins. Without it, teams regularly discover mid-project that different people had fundamentally different ideas about what was being built.

The charter is not a detailed plan. It doesn't list every task or nail down every date. It's a one-to-two-page document that answers the big questions: why are we doing this, what does success look like, who has authority, and what are the known constraints?

Because the sponsor signs the charter, it carries organisational authority. That matters when you need to push back on scope additions or escalate a resource conflict. A signed charter lets you say 'this is what was agreed' rather than relying on memory or meeting notes.

A solid project charter covers: the project purpose (the problem or opportunity being addressed), the high-level objectives (what success looks like in measurable terms), the key deliverables (the major outputs), the timeline (start date, key milestones, target completion), the budget (overall envelope or funding source), the known constraints and assumptions, the key stakeholders, and the project manager's name and authority level.

The purpose statement is the most important section. It should explain why this project exists in one or two sentences. A good purpose statement connects the project to a business outcome — not 'implement a CRM system' but 'reduce sales team admin time by 30% by replacing manual pipeline tracking with a unified CRM'.

Objectives should be specific enough to evaluate at the end of the project. 'Improve customer satisfaction' is not an objective. 'Achieve a Net Promoter Score of 45 or above within three months of go-live' is an objective. The difference matters when the project closes and someone asks whether it succeeded.

Start with a conversation, not a document. Before you open a template, sit down with the sponsor and ask: what problem are we solving, what does good look like at the end, what can't we change, and who else needs to be involved? The answers become your charter.

Keep it short. A charter that runs to ten pages is not a charter — it's a mini plan, and it will either be ignored or become outdated before planning is finished. One to two pages forces you to prioritise what actually matters.

Once drafted, walk the sponsor through it before asking for a signature. The review conversation often surfaces misalignments that are far easier to resolve at this stage than after planning has started. Use the AI document tool below to generate a charter draft based on your project — then refine it with your sponsor.

The project charter authorises the project, appoints the PM, and captures shared understanding before planning begins. It's short by design — one to two pages — and it earns its authority from the sponsor's signature. A good charter has a clear purpose statement, measurable objectives, and explicitly documented constraints.

The next lesson is a quiz that checks your understanding of everything covered in this course. After that, you'll be ready to move into the Intermediate courses where the planning tools get more sophisticated.