What Is Another Name for a Project Charter? Charter vs PID

The closest alternative names for a project charter are the project initiation document (PID), the project brief, the project definition document and the terms of reference. They are not exact synonyms. Each comes from a different method and carries a different amount of detail, and the charter’s particular job is authorisation.

This matters more than it sounds. Teams routinely spend a fortnight arguing about which template to use when the real disagreement is about who is allowed to approve the project and release the money.

What is another name for a project charter?

The name changes with the method your organisation follows, and the document changes with it. These are the terms you will meet most often:

• Project initiation document (PID). The PRINCE2 term. Broader than a charter: it absorbs the authorisation job and adds plans, controls and business justification.
• Project brief. Also PRINCE2, and the nearest true analogue to a charter. It is the short document assembled before full initiation, giving the outline case, scope and roles.
• Project definition document. An in-house name, common in organisations running a light internal method. Content varies by whoever wrote the template.
• Terms of reference (ToR). Standard in the public sector, charities and consultancy. Often applies to a board, working group or steering committee rather than a project, so check what it is describing before you copy one.
• Project mandate. PRINCE2’s trigger from the commissioning body, and not a charter. It comes earlier and authorises investigation, not delivery.
• Statement of work. Supplier-facing and contractual. It defines what a vendor will deliver for a fee. Do not use it as an internal authorisation.

Scope statement gets thrown into the same pile too, but it is a section rather than a document. If someone offers you a scope statement in place of a charter, you have been handed one paragraph of a much larger conversation.

Are the project charter and the project initiation document the same thing?

No. They are close relatives from different traditions. The charter comes from PMI’s body of knowledge, where its job is to authorise the project’s existence, name the project manager and give that person the authority to draw on organisational resources. The PID comes from PRINCE2 and covers far more ground: it is the full initiation-stage record, and it absorbs the charter’s role rather than replacing it.

	Project charter	Project initiation document (PID)
Tradition	PMI, PMBOK Guide	PRINCE2
Primary job	Authorise the project and the project manager	Show the agreed shape of the whole project before delivery commitment
Form	One document, usually short	A set of components assembled together, which is why PRINCE2 calls it Project Initiation Documentation
Written when	At the start, before detailed planning	At the end of the initiation stage, before delivery starts
Contains plans and controls	High level only	Yes, including the plan, the approaches to risk and quality, and the reporting arrangements
Signed by	The sponsor or the person releasing the funding	The project board
Life after approval	Reissued if the mandate changes, rarely edited	Baselined and version controlled through the project

In practice, an organisation running PRINCE2 does not need a separate charter, because the project brief and then the PID do the same work in sequence. An organisation running a PMI-flavoured method does not need a PID, because the charter plus the project management plan cover it. The mess happens in the middle, where a PMO has borrowed vocabulary from both and nobody can say which document actually carries the sponsor’s signature.

What are project initiation documents?

Project initiation documents are the set of records that define a project fully enough for a governance body to commit to delivering it. The plural is not sloppiness. In PRINCE2 the PID is explicitly a collection, assembled from products created during initiation rather than typed out as one file.

A PID normally brings together:

• The project definition: background, objectives, scope, exclusions, constraints, assumptions and interfaces with other work
• The business case, or a reference to it if it lives elsewhere
• The project plan, including stages and the point at which the board reviews progress
• The organisation structure, with named people against named roles
• The approaches to risk, quality, change and communication
• The project controls: tolerances, reporting frequency, escalation route

That is a shape, not a form to fill in. If you want the section-by-section version, including which parts are usually padding, our breakdown of what to include in a project initiation document covers it properly. The same applies on the charter side: who writes the charter and which components it needs is a separate question from what the thing is called.

Is a project charter a project document?

Yes. It is a formal project document, and on most projects it is the first one that carries a signature. The distinction people are reaching for when they ask is between a document that plans the work and a document that permits it. The charter is the second kind.

That has three practical consequences.

It is not part of the project management plan. The charter is an input to planning, not an output of it. Planning happens after somebody has said yes, and the charter is the record of that yes.

