Subcontractor Safety Plan Evaluation and Compliance Reporting

Why Subcontractor Safety Plan Evaluation Matters

On a construction project, the general contractor and construction manager (CM) are responsible not only for their own workers but also for coordinating safety across every subcontractor on site. Before a subcontractor sets foot on the job, their safety plan must be reviewed and approved. A weak or incomplete safety plan is not a paperwork problem — it is a predictor of incidents, OSHA citations, schedule delays, and liability exposure. Learning to audit a subcontractor safety plan systematically is a core CM competency recognized by CMAA, NCCER, and OSHA outreach training alike.

What a Subcontractor Safety Plan Should Contain

A complete subcontractor safety plan typically addresses the following categories:

• Company safety policy and management commitment — a signed statement from leadership establishing safety as a priority
• Designated competent person(s) — OSHA Part 1926 requires a competent person for many specific operations (excavation, scaffolding, fall protection, etc.); the plan must name or describe how that person is designated
• Hazard identification and Job Hazard Analysis (JHA) process — how the sub identifies hazards before each task begins
• PPE requirements — specific PPE for the scope of work, consistent with the hazards present
• Training records and orientation procedures — documentation that workers have been trained before exposure
• Emergency action plan — evacuation routes, assembly points, emergency contacts, and first-aid provisions
• Incident reporting and investigation procedures — how injuries and near-misses are recorded and investigated
• Substance abuse policy — required by most project owners and contract specifications
• Subcontractor's own OSHA recordkeeping — TRIR (Total Recordable Incident Rate) and EMR (Experience Modification Rate) data, often required for pre-qualification

Contract safety specifications and CMAA pre-qualification criteria often add requirements beyond the OSHA minimums, such as minimum EMR thresholds, mandatory site-specific safety plans, and required safety meeting frequencies.

The Compliance Matrix: Your Audit Tool

A compliance matrix converts safety plan requirements into a checklist that can be evaluated objectively. Each row represents one required element drawn from a specific source — OSHA Part 1926, the project contract safety specification, or CMAA pre-qualification criteria. For each element, the reviewer marks one of three findings:

• Compliant — the plan fully addresses the requirement with enough specificity to be implemented
• Partially Compliant — the element is mentioned but lacks adequate detail, assigns no responsible person, or contains contradictions
• Non-Compliant — the element is absent or directly conflicts with the requirement

Using a standardized matrix removes subjectivity and ensures every reviewer evaluates the same items in the same order.

Assigning Priority Ratings

Not every deficiency carries the same risk. Once you have identified findings, you assign a priority rating to guide corrective action:

• Critical — the deficiency creates an immediate or serious risk of injury, death, or regulatory stop-work action. Examples: no fall protection plan for work above six feet, no competent person identified for excavation work. A critical deficiency must be resolved before the subcontractor begins the affected work.
• Major — the deficiency represents a meaningful gap that could result in an OSHA citation or an incident if left uncorrected, but does not require an immediate stop-work order. Examples: training records not maintained in writing, JHA process described but no forms provided.
• Minor — the deficiency is an administrative or formatting issue that does not affect field safety in the short term. Examples: the plan is undated, or the emergency contact list is missing phone number formats.

Rating criteria must be applied consistently. If you rate one missing competent-person designation as Critical, every similar gap must receive the same rating.

Writing the Compliance Report

A formal compliance report is organized by category, not by page order in the subcontractor's document. Each section of your report should:

1. State the category being evaluated (e.g., Fall Protection)

2. Summarize what the subcontractor's plan provides

3. List each deficiency, citing the specific clause violated (e.g., OSHA 29 CFR Part 1926 Subpart M, or Section 3.2 of the project safety specification)

4. Assign the priority rating and state the required corrective action

Avoid vague language. "The fall protection section is inadequate" is not useful. "The plan does not identify a competent person for fall protection as required by OSHA 29 CFR Part 1926 Subpart M; rated Critical — subcontractor must submit a revised plan naming a qualified competent person before elevated work begins" is actionable.

Presenting Findings: The Pre-Construction Safety Meeting

Compliance reports are not filed and forgotten. In practice, the CM presents findings to the subcontractor in a pre-construction meeting so deficiencies can be corrected before work starts. Your oral summary must be:

• Structured — lead with critical findings, then major, then minor
• Specific — reference the standard or specification clause, not just a general complaint
• Professional — the goal is correction, not confrontation; use factual, neutral language

When a subcontractor representative pushes back, respond with the applicable standard or contract language. Personal opinion is not a sufficient basis for a compliance finding — the requirement must be traceable to a document.

Safety Reminder

Approving a deficient safety plan — even informally or under schedule pressure — exposes workers to harm and exposes the CM and owner to regulatory and legal liability. When in doubt, a deficiency that affects life safety is always Critical. The competent person requirement exists because OSHA has determined that some hazards require trained, experienced oversight. Never waive that requirement to meet a start date.