How to Write a Project Charter (Template + Example)

A project that starts without a charter often looks fine for a week or two. Then the arguments begin: Who is in charge? What budget was approved? Why is the team building something the sponsor never asked for? Without a short, signed authorization document, every later decision becomes a negotiation from memory.

A project charter is that document. It is not a full plan. It is the short agreement that says the project exists, who owns it, why it matters, and what success roughly looks like before detailed planning starts. This guide covers what to include, how to write one, a copy-ready template, a filled illustrative example, and how to turn the charter into a schedule.

What is a project charter?

A project charter is a formal authorization for a project. It names the sponsor, appoints the project manager (or lead), states the objective, and sets high-level boundaries for time, money, and outcomes. Once approved, the project is officially on and the team has a shared reference for why the work started.

It is different from a project scope statement. The charter authorizes the project and sets direction at a high level. The scope statement comes next and details what will and will not be delivered, plus acceptance criteria. On small jobs the two can live in one file. What matters is that authorization and boundaries are written down before the team starts spending time and money.

When you need a project charter

You need a charter whenever more than one person will decide, pay for, or be affected by the work.

• Construction and field work: a new phase, temporary site setup, or client-funded change that needs clear ownership before crews mobilize.
• Healthcare operations: a process change that touches multiple units or vendors — for example a new intake workflow.
• Small business projects: an office upgrade, product launch, or system change with a budget, a deadline, and more than one decision-maker.
• Cross-team work: anything where two departments, two trades, or a client and a contractor must agree on purpose and authority first.

If the work is one person's routine task with no shared budget, skip the charter. If people will later disagree about whether the project was approved, write one.

What to include in a project charter

Keep it short. A useful charter usually covers:

1. Project name and date — so everyone refers to the same initiative.
2. Business need / problem — why this project exists now.
3. Objective — one or two outcome-focused sentences.
4. High-level deliverables — the main results, not every task.
5. Sponsor and project manager — who authorizes and who runs day-to-day work.
6. Key stakeholders — people or groups who must be informed or consulted.
7. High-level timeline — target start, major checkpoints, and target end.
8. Budget summary — approved or requested funding, and who controls spend.
9. High-level risks and assumptions — the few items that could stop the project early.
10. Success criteria — how the sponsor will decide the project achieved its purpose.
11. Authority and approval — what the project manager can decide alone, and who signs.

How to write a project charter step by step

1. Clarify the need with the sponsor

Ask what problem triggered the project, and what happens if you do nothing. Vague needs like "improve operations" become fights later; specific needs like "reduce morning check-in wait times before peak winter volume" give the team a target.

2. Draft a one-sentence objective

Name the outcome and, where possible, a date or constraint. "Complete Phase 1 site mobilization so foundations can start by the agreed date" is usable; "Get the site ready" is not.

3. List high-level deliverables only

Stay at results the sponsor cares about: temporary facilities installed, staff trained, office network live. Detailed work packages belong in the WBS and schedule later.

4. Name roles and authority

Write who the sponsor is, who the project manager is, and what the project manager can approve alone — for example purchases under a set amount. Unclear authority stalls projects fast.

5. Capture time, money, and the biggest risks

Record the target dates, the budget figure (even if approximate), and the two or three risks that would kill or reshape the project. You do not need a full risk register yet — just enough honesty that the sponsor authorizes with eyes open.

6. Define success criteria and get a signature

Success criteria answer "how will we know this worked?" Keep them observable: site ready for foundation start, new process live, office move complete. Then walk the draft past the sponsor and the people doing the work, record who approved it and when, and store the signed version where the team can find it.

Project charter template (copy-ready)

Copy these fields into a document and fill them in:

• Project name:
• Date / version:
• Business need:
• Objective:
• High-level deliverables:
• Sponsor:
• Project manager:
• Key stakeholders:
• Target start / end:
• Major checkpoints:
• Budget summary and spending authority:
• Key assumptions:
• High-level risks:
• Success criteria:
• Authority of the project manager:
• Approvals (name, role, signature/date):

Filled example: clinic intake process change

This is an illustrative example, not a real case. A small outpatient clinic wants to redesign weekday patient intake before winter volume rises.

