A recordable incident is a work-related injury or illness serious enough to enter your official injury log, while a reportable incident is a specific subset severe enough that a regulator must be notified directly, usually within hours or days. Every recordable event stays in your internal records, but only a narrow band of the most severe cases become reportable to an authority. EHS teams stumble when they treat the two words as interchangeable, because the criteria, the timelines, and the consequences of getting them wrong are completely different. This guide separates the two concepts cleanly so your log survives an audit.
Recordability answers an internal question: does this event belong in my injury and illness log at all? Reportability answers an external question: must I actively pick up the phone or file a form with a regulator right now? The distinction matters because a plant can generate dozens of recordable cases in a year and still have zero reportable events. Confusing them creates two failure modes: under-reporting a fatality or serious hospitalization (a legal violation with penalties), or over-reporting minor cases and burying your safety team in unnecessary regulator contact.
Think of it as a funnel. Every work-related injury enters at the top. Most are filtered out as first-aid-only. A portion survive as recordable. And a very small slice at the bottom cross the reportability threshold. Getting the funnel right is the foundation of trustworthy safety data, and clean data is exactly what feeds metrics like your reliability and downtime metrics when equipment-related incidents overlap with maintenance events.
An injury or illness generally becomes recordable when it is work-related and results in one of the following outcomes beyond simple first aid:
The key word is work-related. An injury that would have happened regardless of the job, or that clearly stems from a personal condition, usually falls outside the log. Consistency here is what makes trend analysis honest, and the same discipline that powers a good Pareto analysis of your top incident causes applies to deciding what enters the log in the first place.
The single biggest source of over-recording is treating first aid as if it were medical treatment. First aid is a defined, closed list. If the response to an injury appears on that list, the case is not recordable, even if a nurse or clinic administered it. Common first-aid items include:
The moment treatment steps outside that list, prescription-strength medication, stitches, or a rigid immobilizing device used for treatment, the case flips to recordable. A useful mental model borrows from structured problem-solving: run each case through the criteria the same way an 8D investigation runs a root cause, so two similar injuries never get logged two different ways.
Reportability is a much higher bar and comes with a clock. While the exact triggers and windows vary by jurisdiction, the pattern is consistent: only the gravest outcomes require you to notify a regulator directly, and the notification deadline is short. Typical reportable triggers include:
Notice that a case can be recordable without ever being reportable, and in rare cases the reverse timing traps teams. Because the reporting window is measured in hours, the failure is almost never a bad judgment call; it is a delayed one. This is where your incident intake process needs the same rigor as a maintenance control plan, with a named owner and a defined escalation path the moment a severe injury is flagged.
A packaging line logs five injuries over a single week. Here is how each one sorts:
Result for the week: 4 recordable cases (events 2 through 5) and 2 reportable cases (events 4 and 5). Event 1 never enters the log. A plant that recorded all five would inflate its incident rate; a plant that missed the reporting deadline on events 4 and 5 would face a violation. The same event data that feeds these safety metrics can also expose an equipment root cause, tying an injury back to the machine condition tracked in your equipment effectiveness and maintenance strategy.
Whatever framework you follow, three habits keep your log defensible:
Structured intake also lets you connect a person injury back to a machine cause, which is where an asset and work-order system earns its keep. A guard-removal injury, a nip-point amputation, or a burn from an unexpected startup are all events that should generate both a safety record and a maintenance work order.
Fabrico is the real-time data foundation underneath your safety and maintenance workflows, not a compliance-reporting engine that decides recordability for you. Its EU-built, EU-data-residency CMMS captures work orders, assets, preventive schedules, and spare parts, so when an injury traces back to a machine, you can open a linked work order and see the asset history in one place. Fabrico's real-time OEE and production monitoring, including computer vision on machines that have no PLC, timestamps machine state and stoppages precisely, giving your EHS team an accurate record of what the equipment was doing the moment an incident occurred. That clean, time-stamped operational record is exactly what makes an incident log defensible and an investigation fast.
In practice, yes. A fatality, hospitalization, amputation, or loss of an eye all clearly meet the recordability criteria, so any reportable event should also appear in your internal log. The relationship is a nested funnel: reportable cases sit inside the larger set of recordable cases, which sit inside the even larger set of all work-related injuries.
No. Recordability is determined by the type of treatment, not by who provides it. If a licensed nurse applies only first-aid measures from the defined list, such as a bandage and non-prescription pain relief, the case stays first-aid-only and non-recordable. It becomes recordable only when the treatment itself exceeds first aid, for example a prescription or sutures.
Windows vary by jurisdiction, but the common pattern is very short: a fatality is often reportable within about 8 hours, while a hospitalization, amputation, or loss of an eye is often reportable within about 24 hours. Because the clock is measured in hours, always confirm the exact deadline for your region and build an escalation path that triggers the moment a severe injury is flagged.
Want a real-time, time-stamped operational record that makes your incident investigations fast and your logs defensible? Book a Fabrico demo and see how connected OEE and CMMS data supports a cleaner EHS process.