Templates & Documents

Document Generator

45 PM documents that arrive pre-filled with your own workspace — your projects, tasks, risks, registers, controls and the programme / portfolio / PMO centres. Nothing here is an empty form: open a template and read it as if it were already issued.

Choose a document

Initiation

Planning

Governance

Reporting

Risk

Change Control

Closure

Agile

Stakeholders

Scope

Resources

Programme

Portfolio

PMO

When to use this document

Before any estimating or delivery starts. The charter is what makes a project real.

This document is written for a single engagement. Pick one project in the scope selector to see its own charter, RAM or WBS dictionary.

PROJECT MANAGEMENT 360 — VERSION 2.0DOCUMENT TEMPLATE

Project Charter

Authorise the project, name the authority behind it, and bound what it will deliver.

Scope: Full Portfolio

Generated: November 5, 2026

Prepared with: Digi Tracks

1. Purpose & Business Case

Why this project exists and what the organisation gets for the money it spends.

No project selected — pick a project to pre-fill this charter.

**Budget at completion (BAC):** $0

**Target completion date:** —

**Planned completion at reporting date:** 0%

2. Objectives & Success Criteria

Objectives are measurable statements. If a criterion cannot be measured, it is a wish.

•Deliver the scope baseline in section 3 within the approved budget and target date.

•Maintain a cost performance index (CPI) of at least 0.95 and a schedule performance index (SPI) of at least 0.95 throughout delivery.

•Close every approved change request with a recorded CCB decision before the work commences.

•Complete 61 of 125 planned activities to the definition of done.

3. Scope — In and Out

An explicit out-of-scope list is the cheapest defence against assumed scope creep.

In scope

•Draft project charter

•Identify stakeholders

•Gather requirements

•Define scope statement

•Record assumptions and constraints

•Create WBS

•Define milestones

•Sequence dependencies

•Estimate effort

•Build schedule

•Plan resources

•Confirm budget baseline

Explicitly out of scope

•Any deliverable not named in the in-scope list, until agreed through a change request.

•Re-baselining the budget or schedule without Change Control Board approval.

•Third-party licence and hosting costs not listed in the approved budget.

4. High-Level Deliverables & Milestones

The outcomes the sponsor is buying. Detail lives in the WBS dictionary.

•Draft project charter — owner Alice Chen, due Sep 12, 2026

•Identify stakeholders — owner Bob Smith, due Sep 15, 2026

•Gather requirements — owner Carol Davis, due Sep 18, 2026

•Define scope statement — owner Dan Lee, due Sep 21, 2026

•Record assumptions and constraints — owner Eva Brown, due Sep 24, 2026

•Create WBS — owner Frank Wu, due Sep 27, 2026

•Define milestones — owner Alice Chen, due Sep 30, 2026

•Sequence dependencies — owner Bob Smith, due Oct 3, 2026

•Estimate effort — owner Carol Davis, due Oct 6, 2026

•Build schedule — owner Dan Lee, due Oct 9, 2026

5. Roles, Authority & Governance

Who decides, who does, who is consulted and who is informed.

Stakeholder

Role

Organisation

RACI

Engagement

---

Elena Vance

Executive Project Sponsor

Corporate PMO

SUPPORTIVE

Alice Chen

Project Manager

PMO Delivery

LEADING

Dr. Marcus Thorne

Lead Systems Architect

Engineering Group

LEADING

Sarah Jenkins

Client Operations Director

Enterprise Client

SUPPORTIVE

David Ross

Regulatory Compliance Auditor

Independent Quality Assurance

NEUTRAL

6. Assumptions, Constraints & Dependencies

State these explicitly — they are the things that will be blamed later.

•The sponsor remains available for decisions within five working days.

•The budget is released on approval of this charter and is not index-linked.

•Any dependency outside the project boundary has a named owner in this project.

•Up to $455,000 of contingency is held in management reserve, not the work packages.

7. Top Risks & Initial Mitigation

The risks that would change the baseline if they materialise.

Risk

Severity

P x I

Status

Owner

Mitigation

---

Critical Path Sensor Module Lead Time Delay

HIGH

4 x 3 = 12

MITIGATING

Bob Smith

Pre-qualify secondary regional supplier at pre-agreed standby unit rate.

Scope Creep via Direct Stakeholder Requests

CRITICAL

4 x 5 = 20

OPEN

Alice Chen

Enforce formal Change Control Board submission and baseline impact triage.

Regulatory Site Access Certification Window

MEDIUM

3 x 3 = 9

MITIGATED

Carol Davis

Expedited council review fee paid; pre-inspection walkthrough completed.

8. Authorisation & Sign-Off

The charter is not a plan until somebody with authority signs it.

Role

Name

Signature

Date

---

Project Manager

—

Executive Sponsor

Elena Vance

PMO Assurance

—

Practice use only. Project Management 360 is a learning and practice tool. Mock exams are self-scored practice sessions and no certificate, credential or qualification is issued, promised or implied. Prepared with Project Management 360 — Version 2.0 — Developed by Digi Tracks (www.digitracks.net).

Every document above was generated from your practice workspace. Change the workspace data — add a risk, log an action, complete a task — and come back: the document updates with it.

Open the registers