A hospital capital program makes thousands of decisions across a five-to-eight-year lifecycle, and the ones that sink a project are rarely the loud ones — they are the routine choices made by the wrong person, at the wrong altitude, or left to age until they fall onto the critical path. Decision rights, an escalation ladder, and a lifecycle-spanning RACI are the three instruments that govern who decides what, when an unresolved item must move up, and how accountability shifts as the program advances from strategy to go-live.
Where the governance bodies (executive sponsor, steering committee, program/project teams) and the roles (owner, owner's rep, A/E, CM/GC, activation, clinical, biomed/IT, supply chain) are defined is the subject of the companion Articles on governance structure and the integrated PMO. This Article assumes those bodies and roles exist and concentrates on the decision machinery that runs across them.
Decision quality and speed start with a decision-rights matrix that, for each decision type, names exactly one person who is Accountable, identifies who is Responsible for doing the work, and sets the authority threshold at which the decision must escalate. The discipline is to fix these before design mobilizes, so that no decision is improvised in the moment and no decision quietly defaults to whoever happens to be in the room.
The most useful way to bound authority is to tie change approval to dollar bands and risk triggers in combination. A typical delegation structure:
| Authority level | Approves changes | Constraints |
|---|---|---|
| Project/workstream team | Up to ~$50K | Within existing contingency only |
| Steering committee (PSC) | Up to a delegated limit (commonly $250K–$500K, or a defined contingency-draw percentage) | Within board-delegated authority |
| Board / capital committee | Above the PSC limit, or any change touching bed count, licensed services, life-safety strategy, or CON scope | May re-trigger Certificate of Need or state DOH review |
The dollar bands are illustrative and must be calibrated to program size; the risk triggers are the part that does not scale away. Regardless of dollar value, certain changes belong at the board because they alter what the facility is or how it is regulated — a change in bed count or licensed service lines can re-open the Certificate of Need approval in CON states, and a change to the life-safety strategy touches the NFPA 101 design basis that the AHJ approved. A $30,000 change that moves a smoke compartment boundary is a bigger decision than a $200,000 finish upgrade.
Stale decisions are a schedule killer in their own right, independent of how they are ultimately resolved. A correct decision delivered three weeks late can be as damaging as a wrong one, because it ages out an RFI that was sitting on the critical path. For this reason, timeliness is itself a decision right — the matrix should codify how fast each class of decision must be answered, not only who answers it.
Working targets that programs commonly adopt:
The PMO enforces timeliness by tracking decision aging — an open-decision log with the clock running on each item, surfaced on the program dashboard, so that an item approaching its service-level limit is visible before it becomes a slip rather than after. Aging is a leading indicator; a dashboard that shows only the count of open decisions, without their age, hides the decisions that are about to hurt.
Escalation should be engineered as a normal, blame-free mechanic, not an admission of failure. When teams treat escalation as a sign that someone dropped the ball, items stop moving up and instead sit unresolved until they detonate. The ladder follows the governance tiers:
Workstream lead → owner's PM → steering committee (PSC) → executive sponsor → board.
Each rung has a defined trigger, so escalation is rule-based rather than personality-driven. An item moves up when any of these conditions is met: