Project Charter and Project Initiation: Template and Worked Example

Once a project is approved in principle, someone must formally authorise it and give the project manager the authority to start. That is the job of the project charter. Along with the business case, it is one of the most important documents in initiation, the stage in which a vague idea becomes a defined, sponsored project. A charter that is clear and short prevents months of confusion later.

What Is a Project Charter?

A project charter is a document issued by the project sponsor (or initiator) that formally authorises the project, names the project manager and gives that person authority to apply organisational resources. It records the high-level objectives, scope, constraints and success criteria. It is not a detailed plan; it is the agreement on why and within what boundaries the project exists.

Why It Matters

  • Authority: it gives the project manager legitimacy when negotiating for people and decisions.
  • Alignment: sponsor, stakeholders and team share one understanding of the goal.
  • Boundaries: it provides a reference when someone later asks for work outside the agreed scope.
  • Traceability: every later plan can be checked against it.

Typical Contents

SectionWhat it contains
Project title and purposeA short statement of why the project exists
Business case summaryProblem, expected benefits and link to strategy
Measurable objectives and success criteriaHow the sponsor will judge success
High-level scopeWhat is in, and equally important, what is out
Major deliverables and milestonesKey outputs and target dates
Summary budgetFunding limit or estimated range
Assumptions and constraintsConditions taken as true and fixed limits
High-level risksTop threats and opportunities known at this stage
Key stakeholdersSponsor, customers, major contributors
Project manager and authority levelWho leads, and what they may decide
ApprovalSignatures of the sponsor and key leaders

Charter vs Project Plan vs Scope Statement

People often blur these documents. The charter is issued outside the project team (by the sponsor), is high level and authorises the project. The scope statement, covered in Project Scope Statement and WBS, is created by the team and describes deliverables in more detail. The project management plan is the full set of planning documents showing how the work will be executed, monitored and closed.

Worked Example: Customer Support Portal

Title: Customer Support Portal, Phase 1.

Purpose: Reduce phone support volume by letting customers log, track and resolve common requests online.

Objectives:

  • Launch the portal to all existing customers by 31 March.
  • Reduce phone tickets for password and billing queries by 30 per cent within three months of launch.
  • Achieve a customer satisfaction score of at least 4.2 out of 5 for portal users.

In scope: ticket logging and tracking, knowledge base search, password reset, and integration with the existing CRM.

Out of scope: mobile app, live chat, multi-language support and migration of tickets older than two years.

Budget: not to exceed ₹85 lakh including a 10 per cent contingency.

Key assumptions: the CRM vendor will provide API access by 15 December; two business analysts are available for 60 per cent of their time.

Top risks: delay in CRM API access, low adoption by older customers.

Authority: the project manager may approve spending adjustments of up to ₹2 lakh within the budget and must escalate larger changes to the steering committee.

Notice how much value comes from the “out of scope” list. When someone asks for live chat in month four, the charter shows it was a conscious exclusion, and any addition must go through change control.

The Initiation Steps

  1. Understand the business case and why the sponsor wants the project (see Business Case and Project Selection).
  2. Identify the sponsor and key stakeholders and interview them about expectations (see Stakeholder Analysis).
  3. Clarify objectives and success criteria in measurable terms.
  4. Draft the charter in plain language, using the sponsor’s own words where possible.
  5. Review and refine with stakeholders, and surface disagreements early.
  6. Obtain sign-off and store the charter where everyone can find it.
  7. Hold a kick-off meeting to communicate goals, roles and ways of working.

Writing Success Criteria That Work

Vague statements such as “improve customer experience” cannot be judged. Use measurable, time-bound criteria with an agreed way to check them: “Reduce average ticket resolution time from 3 days to 1 day by June, measured from the ticketing system.” Include three types where possible: delivery criteria (on time, on budget), product criteria (meets requirements) and business criteria (benefits achieved).

Charters in Agile Projects

Agile teams often use a lighter equivalent, such as a one-page vision, product goal and team agreement. The purpose is the same: shared purpose and boundaries. See Scrum Framework Explained for how Scrum frames the Product Goal and Sprint Goal.

Common Mistakes

  • Writing a 30-page charter nobody reads.
  • Listing only in-scope items and leaving exclusions unstated.
  • Letting the project manager write and approve the charter alone, with no sponsor ownership.
  • Starting work before sign-off, then arguing over what was agreed.
Key takeaways
  • The charter formally authorises the project and names the project manager.
  • Keep it short, high level and signed by the sponsor.
  • State exclusions as clearly as inclusions.
  • Success criteria must be measurable and checkable.

Related Lessons