The 14-Day Incident Report Deadline Under Pressure
You are the OSHAD-registered OSH practitioner at a mid-sized aluminium fabrication facility in Abu Dhabi with 240 workers. On a Thursday afternoon, a subcontracted welder suffers a partial-thickness burn to the forearm when a hot slag fragment enters his glove. He is treated at the on-site clinic and returns to work the same day. The site supervisor argues that because the injury is 'minor' and the worker lost no time, no OSHAD notification is required and logging it internally is sufficient. The project director, worried about a client audit next week, asks you to 'hold off' reporting anything externally until the audit passes. You know the incident involved a contractor, a burn, and a near-miss component (the glove had a pre-existing tear noted in the toolbox talk that morning). The 14-day clock and classification thresholds are the crux.
1. How do you classify and report this incident under OSHAD requirements, and how do you respond to the supervisor and project director?
Read the worked answer
Classification reasoning, not recall:
A partial-thickness burn requiring clinic treatment is a recordable injury even without lost time. Under OSHAD incident-reporting expectations, injuries requiring medical treatment beyond simple first aid are reportable, and the fact that a contractor was involved does not transfer the duty away from the host employer - the host retains notification responsibility for incidents on its premises.
- The internal log entry happens same day.
- External notification to OSHAD (via the prescribed channel) is triggered because this is a medical-treatment injury, not a pure first-aid case. The 14-day window is a deadline, not a grace period - you report promptly, not on day 14.
Responding to the supervisor: Explain that 'no lost time' is not the test; the test is treatment severity and contractor involvement. Logging internally is necessary but not sufficient.
Responding to the project director: Refuse to delay. Delaying a report to pass an audit converts a minor injury into a regulatory non-compliance and potential integrity breach. The audit will look worse if a suppressed report surfaces. Document the instruction to delay in writing and escalate to the OSH manager. This is a professional-ethics boundary: you do not misrepresent OSH data.
2. The glove had a pre-existing tear flagged at the toolbox talk. What does this change about your investigation scope and corrective actions?
Read the worked answer
The tear converts the event from a single injury into a systems failure with a near-miss dimension: PPE was known-defective and work continued.
Investigation scope expands to:
- PPE management - who inspects gloves, at what frequency, and why a flagged defect was not removed from service before hot work.
- Toolbox talk follow-through - a hazard raised at the talk with no corrective action is a paper exercise; the talk is evidence the hazard was known.
- Contractor oversight - did the host verify the subcontractor's PPE standard and supervision?
Corrective actions should be hierarchical: eliminate/reduce slag exposure (shields, screens, welding position), then administrative controls, with PPE as last line. Add a PPE quarantine-and-replace rule and a closed-loop check that toolbox-talk hazards are actioned and signed off. Track effectiveness - re-inspect after 30 days.