How to Write a Project Charter: Template and Examples
A project charter gives busy stakeholders a shared starting point. Instead of forcing everyone to absorb requirements, risks and schedules in full, it distils the decision that matters most: why this work is being done, what it will deliver, and what could affect it. This guide explains how to build that document, what to include, and how a worked website-redesign example shows each part in practice.
What a charter does
A charter is a concise authorising document. It records the project's purpose and expected benefits alongside its goals, constraints, risks, stakeholders and budget. The Project Management Institute describes it as a document issued by the initiator or sponsor that formally authorises the project and gives the project manager authority to use organisational resources. It may also be called a project brief or project definition document.
Its practical value is alignment. When goals and boundaries are written down early, stakeholders can see whether they agree on the outcome, and the team has a reference point for later choices. That clarity supports delivery that is on time and within budget, because misunderstandings about purpose or scope are surfaced before detailed work begins.
Charter or plan: use each for its own job
The charter answers what and why. It explains the reason for the project and the outcome sought, at a level that can be understood without reading every task. It is usually produced early, often as a short Word, Excel, Google Docs or PDF document.
The plan answers how, when and who. It turns the approved direction into a line-by-line sequence of work, with deadlines, owners and milestones, commonly shown on a timeline such as a Gantt chart. If the charter changes materially, the plan should be revisited; if only task sequencing changes, the charter usually does not need rewriting.
A practical way to draft one
Begin with a conversation, not a blank document. Ask the team and stakeholders about goals, constraints such as deadlines and budgets, risks, stakeholders, and any other detail needed to define the work. That discussion both gathers facts and sets expectations about the effort required.
Then write for a reader who has only a few minutes. Keep the charter at a high level, use short descriptions or bullet points, and avoid a step-by-step account of delivery. There is no single required format, but readability matters more than length: anyone involved should be able to find the purpose, scope, cost, timing and decision-makers quickly.
Use this checklist before circulating a draft:
- Can a new stakeholder state the purpose in one sentence?
- Are goals specific enough to judge success?
- Are scope inclusions and exclusions explicit?
- Are budget, timeline and key milestones visible?
- Are risks, dependencies and owners named?
- Is the sponsor or main approver identified?
Sections to include, illustrated with a website redesign
Business case: state why the project is being undertaken. In the website-redesign example, the case is that the museum site must be redesigned to support aggressive ticket-sales goals and to give visitors who cannot attend in person a new online shop experience. This statement guides later decisions and creates shared accountability.
Goals: move from the broad case to measurable outcomes. The example includes a refreshed look aligned with new branding, visitor information that is easy to find, an online ticketing system expected to add 20% in ticketing revenue, and an off-the-shelf e-commerce platform expected to add 35% in shop revenue and managed by shop staff. SMART goals make this kind of outcome easier to track.
Budget: show the total and its breakdown. The example totals $500,000, split as research $50,000, design $200,000 and development $250,000. Transparency here helps when spending approaches the limit.
Scope and deliverables: name what will be built and what will not. The example lists a home page, ticketing page, shop home page and shop item-description page, with wireframes, page designs and coded templates as deliverables, each design stage allowing up to three revisions.
Resources needed: list people, money, time, materials, equipment and external inputs. The example notes branding files from a partner agency before design kickoff, placeholder photography with possible new photography, font licences, CMS licences, a CMS trainer and content-entry staff.
Timeline: include only key milestones and dates, not the full plan. The example estimates nine months, from an October 31, 2021 kickoff through research, design, development and CMS training, content entry, and QA testing and launch on June 30, 2022.
Risks and issues: name plausible problems early. The example flags a stakeholder team new to website redesign, unknown effort to rewrite most content, and unapproved funding for the e-commerce platform.
Dependencies: show where one party's delay affects another. The example warns that late branding approval would delay the project and that CMS selection and licensing must happen before development begins.
Stakeholders: list approvers and define the lead. The example names a project sponsor and key contact, plus people responsible for IT, ticketing, the museum shop and writing.
From charter to plan
A template helps you start quickly and keep the document brief enough to scan. Adapt the headings to your organisation rather than copying every section: a small internal project may not need a detailed budget breakdown, while a client project usually does. Once the charter is agreed, use it as the basis for the detailed plan, and keep the two documents consistent as dates, costs or scope change.
| Question | Project charter | Project plan |
|---|---|---|
| Main question | What is being done and why? | How, when and by whom? |
| Level of detail | High-level purpose, scope, cost, risks and stakeholders | Tasks, owners, deadlines and milestones |
| Typical timing | Early, before detailed planning | After the direction is approved |
| Example content | Goal: add online ticketing; risk: funding not yet approved | Task sequence from research to launch with dated milestones |
Both documents are normally used; the charter is approved first and the plan details delivery.
Frequently asked questions
What is a project charter?
It is a short, high-level document that records why a project exists, what success looks like, and the main constraints, risks, resources, timeline and decision-makers involved. It is meant to be read quickly by people who will not work through a detailed plan.
How is a charter different from a project plan?
Use the charter for the what and why: purpose, goals, scope, budget, stakeholders and major risks. Use the plan for the how, when and who: sequenced tasks, owners, deadlines and milestones. Most projects need both, with the charter approved first.
Where should I start when writing one?
Start by talking with the team and stakeholders about goals, constraints, risks and stakeholders. Then draft each section in plain, brief language, check it against the discussion, and get the sponsor or key approvers aligned before detailed planning begins.