Most PMOs that fail do not fail because of bad templates or the wrong software. They fail because nobody ever wrote down what the office was allowed to decide. When a senior leader wants to skip the intake process, the PMO has no document to point to, so it folds. The charter is what prevents that. It is the single most important artifact you produce when you stand up a project management office, and it is the one most teams skip.
This guide covers what a PMO charter is, exactly what to include, a section-by-section outline you can adapt, and how to scope the authority that turns the office from an advisory function into a steering one.
Key takeaways
- A PMO charter defines the office's purpose, scope, authority, and who it answers to, in one approved document.
- The authority section is the part that matters most: it states which decisions the PMO owns versus advises on.
- An executive sponsor must sign it. An unsigned charter is a wish list, not a mandate.
What is a PMO charter?
A PMO charter is a short, formally approved document that defines a project management office's purpose, scope of services, authority, and relationship to the rest of the organization. It legitimizes the PMO before the business: it states why the office exists, what it will and will not do, which decisions it owns, and who sponsors it. In practice, the charter is what lets the PMO say no to a powerful stakeholder and have that no stick.
Think of it as the constitution for the function. Everything the PMO does afterward, the intake process, the governance cadence, the reporting, draws its authority from the charter. Without one, the office runs on the personal credibility of whoever leads it, which evaporates the moment that person leaves or loses a political fight.
What should a PMO charter include?
A PMO charter should include the office's purpose and background, its objectives and success metrics, an explicit scope of services, a clear statement of authority and decision rights, the team structure and roles, the stakeholders it serves, the governance framework it will run, and an executive sponsor's signature. The scope and authority sections do the heavy lifting; the rest provides context and accountability.
Here is what each core section covers and why it earns its place in the document.
| Section | What it states | Why it matters |
|---|---|---|
| Purpose & background | Why the PMO is being created and the problem it solves | Anchors the office to a business need, not a trend |
| Objectives & metrics | What success looks like and how it is measured | Lets the PMO be held accountable and prove value |
| Scope of services | What the PMO does, and explicitly does not do | Prevents scope creep and unrealistic expectations |
| Authority & decision rights | Which decisions the PMO owns versus advises on | The clause that gives the office teeth |
| Roles & structure | The PMO team and who is accountable for what | Clarifies ownership inside the office |
| Stakeholders | Sponsors, customers, and who the PMO serves | Defines the relationships the office manages |
| Governance framework | How projects are approved, reviewed, and closed | Sets the rules of engagement up front |
| Sponsor sign-off | Executive approval and the date | Converts the document from proposal to mandate |
A PMO charter template outline
You do not need a 40-page document. A strong PMO charter fits on two or three pages. Use this outline and write each section in plain language a busy executive will actually read.
1. Purpose and background. Two or three sentences on why the office exists. Name the specific failure it addresses: projects starting before they are funded, no trustworthy portfolio view, chronic resource overcommitment. Tie it to a business consequence leadership already feels.
2. Objectives and success metrics. List three to five objectives and the metric for each. Avoid activity metrics like number of reports produced. Use outcome metrics: percentage of projects delivered on budget, reduction in active projects per person, decisions made at governance reviews. These are the numbers that prove the office works.
3. Scope of services. A bulleted list of what the PMO will do, and a short matching list of what it will not. The exclusions are as important as the inclusions: stating that the PMO does not manage individual project teams, for example, heads off the most common misunderstanding before it starts.
4. Authority and decision rights. The clause that matters most. Spell out which decisions the PMO owns outright (which projects pass intake, when a project is paused at a gate), which it recommends on, and which sit with leadership. Vague authority here is why most charters fail to change anything. See project portfolio governance for how to structure those decision rights so they hold up.
5. Roles and team structure. Who is in the office and what each is accountable for. Reference the standard breakdown in PMO roles and responsibilities rather than re-deriving it.
6. Stakeholders and sponsor. Name the executive sponsor, the customers the PMO serves, and the key stakeholders it coordinates with.
7. Governance approach. A summary of the cadence: how requests come in, how often the portfolio is reviewed, and how projects are closed. Point to the detailed process rather than reproducing it.
8. Approval. Signature and date from the executive sponsor.
Who approves a PMO charter?
A PMO charter is approved and signed by an executive sponsor, typically a C-suite leader such as the COO, CFO, or CEO, or a senior VP with budget authority over the portfolio. The seniority of the signer is what gives the charter its weight. A charter approved by a mid-level manager grants only mid-level authority, which is rarely enough for the PMO to overrule a director on which projects proceed.
This is why securing the right sponsor before you write the charter matters more than the document itself. The act of getting a CFO to sign a clause that says the PMO decides which projects pass intake is the moment the office gains real power. If no executive will sign that clause, you have learned something important: the organization is not yet ready to give the PMO authority, and you should scope the charter to what leadership will actually back.
What is the difference between a PMO charter and a project charter?
A PMO charter establishes the project management office as a standing function, defining its purpose, authority, and scope across the whole portfolio. A project charter authorizes a single project, defining that project's objectives, budget, sponsor, and scope. The PMO charter is created once and revisited periodically; a project charter is created anew for every project, often using a template the PMO itself provides.
The two work together. The PMO charter gives the office the authority to require that every project have a project charter before it starts, and to define what that project charter must contain. One sets up the function; the other governs the individual work that flows through it.
Common mistakes that weaken a PMO charter
The most common failure is a charter full of mission statements and empty of authority. It describes a noble purpose, lists services, and never says which decisions the office actually owns. The result reads well and changes nothing. If your draft does not contain a sentence a stakeholder could be annoyed by, it probably grants no real power.
The second mistake is scoping too broad too early. A new PMO that charters itself to standardize everything sets up an expectation it cannot meet and a fight it cannot win. Charter the office to fix the one or two decisions the organization keeps getting wrong, prove it works, then expand the mandate by amending the charter. A focused charter that the business backs beats a sweeping one that it quietly ignores. For the broader context on standing up the function the charter authorizes, start with what a project management office actually does.