The First 90 Days of a Safety Program

    A sequenced 90-day plan for standing up a safety function from nothing — what to do in weeks 1–2, 3–6, 7–12, and what to deliberately defer.

    8 min read
    GuideGeneralBuilding the Safety Function for Your Needs

    Programs fail at launch for a predictable reason: they start with the documents instead of the facts. Ninety days is enough to build a defensible foundation if the sequence is right — assess, stabilize, systematize — and if you resist the urge to write a 200-page manual in week one.

    Days 1–14: Establish the baseline

    1. Pull three years of OSHA 300 logs and workers' comp loss runs. Chart claims by cause, body part, department, shift, and tenure.
    2. Inventory every written program that exists and mark it current, stale, or generic.
    3. Walk every work area with a supervisor and photograph conditions. No corrections yet — just facts.
    4. Interview 8–12 employees across shifts: what almost hurt them, what they'd change, whether they'd report a near miss.
    5. Identify the top five exposures by combined likelihood and severity. Write them down. These are the program.

    Deliverable at day 14: a one-page baseline — top five exposures, the loss pattern, and the compliance gaps that create immediate citation risk.

    Days 15–45: Stabilize the immediate risk

    This phase is about closing the exposures that would hurt someone this month or get cited next week. Nothing here is elegant; all of it is fast.

    • Abate every imminent-danger condition found in the walkthrough, with dated photo evidence.
    • Stand up incident reporting: one form, one route, 24-hour reporting expectation, no blame.
    • Launch the return-to-work program — pre-identified modified-duty task bank and a physician packet.
    • Fix the highest-risk missing written programs first: lockout/tagout, hazard communication, fall protection, powered industrial trucks — whichever apply.
    • Train supervisors on incident response, stop-work authority, and same-day reporting.
    • Build the inspection document binder so an unannounced visit doesn't become a scramble.

    Days 46–90: Systematize

    Now build the machinery that keeps the program alive after attention moves on.

    1. Training matrix: every role mapped to required topics, frequency, and last-completed date.
    2. Inspection calendar with named owners — daily pre-shift, weekly area, monthly formal, annual specialty.
    3. Corrective action tracker with owner, due date, and verification. Closure rate becomes a leading indicator.
    4. Job hazard analyses for the top five exposures, written with the people who do the work.
    5. A monthly one-page metrics review: near misses reported, inspections completed on time, corrective actions closed on time, training compliance, recordable rate.
    6. Management review cadence — 30 minutes monthly with the accountable executive. Without this, everything above decays.

    What to deliberately defer past day 90

    • ISO 45001 certification — build the management system first; certify when the system is real.
    • Software platform selection — buy the tool after you know the process it needs to support.
    • Behavior-based safety observation programs — they require a reporting culture that doesn't exist yet at day 60.
    • Comprehensive policy manuals — write the programs that match your top exposures, not a table of contents copied from a template.

    How to know it worked

    At day 90 the honest test isn't the binder thickness. It's whether a supervisor can tell you the top three hazards in their area, whether a near miss reported last week has a closed corrective action, and whether a document request could be filled in under an hour. If those three are true, the foundation is real.

    Next step

    Fractional vs. Full-Time Calculator

    Compare the true annual cost of a full-time hire against fractional coverage.

    Run the Cost Comparison