On a healthcare project, the approvals path is the schedule

Most capital projects treat permitting as a phase: design finishes, documents go in, a permit issues, construction begins. A healthcare facility does not fit that model. Several agencies review it at different moments, against different editions of the codes, and some of them can stop a project before design begins or keep a finished building empty. Their reviews are not one phase of the schedule. Taken together, they are its spine.

Accountability follows the license, not the contract

Owners are used to moving risk to whoever is best placed to manage it: design risk to the architect and engineers, construction risk to the builder, insurable risk to carriers. Regulatory exposure in healthcare resists that treatment. It attaches to the operating license and to the facility's standing with Medicare and with its accrediting organization, and those belong to the owner and operator.

When a state or accreditation surveyor finds a deficiency in a renovated department, the citation names the facility. Whoever caused the defect, the plan of correction is the facility's to write, and any consequence for its license or certification is the facility's to bear. A builder's liability is a private matter between builder and owner; the regulator does not see it. Every choice about how to govern a healthcare project follows from that asymmetry.

Many authorities review one building, each on its own terms

The list depends on the state, the facility type and the scope, but a healthcare project can pass through most of these:

• Certificate of need, in states that keep a CON program, where new services, beds, major equipment or capital spending above a set threshold require approval before the project may go forward.
• The local authority having jurisdiction, meaning the building and fire officials who issue permits and inspect under the locally adopted codes.
• State health department plan review, in many states, against the edition of the FGI Guidelines and the life safety codes that the state has adopted, sometimes followed by construction-phase and pre-occupancy inspections.
• Specialized state programs, such as radiation control review of shielding for imaging and therapy rooms, and board of pharmacy oversight of compounding spaces subject to USP 797 and USP 800.
• Licensure of the facility or the new service, which can carry its own survey before patients are admitted.
• Medicare certification, through the state survey agency or an accrediting organization with CMS deeming authority, measured against the Conditions of Participation and the editions of NFPA 101 and NFPA 99 that CMS has adopted.

As a rule these reviewers do not coordinate. The local code edition and the edition adopted by the state health department can differ, and a design one reviewer accepts can draw comments from another. Ambulatory projects add a classification question that decides which of these reviews apply at all: ambulatory health care occupancy or business occupancy, licensed or unlicensed, certified or not. Senior living adds the level-of-care license the building has to be designed to support, and behavioral health adds state program requirements tied to the patient population served.

Gates set the critical path, and gates do not compress

The distinction that matters for planning is between a risk and a gate. A risk can be priced, mitigated or carried. A gate is a point the project cannot pass until someone outside it acts: CON approval before commitment, plan approval before construction, inspection before concealment, survey before admission. More crews on site do nothing to shorten a state agency's review queue.

Gates therefore belong on the critical path, each with a realistic duration, an allowance for resubmission and a named person responsible for the submission. A schedule that shows them as zero-duration milestones is not a schedule for a healthcare building.

The path has to be mapped before the design schedule exists

Because the gates are fixed in sequence and largely beyond the owner's control, the most valuable early step an owner can take is to set every one of them out in order: each submission, review, inspection and survey standing between the present decision and the first patient, with its dependencies and the edition of each standard that will be applied.

A map of that kind shapes the project instead of describing it. It shows which design packages must be finished first because a review depends on them. It identifies reviews that can begin while design continues. It exposes conflicts, such as a phasing plan that creates an interim condition the state will not license, or a scope increase that crosses a CON threshold. And it gives proper weight to the end of the project, where inspections, testing, licensure and certification surveys sit between construction completion and opening, beyond any builder's power to accelerate.

Those end-stage reviews are also where phased handbacks in a working hospital succeed or fail, as discussed in construction in an occupied facility. Several depend on equipment data: a shielding review cannot proceed without the selected machine's specifications, which is one reason equipment decisions have to lead design. Testing whether the map exists, and whether the opening date a board is shown was derived from it, is central to a readiness review before capital is committed.

A contract allocates the work of compliance, not the regulatory relationship

Contracts still matter, provided they are drafted with a clear view of their reach. They can make the design team responsible for designing to the applicable editions, supporting agency review and answering comments. They can make the builder responsible for code-compliant installation, readiness for inspection, complete documentation and the cost of correcting nonconforming work. They can require prompt notice when a compliance problem is found.

They cannot move the facility's relationship with its regulators. The owner signs the licensure application, hosts the survey and answers the findings. A claim against a builder can take years to resolve, while a plan of correction is due on the regulator's short clock. That gap is the case for verifying work while it is still visible, through above-ceiling observation before close-in, documentation of every penetration through fire and smoke barriers, and a log recording each deviation and its resolution, rather than relying on remedies later.

The compliance record is built during construction or not at all

Many life safety defects are invisible at opening. A barrier penetration sealed with the wrong system, a damper never connected to the alarm, a room whose pressure relationship shifted once the air system was rebalanced: problems like these tend to surface at a later survey or after an incident, often well after the builder has demobilized. At that point the facility pays for the correction first and pursues recovery second, and recovery depends on records.

Approved submittals, inspection reports, test and balance data, commissioning reports, life safety plans revised to as-built conditions, and a deviation log with every entry resolved serve two purposes at once. They are the facility's defense file and the baseline for maintaining its life safety program. They are as much a project deliverable as the rooms themselves.

Who decides, and who plans for the decision

None of this makes an owner, or anyone advising one, an interpreter of the codes. Interpretation belongs to the design professionals of record and the authorities having jurisdiction, and survey findings belong to CMS, state agencies and accrediting organizations. The owner's task is narrower and harder to hand off: knowing which reviews apply, starting each on time, giving each a realistic place in the schedule, and keeping the record that will be needed after opening. On a hospital, where nearly all of these reviews converge on a single building, that task is part of the foundation.