HCAI (formerly OSHPD) Paperwork, Explained

What California healthcare construction actually requires of the record — the Inspector of Record, the TIO Program, verified reports, and why a change has to be an approved Amended Construction Document before it is built.

The thing that makes healthcare work different

On most commercial jobs the paperwork describes the work. On a California healthcare project regulated by HCAI — the Department of Health Care Access and Information, which was called OSHPD until 2021 — the paperwork is a condition of the work.

That single difference is what catches contractors moving into this market from ordinary commercial construction. The building department model, where you build it and an inspector signs it off afterwards, does not apply. Here the approved documents come first, and the record proving conformance is filed as you go.

The Inspector of Record is not your inspector

Healthcare projects require an Inspector of Record. The IOR is approved by the hospital's governing board and employed by the facility — not by the contractor — and works under the direction of the design professional of record.

They are on the job continuously. HCAI's own construction-observation guidance describes the expectation as adequate, competent and continuous inspection, and says HCAI field staff visit periodically to monitor the IOR's performance and to document where that inspection is not adequate, competent or continuous.

For a contractor the practical consequence is simple: the IOR is a full-time party to your job with an independent duty, and they need to be able to see what you did and when. A record they cannot follow is a problem for them before it is a problem for you.

The TIO Program comes before construction

Healthcare projects run under a Testing, Inspection and Observation Program, which is submitted and approved before construction begins. It sets out what will be tested and inspected, by whom, and what gets filed.

It is maintained by the architect or engineer in responsible charge, and the responsible parties file verified reports in accordance with it. The verified report is the mechanism by which each party states, on the record, that the work they were responsible for conforms to the approved documents.

Whatever tool you use, the TIO Program is the list your filing has to satisfy. It is worth reading at mobilization rather than at closeout.

A change is not a change until the documents are amended

This is the rule that costs money when it is learned late. HCAI's administrative FAQs put it plainly: work shall be executed in substantial conformance with the construction documents approved by the Office, and changes in the work shall be made by Amended Construction Documents approved by the Office.

Read that as a sequence rather than as paperwork. The ACD is approved, and then the change is built. Field-directing a change and papering it afterwards is not a slow version of the right process; it is a different process, and it can put work in the ground that the approved documents do not describe.

HCAI also cautions that added scope may constitute a new project rather than a change to the existing one, and advises talking to the plan review supervisor before submitting.

Deferred approvals

Some elements — commonly ones that depend on a subcontractor's engineering — are deferred rather than approved with the original permit set. They still have to be submitted and approved before that portion of the work proceeds, and HCAI's FAQs point to the California Administrative Code for the stamping and signature requirements on deferred submittals.

On a schedule, a deferred approval behaves like a long-lead item that happens to be made of paper. Treat it as procurement.

What this means for how you keep the record

• The approved document set, and its revision, is the reference for everything. Which revision an answer was given against matters as much as the answer.
• An RFI response that changes the work is a signal that an ACD may be required — not a license to proceed.
• Verified reports and inspection records are filed as the work happens, by the party responsible for it. Reconstructing them later is both harder and less credible.
• The IOR needs continuous visibility, not a monthly summary.

This is the reasoning behind how BuildControl is built: every answer is attached to the question it answers, every record carries who filed it and when, and nothing is reconstructed at closeout.

If you are moving into healthcare work

The discipline is heavier than commercial, and it is learnable. The contractors who struggle are not the ones who cannot build it — they are the ones who run the job the way they run a tenant improvement and discover at closeout that the record does not support what was built.

Start with the TIO Program and the approved set. Everything else follows from those two.

This is general information, not legal or regulatory advice, and HCAI's requirements change. Confirm anything here against HCAI's current published guidance and your project's own approved documents before relying on it.