ZeroLapse

OSHA 300 Log & Section 24 Incident Export: How ZeroLapse Builds Your Records

HSE Compliance Resources · ZeroLapse

Recordkeeping for a workplace injury usually happens twice: once when it's actually dealt with — first aid, an incident report, maybe a corrective action — and again months later, in a scramble, when someone realises the OSHA 300 log or the Section 24 register is due and half the detail has to be reconstructed from memory. ZeroLapse now closes that gap. The same close-out process your team already uses in the Event Log now captures the handful of plain facts that matter for recordkeeping, and turns them straight into a working OSHA or Section 24 / COIDA export.

How it actually works

Nothing new to learn day-to-day. When a manager closes an Injury event — or an Incident event with an employee involved — ZeroLapse now asks a short, optional set of plain questions before it lets the case close:

Did it result in death?
Was the employee hospitalised overnight?
Did it require medical treatment beyond basic first aid?
How many days away from work, or on restricted duty?
What type of injury or illness?

That's deliberate. Nobody on your team is asked to make a legal call like "is this OSHA recordable?" or "is this a Section 24 incident?" — those are exactly the kind of judgement calls that get made inconsistently, or not at all, under time pressure. ZeroLapse asks for the facts, and works out what each jurisdiction's rules do with them.

For US teams: an OSHA 300/300A/301 pack

Download it from Upload/Download, pick a year, and ZeroLapse builds a spreadsheet matching the real forms:

Form 300 log — every recordable case for the year, correctly classified as a death, a days-away case, a job transfer/restriction case, or another recordable case, in that priority order — exactly how OSHA's own form works.
Form 300A summary — the annual totals, plus your average employee count and total hours worked (enter those once, ZeroLapse remembers them for next time).
Form 301 reports — one per case, pre-filled with everything ZeroLapse captured. Anywhere it genuinely doesn't have the detail — like the treating physician's name — the column is there, clearly marked to complete by hand, rather than left out or guessed at.

OSHA explicitly allows an equivalent form in any file format, as long as the required fields are present — this is built to match that column-for-column, so it can be used directly or copied onto the official forms. Form 300A still needs a company executive's sign-off before it's posted from February 1 to April 30; ZeroLapse gets you to that point, it doesn't replace the certification itself.

For South African teams: a Section 24 / COIDA pack

South Africa's OHS Act casts a wider net than OSHA — near-misses and dangerous occurrences are reportable even with nobody hurt, so the export reflects that:

Section 24 register — every near-miss logged, plus every closed injury or incident that crosses the actual Section 24 threshold: death, medical treatment, more than 14 days off normal duties, or an occupational disease. Anything below that threshold is correctly left off, not just dumped in regardless.
Annual statistics summary — the breakdown the Department of Employment & Labour's 1 March submission needs.
WCL1/WCL2 notification prep — WCL1 and WCL2 are the actual prescribed COIDA forms Section 24 notification uses (not a separate "COIDA form"), and each case is automatically routed to the right one: WCL1 for occupational disease and health-related cases, WCL2 for physical injuries — with the 7-day notification deadline worked out for you.

To be direct about scope: this is a records-preparation aid, not a filing service. It doesn't submit anything to the Department of Employment & Labour, OSHA, or the Compensation Fund on your behalf, and it doesn't track contractors on your site — only your own employees. Every export opens with a plain-language page explaining exactly what's filled in automatically and what still needs your input, so nothing is quietly assumed.

Why build it this way

The alternative — asking staff to judge recordability at the moment of closing an incident — tends to produce either under-reporting (nobody wants to be the one who calls it "recordable") or a spreadsheet nobody trusts. Capturing facts instead of judgements means the classification is consistent no matter who closes the case, and it means the same underlying data already works for two very different legal frameworks without asking your team two different sets of questions.

See it against your own incidents

Every plan includes a free 30-day trial, no credit card required — close out an incident, then download the export and see exactly what it produces.

Start Your Free 30-Day Trial

This article is general information and isn't legal advice. OSHA and OHS Act/COIDA requirements vary by industry and jurisdiction — consult OSHA's own published standards, the Department of Employment & Labour, or a qualified safety professional for guidance specific to your operation.