Resource · Planning
IIPP vs. Site-Specific Safety Plan in California Construction: What Contractors Need to Know
A lot of California construction contractors use "IIPP" and "site-specific safety plan" as if they mean the same thing. They do not. An IIPP is the company-level written safety program California employers are required to establish, implement, and maintain — it covers the company's baseline responsibilities for identifying hazards, training employees, correcting unsafe conditions, and maintaining a safe workplace across all of its operations. A site-specific safety plan is the project-level document that applies safety planning to one specific jobsite — covering the actual scope of work, the site conditions, the project-specific hazards, the logistics, the emergency planning, and the documentation expectations that apply to that project.
On many active California construction projects, both documents matter. The IIPP provides the foundation. The SSSP provides the project-specific application. Confusing the two — or assuming one covers the other — is one of the more common documentation gaps we see on active projects, and it shows up in ways that matter: rejected submittals, incomplete planning for project-specific hazards, and documentation that does not hold up when someone actually reads it.
This guide explains the practical difference between an IIPP and an SSSP in California construction, what each document is meant to do, and why the distinction matters for contractors, subcontractors, GCs, and project teams managing active work.
IIPP
What an IIPP Is — The Company-Level Safety Program
An IIPP (Injury and Illness Prevention Program) is the company-level written safety program that California employers are required to establish, implement, and maintain under California Labor Code Section 6401.7 and California Title 8, Section 3203.
In practical terms, the IIPP is the baseline safety framework the company operates under across all of its work. It is not written for any one project — it is written for the company as a whole.
A company-level IIPP typically addresses:
- Management commitment and responsibility for safety across the organization. Who within the company is responsible for the safety program, and how that responsibility is structured.
- A system for identifying and evaluating workplace hazards. How the company identifies hazards across its operations — not hazards on one specific project, but the company's overall approach to finding and assessing hazards.
- Methods for correcting hazards in a timely manner. The company's process for addressing identified hazards, including communication about hazards and follow-through on corrections.
- Employee training requirements. How the company ensures employees are trained on safe work practices, hazard recognition, and the company's safety expectations — both for new employees and ongoing.
- A system for communicating with employees about safety. How the company shares safety information, how employees can report hazards, and how safety communication flows within the organization.
- Recordkeeping practices. How the company maintains records of safety training, inspections, hazard corrections, and related program documentation.
The IIPP is a standing document. It does not change every time the company starts a new project. It represents the company's baseline safety operating system — and in California, every employer is required to establish, implement, and maintain one.
Code of Safe Practices
What a Code of Safe Practices Is
California construction employers must also adopt a written Code of Safe Practices related to their operations, per California Title 8, Section 1509. This is a separate document from the IIPP.
The Code of Safe Practices is a set of written safety rules and practices applicable to the employer's construction operations. It typically covers the safety practices and procedures employees are expected to follow on the company's construction work — general safety rules, PPE requirements, equipment operation rules, and work-practice standards.
The Code of Safe Practices works alongside the IIPP as part of the company's safety documentation foundation. It is not the same thing as a site-specific safety plan, and it is not designed to cover project-specific logistics, hazards, emergency planning, or coordination expectations for any one jobsite.
Where contractors sometimes get confused: the Code of Safe Practices is a legitimate required document, and on some projects it may be submitted as part of a safety documentation package. But it does not replace a site-specific safety plan when one is expected.
SSSP
What a Site-Specific Safety Plan Is — The Project-Level Working Document
A site-specific safety plan (SSSP) is a project-level document that applies safety planning to one specific construction project. It takes the company's baseline safety expectations and makes them specific to the site, the scope of work, the active trades, the project-specific hazards, the logistics, the emergency planning, and the documentation expectations on that job.
In practical terms, the SSSP is the working document that says: this is what the project involves, this is how the site is laid out, these are the hazards that apply here, this is how we plan to address them, this is who is responsible for what, and this is how safety is documented and managed on this specific project.
A useful SSSP typically addresses project identification, scope of work, site logistics, emergency procedures, site-specific hazard assessment, high-risk work planning (fall protection, excavation, crane operations, confined space, hot work, silica, and others where they apply), occupied-site and public-interface controls where relevant, subcontractor coordination expectations, training and orientation requirements, documentation and inspection expectations, and incident reporting and corrective action flow.
An SSSP is often required by the project, the contract, the GC, the owner, the district, the public agency, or the OCIP program. It is typically reviewed by the party that requested it — and on higher-oversight projects, that review is where the quality of the plan shows up.
Side by Side
IIPP vs. Site-Specific Safety Plan: Key Differences
The clearest way to understand the difference is to compare what each document is built for.
IIPP — Company-Level Program
- Scope
- Covers the company's overall safety program across all operations.
- Audience
- Internal — the company, its employees, and Cal/OSHA if audited.
- Content
- Baseline safety responsibilities, hazard identification and correction processes, training requirements, communication systems, recordkeeping.
- Project-specificity
- None. The IIPP is not written for any one project.
- Frequency of change
- Updated when company operations or regulatory requirements change — not with every new project.
- California requirement
- Yes. California employers must establish, implement, and maintain an effective written IIPP.
SSSP — Project-Level Plan
- Scope
- Covers one specific construction project — the site, the scope, the hazards, the logistics, the coordination, the emergency planning.
- Audience
- The project team, the GC, the owner, the district, the agency, or the OCIP administrator reviewing it — whoever the project expects to see it.
- Content
- Project identification, scope of work, site logistics, emergency procedures, site-specific hazard assessment, high-risk work planning, coordination expectations, documentation and inspection expectations, incident reporting.
- Project-specificity
- Entirely. The SSSP is built around the project in front of the team.
- Frequency of change
- Updated when the project changes — new phases, new trades, changed conditions, new hazards.
- California requirement
- Not universally required by law for every project. Typically required by the project environment — owner, GC, district, public works, OCIP, or contract terms.
The two documents work together. The IIPP is the foundation the company operates under. The SSSP applies that foundation to one specific project. One does not replace the other.
Why Contractors Mix Them Up
Why Contractors Mix Them Up
The confusion between IIPP and SSSP is common in California construction, and it is easy to understand why.
Both are written safety documents.
The company has a written safety program. The project asks for a written safety plan. Contractors who are not familiar with the distinction naturally assume their company program answers the project question.
Both may be requested on projects.
On some projects, contractors are asked to submit both their company IIPP and a project-specific SSSP. When both are in the same documentation package, the distinction between the two can blur.
Company programs sometimes include project-level language.
Some IIPP templates include sections that look like they cover project-specific planning — but in practice, those sections are too generic to satisfy a real project-specific submittal expectation.
Templates blur the lines.
Off-the-shelf safety program templates sometimes combine IIPP, Code of Safe Practices, and SSSP-like content into one document without clearly separating what is company-level and what is project-level.
Subcontractors may be operating under the GC's framework.
On some projects, subcontractors operate under the prime contractor's safety program framework while still being expected to have their own company IIPP and potentially their own project-level documentation. The layers of documentation create confusion.
Nobody explained the difference.
On many projects, the distinction between IIPP and SSSP is never clearly explained to the contractors who need to produce the documents. The request comes as a submittal line item, and the contractor fills it with what they have.
Why It Matters
Why the Distinction Matters on Active California Construction Projects
The difference between an IIPP and an SSSP is not just a documentation technicality. It shows up on active projects in ways that matter.
Submittal expectations. When a GC, owner, district, or OCIP program asks for a site-specific safety plan and the contractor submits their company IIPP, the submittal does not meet the expectation. The reviewer is looking for project-specific content — site logistics, project hazards, emergency contacts, coordination expectations — and a company-level program does not provide that.
Incomplete project-specific hazard planning. An IIPP covers how the company identifies hazards generally. It does not address the specific hazards on the project the team is working on today. If the only safety documentation on the project is the company IIPP, the project-specific hazards may not be planned for in writing.
Weak emergency and logistics planning. Emergency contacts, hospital directions, evacuation routes, site access points, staging plans, and traffic patterns all need to be project-specific. The company IIPP does not carry that information for any one jobsite.
Documentation gaps during inspections and reviews. When an inspection identifies deficiencies, the written plan should be the baseline the project team works against. If the only written plan is the company IIPP, there is no project-specific baseline for the inspector, the superintendent, or the reviewer to reference.
Review-readiness problems. When an agency visit, an owner walk, or a formal review happens, the reviewer expects to see documentation that reflects the project. A company IIPP that does not address the project-specific conditions on the ground creates a gap in review readiness.
Coordination confusion. On multi-trade projects with multiple subcontractors, coordination expectations should be defined at the project level. A company IIPP does not address who coordinates with whom on this project, how safety communication flows between contractors on this site, or how overlapping hazards between trades are managed here.
None of these are catastrophic on their own. But when they add up — and on higher-oversight projects, they tend to — the gap between having a company program and having project-specific planning becomes visible.
When Both Matter
When Both Documents Matter at the Same Time
On many California construction projects, both the company IIPP and a project-specific SSSP matter — and the project environment determines how much detail the SSSP needs to carry.
Public works projects
Public works environments commonly require both a company safety program and project-specific safety planning as part of contract documentation. The agency and the owner-representative review both.
K-12 school district construction
School districts typically expect project-specific planning that addresses occupied-campus conditions, separation controls, coordination with school operations, and district documentation standards — content a company IIPP is not designed to carry.
Community college and educational facilities
Community college and institutional projects carry similar expectations around institutional review, occupied-campus coordination, and project-specific documentation.
OCIP-managed projects
OCIP programs typically include SSSP review expectations layered on top of the contractor's company-level program. The OCIP administrator reviews the plan — and it needs to address program-specific documentation standards in addition to standard project-level content.
Owner-representative and district-visible projects
Any project where an owner representative, a district representative, or a public agency is actively reviewing safety documentation carries heavier expectations for project-specific planning. The IIPP provides the company foundation; the SSSP provides what the reviewer actually needs to see.
Occupied-site projects
Projects on active campuses, adjacent to occupied buildings, or in environments where the public is present require project-specific planning that addresses separation, access, coordination, and protection in detail.
Higher-risk scopes
Projects with elevated structural work, deep excavation, crane-intensive operations, confined space, heavy demolition, or other higher-risk activities benefit from detailed project-specific hazard planning that goes well beyond what a company IIPP covers.
Life science and technical environments
Specialized technical environments often carry their own coordination and documentation expectations that only make sense when addressed at the project level.
Common Mistakes
Common Contractor Mistakes Around IIPP and SSSP Documentation
The mistakes below are the ones we see most often on active California construction projects. They are almost always avoidable — and they usually stem from the same root cause: not understanding the difference between the company program and the project plan.
Submitting the IIPP when the project asked for an SSSP.
The most common mistake. The GC, owner, or OCIP administrator asks for a site-specific safety plan, and the contractor submits their company IIPP. The submittal does not meet the expectation because it does not address the project.
Turning in a generic SSSP with no real project detail.
A step better than submitting only the IIPP, but still a common gap. A plan with the project name on the cover but generic content inside — no real site logistics, no project-specific hazard assessment, no project-specific emergency information — does not hold up when someone reads it.
Assuming the Code of Safe Practices fills the same role.
The Code of Safe Practices is a legitimate required California construction document, but it is not a site-specific safety plan. Submitting it as one does not satisfy the project-level planning expectation.
Failing to update the SSSP when the project changes.
Plans that are written at the start of a project and never updated lose their connection to the field as the project evolves. New phases, new trades, changed site conditions, and new hazards should all be reflected in the plan.
Not aligning inspections and field conditions with the written plan.
When the SSSP says one thing and the field shows another, the documentation gap is visible to anyone looking at both. The plan and the inspection record should be working together — and when they are not, the gap shows up under review.
Treating safety documentation as a paperwork exercise.
When the IIPP exists to satisfy Cal/OSHA and the SSSP exists to satisfy a submittal deadline, neither document serves its practical purpose. The company program should be the foundation the company actually operates under, and the SSSP should be the working document the project team actually uses.
FAQ
Frequently Asked Questions
Need Help with Your IIPP, Code of Safe Practices, or Site-Specific Safety Plan?
If you are a California construction contractor or subcontractor and need qualified help developing, reviewing, or strengthening your company-level safety program, IIPP, Code of Safe Practices, or a project-specific site-specific safety plan for an active or upcoming project, our service pages cover how we approach both sides of this work.