Governance is the decision-making spine of a hospital capital program. Because a new or expanded acute-care facility is at once a real-estate development, a regulated licensure event, a clinical-operations transformation, and a multi-hundred-million-dollar commitment, the owner must organize authority so the right people decide at the right altitude — and so decisions stay traceable when survey bodies later ask. This article defines the governance bodies and the roles that fill them; how decisions move between them — decision rights, escalation, RACI — is covered in decision rights escalation and raci.
Establish a three-tier structure and document it in a Project Governance Charter ratified at the earliest milestone — typically board capital approval or Certificate of Need (CON) filing where required. The tiers separate strategic, integrative, and executional decisions so escalations move predictably and meetings do not collapse into one over-attended forum.
| Tier | Body | Cadence | Owns |
|---|---|---|---|
| 1 | Sponsor + Board/Capital Committee | Milestone | Business case, funding, total budget, financing |
| 2 | Steering Committee (PSC) | Monthly | Integration; budget/schedule baselines; delegated scope changes |
| 3 | Program/Project Teams | Weekly | Execution by workstream |
A single named executive sponsor — commonly the CEO, COO, or a dedicated SVP of Facilities/Construction — owns the business case and is the ultimate decision authority below the board. The sponsor protects funding, removes obstacles the program team cannot, and is accountable to the board's finance/capital committee for budget, schedule, and the strategic intent (added ED capacity, a new service line, seismic or licensure compliance). The board retains authority over total budget, financing structure, and changes exceeding a defined threshold — e.g., more than 2–3% of GMP, or any scope change altering bed count or licensed service lines, which may re-trigger CON or state Department of Health (DOH) review.
A "phantom sponsor" who delegates everything is a recurring failure: without an engaged executive, escalations stall and the program absorbs avoidable schedule risk.
The PSC is a cross-functional body chaired by the sponsor or a designee. Membership spans CFO/finance, CNO and CMO (or service-line chiefs), facilities/real estate, the owner's project director, IT/IS, supply chain, compliance/regulatory, and infection prevention.
The PSC owns integration: it approves budget and schedule baselines, authorizes major scope changes within board-delegated limits, resolves cross-functional conflicts (clinical adjacency vs. structural grid vs. cost), and confirms tollgate readiness. Keep it to roughly 8–12 voting members — larger groups dilute accountability. A common failure is conflating the PSC with user/clinical advisory groups, which inform design but hold no budget authority; blurring the two produces design-by-committee and scope creep.
The execution layer is organized by workstream. On a large program a Program Director sits above several project managers, each owning a discrete project or phase (bed tower, central utility plant, ED renovation), plus integration workstreams that cut horizontally: design, construction, activation/operational readiness, IT/low-voltage, medical equipment/biomed, and regulatory/compliance. Each has a named lead, a charter, and a standing cadence. Critically, the activation workstream is stood up at design start, not at the end — operational readiness drives dozens of design decisions (RTLS coverage, nurse-call architecture, ADT/EHR integration, par locations) that are costly or impossible to retrofit.
Define each role in the charter with explicit scope and authority limits.