Enterprise Project Charter Template: Steering Committee, Audit Trail, Program Charter (2026)

Project vs Program vs Portfolio Charter

The three charter types exist at different levels of organisational governance. Pick the right one before you start writing.

Type	Scope	Duration	Sponsor	Governance	Document
Project Charter	Single project (one outcome, one team, one budget envelope)	Weeks to 24 months	Director / VP / Sometimes C-Suite	Sponsor + 3-5 person steering	5-15 pages
Program Charter	Multiple related projects coordinated to deliver a strategic outcome	12 months to multi-year	Senior VP / C-Suite	Program board (5-9 person steering) + project sponsors	15-35 pages
Portfolio Charter	Set of programmes and projects aligned to a strategic theme or business unit	Ongoing (refreshed annually)	C-Suite / Board	Portfolio board / Investment committee	10-25 pages plus annual portfolio refresh artefacts

Reference: PMI Standard for Program Management (5th ed., 2022) and Standard for Portfolio Management (4th ed., 2017); AXELOS MSP (Managing Successful Programmes) and MoP (Management of Portfolios).

Steering Committee Composition

An enterprise charter without a defined steering committee is not enterprise-grade. The six roles below cover the standard composition; smaller enterprise projects may consolidate (e.g. Senior User and Risk Partner held by one person) but should not skip.

Executive Sponsor (chair)

Accountable for benefits and budget; chairs steering; signs charter and major changes.

Senior User

Represents the users / customers of the outcome. Approves user-facing acceptance criteria.

Senior Supplier

Represents the team / vendors building the project. Provides delivery confidence.

Finance Partner

Approves budget variances above tolerance; signs off on benefit realisation reporting.

Risk and Audit Partner

Provides independent assurance to steering. Often Internal Audit or external IV&V partner.

Programme Director (where applicable)

On programme charters, the dedicated programme leader who runs delivery between steering meetings.

15-Section Enterprise Charter Format

Target total: 15-20 pages. Each section length below is approximate; substance matters more than length. Sections 11-14 are the ones most often skipped in non-enterprise charters; including them is the test that distinguishes enterprise format from standard PMBOK.

Section	Pages
1. Executive Summary	1-2
2. Strategic Context and Business Case	2-3
3. Project Definition	1-2
4. Objectives and Success Criteria	1-2
5. Scope (In, Out, Boundaries)	2-3
6. Deliverables and Acceptance Criteria	1-2
7. Milestone and Stage Plan	1-2
8. Resources, Team, and RACI	1-2
9. Budget (Capex, Opex, Contingency, Drawdown)	1-2
10. Risk Register (top 10-15) and Risk Management Approach	2-3
11. Quality Management Approach	1
12. Communication and Stakeholder Engagement	1-2
13. Change Control Approach	1
14. Tolerances and Escalation	1
15. Approval and Signatures	0.5

Enterprise Charter Failure Modes

Over-engineering: 60-page charters nobody reads

Length signals risk-aversion not rigour. Sponsors stop reviewing in detail and approve based on cover memo. The charter becomes performative.

Steering composition that excludes the senior user

Decisions made without user representation produce launches that user-side teams will not adopt. The most common failure mode in enterprise IT charters.

Treating the charter as the project plan

Detailed task plans in the charter become stale within weeks. The charter should reference the project plan, not contain it.

Skipping the change control approach section

First scope-change request becomes an argument because no one agreed on the process. Charter approval should establish the process.

Conflating sponsor and PM accountability

If both sponsor and PM are 'accountable' for the budget, the budget has no real owner. Sponsor is accountable for the envelope; PM is accountable for delivery within it.

Frequently Asked Questions

When does a project become a program?

When two or more related projects must be coordinated to deliver a strategic outcome, and the coordination value exceeds the overhead of programme management. PMI defines a programme as 'a group of related projects, subsidiary programmes, and programme activities managed in a coordinated manner to obtain benefits not available from managing them individually'. Typical inflection points: when projects share critical resources or vendors, when projects have interdependent milestones, or when the outcome of one project unlocks the next. Below the inflection, run projects independently; above it, formalise as a programme.

What is the difference between PMBOK and the PMI Standard for Program Management?

PMBOK governs single projects; the Standard for Program Management (currently 5th edition, 2022) governs programmes. The two are complementary: a programme charter references the Standard for Program Management; the constituent project charters reference PMBOK. UK government uses the AXELOS MSP (Managing Successful Programmes) for the equivalent role, with MoP (Management of Portfolios) at portfolio level.

How long should an enterprise project charter be?

10-20 pages for a single project; 20-35 pages for a programme; 15-25 pages for an annual portfolio charter. Above 35 pages, the document is unreadable for executive review. Below 10 pages for an enterprise project, the charter likely lacks the audit trail required for capex sign-off, board reporting, or external assurance. PMI's published examples and AXELOS's PRINCE2 7 PID examples both sit in the 15-25 page range for typical enterprise projects.

Who chairs the steering committee?

The Executive Sponsor. Not a delegate, not the PM, not the Senior Supplier. The Sponsor's authority is the source of the project's authority, and the chair role is how the Sponsor exercises that authority. If the named Sponsor delegates the chair role to a Programme Director or PMO Director, this should be explicit in the charter (and recognised as a partial accountability transfer).

Should the charter include the full risk register?

The top 10-15 risks should be in the charter; the full risk register (typically 30-80 risks for an enterprise project) lives in a separate document or risk-tracking tool. The charter's risk section should explain the risk management approach (matrix used, scoring methodology, escalation thresholds) and present the most material risks as a sample.

How does an enterprise charter handle vendor relationships?

Vendors appear in three sections. (1) Resources and Team / RACI: who is responsible for what. (2) Budget: vendor cost as a line. (3) Stakeholder Engagement: vendor relationship management approach, escalation paths, and named relationship owners. The actual contracts and SOWs live outside the charter; the charter references them.

What is the difference between tolerance and contingency?

Tolerance is the variance band within which the PM can act without escalating to the sponsor; contingency is the budget reserve available within the tolerance band. PRINCE2 formalises tolerance across six dimensions (time, cost, quality, scope, risk, benefit); PMBOK uses 'control thresholds' as the equivalent term. The charter should name the tolerance band; the budget section should show the contingency available within the cost tolerance.

Related on this site

PMBOK charter format PRINCE2 PID (UK enterprise pattern)PMO charter (the function that runs enterprise charters)Government charter (statutory enterprise pattern)Hybrid waterfall-agile charter Charter budget section (capex + contingency)