CSP-11 CSP-11 D2.04 · Domain 2 · Program Management · 25%
Incident Investigation: Move from Event Facts to System Causes
At 21:00 Friday, a US machine shop learns that a lathe injury is a fingertip amputation. The supervisor writes 'operator not paying attention,' washes down the area, and plans to investigate Monday. You are the CSP: protect the worker, preserve evidence, run the correct regulatory clock, and decide what must be explained beyond the operator's last action.
Updated . Independent CSP-11 practice. Not BCSP-endorsed. No pass guarantee.
Class overview
Investigation
Incident investigation should explain how and why an event occurred well enough to prevent recurrence. That requires separating evidence from assumption, preserving perishable information, building a reliable event sequence, and examining conditions beyond the final worker action.
A useful investigation considers task design, supervision, equipment, procedures, change, workload, training, maintenance, organizational decisions, and failed barriers. Terms such as immediate cause and root cause can be useful, but the deeper objective is to identify controllable factors that contributed materially to the event.
Corrective recommendations should be tied to findings. Investigations lose value when they jump directly to retraining without showing that knowledge or skill was actually causal.
Decision rule
Investigate to change the system that allowed the energy to reach a person. Blame is not a finding.
Batch A decision cue
Establish the event sequence from evidence, then analyze why barriers failed and which system conditions enabled the event. Match corrective actions to demonstrated causes.
Collect facts, build the timeline, identify failed and missing barriers, then write actions that restore or add controls.
In 20 seconds
- Investigate to change the system that allowed the energy to reach a person.
- Blame is not a finding.
- Find systemic causes — not a single blame target.
- Preserve the scene and evidence before cleanup when safe.
How to apply Investigation
THEORY: Incident investigation is barrier and condition analysis, not a hunt for a bad employee. 5-Why is a prompt; MORT/barrier methods belong when the system is complex (Class 105/119). CALC: None unless the stem gives rates. Do not compute TRIR as the investigation. FIELD: Laceration at an unguarded infeed. The finding is the missing guard and why it stayed missing, not “worker inattention.” ASSESS: Retraining only, with the nip still open, is the wrong first move.
Worked case
Wrong first move: close the file with ‘be more careful.’ Correct move: timeline, failed barrier, redesign or restore the guard, verify it stays.
Field case
An employee bypasses a machine guard and is injured. The losing answer is to close the investigation with 'employee failed to follow procedure' and schedule retraining. Evidence shows the guard repeatedly jammed production, supervisors tolerated bypassing, and maintenance requests had been deferred. A stronger investigation documents those contributing factors and targets the equipment reliability, production pressure, supervisory controls, and bypass opportunity.
Why the rule holds
Related: 21, 105, 119.
Same rule, different setting
A tong takes a fingertip at 21:00 Friday on a land rig. The company man writes “not paying attention” and goes home. You are the CSP. The question is clocks, causes, and whether the guard was ever in the story.
A chop saw takes a fingertip at 21:00 Friday. The foreman writes “not paying attention” and goes home. You are the CSP. The question is clocks, causes, and whether the guard was ever in the story.
Picture / model
Conduct an evidence-based incident investigation that preserves the scene, reconstructs the sequence, identifies underlying control failures, distinguishes fact from hypothesis, and runs applicable notification and recordkeeping obligations on separate clocks.
Exam traps
Original SafePath contrasts for Investigation. These are study traps, not recalled BCSP items.
| Trap | Correct read |
|---|---|
| Root cause = the operator | Usually a symptom; look at energy, design, MoC, incentives |
| 8 hours | Fatality notification — not amputation |
| 24 hours | Amputation, in-patient hospitalization, loss of an eye |
| 7 calendar days | Record on the OSHA 300 — not the severe-injury call |
More traps to recognize
- Stopping at unsafe act or human error without examining enabling system conditions.
- Interviewing witnesses long after the event while allowing physical evidence to change.
- Recommending training automatically when the investigation does not identify a knowledge or skill gap.
Field move
A 03:00 fatality does not wait for the next business day.
Scenarios
Scenario 1 · Applied Scenario · CSP-11 D2.04
A worker dies at 03:00 Sunday on a shutdown. Best notification clock?
Best action: 8 hours from the fatality.
Why: Evaluate the best response. The fatality was Sunday at 03:00. The best clock is 8 hours from the fatality. Analysis, the weekend, and the injury log do not move that notice. Twenty-four hours is the amputation clock, not the clock for a death at 03:00 Sunday. Seven calendar days records the case. I…
Scenario 2 · Applied Scenario · CSP-11 D2.04
ER treats a crushed hand and releases the worker the same night. No admission. No amputation. What 1904 notification is required?
Best action: No 8/24-hour OSHA notification for treat-and-release without amputation; still decide 300 recording within 7 calendar days.
Why: Evaluate the best response. The worker was treated and released. There was no admission and no amputation. The best call is no 8-hour or 24-hour OSHA notification, and a recording decision within 7 calendar days. Treat-and-release without admission is not in-patient hospitalization, so it is not a…
Scenario 3 · Applied Scenario · CSP-11 D2.04
A team runs an FMEA after a press incident and funds “better warning labels” because detection RPN was worst. The light curtain was unplugged. What went wrong?
Best action: Wrong tool use after an event: detection scoring hid the defeated engineering barrier.
Why: Evaluate the best response. After the event, the team scored detection and hid an unplugged light curtain. The best call is that detection scoring hid the defeated engineering barrier. Accepting the detection ranking as the right action leaves the light curtain unplugged. Environmental aspects do n…
If the stem says this
| Stem signal | Best direction |
|---|---|
| only retraining is proposed after a design failure | fix the system/design cause |
| the scene is being cleaned before photos | preserve evidence when safe |
| five-why stops at operator error | keep asking for system factors |
| interim risk remains high | install interim controls immediately |
| two answers work | higher hierarchy / system / design |
Check before you leave
- ✓ Find systemic causes — not a single blame target.
- ✓ Preserve the scene and evidence before cleanup when safe.
- ✓ Five-why without evidence is storytelling.
- ✓ Corrective actions must address root causes with hierarchy preference.
- ✓ Timeline, people, process, equipment, and environment all get examined.
- ✓ Interim controls protect people while the investigation runs.
Blueprint mapping
Investigation is the SafePath study class for CSP-11 D2.04 inside CSP-11 Domain 2, Program Management (25%). A high-weight management domain focused on measuring performance, investigating incidents, managing change, building systems, leading people, controlling records and resources, and interpreting data.
SafePath uses the publicly posted CSP-11 outline as a study map. It does not reproduce official exam content, and it is not affiliated with or endorsed by BCSP or Pearson VUE.
Batch A mapping note: D2.04 — investigate incidents, identify contributing and causal factors, and develop prevention-focused findings.
Practice / flashcards / formulas
More classes in Program Management
Nearby lessons mapped to the same CSP-11 domain.
CSP-11 D2.04
Other classes on this task
Related study
Guides that use Investigation
- Oil and gas safety study guideProcess safety, change, and investigations
- CSP application and exam guideEligibility, scheduling, and exam method
- CSP-11 exam prep guideDomain weights, sample items, and a study sequence
- CSP-11 blueprint and weightsSeven published domains and the class map
- Seven-domain study directoryScope, tasks, and links into each lesson
Investigation study questions
- What decision does the Investigation class train?
- Investigate to change the system that allowed the energy to reach a person. Blame is not a finding. This is independent SafePath CSP practice for CSP-11 D2.04. It is not an official BCSP item and it is not a pass guarantee.
- What exam trap shows up in Investigation?
- A common miss treats this as sufficient: Root cause = the operator The stronger read is: Usually a symptom; look at energy, design, MoC, incentives
- How does Investigation map to the CSP-11 blueprint?
- SafePath maps this class to CSP-11 D2.04 in Domain 2, Program Management (25% of the published blueprint). Use the public outline for study planning. SafePath is not affiliated with or endorsed by BCSP.
- What should be done first in an incident investigation?
- After emergency needs and scene safety are addressed, preserve time-sensitive evidence and begin documenting facts before conditions change.
- Is worker error a root cause?
- It may describe an action, but investigators should usually examine why that action was possible, expected, tolerated, or not prevented by system controls.
- Why build a timeline?
- A timeline helps separate sequence, conditions, decisions, barrier failures, and assumptions so causal relationships can be tested.
Verify
Verify: Confirm current certification requirements with BCSP and technical requirements with the cited authoritative standard.