Building your PMO charter

Before you do anything else as a new PMO — before you build templates, run workshops, or start reporting — write a PMO charter.

A PMO charter is a short document that defines what your PMO is, what it’s authorised to do, who it reports to, and how its success will be measured. It’s not bureaucracy for the sake of it. It’s the foundation that stops you spending six months building something nobody asked for, or finding yourself unable to act because your authority was never properly defined.

Without a charter, you’re operating on assumptions. With one, you’re operating on agreement.

What a PMO charter covers

A good charter doesn’t need to be long — four to six pages is usually enough. What matters is that it answers the right questions clearly:

Purpose and mandate

Why does this PMO exist? What problem is it solving? What would the organisation look like in 12 months if the PMO is working well? This is the most important section — if you can’t articulate the mandate clearly, you don’t have one yet.

Scope

Which projects, programmes, or portfolios does the PMO cover? Which business units? Are there any areas explicitly excluded? Scope creep kills PMOs as reliably as it kills projects. Define the boundaries early and get them agreed.

Services and functions

What will the PMO actually do? List the specific services — templates and standards, portfolio reporting, governance support, assurance reviews, training, resource management. Be concrete. “Supporting project delivery” is not a service. “Producing a monthly portfolio dashboard for the executive team” is.

Authority and governance

What is the PMO authorised to do — and what is it not? Can it mandate standards or only recommend them? Does it have a role in project approval? Who can override the PMO, and under what circumstances? This section often gets softened to avoid conflict. Don’t let it. Vague authority leads to vague outcomes.

Reporting line and sponsorship

Who does the PMO report to? Executive sponsorship is not optional — a PMO without a senior champion will be ignored when it matters most. The sponsor should be named in the charter and should have signed it.

Resources

What headcount, budget, and tooling does the PMO have? A charter that describes ambitious services without the resources to deliver them is a document for disappointment. Be realistic about what you can actually do with what you have.

Success measures

How will you know the PMO is working? Identify three to five measurable outcomes — not activities. “Produced 12 portfolio reports” is an activity. “Leadership confidence in portfolio visibility increased from 3/10 to 7/10 within 12 months” is an outcome. The difference matters when you’re justifying your existence at year-end.

Getting it signed off

A PMO charter that isn’t formally approved is just a document. It needs sign-off from your executive sponsor at minimum — ideally from the leadership team it will serve.

The sign-off process is as valuable as the document itself. Walking your sponsor through the charter forces a conversation about expectations, authority, and resources before you start. Disagreements that surface here are far cheaper to resolve than disagreements that surface six months in when you’re trying to enforce a standard nobody agreed to.

Some PMO managers avoid this conversation because they’re worried about pushback. That’s backwards — pushback before you start means you can adapt. Pushback after you’ve built something means you’re starting over.

Keeping it current

A charter isn’t written once and filed. Revisit it annually, or whenever something significant changes — new executive sponsor, major shift in organisational priorities, significant change in PMO scope. An outdated charter that no longer reflects reality is worse than no charter at all, because it creates false expectations on both sides.