It is not a living document in the way a risk register is. You do not update a charter weekly. If the objectives, funding or accountable owner change materially, the charter is reissued and re-signed, which forces the sponsor to notice that they are approving something different from what they originally approved.

It belongs under version control with the rest of the governance record. Audit, assurance and any subsequent dispute will ask for the approved version and the date. A charter that only exists as an attachment on a nine-month-old email thread is not much use to anybody.

A charter with no named approver is a memo. The signature is the entire point of the document, and it should come from whoever controls the budget rather than whoever chaired the meeting.

What is the standard project initiation document?

There is no single cross-industry standard PID. The nearest thing to one is the PRINCE2 Project Initiation Documentation, which most UK templates are descended from, and it is a specified set of components rather than a fixed form with numbered fields. Beyond that, standard means whatever your PMO or your funder says it means.

Three versions you will actually encounter:

1. The PRINCE2 shape. The components listed above, tailored to project size. PRINCE2 expects tailoring, so a small project producing a six-page PID is following the method, not cutting corners.
2. The funder’s template. Public bodies, grant funders and large clients often mandate their own format, sometimes with a business case in a prescribed structure attached. If money is coming from outside, their template is the standard, whatever your internal one says. How to write a business case covers what that attachment usually has to prove.
3. The in-house one-pager. Common in software and startups, where the initiation record is a short document covering problem, scope, owner, budget and decision rights. Perfectly legitimate, provided somebody with authority signs it.

Be suspicious of any template that runs to forty headings and asks for none of the four things that decide whether a project can start: what it is for, what it costs, who is accountable, and what is out of scope.

Which name should your organisation use?

Pick one and enforce it, because the cost of two names is not confusion, it is two approval routes. Nobody has ever been rescued from a scope dispute by the file name. What rescues them is knowing which person’s signature the organisation treats as permission to spend.

A workable way to settle it:

1. Find out which document your finance and governance functions already recognise. They will have one. Start there rather than from a methodology textbook.
2. Name the approver, not the role. “Director of Operations” is a role. A specific person with a delegated financial limit is an approver.
3. Decide what the approval covers. A budget envelope, a stage, or the whole project. Charters that approve everything forever are the reason change control gets ignored.
4. Fix the other names as aliases in the template itself. One line saying this document is also referred to as the project brief internally kills most of the argument.
5. Write down what happens when scope changes. Reissue and re-sign, or raise a change request against the baseline. Both work. Only one of them can be your default.

Where the approver is genuinely unclear, a facilitated pass through the initiation questions is more use than another template. Projan holds that discussion in Slack or Microsoft Teams and will not move on until someone names who signs, what the money is being released for and which of the two documents the organisation will actually keep, then writing the agreed answers into a document you can export to Confluence. What settles the argument is the naming decision itself, not the method used to reach it.

If none of this is resolved yet, the problem is upstream of documents entirely. What actually happens during project initiation is the better place to start than a template library.

Frequently asked questions

Is a project brief the same as a project charter? In PRINCE2 the project brief is the short document assembled before initiation proper, so it sits closer to a charter than the PID does. Outside PRINCE2, project brief usually means something looser: a marketing or design brief describing what the client wants. Ask which meaning is in play before you agree to write one.

Can a project have both a charter and a PID? Yes, and plenty do, usually because the organisation runs a PMO template while the funding sponsor wants a one-page authorisation to sign. It only causes trouble when the two disagree. Keep the charter as the signed authorisation and treat the PID as the fuller version of the same scope, updated in one place.

What is a project mandate? In PRINCE2 the mandate is the trigger: the instruction from the commissioning body that a project should be looked at, often a few paragraphs or an email. It comes before both the project brief and the PID. It is not an authorisation to spend, and treating it as one is a common way to start work that nobody has actually approved.

How long should a project charter be? Short enough that the sponsor reads it before signing, which in practice means two or three pages. If it runs longer, the detail probably belongs in the project plan or the business case. The test is whether a reader can tell what is being approved, who is accountable and what falls outside it.

The charter and the PID are not the same document, and swapping the labels solves nothing. Decide which one your organisation signs, name the person who signs it, and make every other term in circulation an alias for that one thing.