Governance only works if something runs it day to day. The integrated Project Management Office (PMO) is the operating system of a hospital capital program — the body that maintains the single source of truth, enforces the meeting and reporting cadence, and stages every phase transition through formal tollgates. Equally foundational is the question that precedes staffing the PMO at all: who actually runs the owner's program, and whose payroll they sit on.

This article covers the PMO operating system and the program-management sourcing decision. The companion Articles in this chapter cover the governance bodies and role definitions (Governance Structure & Roles) and the formal authority instruments — decision-rights matrices, escalation ladders, and the lifecycle RACI (Decision Rights, Escalation & RACI). The cadence and tollgates described here are how those structures are exercised over a five-to-eight-year lifecycle.

The integrated PMO as the program's operating system

An integrated PMO is the standing function that converts a chartered governance structure into running practice. Ideally it operates as a co-located or virtual Big Room / Integrated Project Delivery environment where the owner, designers, builders, and key trades work against shared, live information rather than periodically reconciled silos.

The PMO's core obligation is a single source of truth spanning:

• Schedule — the integrated master program timeline, critical path, and float.
• Budget — baseline, commitments, forecast-at-completion, and contingency burn.
• Risk and issues — the standing risk and issue logs with named owners and due dates.
• Decisions — the decision log, including open-decision aging.
• Document control — the controlled-document protocol (drawings, submittals, RFIs, change orders) so everyone is working from the current revision.

When schedule, budget, risk, decisions, and documents live in separate, manually reconciled places, the program loses traceability — and traceability is exactly what survey bodies and the board both expect. A program that cannot show who decided what, when, and against which document is one that will struggle to defend a value-engineering cut at survey two years later. The PMO exists to make that trail automatic rather than reconstructed under pressure.

Layered meeting cadence — each tier at its own altitude

The fastest way to wreck a program's calendar is to run every conversation in one over-attended forum. A working PMO layers cadence so each tier meets at its own frequency and altitude, and so escalation moves predictably between layers rather than collapsing upward into a single meeting.

The discipline that keeps this from becoming meeting overload is non-redundancy: each forum owns a distinct altitude of decision. Field meetings do not re-litigate budget baselines; the PSC does not coordinate trade sequencing. When a chapter is being chewed in the wrong forum, that is itself a governance signal — it usually means a decision is escalating because no one at the correct tier has been empowered to make it.

Reporting — trend, don't just snapshot

The PMO publishes a one-page program dashboard on a fixed cycle. The dashboard is not a status email; it is the instrument the PSC uses to confirm the program is on baseline and the board uses to confirm its capital is protected. A complete dashboard covers:

• Budget — actuals and forecast versus baseline, plus contingency burn.
• Schedule — status and float on the critical path.
• Risks and issues — the top items, each with an owner and a due date.