Two Authorities, One Dispatch Board — and a Lot of Room for Error
Picture this: it's Monday morning, and your scheduler is filling the week's inspection assignments. One inspector is heading to a K–12 school addition. Another is covering a new hospital wing across town. Both are seasoned, certified professionals. But are they certified under the right authority for each project? If your answer is "I think so," you already have a compliance gap.
California construction materials testing and special inspection firms that work across public school, community college, and healthcare projects operate under two distinct regulatory regimes — the Division of the State Architect (DSA) and the Health Care Access and Information department (HCAI), formerly known as OSHPD. The two agencies share a broad mission — ensuring life-safety in critical public buildings — but their certification frameworks, documentation standards, and enforcement postures differ in ways that trip up even experienced operations leads.
This article breaks down those differences clearly, identifies the most common compliance gaps, and offers practical guidance for structuring inspector assignments before problems reach the field.
Governing Authority: Who Owns What
Division of the State Architect (DSA)
DSA has jurisdiction over K–12 public schools, community colleges, and state-owned essential services buildings under the California Education Code and the Field Act. Its mandate is to ensure that construction on these facilities meets the structural and fire-life-safety standards of the California Building Code as interpreted and enforced by DSA. On a DSA inspection project, the agency assigns a project inspector (PI) and requires that all special inspectors be approved by DSA before work begins.
DSA's regulatory framework is detailed in its program guidelines and IR (Interpretation of Regulations) bulletins, which govern everything from approved testing lab qualifications to the format of inspection cards and final close-out documentation.
HCAI (Formerly OSHPD)
HCAI governs the design, construction, and inspection of licensed healthcare facilities — acute care hospitals, skilled nursing facilities, and certain clinics — under the Alfred E. Alquist Hospital Facilities Seismic Safety Act. HCAI compliance is enforced through its own Office of Regulatory Compliance and the OSHPD 1–4 project classification system, which determines the level of oversight required based on facility type and project scope.
Unlike DSA, where the project inspector role carries a specific formal title, HCAI uses a Compliance Inspector model under which the agency's own compliance inspectors (CIs) have broad authority to stop work, require corrective action, and demand re-inspection. Your firm's special inspectors operate in close coordination with — and under the scrutiny of — HCAI's own field staff.
Certification Requirements: Where the Two Systems Diverge
This is where many multi-market firms encounter their most damaging blind spots. The certification pathways for California special inspection differ meaningfully between the two programs.
DSA Inspector Certification
DSA requires that special inspectors hold a DSA Special Inspector certification in the specific category of work being inspected — structural steel, reinforced concrete, masonry, soils, and so on. Certifications are issued per trade type, meaning an inspector certified for reinforced concrete is not automatically qualified to inspect structural masonry on the same project. Renewal cycles and continuing education requirements apply, and DSA maintains a public lookup tool that owners and project inspectors can — and do — use to verify your inspectors.
HCAI Inspector Certification
HCAI does not issue its own special inspector certifications in the same direct way. Instead, it recognizes inspectors who hold certifications from DSA or from approved third-party organizations such as ICC (International Code Council) and ACI (American Concrete Institute) for specific trade categories. However, HCAI projects carry additional expectations: inspectors must be familiar with HCAI-specific regulations found in Title 24, Part 1, the HCAI construction oversight manuals, and any project-specific special inspection programs approved by HCAI. Firms that assume a DSA-certified inspector is automatically ready for an HCAI compliance project without additional orientation have discovered, often painfully, that this assumption is wrong.
Furthermore, HCAI's OSHPD 1 projects (major acute care facilities) involve seismic anchorage and equipment inspection requirements that go well beyond typical school construction. Inspectors unfamiliar with HCAI's specific expectations for MEP anchorage, equipment anchorage, and OSHPD-specific concrete and steel details can generate nonconformance reports that delay a hospital project and damage your firm's standing with the agency.
Reporting and Documentation Expectations
DSA Documentation Requirements
DSA projects require structured daily inspection reports submitted on DSA-approved forms (or equivalent software output accepted by the project inspector). Reports must identify the DSA project number, the inspector's certification number and category, the work observed, materials sampled, test results, and any deviations from approved plans. The project inspector consolidates these reports as part of the official project record that DSA uses during closeout verification. A missing or incorrectly formatted report is not a minor inconvenience — it can hold up a certificate of occupancy.
HCAI Documentation Requirements
On HCAI projects, inspection reports must align with the project's HCAI-approved special inspection program, which is a formal document submitted at the start of construction. Inspectors must reference the specific inspection items listed in that program, log observations in a format the HCAI compliance inspector can cross-reference, and flag nonconformances formally rather than informally. HCAI has historically been more prescriptive than DSA about how nonconformances are tracked and resolved, and the agency's compliance inspectors have authority to independently require documentation they consider insufficient.
In practical terms, this means your firm needs separate report templates, separate QA review checklists, and separate closeout procedures for DSA and HCAI projects — and your field staff needs to know which template they are on before they show up in the morning.
Common Compliance Gaps When a Firm Works on Both
Firms that serve both school districts and healthcare systems — a common growth path in California — tend to encounter the same cluster of problems repeatedly.
- Certification category mismatches at dispatch: An inspector is sent to a hospital structural concrete pour holding only a DSA reinforced concrete certification, without verifying that their certification is recognized by HCAI for that project's special inspection program. The HCAI compliance inspector flags the issue on site.
- Expired certifications that slipped renewal tracking: Inspectors who work primarily on one project type tend to focus renewal energy on the certification that matters most to their daily work. When they are cross-deployed, an expired secondary certification surfaces at the worst possible time.
- Wrong report form used in the field: An inspector accustomed to DSA projects submits a DSA-formatted report on an HCAI project. The content may be substantively accurate, but it does not map to the HCAI special inspection program, creating a documentation gap.
- Unfamiliarity with HCAI nonconformance protocols: Inspectors trained primarily in the DSA environment may attempt to resolve minor field issues informally — a practice that is more tolerated under certain DSA project inspector arrangements but can generate formal NCRs under HCAI if the compliance inspector is present and observant.
- Gaps in the special inspection program coverage matrix: HCAI projects require that the special inspection program explicitly lists every inspection type. Firms sometimes win HCAI scopes based on DSA experience and fail to notice that the HCAI program requires trade categories they are not resourced to cover under that program's specific terms.
How to Structure Inspector Assignments to Avoid Certification Mismatches
The structural fix is not complicated, but it requires discipline at the assignment level rather than relying on inspectors to self-police their own credentials against project requirements.
Maintain a Certification Matrix Per Inspector
Every inspector in your roster should have a documented profile listing each active certification, the issuing authority (DSA, ICC, ACI, ICBO, etc.), the specific trade category, the expiration date, and — critically — which project types that certification is recognized for. This is not a one-time exercise; it needs to live in whatever system your schedulers use at the moment of dispatch.
Map Project Requirements Before the First Assignment
When a new project comes in, your ops team should pull the approved special inspection program (HCAI) or the DSA-approved submittal log and create a checklist of required certification categories. That checklist should travel with every dispatch decision on that project. Schedulers who do not have visibility into project-level requirements will inevitably rely on memory and familiarity, which is where mismatches originate.
Build a Pre-Dispatch Verification Step
Before confirming an inspector's assignment to a project, the scheduler or QA lead should run a quick check: Does this inspector hold an active, recognized certification for this specific trade category on this specific project type? This step does not need to be onerous — if your certification data and project requirements are both accessible in the same workflow, the check takes seconds. The problem is that in most firms, these data points live in different places: certifications in a spreadsheet, project details in email, dispatch in a whiteboard or calendar tool.
Separate Onboarding Tracks for DSA and HCAI
Inspectors who are new to HCAI projects should receive explicit orientation on HCAI-specific documentation expectations, the role of the compliance inspector, nonconformance protocols, and the OSHPD-specific technical requirements relevant to their trade category. Do not assume that DSA experience transfers automatically. A brief, structured onboarding checklist — reviewed by your QA manager before an inspector's first HCAI assignment — closes this gap at low cost.
A Note on the OSHPD-to-HCAI Transition
Many firms still use the legacy term OSHPD internally — in templates, training materials, and even verbal shorthand. The agency was renamed HCAI (Health Care Access and Information) effective July 1, 2021, as part of a broader reorganization under the California Health and Human Services Agency. While the regulatory requirements did not change substantively at renaming, the department's branding, website structure, and some of its publicly facing materials have been updated. Firms still using OSHPD branding on client-facing documents and reports should update those materials — an auditor or compliance inspector who notices outdated agency references may flag it as an indicator of documentation hygiene issues more broadly.
The Division of the State Architect and HCAI represent two of California's most rigorous construction oversight programs. Firms that understand both — at the level of certification categories, documentation formats, and field protocols — are positioned to serve the full range of public-sector clients without the compliance exposure that comes from treating them as interchangeable.
Bringing It Together for Your Operations Workflow
The compliance gap between DSA and HCAI projects is not a knowledge problem for most experienced firms — ops leads and QA managers generally understand the distinction in principle. The breakdown happens at execution: in the space between knowing that certifications differ and actually verifying them at the moment of dispatch, for every assignment, every week.
Closing that gap requires the right information to be available at the right moment in the scheduling workflow, not buried in a spreadsheet that gets checked monthly.
Inspectra360 maintains a per-inspector certification profile — including trade category, issuing authority, and expiration date — and surfaces active project-type requirements at the point of dispatch, flagging mismatches between an inspector's credentials and the specific DSA inspection or HCAI compliance requirements of the assigned project before the inspector ever leaves the office. For firms managing mixed portfolios of school and healthcare work, that pre-dispatch check is built into the assignment workflow rather than left to manual verification.