Docs & technical writing
AuraScore 81/100

Site Safety Manual Audit for Commercial Contractors

Evaluate site-specific safety manuals and job hazard procedures for OSHA compliance, field clarity, and contractor adoption.

Use this template when auditing or overhauling construction health and safety documentation before project mobilization. It identifies regulatory compliance gaps, readability barriers for trade workers, and operational blind spots.

Template

Role: Senior Construction Safety Documentation Specialist with 15+ years auditing field operating procedures and OSHA compliance.

Context

  • Contracting organization: {{contractor_name}}
  • Project typology: {{project_typology}}
  • Governing regulatory jurisdiction: {{jurisdiction_code}}
  • Current safety manual excerpt: {{current_sop_sample}}
  • Critical high-risk activities: {{high_risk_activities}}
  • Field workforce literacy and language mix: {{workforce_literacy_profile}}

Task

Conduct a rigorous technical audit of the provided safety procedures, delivering an actionable gap analysis that pinpoints statutory compliance deficiencies, procedural ambiguities, and comprehension barriers for jobsite trades.

Method

  1. Cross-reference {{current_sop_sample}} against governing safety mandates under {{jurisdiction_code}} to detect missing statutory requirements.
  2. Evaluate documentation clarity for {{high_risk_activities}} against field-level hazard communication norms.
  3. Analyze sentence structure, technical jargon, and visual layout against {{workforce_literacy_profile}} to identify readability friction.
  4. Map procedural handoffs between trade subcontractors and general contractor supervisors for ambiguity in safety sign-offs.
  5. Audit emergency response workflows and critical incident reporting sequences for missing procedural escalation steps.
  6. Classify discovered documentation defects by risk severity (Critical, Major, Minor) based on jobsite liability and worker safety impact.
  7. Formulate specific technical revisions, visual communication recommendations, and drafting corrections for each documented gap.

Constraints

  • MUST cite specific regulatory clauses from {{jurisdiction_code}} for every identified statutory gap.
  • MUST NOT provide generic safety guidelines; all recommendations must directly reference {{project_typology}} operations.
  • Findings MUST differentiate clearly between legal non-compliance and documentation usability issues.
  • Language must remain technical, objective, and legally precise.

Output format

Provide your analysis structured as follows:

  1. Executive Audit Summary (max 150 words)
  2. Regulatory & Statutory Compliance Matrix (table: Clause, Finding, Risk Level)
  3. Field Readability & Comprehension Analysis (3-4 focused paragraphs addressing {{workforce_literacy_profile}})
  4. Critical Work Activity Technical Breakdown (bulleted gap analysis for {{high_risk_activities}})
  5. Remediation Action Table (table: Section, Required Rewrite, Priority)

Self-review

  • Have I addressed every high-risk activity listed in {{high_risk_activities}}?
  • Are all compliance findings explicitly grounded in {{jurisdiction_code}}?
  • Does the readability critique accurately reflect the workforce profile in {{workforce_literacy_profile}}?
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

writing-content
writing-docs
real-estate-construction
construction
safety-writing
compliance-audit