The Audit Finding Nobody Saw Coming
Your inspectors were on-site every day. Your daily reports were filed. The concrete passed every cylinder break. Then the project closes out — and the gaps appear. The building official's final inspection stalls because the special inspection final report doesn't cover everything the approved plans required. The clinic operator's licensing consultant asks for construction records your field team never knew they were supposed to produce. The work was done right. The paperwork tells a different story.
For operations leads and QA managers at CMT and special inspection firms in California, OSHPD 3 clinic projects are deceptively tricky — not because the oversight is heavier than a hospital job, but because it is differently shaped. Firms that spend most of their time on DSA school work or HCAI hospital work tend to import assumptions from those worlds, and nearly every routine miss on an OSHPD 3 project traces back to one of those imported assumptions. This article walks through the four most common ones.
What OSHPD 3 Actually Covers — and Who Enforces It
California's building code sorts regulated healthcare facilities into categories that carried over from HCAI's predecessor agency, OSHPD. In general terms: OSHPD 1 is general acute-care hospitals, subject to the seismic requirements of the Alfred E. Alquist Hospital Facilities Seismic Safety Act; OSHPD 2 is skilled nursing and intermediate-care facilities; OSHPD 3 is licensed clinics — primary care, specialty, surgical, and chronic dialysis clinics licensed under the Health and Safety Code; OSHPD 4 is correctional treatment centers; and OSHPD 5 is acute psychiatric hospitals eligible for alternate standards. The requirements for OSHPD 3 clinic construction live primarily in CBC Section 1226, and HCAI publishes per-clinic-type compliance checklists — Section 1226.6 for primary care clinics, 1226.8 for surgical clinics, 1226.9 for chronic dialysis — that designers and reviewers use to demonstrate compliance.
The Jurisdiction Fact Most Ops Teams Get Wrong
Here is the single most important operational fact about OSHPD 3, and the one most often missed: for a freestanding clinic building, the enforcing agency is the local building department — not HCAI. The city or county building official plan-checks the project, issues the permit, and inspects the construction. HCAI's own Code Application Notice 1-7-2100 spells this out: HCAI reviews and certifies clinic plans for OSHPD 3 compliance only when requested by the local building official or by the facility owner. Unless that request was made, there is no HCAI plan approval, no HCAI conditions of approval, and no HCAI field presence on your project at all.
That cuts both ways. Teams that assume "healthcare project = HCAI project" burn effort preparing for oversight that never arrives — while missing the requirements the local building official actually enforces. There is no continuously present inspector of record requirement the way there is on an OSHPD 1 hospital job; the documentary record your firm produces under CBC Chapter 17 is the compliance record. When it slips, no agency inspector is standing there to catch it in real time.
The Exception That Bites: Clinics Inside Hospital Buildings
The clean rule above applies to freestanding clinic buildings. A clinic located within a hospital building under HCAI jurisdiction is a different animal — work on it falls under HCAI as part of that building, per HCAI's jurisdiction guidance in CAN 2-0. This is why dispatch needs to distinguish projects by building and enforcing agency, not by client type. The same healthcare system can hand you two tenant-improvement projects in the same month — one in a medical office building (local jurisdiction), one on a hospital campus inside an OSHPD 1 structure (HCAI jurisdiction, HCAI-certified personnel, HCAI report forms). Inspectors who float between them without the project file making the distinction explicit will file the wrong paperwork on one of them.
Miss #1: Staffing an OSHPD 3 Job Like a Hospital Job
Because the enforcing agency is the local building official, special inspection on a freestanding OSHPD 3 project runs the way it does on any CBC Chapter 17 project: the approved plans and the statement of special inspections define what gets inspected, and the building official — not HCAI — decides which special inspectors are acceptable. Many jurisdictions maintain their own recognition or registration programs (Los Angeles' deputy inspector program is the best-known example). An inspector whose credentials satisfy HCAI or DSA is not automatically approved in every city and county.
The operational consequences run in both directions:
- Over-staffing: assigning HCAI-certified hospital inspectors — usually your scarcest, most expensive people — to a clinic TI that any locally approved ICC special inspector could cover. The margin on the project quietly disappears into credential overkill.
- Under-qualifying: dispatching an inspector who holds the right ICC certificates but isn't registered or approved with that specific jurisdiction. The work gets done, and then the building official declines to accept the reports.
Both failures happen at dispatch time, which is why credential matching belongs in the dispatch workflow itself — the argument we make in more depth in why CMT and special inspection firms need purpose-built field operations software. A dispatcher working from a spreadsheet cannot realistically check jurisdiction-specific approvals for every assignment on a forty-dispatch morning.
Miss #2: Certification Assumptions Imported From DSA Work
Firms with heavy K-12 and community college portfolios carry DSA habits into clinic work: DSA project inspector classes, DSA-accepted testing lab status, DSA reporting rhythms. None of it transfers automatically. The two regimes differ in who accepts the inspector, what continuous-versus-periodic inspection means for each material, and what the closeout package looks like — differences we've mapped side by side in our guide to DSA vs HCAI for California inspection firm ops leads. OSHPD 3 adds a third regime to the matrix: local-AHJ special inspection with healthcare-specific plan requirements layered on top.
The practical failure mode is subtle. A scheduler sees "dialysis clinic, structural steel, welding inspection" and assigns the same AWS-certified inspector who covered last month's school gym. The inspector is competent. But the school project ran under DSA acceptance and DSA forms, and this one runs under the City's deputy inspector registration and the City's report format — and nobody told the inspector, because nobody's system recorded the difference. The fix is unglamorous: the enforcing agency, the acceptance basis for each inspector, and the required report format need to be attributes of the project record that dispatch reads automatically, not tribal knowledge in a PM's head.
Miss #3: Documentation That Doesn't Match the Enforcing Authority
Report-form mismatches are the most common documentary finding on clinic work. Inspectors accustomed to DSA or HCAI hospital projects submit DSA-formatted or HCAI-formatted daily reports on a local-jurisdiction clinic project. The substance is usually fine; the form is wrong, and closeout is where it surfaces. Under CBC Chapter 17, special inspectors furnish reports to the building official and the registered design professional, and the project cannot close cleanly without a final report documenting that the special-inspected work was completed in conformance with the approved construction documents. If your dailies were filed on the wrong template, or your final report's scope list doesn't reconcile against the statement of special inspections, expect the building official to bounce it.
Two other documentation gaps recur on OSHPD 3 projects specifically:
- The 1226 compliance record. The clinic operator's path to licensure depends on demonstrating the space was built to CBC 1226 requirements for its clinic type. The HCAI compliance checklists are primarily plan-stage artifacts — but licensing reviews and future tenant changes routinely reach back for construction-phase evidence. If your field records can't be retrieved and mapped to the project years later, your client feels that pain, and remembers where it came from.
- Mixed-authority paper trails. When an owner did request HCAI plan review on a clinic (it happens, particularly with hospital-system owners standardizing their portfolio), the project carries HCAI-certified plans enforced by a local building official. Field teams need to know which authority's expectations govern which artifact — and that only works if someone recorded it at project setup.
Miss #4: Losing the Thread Between Dispatch, Field, and Closeout
Every gap above is individually survivable. What turns them into audit findings is fragmentation: the dispatch lives in a scheduling tool, the daily report lives in a PDF on someone's laptop, the inspector's jurisdiction approvals live in an HR folder, and the closeout package gets assembled months later by someone who wasn't on the project. On hospital work, HCAI's continuous field presence forces a certain discipline. On OSHPD 3 work, nobody external is enforcing your record-keeping until the moment it's too late to fix.
The ops-level countermeasures are the same ones that pay off across every project type, and they're worth evaluating deliberately when you select tooling — our buyer's checklist for evaluating inspection dispatch software covers the full list. For clinic work specifically:
- Record the enforcing agency on every project — local AHJ, DSA, or HCAI — and make it visible on the dispatch and the inspector's assignment, not just the project brief.
- Track jurisdiction-specific inspector approvals (city registrations, deputy inspector cards, agency acceptances) as first-class credentials with expiration dates, so dispatch can match against them the same way it matches ACI and ICC certs.
- Tie every daily report to its dispatch record so the closeout package assembles itself from the project timeline instead of from memory.
- Reconcile the final report scope against the statement of special inspections before you tell the building official you're done — not after they tell you you're not.
OSHPD 3 projects reward firms that treat jurisdiction as data. The firms that struggle are the ones treating it as something everyone just knows.
Disclaimer: This article is for general informational purposes only and is not legal or code-compliance advice. OSHPD categories, jurisdiction, plan review, special inspection, and licensing requirements vary by project, building, jurisdiction, and agency direction, and code provisions change between editions. Firms should verify requirements with the enforcing agency, HCAI, the registered design professional, or qualified counsel before relying on any interpretation here.