Safety Program vs Safety Manual vs Site-Specific Safety Plan: What Your GC Means
Published September 6, 2026 · 6 min read
A project manager emails and asks for your safety manual. A week later the same company's safety coordinator asks for your SSSP before mobilization. Then a prequalification portal asks you to upload a safety program. It is reasonable to wonder whether these are three different documents or three names for the same one.
They are not the same, and confusing them is what leads contractors to submit the wrong file and lose a week. This guide defines each document in plain terms, tells you which one a given request is actually asking for, and shows how your company program feeds every project level document that follows.
Written safety program: your company level document
A written safety program is the company wide document that states your safety policies and procedures. It applies to every job you run, not to one project. It contains your signed policy statement, responsibilities, training and orientation practice, hazard communication, PPE hazard assessment, the hazard specific programs your work triggers, incident reporting, disciplinary policy, and an employee acknowledgment form.
This is the document that satisfies the accident prevention program expectation in 29 CFR 1926.20(b), the one your insurer asks for at renewal, and the one prequalification networks grade. You write it once, you keep it current, and you send the same file to every client who asks.
Safety manual: the same thing, older term
Safety manual is the older name for the company written safety program. It comes from the era when the document lived in a physical binder on a shelf in the trailer, and plenty of experienced project managers still use it out of habit.
When someone says send me your safety manual, they want your company written safety program. There is no separate deliverable. Some companies use manual to describe a larger reference volume and program to describe the policy core, but that distinction is internal to those companies and not a standard anyone enforces.
Site-specific safety plan: the project level document
A site specific safety plan, usually abbreviated SSSP and sometimes called a project safety plan, applies to one project. General contractors require it on jobs where the risk, the owner, or the contract terms justify a project level document, and it is standard on most large commercial, institutional, industrial, and public work.
An SSSP does not repeat your whole company program. It references it and then adds the things that only make sense once you know the address. Typical contents include the project name and location, your project specific personnel and their contact numbers, the scope of work you are performing on that job, the hazards created by that specific site, the emergency information for that location, and the site logistics that affect safety.
- Project name, address, and your scope of work on that job.
- Your named site supervisor, competent person, and emergency contacts with phone numbers.
- Hazards specific to the site, such as adjacent traffic, overhead power lines, occupied buildings, or confined spaces present on the property.
- Emergency information: nearest hospital, muster point, evacuation route, and reporting chain to the GC.
- Site logistics: access routes, laydown and storage areas, crane or lift zones, and coordination with other trades.
- References back to your company program for the policies that do not change per job.
Job hazard analysis: the task level document
A job hazard analysis, also called a JHA, a job safety analysis, or an activity hazard analysis, is the smallest of the four. It covers one task. You break the task into steps, list the hazard in each step, and state the control that removes or reduces it.
GCs commonly require a JHA before a specific high risk activity, such as a lift, a roof edge installation, an energized work permit, or a trench entry. Many require a fresh one for each new activity and expect the crew performing the work to sign it during that morning's pre task briefing.
The relationship to everything above is simple. Your company program says you assess hazards before high risk work. Your SSSP says which activities on this project require it. The JHA is the actual assessment for one task on one day.
How the four fit together
Think of it as three levels of zoom. The company program is the widest view and covers policy for every job. The SSSP zooms into one project and adds the facts that only exist at that address. The JHA zooms into one task on one day. The safety manual is not a fourth level, it is another name for the first one.
This matters because each level borrows from the one above it. If your company program is thin, every SSSP you write for the rest of the year is thin too, because there is nothing solid to reference. Contractors who fight with SSSP paperwork on every job almost always have a weak company program underneath.
Decoding the phrasing you actually receive
Requests rarely arrive with the right vocabulary. Here is what the common phrasings almost always mean.
- Send me your safety manual: they want your company written safety program.
- Upload your safety program to ISNetworld or Avetta: they want your company written safety program, as a single PDF, graded against that network's question set.
- We need your SSSP before mobilization: they want a project level plan naming this job, your site supervisor, the site hazards, and the emergency information.
- Send your safety plan for the project: SSSP, same as above, informal phrasing.
- We need a JHA for that lift on Thursday: task level analysis for that single activity, usually signed by the crew that morning.
- Send your written programs: they want the hazard specific written elements such as hazard communication, silica exposure control, or respiratory protection, which live inside your company program.
- Send your EMR and your program: your experience modification rate from your workers compensation carrier plus the company program. The EMR comes from your insurer, not from any document you write.
How the company program feeds the SSSP
Writing an SSSP from scratch each time is slow. Writing one that references a solid company program takes under an hour once you have the project details.
The mechanics are straightforward. Start the SSSP with a line stating that all work is performed under your company written safety program, dated and attached. Then add only the project variables: the address, the site supervisor and competent person for this job, the scope you are performing, the hazards this particular site presents, the nearest hospital and muster point, and the coordination arrangements with the GC and the other trades on site.
For each hazard you list, point at the section of your company program that governs it. If the site has a twelve foot leading edge, reference your Fall Protection section. If you are cutting slab, reference your silica exposure control plan. That referencing is exactly what a reviewer wants to see, because it proves the project plan is backed by a real program rather than assembled for the occasion.
What to build first
Build the company written safety program first, always. It is the document that unlocks prequalification, satisfies your insurer, and gets you through subcontract execution. Every project level document you write afterward becomes a short exercise in filling in project variables.
If you do not have one yet, our six question intake maps your trade, crew size, work environments, and activities to the correct 29 CFR sections and produces the full program as a PDF. The trade pages show the sections a program for your kind of work typically includes, so you can see what you will be referencing in your next SSSP before you start.