What is a project charter?

A project charter is a short document that formally authorises a project and gives the project manager the authority to use resources. It captures the purpose, scope, stakeholders, deliverables, timeline, budget, and success criteria so everyone starts aligned.

Why does scope need an out-of-scope section?

Listing what the project will not do is the single most effective way to prevent scope creep. An explicit out-of-scope section gives you a clear reference when someone later requests work that was never agreed, so you can manage it as a change rather than silent expansion.

Who signs off a project charter?

The project sponsor — typically the executive funding the work — signs the charter, which is what grants the project manager authority. Including a sign-off block with names and dates makes that authorisation explicit and traceable.

How is a charter different from a project plan?

A charter is high-level and authorises the project; it is written at the start and rarely changes. A project plan is detailed and operational, covering tasks, schedules, and resources, and it evolves throughout delivery. The charter sets the boundaries the plan works within.

Is my data sent anywhere?

No. The charter is generated entirely in your browser and nothing is uploaded. Copy the Markdown to save it in your own project tools.

Project Charter Builder

Email me this result

Get this tool's output sent to your inbox, plus one useful tool a week. No spam, unsubscribe any time.

Projects fail at the start more often than at the end — usually because nobody agreed on what “done” means or who is allowed to say yes. A project charter fixes that by capturing the purpose, scope boundaries, stakeholders, deliverables, timeline, budget, risks, and success criteria in one authorising document. This builder assembles all of those sections and a sponsor sign-off block, then gives you clean Markdown to share.

How it works

The charter is organised the way most project frameworks recommend: a purpose and business case up top, explicit in-scope and out-of-scope lists, concrete deliverables, the stakeholders who care, measurable success criteria, and known risks and assumptions. Each list is editable, the budget is formatted automatically, and the tool appends a sign-off table so the sponsor and project manager can authorise the work. Everything is generated in your browser as Markdown.

Tips and notes

Write the out-of-scope list before anything else — it is your strongest defence against scope creep later.
Make success criteria measurable (“support tickets down 25% within 90 days”), not aspirational, so you can prove the project worked.
Keep the purpose to a few sentences that a busy executive can read in fifteen seconds and approve.
Revisit the charter at major milestones; if reality has drifted far from it, that is a signal to run a formal change, not to quietly rewrite history.