What this form is
This is a fillable, printable log modeled on OSHA Form 300, the Log of Work-Related Injuries and Illnesses referenced on the page as 29 CFR Part 1904. It is a data-entry form with a running tally, not a calculator. You enter one row per case and the summary block updates as you type. A new log opens with the current year, today’s date in the certification block, and three blank case rows numbered 001, 002, and 003. Case numbers are zero-padded to three digits and renumber themselves whenever you delete a row, so the sequence never develops gaps.
The establishment header sits above the table: establishment name, address, year, industry description, SIC or NAICS code, average annual employees, and total hours worked by all employees. Company name pre-fills from your saved business profile if you have one. Worth knowing up front: the employee-count and hours fields are stored and printed, but no calculation uses them. This tool does not compute an incident rate from them.
Filling out a case row
Each row holds the case number, employee name, job title, date of injury or onset, where the event occurred, and a free-text description of the injury and body part. Then come two mutually exclusive choices. Classification is one of four radio buttons — Death, Days away from work, Job transfer or restriction, or Other recordable case — and because they are radios, selecting one clears the rest, so every case carries exactly one classification. Injury type is one of six — Injury, Skin disorder, Respiratory, Poisoning, Hearing loss, or All other illnesses — and every new row starts on Injury by default. The two numeric columns, days away and days restricted or transferred, are tallied separately and never combined.
How the annual summary totals are built
Total Cases counts every row in the table, checked or not. The four classification counters only increment when their radio is selected. Total Days Away and Total Days Restricted are plain sums of the two numeric columns, and any non-numeric entry contributes zero. The Cases by Injury Type block at the bottom is stricter still: it counts a row only if that row has both the injury type you are looking at and a classification selected.
Worked example on a fresh log. Mark case 001 as Days away from work with 8 days away, mark case 002 as Job transfer or restriction with 5 days restricted, and leave case 003 untouched. The summary reads Total Cases 3, Deaths 0, Days-Away Cases 1, Restricted Cases 1, Other Recordable 0, Total Days Away 8, Total Days Restricted 5. Cases by Injury Type shows Injury 2, since both filled rows are still on the default injury type, and zero across the other five. That gap between 3 and 2 is your signal that a row is sitting there unclassified.
Saving, printing, and exporting
Save Log writes to browser local storage on the current device. Print / PDF saves first, then opens the print dialog with a centered title block and a signature rule beneath the certification statement. Export CSV downloads ten columns — case number, employee name, job title, date, location, description, classification, days away, days restricted, and injury type, with the two radio selections written out as readable labels — named for the log year. When an incident actually happens, the narrative detail belongs in a workplace incident report first; this log is the annual roll-up, not the investigation record.
Common mistakes and limitations
Two mistakes account for most bad logs here. The first is leaving default blank rows in place, which quietly inflates Total Cases. The second is treating the injury-type radio as scenery: it silently defaults to Injury, so hearing loss and respiratory cases get miscategorized unless you actively change it. If your prevention work is what needs attention rather than your paperwork, the job hazard analysis builder and the safety inspection checklist are the upstream tools.
Limitations.This form is an educational planning aid and a convenient way to keep your own records legible. It is not the official OSHA form, it does not determine recordability, and it does not replace your employer determination or a competent person’s judgment. Which establishments are covered, what counts as recordable, how long records must be kept, when a summary must be posted, and whether electronic submission applies to you are all set by the standard itself. Verify every one of those against the current text of the applicable OSHA recordkeeping standard and your own safety program before you rely on anything produced here.
Frequently Asked Questions
Does the tool decide whether an injury is recordable?
No. It records what you enter and nothing more. There is no logic in the form that evaluates first aid versus medical treatment, work-relatedness, or whether a case belongs on the log at all. That determination is yours to make against the applicable OSHA recordkeeping standard, with your safety director or counsel. The form only gives you a structured place to write the decision down once you have made it.
Why does Total Cases not match the Cases by Injury Type totals?
Total Cases counts every row in the table, including rows you have not filled in. The Cases by Injury Type sub-totals only count rows that have a classification radio selected. A new log opens with three blank rows, so if you enter two cases and leave the third row alone, Total Cases reads 3 while the injury-type totals add up to 2. Delete the unused rows before printing and the two numbers will agree.
Where is my log data stored?
In your browser local storage on the device you are using. Nothing is uploaded to a server. That means the log is private to that browser, but it also means clearing site data, switching machines, or using a different browser will lose it. Export CSV after any substantial editing session and keep the file with your other year-end records.
Can I keep separate logs for more than one establishment or year?
Yes. Each save creates its own record, and the All Logs screen lists them sorted newest year first, labeled with the establishment name, the year, and the number of case rows. Use New Log to start a clean one rather than editing last year in place, since establishment-level fields such as average annual employees and total hours worked are stored per log.