Job Safety Analysis and Incident Documentation

Why Documentation Is a Safety Tool

Every elevator job carries real hazards: moving counterweights, high-voltage equipment, confined pits, and heavy wire rope. Written documentation—Job Safety Analysis (JSA) forms and incident reports—turns the lessons learned from those hazards into actionable guidance that protects the next mechanic on the job. IUEC contractors and NAEC member companies both require field-ready documentation before work begins and immediately after any unplanned event. Producing accurate paperwork is not a clerical task; it is a professional safety responsibility.

Job Safety Analysis (JSA): Structure and Purpose

A JSA breaks a maintenance or installation task into discrete, ordered steps. For each step the form captures three things:

1. Job step – a brief, active-verb description of what the worker does (e.g., "Open hydraulic pump access panel").

2. Potential hazards – every foreseeable way that step could cause harm or equipment damage (e.g., "Residual hydraulic pressure; pinch points on panel edges").

3. Preventive measures / controls – the specific actions, PPE, or procedures that eliminate or reduce each hazard (e.g., "Relieve system pressure per manufacturer procedure; wear cut-resistant gloves; apply LOTO before removing fasteners").

Hazard controls should follow the hierarchy of controls: eliminate the hazard first, then substitute, then use engineering controls, then administrative controls, and finally PPE. On a JSA form, a control that names only PPE without considering higher-level options is considered incomplete.

A complete JSA also identifies who performs the task, the date, the location, the equipment involved, and the supervisor or lead approving the plan. These fields matter for OSHA compliance and contractor liability.

Lockout/Tagout and the JSA

For any elevator maintenance task involving electrical, hydraulic, or mechanical energy, LOTO (29 CFR 1910.147 for general industry; ASME A17.1 safety code governs elevator-specific procedures) must appear as a preventive measure at the appropriate step. A JSA that omits LOTO where energy isolation is required will fail review. Before listing PPE for a step, always ask: has the energy source been controlled? If not, that control belongs on the form before PPE.

Incident Reports: What They Capture and Why

An incident report documents any unplanned event—injury, near-miss, property damage, or hazardous condition—immediately or as soon as it is safe to do so. Prompt reporting preserves accurate memories, witness availability, and physical evidence.

A contractor-style incident report typically includes:

• Basic event facts: date, time, location, equipment involved, personnel present.
• Event description: a factual, first-person narrative of what happened in sequence.
• Injury/damage outcome: nature of injury (or "no injury – near-miss") and any medical treatment.
• Witness statement block: signed accounts from anyone who observed the event.
• Root-cause analysis section: the underlying reason(s) the event occurred, not just the immediate trigger.
• Corrective actions: specific steps, with assigned responsible parties and target completion dates, that will prevent recurrence.
• Cause classification: categories such as "unsafe act," "unsafe condition," "equipment failure," "inadequate training," or "environmental factor." These classifications are used by contractors and IUEC safety programs to spot trends across multiple sites.

OSHA requires employers to record certain work-related injuries and illnesses on the OSHA 300 Log (29 CFR 1904). A near-miss with no injury or lost workdays is generally not OSHA-recordable, but it must still be documented internally by most contractor policies and IUEC safety programs because near-misses predict future injuries.

Root-Cause Analysis: The 5 Whys Method

Identifying the true cause of an incident prevents the mistake of applying a surface-level fix that allows the same event to recur. The 5 Whys technique asks "Why did this happen?" repeatedly until the root cause is reached—usually after three to five iterations.

Example chain (wet pit floor slip):

• Mechanic slipped on wet pit floor. Why? → Floor was wet.
• Why was the floor wet? → Pit sump pump had failed.
• Why had the sump pump failed? → Pump motor had burned out.
• Why was the burnout not caught? → No scheduled inspection of the sump pump was on the maintenance checklist.
• Why was it not on the checklist? → Checklist had not been updated after the pump was installed.

The root cause is a system failure (inadequate maintenance checklist), not the immediate event (wet floor). The corrective action must update the checklist, assign inspection frequency, and establish accountability—not simply post a "Wet Floor" sign.

Putting It All Together

Field-ready documentation means both forms are complete before you leave the jobsite or close out a shift. An incomplete JSA is not a usable JSA; an incident report filed a week later is a liability and may omit critical details. Contractors reviewed by IUEC safety auditors and NAEC certification programs expect mechanics at every level—including pre-apprentices—to understand and produce these documents accurately. The habits you build now carry into your apprenticeship and beyond.