Lesson 2 of 6
Incident management
9 min
Listen to this lesson
EHS incident management records what happened, investigates why, tracks what will prevent it, and produces the reports regulators require. SAP Learning describes three record types: incidents (something happened, such as an injury, a spill or property damage), near misses (it almost happened) and safety observations (an unsafe condition or behavior someone noticed). Recording works from mobile devices, browsers or automated triggers, online and offline, for skilled and occasional users.
An incident at WIND-10
On a Tuesday afternoon, an operator at WIND-10 gets a splash of insulating varnish in the eye while changing a varnish drum. A colleague takes him to the eyewash station and the plant nurse refers him to a clinic, where he receives prescription eye drops and is back at work the next day with no restrictions. His supervisor records the incident on a tablet at the line within the hour: location, time, people involved, what happened, immediate actions.
- RecordSupervisor records the incident on a mobile device: who, where, when, what, first aid
- NotifyWorkflow notifies Monique and the plant manager; severity drives escalation
- InvestigateMonique's team collects statements, photos and the drum change procedure; root cause analysis
- Assess recordabilityMedical treatment beyond first aid makes the injury recordable under OSHA rules
- ActCorrective actions assigned with owners and due dates (for example a drum pump and face shields)
- Report and closeRegulatory records updated; incident closed when actions are verified
Recordability and regulatory reports
In the US, OSHA's recordkeeping rule (29 CFR Part 1904) requires employers to record work-related injuries and illnesses that meet its criteria, such as medical treatment beyond first aid, days away from work or restricted work, on the OSHA 300 log, with an incident report (Form 301 or an equivalent) and an annual summary (Form 300A). Prescription medication counts as medical treatment, so the varnish splash is recordable. The incident record in SAP must capture the data these forms need, and the decision on recordability must be documented, because inspectors check it.
| Data point | Why it matters | Contoso value (illustrative) |
|---|---|---|
| Date and time, location | Required on regulatory records | Tuesday 14:20, WIND-10, plant 1710 |
| Injured person and job | Log entry; privacy rules apply | Winding operator |
| Injury type and body part | Classification of the case | Chemical splash, eye |
| Treatment | Decides recordability | Prescription eye drops: medical treatment beyond first aid |
| Days away or restricted | Classification and counts | None |
| Recordability decision and reason | Audit trail for inspectors | Recordable: prescription medication |
Incident data that drives regulatory recordkeeping.
Root cause and corrective actions
The investigation finds that drums are tipped by hand to fill the varnish tank, and face shields are not required for the task. Corrective actions: install a drum pump, update the job procedure, require face shields, and retrain the shift. Each action has an owner, a due date and a verification step. Actions that involve equipment, such as the pump installation, can create maintenance work in EAM, so Rosa, the Detroit maintenance planner, receives a notification rather than an email.
What would you do?
During UAT, a tester records an injury with prescription medication and finds that the record can be closed without a recordability decision. What do you do?
What goes wrong in testing
| Symptom | Cause | Test |
|---|---|---|
| Incidents recorded offline never arrive | Mobile sync not tested with real devices and network gaps | Record offline at the line, reconnect, check the record |
| Notifications go to the wrong people | Org data or location assignments incomplete | Record one incident per location and check recipients |
| Regulatory forms miss data | Required fields not mandatory for recordable cases | Record a recordable case and generate the forms |
| Privacy breach in reports | Injured person visible to all users | Check roles: who sees names and medical details |
Incident management defects found in testing.
Near misses and safety observations
Near misses and safety observations are where prevention happens: a forklift that nearly hit a pedestrian at the 171A pick area, a missing guard on a press, a blocked fire exit. They are only useful if people record them, which means recording must take under a minute on a phone, and if someone acts on them. A good test measures exactly that: an operator records an observation offline in the warehouse, it reaches the right supervisor, an action is created, and the operator can see that something happened. If the feedback loop is broken, reporting dries up within weeks.
| Measure (illustrative) | Why it matters |
|---|---|
| Time to record an observation on a phone | Long forms kill reporting |
| Share of observations with an action within a week | People report when they see results |
| Near misses per recordable injury | A low ratio suggests under-reporting |
Measures that show whether incident recording works in practice.
- Incident management records incidents, near misses and safety observations, online or offline.
- Investigation, root cause and corrective actions follow the record, with workflow.
- Recordability under OSHA rules depends on treatment and outcomes; document the decision.
- Test notifications, offline recording, forms and privacy, not only data entry.
Check your understanding · not graded
Lesson check
1. Which three record types does SAP EHS incident management distinguish?
2. Why is the varnish splash recordable under OSHA rules?
3. What should be required before an injury record can close?
4. Why test incident recording offline?