ROMAN Consulting Group
Fractional PMO
Every capital project runs the same core governance functions, alignment, risk, performance, and communications, whether anyone has clearly assigned them or not. Most owner organizations already flex their governance staffing informally; almost none have decided to do it on purpose. ROMAN Consulting Group provides fractional PMO support, formalizing that flex into a deliberate model, sized to what the project actually needs, without the overhead of building a full department.
What Is a Fractional PMO?
A fractional PMO provides dedicated ownership of specific project management office functions, without requiring an owner to build or staff a full in-house department. It does not mean lighter governance, it means the same twelve functions, sized to complexity, staffed through a deliberate model that mixes dedicated and shared coverage rather than a single fixed headcount. Nor is it outsourcing in the usual sense: a fractional PMO can involve external support, internal staff shared across a portfolio, or a mix of both. The defining feature isn't who does the work, it's that governance capacity scales to what the project actually needs, on purpose, with a documented model behind the decision.
Our Approach
Function-by-Function Clarity — establishing exactly which of the twelve PMO functions are in scope, and confirming clear ownership for each, rather than leaving functions like Risk or Communications informally absorbed into someone's existing workload
Accountability, Not Just Coverage — assigning one accountable name to every function, even where execution hours are shared, with a defined response-time expectation, a named backup for any function carrying real schedule risk, and a cap on how many active projects a single shared resource can realistically cover
Authority, Not Just Attention — confirming each function's owner has real standing to escalate a variance or hold a gate, not just visibility into it. A resource that only monitors and reports is providing coverage without governance; that authority has to be assigned explicitly, whether it sits with the fractional resource directly or routes through a named executive sponsor
Complexity-Based Sizing, Reassessed Over Time — right-sizing governance intensity to the project's actual complexity per CII research, and revisiting that sizing when a defined trigger occurs, a JV partner exits, a regulatory requirement shifts, a variation order lands, or schedule variance crosses a set threshold, rather than sizing once at sanction and never again
Fractional PMO support typically takes one of three structural forms, and most owners don't need to commit to all three at once:
Retained advisory — external coverage for a specific function, best suited to continuous attention on something like Risk or Cost, ending when renewed or scaled down as needed
Internal split role — staff time formally split and protected, best suited to steady work that doesn't need a full-time seat
Defined-period surge — temporary support for a complexity spike, such as a JV negotiation or a permitting push, that either winds down when the spike passes or converts into a standing model if the complexity turns out not to have been temporary
Most owners starting from zero begin with retained advisory on a single high-risk function, most often Risk or Cost, since it's the lowest-commitment way to test whether formalized coverage actually changes anything before extending the model further.
Built for Owners Without a Full PMO
Owners and developers who don't have a dedicated PMO, or whose PMO coverage happens informally rather than by design. Organizations where the same one or two people are, in practice, accountable for most PMO functions, a common early sign of under-resourced governance. Smaller owners, developers, and startups needing project infrastructure without the overhead of a full in-house team.
Case Study
An owner organization's project controls setup had seven documents, each with a single named owner, but two functions, Communications and Risk, had no register at all. Neither gap was a systems problem; the underlying tools were sound. ROMAN's fractional PMO support assigned a retained advisory resource to Risk, given how directly a stale risk register turns into unescalated findings, and folded Communications into an internal split role, since it ran continuously rather than spiking and needed a protected slice of someone's time more than a dedicated seat. Neither fix required new headcount. On the next major decision gate, the newly current risk register surfaced an exposure that had been informally known but never formally raised, giving the capital committee a clearer picture before approval rather than after.
Frequently Asked Questions
Q. Is a fractional PMO the same as outsourcing?
A. Not necessarily. A fractional PMO can involve external support, internal staff shared across a portfolio, or a mix of both. The defining feature is that governance capacity scales to what the project needs rather than following a fixed headcount, regardless of who does the work.
Q. Does shared coverage mean shared accountability?
A. It shouldn't. Updates under shared ownership aren't always clear or correct, since no one person is accountable when several people could have made the update. A working fractional model assigns one accountable name to each function, with a defined backup where schedule risk is real.
Q. How is fractional PMO different from Fractional Project Controls?
A. Fractional PMO focuses on governance, decisions, oversight, and accountability, across the full twelve-function framework. Fractional Project Controls focuses specifically on the operational estimating, cost, schedule, and progress tracking discipline within a project, pre-FID.
Related Reading
