Project initiation

How to Write a Project Charter

Learn how to draft a project charter that defines purpose, success criteria, boundaries, and decision ownership before planning starts.

How this page is maintained

Written for learners, checked against the sources below, and reviewed every year. Last reviewed July 22, 2026.

Short answer

A project charter is a short agreement that explains why the project exists, what success looks like, and who can make key decisions. Keep it clear enough that a new stakeholder can read it and understand scope in one pass.

  • State business outcome and measurable success criteria in plain language.
  • Define what is in scope and out of scope to avoid rework later.
  • Name a single project sponsor and project manager for decision clarity.

What a charter must include

A strong charter includes problem statement, objective, success metrics, high-level scope, assumptions, and constraints. It also lists primary stakeholders and decision owners.

Do not treat the charter as a long technical plan. It should set direction and guardrails so detailed planning can proceed with fewer disputes.

  • Business need and target outcome
  • Scope boundaries and known constraints
  • Named sponsor and project manager

How to align people quickly

Share the draft charter in a short review meeting. Ask each stakeholder to confirm success metrics and scope boundaries, not word choice.

Capture unresolved questions in a parking lot and assign owners. Unclear ownership at charter stage usually becomes delay during execution.

Charter for Harbor Health patient portal launch

A hospital group wants a patient portal that supports appointment booking, lab result viewing, and secure messaging in six months.

  1. Define objective: reduce appointment call volume by 30 percent within one quarter of launch.
  2. Set scope: include booking, lab results, and messaging; exclude billing and insurance claims in phase one.
  3. Assign sponsor as COO and project manager as Digital PM lead, then document approval rights.
  4. Record constraints: fixed launch date tied to fiscal planning window.
Result: The team starts planning with a shared definition of success and fewer scope debates.

Common mistakes

  • Using vague goals such as improve experience without measurable targets.
  • Skipping out-of-scope items and assuming everyone interprets scope the same way.
  • Naming multiple final approvers for the same decision category.
  • Treating the charter as optional once scheduling begins.

Try one

What is the main reason to list out-of-scope items in a charter?

It prevents hidden expectations from being treated as committed deliverables later.

Sources

Learn this with a tutor

Tell LearnLive what you already know and what you need to do with project charter.

Build this course