PMO Charter Template: The Document That Authorises the PMO Itself (2026)

PMO Charter vs Project Charter

A project charter authorises a single project; a PMO charter authorises the PMO function itself. The PMO charter is reviewed and re-approved typically annually, while a project charter is a one-time artefact for one project. The PMO charter sets the standard by which all subsequent project charters in that organisation will be approved.

PMI Pulse of the Profession 2024 reports that organisations with a chartered PMO are 38% more likely to deliver projects on time and 29% more likely to meet original budget. Gartner's PMO research consistently identifies executive sponsorship and explicit scope as the two strongest predictors of PMO longevity past the four-year mark.

Pick the PMO Type Before You Write the Charter

The four PMO archetypes have different scope, authority, and headcount. Picking the wrong type produces a charter that the organisation cannot enforce or that the PMO cannot deliver against.

PMO Type	Role	Authority	Best fit	Size
Supportive PMO	Consulting and templates	Low	Small organisations or distributed delivery teams. PMO advises but does not enforce.	1 to 3 FTE
Controlling PMO	Standards enforcement and assurance	Medium	Mid-size companies with multiple delivery teams. PMO defines standards and audits compliance.	3 to 8 FTE
Directive PMO	Direct delivery management	High	Large enterprises with portfolios over USD 50M. PMs report into the PMO rather than business units.	10 to 30+ FTE
Centre of Excellence (CoE)	Methodology, training, and continuous improvement	Advisory	Organisations with mature delivery, focused on raising practitioner capability.	2 to 6 FTE

PMO Charter Sections

1. Purpose and Mandate

Why the PMO exists and what authority it has. Should reference the corporate strategy and the executive sponsor.

2. Scope of Services

What the PMO does (and explicitly does not). Common services: portfolio management, project assurance, capability development, tooling, reporting.

3. PMO Type and Operating Model

Supportive / Controlling / Directive / CoE. Reporting line. Decision rights between PMO and delivery teams.

4. Structure and Roles

Headcount by role, reporting lines, governance forums the PMO chairs or participates in.

5. Service Catalogue

The specific services the PMO offers, with SLAs and engagement model.

6. Governance

Forums (portfolio board, change advisory board, capability council). Decision rights matrix. Escalation paths.

7. RACI

For the top 10 to 15 decision types: who is responsible, accountable, consulted, informed.

8. KPIs and Reporting

How the PMO measures its own success. Common KPIs: on-time delivery rate, on-budget rate, benefit realisation rate, methodology adherence.

9. Budget and Resources

PMO operating budget, separate from project budgets. Tooling, training, contractor envelope.

10. Maturity Roadmap

Where the PMO is on a maturity curve (often Gartner or P3M3) and where it intends to be in 12 / 24 / 36 months.

Filled Example: Aurora Cloud Services PMO

Organisation

Aurora Cloud Services (mid-size B2B SaaS, USD 180M ARR, 720 employees, 14 active projects)

PMO type

Controlling PMO transitioning toward Directive over 24 months

Reports to

Chief Operating Officer (with dotted line to CFO for portfolio reporting)

Headcount and budget

5 FTE at launch: PMO Director, Portfolio Manager, 2 Project Assurance Analysts, 1 Tooling and Reporting Lead

USD 1.42M Year 1 operating budget (4 of 5 FTE loaded, Workfront seat licences for 60, training partnership with PMI Authorised Training Partner, contractor reserve USD 200K)

Service Catalogue

Project intake and prioritisation (quarterly portfolio review with executive team)
Project assurance reviews (Discovery exit, mid-build, pre-launch)
Methodology and template authoring (PMBOK-aligned charter, status report, RAID log)
Tooling administration (Workfront for portfolio, Jira for delivery, integration to Salesforce)
Practitioner development (PMP certification sponsorship, monthly community of practice)
Monthly portfolio status and benefit realisation report to executive team

KPIs (How the PMO Measures Itself)

On-time delivery rate (target: 78% in Year 1, 85% by Year 2; baseline: 61% in 2025)
On-budget delivery rate (target: 82% in Year 1; baseline: 67%)
Benefit realisation rate measured 6 months post-launch (target: 75% of projected benefits achieved; baseline: not currently measured)
Methodology adherence (% of projects with approved charter, signed-off scope, baselined plan; target: 95% by Year 2)
Practitioner satisfaction (annual survey, target NPS +20)
Average project review turnaround (target: 5 business days, baseline: ad-hoc)

Explicitly Out of Scope

Direct project management (PMs continue to report to BU heads; PMO provides standards and assurance, not line management)
Vendor management (procurement function retains)
IT operations and run-state systems (handled by separate Tech Ops org)
HR for project staff (handled by central People function)

Frequently Asked Questions

What is the difference between a project charter and a PMO charter?

A project charter authorises a single project. A PMO charter authorises the PMO function itself, which then oversees many projects. The PMO charter has roughly twice the section count (purpose, scope, type, structure, services, governance, RACI, KPIs, budget, roadmap) and is typically reviewed annually rather than at project end. Most large enterprises require both: a PMO charter for the function and individual project charters for each project the PMO oversees.

How long should a PMO charter be?

8 to 20 pages for most organisations. The Gartner PMO research suggests directive PMOs in enterprises over 5,000 employees typically have 15 to 25-page charters because the governance and RACI sections are more complex. Supportive PMOs in organisations under 500 employees can fit a charter in 6 to 10 pages. The charter should be revisited annually because the PMO's scope and authority typically evolve.

Who approves a PMO charter?

The executive sponsor of the PMO, typically the COO, CFO, or CIO depending on the PMO's focus. In a strategic PMO with portfolio authority, the CEO often co-signs. The signing process is consequential because the PMO charter creates an internal authority structure that crosses business unit boundaries. Without explicit executive sign-off, the PMO will lack the political cover to enforce standards on uncooperative business units.

Should the PMO charter define what it will NOT do?

Yes, explicitly. The most common PMO failure mode is scope drift: the PMO starts as an assurance function and slowly becomes the dumping ground for every governance task nobody else wants. The 'out of scope' section is the political defence against this. PMI Pulse data consistently shows PMOs with clearly bounded scope outperform PMOs with ambiguous scope on every measured dimension.

What is P3M3 and how does it relate to a PMO charter?

P3M3 is the Portfolio, Programme, and Project Management Maturity Model published by AXELOS. It measures organisational maturity on a 1-to-5 scale across seven process perspectives. A PMO charter often references the organisation's current P3M3 level (typically Level 2 for organisations setting up their first PMO) and target level (Level 3 within 24 months is a common goal). The roadmap section of the charter ties to specific P3M3 perspectives the PMO will improve.

How long does setting up a PMO typically take?

Charter approval to first delivered service: 3 to 6 months for a supportive PMO, 6 to 12 months for a controlling PMO, 12 to 24 months for a directive PMO. Gartner research on PMO maturity suggests 60% of new PMOs are disestablished or substantially restructured within 4 years, usually because they were chartered without explicit executive sponsorship or with ambiguous scope. The charter is the primary defence against both failure modes.

Does an agile organisation need a PMO?

Often yes, but it looks different. Pure agile organisations replace the traditional PMO with an Agile Centre of Enablement (ACE) or Agile PMO that focuses on coaching, tooling, and metrics rather than assurance and gating. The charter sections are largely the same but the services and KPIs change: instead of on-time and on-budget rates, agile PMOs typically measure cycle time, predictability of forecasts, and team health.

Related on this site

Enterprise project charter (the PMO authorises projects with this format)PMBOK charter format Methodology (about this site)Government PMO context Hybrid waterfall-agile charter Portfolio risk matrix