• Project name: Weekday Intake Redesign
• Date / version: 7 November 2026, v1.0
• Business need: Peak morning check-in queues are delaying first appointments and stressing front-desk staff.
• Objective: Put a redesigned weekday intake process live by 15 January 2027 so morning wait times fall without adding headcount.
• High-level deliverables: mapped current and new intake steps; updated scripts/checklists; staff training; go-live; two-week post-go-live review.
• Sponsor: Clinic operations director
• Project manager: Front-office supervisor
• Key stakeholders: Front-desk team, nursing lead, IT support, patient communications lead
• Target start / end: 17 November 2026 – 31 January 2027
• Major checkpoints: current-state map approved; new process signed off; training complete; go-live; two-week review
• Budget summary: Within existing operations budget for overtime training and minor print/signage; PM may approve training overtime up to the agreed cap
• Key assumptions: Scheduling screens already support the needed fields; no new software purchase required
• High-level risks: Staff resistance if new steps feel slower at first; IT delay on screen changes; absences during training week
• Success criteria: New process used for all weekday morning check-ins; training attendance recorded; two-week review done with follow-up actions assigned
• Approvals: Operations director (sponsor); front-office supervisor (project manager)

After the charter is signed, the team would write a detailed scope statement, then build the schedule from the deliverables.

Common project charter mistakes

• Writing a plan instead of a charter. If you are listing every task, you have jumped ahead. Keep the charter high level.
• Skipping the sponsor signature. An unsigned charter does not settle later arguments about authority or budget.
• Vague objectives. "Improve the process" gives no target. Name the outcome and a date or constraint.
• No spending or decision authority. If every small purchase needs the sponsor, the project manager cannot run the work.
• Ignoring assumptions. Unstated assumptions become surprises — write the shaky ones down.
• Filing it and forgetting it. Bring the charter into kickoff, change discussions, and closeout.

Turning the charter into the plan

Once the charter is approved, use it as the seed for everything else:

1. Expand high-level deliverables into a scope statement (in-scope, out-of-scope, acceptance criteria).
2. Break deliverables into a work breakdown structure, then into tasks and subtasks.
3. Add checkpoint tasks for the major dates named in the charter — short tasks that mark approvals, go-live, or phase starts.
4. Link tasks with dependencies so work that must wait cannot be scheduled too early.
5. Move high-level risks into a risk register with owners, and track the budget against the approved figure.
6. Assign people and teams so the roles in the charter show up as real assignments.

The charter stays short on purpose; the plan gets detailed. When a change request arrives, compare it to the charter's objective and authority first, then to the scope statement.

Building the charter into a schedule with GanttMaster

GanttMaster is our iPhone and iPad project manager. After the charter is signed, turn its pieces into a living plan:

• Tasks and subtasks. Create a project from a template or from scratch, then add each high-level deliverable as a task with subtasks.
• Checkpoint tasks. Add short tasks for charter checkpoints such as "Process signed off" or "Go-live" on the Gantt timeline.
• Dependencies. Use Finish-to-Start, Start-to-Start, and Finish-to-Finish links so training cannot start before sign-off.
• Team assignment and roles. Assign tasks to users or teams, with role-based access for Project Manager, Team Manager, and User.
• Risk and budget tracking. Capture the high-level risks from the charter, and track spend against the approved budget.
• Comments and file links. Attach the signed charter as a file link on the kickoff task, and keep discussion in comments.
• Today view with reminders. Upcoming checkpoints and near-term tasks show up in the daily view.
• Progress and Stats. Project cards and the Stats screen show total, completed, and overdue tasks at a glance.

There is no per-user pricing, so you can include the sponsor, project manager, and team under one subscription. It is free to download with a 1-week trial, then $5.99 a month or $34.99 a year.

Quick project charter checklist

• Business need and objective written in plain language.
• Sponsor and project manager named, with clear decision authority.
• High-level deliverables, timeline, and budget summarized.
• Key assumptions, risks, and success criteria recorded.
• Charter reviewed with the people who will do the work.
• Sponsor approval dated and stored where the team can find it.
• Charter checkpoints turned into scheduled tasks before detailed work starts.

A clear charter will not replace good planning, but it stops the early fights that no schedule can fix. Write it short, get it signed, then build the plan on top of it.