What is a project charter?
A project charter is an official document that formally authorises a project, records goals, scope, budget, timeline, and responsibilities, and is signed by the sponsor.
DEFINITION
The project charter is the founding document of a project. A project manager needs the charter as a formal basis: it assigns the authority to deploy resources and documents what the project should and should not deliver. A good project charter contains at minimum: project goal and business case, scope and non-goals, high-level milestones, budget and resource requirements, high-level risks, stakeholders and decision owners, and the sponsor’s signature. The charter is usually created in the initiation phase, before the detailed project plan exists. It is deliberately brief — typically two to three pages — because it should create alignment and overview, not a technical specification. Without a charter, the formal mandate is missing. That leads to resource conflicts, unclear expectations, and scope creep.
CONNECTIONS
Leadership
The project charter is a leadership document: it names the project manager and gives them formal authority. Without a charter, the mandate for clear decisions is missing, which leads to role conflicts and scope creep.
Artificial Intelligence
A system prompt for an AI assistant serves the same function as a project charter: it defines goal, context, boundaries, and behaviour. Those who write good charters can also formulate effective prompts.
Agility
In agile projects, the Product Backlog takes on the function of the charter: it prioritises what should be built. The charter as an overarching document remains useful in agile projects too.
KEY POINTS
- The charter formally authorises the project and assigns authority to the project manager.
- It contains goal, scope, budget, milestones, and stakeholders.
- It is created in the initiation phase, before the detailed plan.
- Without a charter, the formal mandate for resources and decisions is missing.
- It is deliberately short: alignment and transparency, not a specification.
EXAMPLE
A company wants to introduce a new CRM system. The head of IT creates a three-page project charter: the goal is rollout in six branches by Q3, budget €180,000, project start in May. Explicitly out of scope: training for external partners. The board signs the charter. The team now has a clear mandate and everyone knows what belongs in the project and what does not.
MISCONCEPTIONS
Is the project charter the same as the project plan?
No. The charter is a high-level authorisation document. The project plan contains the detailed time, resource, and cost plan. The charter comes first.
Do I need a charter for small internal projects too?
For very small projects, a brief briefing document is often enough. But the principle remains the same: recording goals, scope, and responsibility in writing protects against misunderstandings.