A project charter is the short document that formally authorises a project, names its sponsor and manager, states its purpose, its intended outcomes and its boundaries, and gives the manager the authority to spend the organisation's resources on it.
Our take. A charter that runs past two pages has stopped being a charter and become a plan written before anyone knew enough to plan. The document's job is to answer four questions in a way a sponsor will sign: why, what, who decides, and what is out. Everything else belongs in documents that come later and change more often.
Projects that fail at the end usually failed at the start, when nobody wrote down what success meant and who would say so. The charter is where that gets written. It records why the organisation is doing this and what it expects to be different afterwards; it names the sponsor who owns that outcome and the manager who will deliver it; it states, at whatever precision is available so early, the boundaries of scope, time and money; and it is signed by someone with the authority to commit the resources. From that signature the manager may spend, assign and decide within the boundaries, and everyone else knows who to argue with.
Purpose and justification: the problem or opportunity, and why now. If this cannot be stated in a paragraph the project is not ready to be chartered.
Objectives and success criteria: what will be measurably different, so that finished has a definition.
High-level scope and exclusions: what is in, and, more usefully, what is explicitly out.
Sponsor, manager and their authority: who owns the outcome, who runs the work, and what the manager may decide alone.
Known constraints, assumptions and top risks: the things that could stop it, as understood on day one.
Signature: the sponsor's, which turns a proposal into a mandate.
The methods differ in name and agree in substance. PMI's body of knowledge treats the charter as the output of initiation and the manager's source of authority. PRINCE2 splits the same content across a project mandate, a brief and an initiation document, with the brief closest to a charter. IPMA's competence standard asks whether the manager can secure and use such a mandate rather than what it is called. The entry-level certificates test the contents and who signs; the professional ones examine the manager's move when the charter's assumptions turn out to be wrong, which is escalate to the person who signed it rather than quietly redefine the project.
In practice
A department head asks an analyst to build a reporting dashboard, and eight months later the dashboard is finished, the department head has moved on, and the new one has never heard of it. Nobody can say whether it succeeded because nobody wrote down what it was for. The chartered version takes an afternoon: purpose, to replace the monthly manual report; success, the report is produced from the dashboard without manual steps by a stated date; scope, the four data sources named, nothing else; sponsor, the department head, who signs. When the sponsor leaves, the successor reads a page, decides whether the purpose still holds, and either re-signs or stops the work. Either is a decision; the unchartered version allowed neither.
The charter states scope at the level available on day one and gives the authority to define it properly. The scope statement and the work breakdown that follow are where the definition actually happens.
A statement of work is a contractual description of deliverables between a client and a supplier. A charter is an internal authorisation. Where a project is delivered by a supplier, the two exist side by side and should not contradict each other.
A brief describes what a client wants from a piece of work, usually creative or freelance. A charter authorises a project inside an organisation and names who may decide; it is about mandate more than about wants.
Key takeaways
→Why, what, who decides, what is out: a page or two, signed by the sponsor.
→The signature is the authority to spend and decide within the boundaries.
→When the charter's assumptions fail, escalate to the signer; do not redefine the project quietly.
Certifications that test this
Vendor exams whose syllabus covers this concept — facts, cost and a preparation path on each page.
A rotating selection from the course directory, drawn from the subcategories where this concept is taught rather than picked for it. Details, price and the provider link are on the course page.
Strategic Planning: Business Strategy using Ancient MappingPlan your business strategy using a world-renowned theory of…
Udemy
FAQ
Who writes the charter?
Usually the project manager, on the sponsor's behalf, because the manager has to live with it. The sponsor owns it and signs it, and a sponsor who will not put a name to the purpose and the boundaries is telling you something about the project.
How long should a charter be?
One to two pages. It records decisions made before the project knew enough to plan, and it should be readable by a new sponsor in five minutes. Detail belongs in the scope statement, the schedule and the risk register, which will change; the charter should not.
Does an agile project need a charter?
Something that does its job, yes: a stated purpose, a named owner, and boundaries on money and time. Agile methods call it a product vision or a lean canvas or simply a funded team with a goal. The name changes; the need for someone to have said why and to own the answer does not.
Sources
The primary text this definition rests on. Read it before you trust ours.
Project Management Institute, A Guide to the Project Management Body of Knowledge (PMBOK Guide), Seventh Edition (2021)
PeopleCert, Managing Successful Projects with PRINCE2, 7th Edition (2023)
ISO 21502, Project, programme and portfolio management, Guidance on project management (2020)
