---
artifact_id: A04
name: Project Charter
template_version: 1.0.0
status: Template · Active
category: Governance
authority: "PMBOK8 Guide §4.5.1"
source_type: PMI-derived
file_path: artifacts/initiating/A04-project-charter-template.md
---

# A04 — Project Charter Template

**Artifact ID:** A04  
**Artifact Name:** Project Charter  
**Template Version:** 1.0.0  
**Status:** Template · Active  
**Authority:** PMBOK8 Guide §4.5.1 — Initiate Project or Phase  
**Source Type:** PMI-derived  
**File Path:** `artifacts/initiating/A04-project-charter-template.md`

> **Usage note:** Complete all Mandatory fields before the project proceeds to planning. Fields marked Optional may be deferred only when the information is genuinely unavailable at chartering time and a plan exists to obtain it during planning. Do not use the charter as a substitute for the full project management plan.

---

## Section 1 — Project Identity

| Field | Value |
|---|---|
| **Project Name** | [FIELD: Full name of the project] |
| **Project ID / Code** | [FIELD: Internal project identifier or reference code] |
| **Project Type** | [FIELD: e.g. Capital, Operational, Transformational, Regulatory, Product Development] |
| **Delivery Approach** | [FIELD: Predictive / Adaptive / Hybrid — preliminary; confirmed in A06] |
| **Charter Date** | [FIELD: YYYY-MM-DD] |
| **Charter Version** | [FIELD: e.g. 1.0] |
| **Prepared By** | [FIELD: Name and role] |

---

## Section 2 — Project Purpose and Justification

### 2.1 Business Need or Opportunity

[FIELD: Describe the problem, opportunity, or strategic need that this project addresses. State why the organization is undertaking this work now. Reference the Business Case (A01) if one exists.]

### 2.2 Strategic Alignment

[FIELD: State which organizational strategy, goal, portfolio objective, or regulatory requirement this project supports. Be specific — name the strategy or mandate.]

### 2.3 Expected Outcome

[FIELD: Describe what will be different, better, or resolved when the project is complete. Focus on the outcome for the organization, not just the deliverable produced.]

---

## Section 3 — High-Level Scope

### 3.1 In Scope

[FIELD: List the major deliverables, work areas, products, services, or results this project will produce. Use bullet points. Be specific enough to prevent scope creep without pre-empting detailed planning.]

- [Deliverable / work area 1]
- [Deliverable / work area 2]
- [Deliverable / work area 3]

### 3.2 Out of Scope

[FIELD: Explicitly list what this project will NOT deliver or address. This prevents scope assumptions.]

- [Exclusion 1]
- [Exclusion 2]

### 3.3 Key Assumptions

[FIELD: List the major assumptions that the project is based on. These will be refined and tracked in the Context Register (A05).]

| # | Assumption | Owner | Impact if False |
|---|---|---|---|
| 1 | [Assumption statement] | [Owner] | [Impact] |
| 2 | [Assumption statement] | [Owner] | [Impact] |

### 3.4 Key Constraints

[FIELD: List the binding constraints on scope, schedule, budget, resources, or technical approach. These will be documented fully in A05.]

| # | Constraint | Type | Source |
|---|---|---|---|
| 1 | [Constraint statement] | Budget / Schedule / Scope / Resource / Regulatory / Technical | [Source] |
| 2 | [Constraint statement] | [Type] | [Source] |

---

## Section 4 — High-Level Milestone Intent

> **Note:** These are indicative milestones only. Detailed schedule planning occurs in A15.

| Milestone | Target Date (or Phase) | Notes |
|---|---|---|
| Project kickoff | [FIELD: date or phase] | |
| Planning complete / baseline approved | [FIELD: date or phase] | |
| [Key delivery milestone 1] | [FIELD: date or phase] | |
| [Key delivery milestone 2] | [FIELD: date or phase] | |
| Project closure | [FIELD: date or phase] | |

---

## Section 5 — Budget Boundary

| Field | Value |
|---|---|
| **Approved Budget (indicative)** | [FIELD: Amount and currency, or range if not yet confirmed] |
| **Funding Source** | [FIELD: Budget line, cost centre, program fund, or other source] |
| **Budget Approval Authority** | [FIELD: Name or role of the person/body who approved this budget] |
| **Cost Tolerance** | [FIELD: Acceptable variance before escalation is required — e.g. ±10%] |

---

## Section 6 — Governance and Authority

### 6.1 Named Roles

| Role | Name | Contact |
|---|---|---|
| **Sponsor** | [FIELD: Full name] | [FIELD: email / contact] |
| **Project Manager** | [FIELD: Full name] | [FIELD: email / contact] |
| **Project Steering Group / Governance Body** | [FIELD: Name or N/A] | [FIELD: meeting cadence] |
| **PMO Representative** | [FIELD: Name or N/A] | [FIELD: contact] |

### 6.2 Project Manager Authority

[FIELD: Describe the level of authority delegated to the project manager. Specify what the PM can approve without escalation (e.g. budget reallocation up to X, scope changes within agreed boundaries, team assignments).]

### 6.3 Escalation Path

[FIELD: Describe the escalation chain — from project manager to sponsor to governance body. State what types of decisions require escalation.]

---

## Section 7 — Initial Success Criteria

[FIELD: Define how the project will be judged as successful. Include at minimum: scope delivery standard, time boundary, cost boundary, and key quality or benefit measures. These will be baselined in the project management plan.]

| Criterion | Measure | Target |
|---|---|---|
| Scope delivery | [FIELD: how scope completion is measured] | [FIELD: target] |
| Schedule adherence | [FIELD: e.g. complete by date / phase] | [FIELD: target date] |
| Cost performance | [FIELD: e.g. within approved budget] | [FIELD: budget figure] |
| Quality / acceptance | [FIELD: acceptance criteria summary] | [FIELD: standard] |
| Benefits / value | [FIELD: key benefit or value measure] | [FIELD: target value] |

---

## Section 8 — Initial Risk Summary

[FIELD: List the 3–5 most significant risks known at chartering time. Full risk planning occurs in A19.]

| # | Risk Description | Preliminary Severity | Owner |
|---|---|---|---|
| 1 | [Risk statement] | High / Medium / Low | [Owner] |
| 2 | [Risk statement] | [Severity] | [Owner] |
| 3 | [Risk statement] | [Severity] | [Owner] |

---

## Section 9 — Approvals

| Role | Name | Signature | Date |
|---|---|---|---|
| Sponsor | [FIELD: Name] | [FIELD: Signature or digital approval] | [FIELD: YYYY-MM-DD] |
| Project Manager (acceptance) | [FIELD: Name] | [FIELD: Signature or digital approval] | [FIELD: YYYY-MM-DD] |
| PMO (if required by policy) | [FIELD: Name or N/A] | [FIELD: Signature or N/A] | [FIELD: YYYY-MM-DD] |

---

## Change Log

| Version | Date | Author | Change Description |
|---|---|---|---|
| 1.0.0 | 2026-05-30 | B2 Batch 1 | Initial template — Phase B2 |

---

*Template for: A04 — Project Charter*  
*Authority: PMBOK8 Guide §4.5.1*  
*See definition file: `artifacts/initiating/A04-project-charter.md`*
