PMO structure is the organizational design of the project management office: how the office is arranged as a unit, where it reports in the hierarchy, and how it is staffed. It is a different question from the PMO's authority type. The authority type (supportive, controlling, or directive) tells you what the office can enforce. The structure tells you how the office is physically organized across the business, whether one central team serves everyone or embedded teams serve each division, and who the head of the PMO answers to.
Getting the structure wrong is a quiet failure. An office with the right mandate but the wrong structure ends up too far from the projects to help, or so fragmented that no two divisions report the same way. This guide covers the three common structural models, where a PMO should report, how to size and staff it, and how to choose the model that fits your organization.
Key takeaways
- PMO structure (how the office is organized) is separate from PMO type (how much authority it holds). You choose both.
- The three structural models are centralized, decentralized, and hub-and-spoke. Match the model to how your business is organized, not to a textbook ideal.
- Where the PMO reports decides its influence. A PMO buried three levels down cannot steer the portfolio no matter how good its process is.
PMO structure vs PMO type: the difference
These two ideas get conflated constantly, so it is worth separating them before anything else. The PMO type describes the degree of control the office exerts over projects, and there are three: supportive, controlling, and directive. That distinction is covered in the project management office overview. PMO structure describes how the office is organized as an entity: is it one team, several teams, or a central team with satellites, and where does it sit in the org chart.
You choose both independently. A single centralized office can be supportive (advisory) or directive (running the work). A hub-and-spoke arrangement can enforce standards centrally while advising locally. Deciding the structure first, then the authority level, keeps the two conversations from muddying each other.
| Question | What it decides | The answer set |
|---|---|---|
| PMO type (authority) | How much control over how projects run | Supportive, controlling, directive |
| PMO structure (organization) | How the office is arranged and where it reports | Centralized, decentralized, hub-and-spoke |
| PMO scope (reach) | Which layer of work it governs | Project, program, portfolio, enterprise |
The three PMO structure types
Centralized PMO
A centralized PMO is a single, organization-wide office that owns the project management practice for the whole business. One team sets the standards, runs the governance cadence, and produces one consolidated view of every project. The strength of this model is consistency: reporting is standardized, executive oversight is straightforward, and audit or compliance readiness is easier because one office controls the process end to end.
The weakness is distance. A single central team can drift away from the realities of individual divisions, and if the organization is large or geographically spread, the office becomes a bottleneck. Centralized works best in smaller or single-site organizations, in businesses where standardization is the main problem to solve, and in regulated environments that need one auditable process.
Decentralized PMO
A decentralized structure places a separate PMO inside each division, business unit, or region, each reporting into its own local leadership. The advantage is proximity and speed: each office understands its unit's work, tailors its process to local needs, and makes decisions without waiting on a central body. This model fits large, diverse organizations where divisions run genuinely different kinds of projects.
The cost is fragmentation. Left alone, three decentralized PMOs will invent three different scoring models, three report formats, and three definitions of "on track," which makes portfolio-level comparison across the company nearly impossible. Decentralized structures need a deliberate mechanism to keep the units comparable, which is exactly what the third model provides.
Hub-and-spoke PMO
A hub-and-spoke PMO (sometimes called a federated model) is a hybrid: a central hub sets policy, standards, tooling, and the portfolio view, while satellite PMOs embedded in each division run the day-to-day support for their projects. The hub defines the rules; the spokes apply them locally. This is the model most large organizations converge on because it captures the consistency of centralization and the responsiveness of decentralization at the same time.
The design choice inside a hub-and-spoke model is how much authority the hub holds. In some organizations the hub is advisory, promoting best practice with no power to mandate. In others the hub has real authority to set policy the spokes must follow. The stronger the hub's mandate, the more the whole structure behaves like a centralized office with local delivery arms. When the hub sits at the enterprise level and governs the whole portfolio of programs, this arrangement is effectively an enterprise PMO or EPMO.
| Model | How it is arranged | Best for | Main risk |
|---|---|---|---|
| Centralized | One office serves the whole organization | Smaller or single-site firms; standardization needs | Too distant from local project reality; bottleneck |
| Decentralized | A separate PMO per division or region | Large, diverse orgs with very different work | Fragmentation; no comparable portfolio view |
| Hub-and-spoke | Central hub sets standards; satellites deliver locally | Large orgs that need consistency and local speed | Unclear hub authority; duplicated effort if roles blur |
Where should a PMO report?
The reporting line matters as much as the internal design, because it sets the ceiling on the PMO's influence. A PMO exists to steer the portfolio toward the highest-value work, and it cannot do that if it sits three levels below the people who fund projects. As a rule, the more strategic the PMO's mandate, the higher it should report.
An enterprise or portfolio PMO that governs funding and prioritization should report to a C-level executive, often the COO, CFO, or a chief strategy officer, and in some organizations directly to the CEO. A departmental PMO that supports one function's projects can report to the head of that function. The failure pattern to avoid is placing a PMO with a portfolio-steering mandate under a mid-level IT or delivery manager, where it has the responsibility to govern the portfolio but none of the standing to make the tradeoffs stick. When the PMO owns real prioritization and governance decisions, its reporting line has to reflect that, which ties directly to how project portfolio governance assigns decision rights.
How to structure and staff a PMO by size
Structure is not only the model on the org chart; it is also how many people staff the office and in what roles. A common mistake is copying a large enterprise's PMO structure into a company that runs a dozen projects, producing an office heavier than the portfolio it governs. Size the office to the portfolio.
| Portfolio size | Typical structure | Core staffing |
|---|---|---|
| Small (under ~15 projects) | Centralized, often part-time | A PMO lead, sometimes shared with another role |
| Mid (15 to 50 projects) | Centralized with dedicated staff | PMO manager, one or two analysts, a reporting owner |
| Large (50+ projects, multi-division) | Hub-and-spoke or decentralized | PMO director, central analysts, embedded coordinators per division |
Whatever the size, the roles inside the office follow a consistent pattern of responsibilities, from the PMO lead who owns the mandate down to analysts who run reporting and coordinators who support delivery. Those roles, and who owns what, are laid out in PMO roles and responsibilities. Structure decides how many of each you need and where they sit; the role definitions decide what each one does.
How to choose the right PMO structure
Choosing a structure is a matter of matching the office to the shape of the business, not chasing a best-in-class model. Three questions settle it in most cases. First, how is the organization itself arranged? A single-site company rarely needs anything beyond a centralized office; a multi-division conglomerate almost always needs satellites. Second, how different is the work across units? The more genuinely different the projects, the more a decentralized or hub-and-spoke model earns its complexity. Third, how much does the business need one comparable portfolio view? The stronger that need, the more the hub, or a fully centralized office, is the answer.
Whichever you pick, write the choice down. The structure, the reporting line, and the staffing should be captured in the office's founding document so they survive the first reorganization, which is one of the things a good PMO charter exists to record. And revisit the structure as the office matures: a startup-stage PMO that begins centralized often needs to move to hub-and-spoke as the portfolio grows, a transition the PMO maturity model helps you plan.
Frequently asked questions
What is a PMO structure?
A PMO structure is the organizational design of the project management office: how the office is arranged as a unit, where it reports in the hierarchy, and how it is staffed. It answers whether one central team serves the whole business, separate teams serve each division, or a central hub sets standards while satellite teams deliver locally. Structure is separate from PMO type, which describes how much authority the office holds.
What are the three types of PMO structure?
The three PMO structure types are centralized, decentralized, and hub-and-spoke. A centralized PMO is one office serving the whole organization. A decentralized PMO places a separate office inside each division or region. A hub-and-spoke PMO combines both: a central hub sets policy and standards while satellite offices deliver support locally. Most large organizations end up with the hub-and-spoke model because it balances consistency with local responsiveness.
Where should a PMO sit in the organization?
A PMO should report at a level that matches its mandate. An enterprise or portfolio PMO that governs funding and prioritization should report to a C-level executive such as the COO, CFO, or CEO. A departmental PMO supporting one function can report to that function's head. The common mistake is placing a portfolio-steering PMO under a mid-level manager, where it lacks the standing to enforce the tradeoffs it is responsible for.
What is the difference between PMO structure and PMO type?
PMO type describes how much authority the office has over projects: supportive (advisory), controlling (enforces standards), or directive (runs the projects). PMO structure describes how the office is organized as an entity: centralized, decentralized, or hub-and-spoke, and where it reports. Type is about control; structure is about organization. You choose both independently, so a centralized office can be supportive or directive, and a hub-and-spoke office can enforce standards centrally while advising locally.
How many people should a PMO have?
Staff a PMO to the size of the portfolio it governs, not to a fixed ratio. A small portfolio under roughly 15 projects may need only a single PMO lead, sometimes part-time. A mid-sized portfolio of 15 to 50 projects typically needs a manager plus one or two analysts and a reporting owner. A large, multi-division portfolio needs a director, central analysts, and coordinators embedded in each division. Oversizing the office relative to the portfolio is a common and costly error.