Project Charter
A concise authorization document that establishes why a project exists, who sponsors it, what success means, and what authority the project manager holds.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/project-charter/
01What it means
A project charter is an early governing artifact issued or approved by a sponsor to formally authorize a project and empower its project manager to use organizational resources. It usually records the purpose, objectives, high-level scope, success criteria, principal stakeholders, assumptions, constraints, major risks, broad milestones, budget boundaries, and approval authority without attempting to replace the detailed project plan.[1][2]
02Why it matters
The charter turns an attractive idea into an accountable commitment. It gives the team a stable reference for resolving disagreements about purpose and boundaries, makes sponsorship visible, and clarifies who may make which decisions. A strong charter also creates an explicit test for later change requests: proposed work should support the authorized objectives or be deliberately reauthorized.
03When to use it
Create a charter before substantial planning or delivery resources are committed, especially when work crosses departments, has material cost or risk, or depends on executive sponsorship. Revisit or reauthorize it when the business case, intended outcomes, funding, leadership, or project boundaries change materially.
04How it works
- State the problem or opportunity, strategic rationale, intended outcomes, and measurable success criteria.
- Define high-level scope, exclusions, major deliverables, assumptions, constraints, milestones, budget range, and risks.
- Name the sponsor, project manager, governance bodies, key stakeholders, and decision or escalation rights.
- Review the draft with delivery leads and affected stakeholders to expose ambiguity before authorization.
- Obtain documented sponsor approval, communicate the charter, and use formal change control for material revisions.
05A practical example
A retailer charters a project to reduce online return-processing time from ten days to four. The charter authorizes a named manager, includes warehouse and finance workflows, excludes carrier-contract renegotiation, sets a six-month target and budget range, identifies data-quality risk, and requires the operations sponsor to approve scope or funding changes.
06Where it breaks
A charter is intentionally high level and cannot substitute for discovery, estimates, schedules, risk analysis, or delivery plans. Early assumptions may prove wrong, and ceremonial approval does not create genuine sponsorship. If the document becomes excessively detailed, stale, or treated as an unchangeable contract, it can conceal uncertainty rather than guide decisions.
Common mistakes
- Starting delivery before a sponsor has clearly authorized the project and manager.
- Writing vague aspirations without measurable outcomes or explicit exclusions.
- Confusing the charter with a complete project management plan.
- Updating scope informally without revisiting the authorization and business case.
07Sources
- PMI Lexicon of Project Management Terms, Version 5.0Project Management Institute · Professional standards lexiconPMI Lexicon of Project Management Terms, Version 5.0
- The Charter: Selling Your ProjectProject Management Institute · Professional conference paperThe Charter: Selling Your Project