Uncontrolled change is the most common cause of hospital cost and schedule overruns — and the most dangerous, because a single modification can ripple silently into life-safety compartmentation, ventilation balance, or accreditation readiness. Change control exists to guarantee that no modification, from whatever source, is implemented without a documented, multi-disciplinary impact analysis and the right level of authorization.

Why change control is non-negotiable on acute-care projects

A generic construction change process treats change as a commercial event: scope shifts, cost adjusts, schedule moves, a change order is signed. On an acute-care project that framing is incomplete and unsafe. The same change that adds a few thousand dollars and a few days can also:

• Breach an FGI Guidelines clearance or room-area requirement;
• Disturb an ASHRAE 170 air-change rate or pressure relationship;
• Compromise an NFPA 101 Life Safety Code egress path, smoke compartment, or rated assembly;
• Invalidate an ADA/ABA accessibility provision;
• Force a re-submission to state DOH plan review (or an HCAI/OSHPD-style structured review where one operates) and a fresh AHJ inspection before the space can be occupied.

Because the consequence of a missed change can be a delayed licensure survey, a Life Safety Code deficiency cited at survey by The Joint Commission or DNV, or a space that cannot legally open, change control on a hospital is a patient-safety and regulatory-compliance discipline first, and a cost-management discipline second. Every owner-requested, design-evolution, regulatory-driven, and field-condition change must pass through one controlled gate.

The single change-control pipeline

Run one formal change-control process for the project — not a patchwork of trade-by-trade or discipline-by-discipline handling. The pipeline has a defined, auditable sequence:

1. Change identification — a need to modify scope, design, sequence, or specification is surfaced from any source.
2. Change request (CR) logged — the change is entered in the single change log with a unique ID and its source.
3. Impact analysis — the four-axis analysis (below) is completed, with the code-review flag set where applicable.
4. Review / disposition by the Change Control Board (CCB) — the board evaluates the analysis and decides.
5. Approval or rejection — at the authority tier the change's magnitude requires.
6. Incorporation into baselines — scope, budget, and schedule baselines are updated to reflect the approved change.
7. Execution and verification — the change is built and confirmed complete; the CR is closed.

No step is skippable. The discipline of incorporating approved changes back into the baselines is what keeps the project's scope, budget, and schedule of record trustworthy; skipping it produces the familiar end-of-project surprise where actual scope no longer matches the documents anyone is managing to.

Document types — keep them disciplined