A PMO assessment is a structured review of how well a project management office actually performs its job, scored across a fixed set of domains so the result can be compared year over year. It is not the same thing as asking the PMO how it thinks it is doing. The value comes from the evidence: what the intake queue looks like, whether the prioritization list matches where people are really working, and whether anyone outside the office can name a decision the last portfolio review produced.
Key takeaways
- Score six domains: intake, prioritization, governance, resource and capacity management, reporting, and delivery support. Fewer than six and you miss a failure mode; more and nobody finishes the assessment.
- Ask the questions of delivery leads, finance, and sponsors, not only of the PMO. The gap between the two sets of answers is the real finding.
- Score each question 0 to 3 against observable evidence, not opinion. "We have a process" scores 1. "The process ran on the last eleven requests and here they are" scores 3.
- A PMO assessment answers "is this office working"; a PMO maturity assessment answers "how capable is it on a 1 to 5 scale". They use the same evidence and different scales.
- Three weeks is enough: one week to gather evidence, one to interview, one to score and write up. Anything longer stops being an assessment and becomes a project.
- The output that matters is three prioritized gaps with owners and dates, not a heat map.
Last updated July 2026.
What is a PMO assessment?
A PMO assessment is a periodic evaluation of a project management office against defined criteria, covering the processes it owns, the value it delivers, and how the rest of the organization experiences it. A typical assessment gathers evidence from systems and documents, interviews the people the PMO serves, scores each domain against a fixed scale, and ends with a short list of gaps ranked by how much they cost the business.
The reason organizations run one is almost always friction. Delivery leads complain that the reporting burden buys them nothing. Finance cannot reconcile the portfolio spend to the project list. An executive asks why the office costs what it costs. An assessment converts that vague dissatisfaction into specific, testable statements, which is the only way to argue about it productively. If your office is new enough that there is nothing yet to assess, the sequence in how to set up a PMO comes first.
PMO assessment vs PMO maturity assessment
The two overlap enough that people use the terms interchangeably, and the distinction is still worth holding. A maturity assessment rates capability against a published ladder, usually a five-level scale from ad hoc to optimizing, and produces a number you can benchmark. A PMO assessment is broader and more situational: it asks whether this office, with this mandate, in this organization, is doing what it was set up to do.
| Question | PMO assessment | PMO maturity assessment |
|---|---|---|
| Core question | Is this PMO working? | How capable is this PMO? |
| Scale | Domain scores against your own criteria | Levels 1 to 5 against a published model |
| Reference | The office's charter and mandate | OPM3, P3M3, or a similar framework |
| Typical trigger | Complaints, a new CIO, a cost review | An improvement program or a benchmark request |
| Best for | Deciding what to fix next quarter | Tracking capability over several years |
| Risk | Turns into a blame exercise | Turns into scoring theater |
In practice most teams run one exercise and report it two ways. Gather the evidence once, score your six domains for the improvement plan, then map those scores onto the ladder described in the PMO maturity model when an executive wants a single number.
The six domains a PMO assessment should score
Assess what the office actually owns. If your PMO does not run intake, do not score it on intake, score it on what it was chartered to do. For most offices the chartered work falls into these six areas, and the same six map cleanly onto the standard set of PMO functions.
| Domain | What good looks like | The evidence to pull |
|---|---|---|
| Intake | Every request enters one front door in a comparable format; screening is fast and visible. | The last 20 requests, their submission dates, and how long each waited before a decision. |
| Prioritization | A ranked list exists, the ranking rules are written down, and the ranking survives contact with senior people. | The current ranked list, the criteria used, and the last three ranking changes with their reasons. |
| Governance | Named forums make named decisions on a schedule, and the decisions are recorded and honored. | The last six meeting packs and the decision log. Count decisions, not agenda items. |
| Resource and capacity | Someone can say what the organization can deliver next quarter and be roughly right. | The capacity view, and a comparison of planned versus actual allocation on five projects. |
| Reporting | Reports drive decisions; status is trusted enough that bad news arrives early. | Every recurring report, its audience, and the last decision each one changed. |
| Delivery support | Teams get real help: templates, facilitation, escalation, and coaching they would ask for again. | What support was requested in the last quarter, and what was delivered. |
Two of these carry most of the diagnostic weight. Reporting, because a report nobody uses is the clearest sign of an office optimizing for activity. And governance, because an office with no decision rights cannot fix anything it finds. The decision rights themselves belong in project portfolio governance, and if they were never written down, that is your first finding.
The PMO assessment questionnaire
Run the same questions past three audiences: the PMO team, the delivery leads and project managers the office serves, and the executive sponsors and finance partners who consume its output. Ask for examples, not ratings. Where the three groups disagree, you have found something worth writing down.
Intake and demand
- How does a new project get started here? Walk me through the last one.
- What happens to a request that arrives without a sponsor or a budget?
- How long does a typical request wait before someone decides on it?
- How much work is currently running that never went through intake?
Prioritization
- Where is the ranked list of active and proposed work, and when was it last updated?
- What criteria decide the order, and who agreed to them?
- When did we last stop or defer something because of the ranking?
- If two projects need the same person next month, who decides and how?
Governance
- Which forum can approve funding, change scope, or stop a project?
- What decisions did that forum make in its last three meetings?
- How long does it take to get an escalation resolved?
- Has a decision made in governance ever been quietly reversed outside it?
Resource and capacity
- How many projects is an average delivery person assigned to right now?
- Can you tell me what capacity is available for new work next quarter?
- How accurate was last quarter's capacity view, checked against what happened?
Reporting
- List every recurring report the PMO produces and name the decision each one supports.
- How long does status reporting take a project manager each week?
- When a project first goes red, how many weeks earlier did the team know?
- Which report would you miss if it stopped tomorrow?
Delivery support and value
- What has the PMO done for you in the last quarter that you valued?
- What does the PMO ask of you that you would drop if you could?
- If the office disappeared on Monday, what would break first?
That last question is the single most useful one in the set. An office where nobody can name what would break is an office that documents delivery instead of enabling it, which is the failure pattern described at length in PMO best practices.
The PMO assessment scorecard
Score each domain 0 to 3 on evidence. Keep the scale short: four values force a judgment, where a ten point scale invites everything to land on six or seven.
| Score | Meaning | Test |
|---|---|---|
| 0 | Absent | Nothing exists. Nobody claims otherwise. |
| 1 | Documented | A process exists on paper. Recent work did not follow it. |
| 2 | Practiced | Most recent work followed it. Exceptions happen and are not tracked. |
| 3 | Relied on | It runs consistently, produces evidence, and people outside the PMO depend on it. |
Weight the domains by your charter rather than scoring them equally. An office chartered for delivery assurance should carry more weight on governance and reporting; a resource-focused office should carry more on capacity. A simple worked total looks like this.
| Domain | Weight | Score (0 to 3) | Weighted |
|---|---|---|---|
| Intake | 15% | 2 | 0.30 |
| Prioritization | 25% | 1 | 0.25 |
| Governance | 20% | 2 | 0.40 |
| Resource and capacity | 20% | 1 | 0.20 |
| Reporting | 10% | 3 | 0.30 |
| Delivery support | 10% | 2 | 0.20 |
| Total | 100% | 1.65 of 3.0 |
These numbers are illustrative, but the shape is one you will meet often: strong reporting, weak prioritization, weak capacity. It describes an office that is good at describing the portfolio and has no authority to change it.
How to run a PMO assessment in three weeks
Week one, gather evidence. Pull the artifacts listed in the domain table before you talk to anyone. Requests, the ranked list, six meeting packs, the decision log, the capacity view, every recurring report. What you cannot find is already a result.
Week two, interview. Six to ten conversations, 45 minutes each, using the questionnaire. Include at least three people who do not work in the PMO and one who is openly skeptical of it. Take quotes.
Week three, score and write up. Score against evidence, not impressions. Write no more than four pages: the scores, the three gaps that cost the most, what each would take to close, and who owns it. Attach the scorecard.
Then hand it over and stop. The trap is turning the assessment into a transformation program in the same document. Three gaps, three owners, three dates, reassessed in twelve months.
What to do with the findings
Rank the gaps by cost, not by score. A prioritization domain scoring 1 in an organization running 40 simultaneous projects with 25 people is expensive; a reporting domain scoring 1 in an office of four with a single sponsor may cost nothing at all. Pick the two gaps with the biggest business consequence and fund those. Leave the rest documented and untouched.
Then check the mandate itself. A surprising share of PMO assessments conclude that the office is executing well against the wrong charter: it was set up to standardize methodology and the organization now needs it to allocate capacity. That is a re-chartering conversation, not an improvement backlog, and it belongs with the sponsor. The document to revisit is the PMO charter. If the reporting domain scored well but nobody uses the output, rebuild the report set around decisions using PMO reporting and portfolio dashboards.
Frequently asked questions
What questions should a PMO assessment ask?
A PMO assessment should ask evidence-based questions across intake, prioritization, governance, resource management, reporting, and delivery support: how does work get started, what ranks it, which forum decides, who knows what capacity exists, which report changed a decision, and what would break if the office disappeared. Ask for examples rather than ratings.
How often should you assess a PMO?
Once a year is right for most offices. Annual cadence is long enough for improvement work to show results and short enough that the findings stay relevant. Assess sooner if the sponsor, the mandate, or the portfolio size changes materially, since all three change what "working well" means for the office.
Who should run a PMO assessment?
Either an internal reviewer outside the PMO, such as internal audit or a delivery leader from another business unit, or an external consultant. The PMO can run a self assessment for its own planning, but a self assessment cannot settle a question about the office's value, because the office is the interested party.
What is a PMO self assessment?
A PMO self assessment is the same exercise scored by the PMO team on its own work, usually annually and usually as an input to its improvement plan. It is faster and cheaper than an independent review and is useful for tracking progress. It carries little weight when leadership is questioning whether the office should exist.
What is a PMO assessment framework?
A PMO assessment framework is the fixed set of domains, questions, and scoring rules used so results are comparable across years and business units. Some teams adopt a published model such as P3M3 or OPM3; many build a lightweight framework of five or six domains scored 0 to 3. Consistency matters more than which framework you pick.
What should a PMO assessment template include?
A workable template has one row per question, grouped by domain, with columns for the evidence reviewed, the score, the person interviewed, and a note. Add a summary tab that weights domain scores into one total, and a findings tab with three prioritized gaps, each with an owner and a date. Anything more elaborate rarely gets filled in.
What is the difference between a PMO assessment and a PMO audit?
An assessment measures effectiveness against a mandate and produces improvement priorities. An audit tests compliance against a defined control set and produces findings that must be remediated. Audits are narrower, more formal, and usually run by a function with independence requirements. Most organizations want an assessment and ask for an audit.
Where this fits
An assessment is a checkpoint, not an achievement. It is most useful in the years when the office is under pressure, because it replaces argument with evidence, and least useful when it becomes an annual ritual producing the same heat map with better formatting. If the results tell you the office has drifted from what the organization needs, go back to first principles in what a project management office is, and rebuild the mandate from there.