In brief

Use this checklist to test whether a project charter is clear enough for sponsor or governance review. Review the core checks, identify common warning signs or explore the editable Project Charter template.

1. What a project charter checklist is

A project charter checklist is a structured review of whether a draft charter gives a decision-maker enough clarity to understand the proposed mandate, boundaries, authority and uncertainty. It is a quality check. It does not replace the judgement of a sponsor, governance forum or other authorised decision-maker.

Under Project Management Institute terminology, a project charter formally authorises a project and records the project manager's authority to apply organisational resources to the work. Organisations use different names and document models. Your equivalent may be a project mandate, project brief, Project Initiation Document or part of a combined approval pack.

The checklist tests whether the charter is useful for a decision, not whether someone has completed every field. A reviewer should be able to understand:

  • what decision is being requested
  • why the project is proposed and what outcomes it should support
  • where the high-level boundaries sit
  • who owns the project and who may make which decisions
  • what remains uncertain
  • what evidence will record the approval and any conditions

The depth of review should reflect the project's size, complexity and risk. Follow your organisation's initiation, assurance, legal, procurement, security and records-management requirements. Involve relevant specialists where needed.

If you are still developing the charter, use the guide to writing a project charter before applying this final review.

2. When to use the checklist

Use the checklist when the charter is intended to support a real decision. Useful review points include:

  • before circulating a draft to the sponsor or governance forum
  • during a collaborative review with the sponsor, business owner and relevant PMO contact
  • before recording an approval decision or conditions
  • when a stalled review suggests the mandate, boundary or ownership is unclear
  • after a material change affects the objectives, scope, sponsorship, authority, funding, governance or target milestones

A material change should prompt reassessment. It does not automatically mean that every organisation will require formal re-authorisation. Use the decision pathway and tolerances that apply in your context.

Who should contribute

As a practical model, the project manager can coordinate the review. The sponsor can confirm the mandate and decision pathway. The business owner can test the intended operational outcomes and acceptance needs. A PMO or relevant specialist may contribute where the project's context warrants it.

These are useful working roles, not a universal allocation of responsibility. One person may cover several roles on a small project. Approval may sit with the sponsor or a separate delegated body.

3. Common project charter warning signs

Every field contains text, but the decision is unclear

Completion is not the same as approval readiness. State whether the request is to plan, mobilise, deliver or proceed subject to named conditions.

Objectives describe activity rather than outcomes

An activity such as implementing a system does not explain the change the project should produce. Reframe objectives around intended outcomes. Use proportionate success measures where evidence is available.

Scope is broad and exclusions are missing

A list of inclusions may still leave reasonable assumptions unchallenged. Name the material exclusions that a reviewer might otherwise expect to be included.

Responsibilities are listed without decision authority

A role title alone does not show who can approve funding, accept a deliverable, change scope or resolve an escalation. Make the relevant decision rights and limits visible.

Early estimates appear final

Some dates, costs and targets may remain provisional during initiation. Label assumptions and items needing confirmation instead of presenting immature information as a commitment.

Detailed plans have been copied into the charter

Task-level schedules and complete registers can obscure the approval-level mandate and become stale quickly. Keep the charter concise and refer to detailed controls where appropriate.

The approval record is ambiguous

A signature is one possible form of evidence, but it is not the only one. Record the decision, conditions, approver or approving body, date and document version. Use a mechanism accepted by your organisation.

Connected documents disagree

If the charter conflicts with the business case, funding record or other controlling information, the reviewer cannot tell which version represents the current proposal. Resolve material contradictions before approval or record an explicit decision about them.

4. Project charter review checklist

Use Yes, No or Needs confirmation for each question. Add a short note or evidence reference where the answer is not self-explanatory. The materiality and ownership of a gap matter more than the number of checked items.

Mandate and intended outcome

  • Is the decision being requested stated in plain language?
  • Is the reason for acting now clear enough for the reviewer to understand the proposal?
  • Do the objectives describe intended outcomes rather than only activities or outputs?
  • Are success measures proportionate to the available evidence, with provisional targets identified?

Boundaries and delivery intent

  • Can the reviewer distinguish what is included from the material exclusions?
  • Are the principal deliverables connected to the intended outcomes?
  • Are target milestones useful for governance decisions rather than copied from the detailed schedule?
  • Can the reviewer distinguish the funding position, estimate status and important timing assumptions?

Ownership, governance and authority

  • Are the sponsor, business owner, project manager and relevant decision pathway identifiable?
  • Are key responsibilities clear enough for the project's scale?
  • Is the authority being granted to the project manager stated with its limits?
  • Are reserved decisions and the escalation path visible?

Uncertainty and dependencies

  • Are material assumptions and constraints visible rather than disguised as confirmed facts?
  • Are the most important initial risks and known issues clear enough for the decision?
  • Are external dependencies and their likely decision impact identified?
  • Does each significant item needing confirmation have an owner or next action?

Approval evidence and consistency

  • Does the approval record identify the exact decision, any conditions, the decision-maker, the date and the version considered?
  • Is the proposed approval mechanism valid under the organisation's process?
  • Is the charter consistent with the current business case and other relevant records?
  • Is the document concise, internally consistent and understandable without unexplained terminology?

Where high-level roles point to a wider group of affected or influential people, use a Stakeholder Register for the fuller analysis. Avoid expanding the charter indefinitely.

Interpret the result

Individual answers are evidence for the review, not a score. Choose the overall outcome by considering the materiality and decision impact of each gap, who owns it and whether the authorised reviewer can accept it.

Use these outcomes as practical PMOEasy guidance, not as a universal approval rule:

  • Ready for review: The mandate, boundaries, authority, uncertainty and requested decision are clear enough to put to the authorised reviewer. This means ready to be reviewed, not approved or authorised to proceed.
  • Needs confirmation: A limited gap does not prevent an informed decision. The authorised reviewer accepts it as an explicit condition within their authority and records an owner, closure action, due point and limit on what may proceed before closure.
  • Return for revision: A material gap prevents an informed decision about the mandate, boundaries, authority or requested approval. Naming an owner does not make a decision-blocking gap suitable for conditional acceptance.

A completed checklist does not prove that the project should be approved. It gives the authorised reviewer a clearer basis for applying organisational requirements and judgement. If the wider initiation evidence also needs review, continue with the Project Initiation Checklist.

5. How PMOEasy helps

You can use this checklist without buying a product. If the review exposes material gaps, the PMOEasy Project Charter template provides an editable DOCX working document with practical prompts, examples, document controls and reviewer guidance.

The template gives your team a consistent place to develop the mandate. It does not replace the collaboration or judgement needed for approval, and it does not guarantee completeness, compliance, approval or a successful project outcome.

If you also need connected initiation artefacts, the Project Starter Bundle combines the charter with a business case, stakeholder register and kick-off meeting record. Each artefact has a distinct role. The evidence can support the same decision without being collapsed into one oversized document.

6. Explore the project charter template

Turn the review findings into a clearer, decision-ready draft using an editable starting point.

Explore the Project Charter template.

Need the connected set of initiation documents? View the Project Starter Bundle.

Adapt the template and checklist to your organisation's scale, delivery approach and approval requirements.