A Temporary Certificate of Occupancy sits at the end of most hospital construction schedules as a single milestone, one bar, a few days of assumed duration, right before the phase transition date everyone is counting on. That single bar is hiding a sequence of separate life safety inspections, each with its own authority having jurisdiction, its own scheduling constraints, and its own real chance of requiring a re-inspection. Treating it as one milestone instead of a sequence is one of the most common reasons hospital phase transition dates slip in the final weeks.

What Actually Sits Inside “TCO Inspection”

Depending on jurisdiction and project scope, a hospital seeking a Temporary Certificate of Occupancy typically needs sign-off from several distinct inspection authorities, each evaluating a different system. Fire alarm system testing and acceptance, confirming detection and notification devices function correctly and interface properly with the building’s fire alarm panel. Sprinkler system testing, confirming coverage and water flow meet code requirements for the space. Egress and life safety walkthrough, confirming exit paths, signage, and emergency lighting meet requirements. Smoke barrier and compartmentation verification, particularly relevant in a healthcare occupancy where smoke compartments are a core life safety strategy. And in many jurisdictions, a separate building department inspection distinct from the fire marshal’s life safety walkthrough.

Each of these is a separate scheduled event, often requiring a different inspector or inspecting authority, and each carries its own real possibility of a failed inspection requiring correction and re-inspection before it can be signed off.

Why Compressing These Into One Milestone Creates Real Schedule Risk

Inspector scheduling itself is an external dependency the project doesn’t control. Fire marshals and other authorities having jurisdiction have their own scheduling constraints and their own queue of other inspections across other projects. A schedule that assumes an inspection can be booked and completed within a few days of construction completion is assuming an availability the inspecting authority hasn’t actually confirmed.

A failed inspection on any one system can hold up the entire TCO, not just that system. If the fire alarm inspection passes but the sprinkler inspection reveals a coverage gap, the TCO doesn’t get issued for the systems that passed while the sprinkler issue is corrected. The entire occupancy approval typically waits on all required inspections passing, which means the schedule risk of any single inspection failing effectively becomes the schedule risk of the whole milestone.

Correction and re-inspection cycles have real duration that a generic milestone doesn’t capture. A failed inspection triggers a correction, which then requires the inspecting authority to return and re-verify, and that return visit is subject to the same external scheduling constraint as the original inspection. A schedule that shows TCO as a single few-day milestone, with no explicit allowance for a potential failed inspection and re-inspection cycle, is showing a best case scenario as if it were the only scenario.

How to Build Real Float Around This Milestone

The master schedule should show each required inspection as its own activity, with its own predecessor requirements, tied to the actual completion of the specific system being inspected rather than to general construction completion. Scheduling coordination with each authority having jurisdiction should happen well ahead of the anticipated inspection date, treating inspector availability as a real external dependency to be confirmed, not assumed. And the schedule should carry explicit float for at least one potential correction and re-inspection cycle on the systems most likely to have an issue, rather than assuming every inspection passes on the first attempt.

A hospital phase transition date built on this level of specificity is a realistic date. One built on a single generic “TCO inspection” bar is a hope.

---

Frequently Asked Questions

What inspections are typically required for a hospital to receive a Temporary Certificate of Occupancy? Common requirements include fire alarm system testing and acceptance, sprinkler system testing, an egress and life safety walkthrough, smoke barrier and compartmentation verification, and in many jurisdictions a separate building department inspection, each potentially requiring a different inspecting authority.

Why do hospital construction schedules often underestimate the time needed for TCO inspections? Because they’re frequently shown as a single generic milestone rather than a sequence of separate inspections, each with its own scheduling constraint tied to inspector availability and its own real risk of requiring a correction and re-inspection cycle if an issue is found.

Can a failed inspection on one system delay the entire occupancy approval? Yes. A Temporary Certificate of Occupancy typically requires all applicable inspections to pass. A failure on any single system, such as a sprinkler coverage gap, generally holds up the overall approval even if other systems like fire alarm passed inspection.

How should float be built into the schedule for life safety inspections? Each required inspection should appear as its own scheduled activity tied to the completion of the specific system it evaluates, with coordination for inspector availability confirmed well in advance, and explicit float reserved for at least one potential correction and re-inspection cycle rather than assuming a first-attempt pass on every inspection.