Project Charter: Definition, Examples & How to Write It

What is Project Charter?

What good project charter looks like

A useful charter is specific enough to prevent scope confusion but brief enough to guide decisions; it distinguishes goals from deliverables, names decision authority, and records assumptions and constraints before detailed planning begins.

• Open with the context or purpose quickly so the reader knows why the project charter matters.
• Organize the middle around the information the reader needs to act on: purpose, measurable objectives, scope boundaries, authority, constraints, dependencies, and success measures.
• Close with a clear next step, date, owner, contact point, or courteous sign-off instead of leaving the reader to infer what happens next.

A practical structure to follow

Use these elements as a decision checklist, not as a rigid formula. The exact wording should still fit the reader, context, and purpose.

• Open with the context or purpose quickly so the reader knows why the project charter matters.
• Organize the middle around the information the reader needs to act on: purpose, measurable objectives, scope boundaries, authority, constraints, dependencies, and success measures.
• Close with a clear next step, date, owner, contact point, or courteous sign-off instead of leaving the reader to infer what happens next.

How to write project charter step by step

1. 1
   Identify the reader, relationship, and practical outcome before drafting.
2. 2
   Put the main purpose in the opening rather than hiding it behind unnecessary background.
3. 3
   Add only the context, evidence, dates, names, or constraints required for the reader to respond correctly.
4. 4
   State the next action or expectation explicitly where the document requires one.
5. 5
   Proofread names, dates, links, commitments, tone, and any information that could create operational confusion.

Read the examples for structure and choices rather than copying surface wording. Notice what stays consistent and what changes with audience or purpose.

Replace every bracketed field with situation-specific information. A template is a starting structure, not finished copy.

Project: [name]
Purpose: [problem/opportunity]
Objective(s): [measurable outcomes]
In scope: [items]
Out of scope: [items]
Sponsor: [name/role]
Lead: [name/role]
Success measures: [metrics]
Constraints: [limits]
Dependencies: [items]
Target milestone: [date].

Problem → outcome: We are addressing [problem] so that [stakeholder] can [desired result], measured by [metric] by [date].

Scope boundary: This project includes [A, B, C]. It explicitly does not include [X, Y].

Common mistakes to avoid

• Making the project charter longer than the decision or action requires.
• Using vague courtesy language that obscures the actual request, update, decision, or transition.
• Omitting dates, owners, attachments, contact details, or next steps that the reader needs to proceed.

Final revision checklist

• Does the opening make the purpose clear quickly?
• Is every important claim, detail, or example doing a distinct job?
• Could a reader misunderstand any pronoun, transition, time reference, or instruction?
• Is the tone appropriate for the relationship and situation?
• Can you remove repetition without removing necessary context?
• If the writing contains factual claims, names, dates, quotations, or citations, have you verified them independently?

Questions about Project Charter