OSHA 300 Log Quality Control Checklist Before Certification

Before certification, check each case, not just the totals: work-relatedness, recordability, column, day counts, privacy status, and open updates. One late restriction or privacy flag can change the public annual summary.

The 300A summary is only as strong as the log review behind it.

Gather these first, and keep them with the record afterward:

• A sample of cases compared against their source documents
• Reconciliation of log totals with the 300A and any ITA file
• A list of corrections with dates and reasons
• Sign-off by the reviewer before the executive certifies

At the end of each year, 29 CFR 1904.32(a) requires you to review the 300 Log to verify that the entries are complete and accurate and to correct any deficiencies before you total and certify it. The review has to be as extensive as needed to make sure the entries are right. Recordkeeping violations carry maximum penalties of $16,550 per serious or other-than-serious violation and $165,514 per willful or repeated violation (2026 amounts), so the review is where most of the risk is removed.

1. Is each case work-related, with the basis or exception written down?
2. Is each case new, not a continuation of an earlier entry?
3. Does the recording criterion match the source documents (treatment, restrictions, days away)?
4. Is the right column checked, and are day counts calculated in calendar days from the day after the injury?
5. Are privacy concern cases flagged, with the names on the confidential list?
6. Is each description specific enough to identify the case without oversharing?
7. Do the log totals match the 300A, and does the 300A match any ITA file?
8. Can the establishment's records be produced within 4 business hours?

1. Review each case.
2. Reconcile the totals.
3. Resolve open facts.
4. Save the quality-control packet.

Tip: Check work-relatedness, recordability, classifications, day counts, privacy cases, and open medical updates before certification.

Teams review totals but skip individual case logic.

Most year-end corrections trace back to a fact missed months earlier: a restriction note that never reached safety, a case logged twice, or hours pulled from the wrong report. The fix is a monthly review of a sample of cases against their source documents, so year end is a confirmation rather than an investigation.

As the safety manager you usually own the decision itself, so the most useful habit is writing down the fact each call rests on at the time you make it.

• One late restriction or privacy flag can change the public annual summary.
• Sites that use their own local spreadsheets drift apart; one intake standard across sites prevents most of it.

Before certification, a safety manager works through the checklist for 26 cases. Twenty-three pass. One restricted case has no day count, one is missing its work-relatedness note, and one needlestick shows the employee's name instead of “privacy case”. All three are fixed, and the totals are rechecked against the draft 300A before it goes to the plant manager.

Every correction flows through to the 300A, the rates, and, for covered establishments, the ITA data, so a review that fixes the log has to reconcile those too.

300log shows which incidents are still in progress, keeps the 301 facts next to each log entry for review, and recalculates the 300A as you correct cases.

• OSHA Recordkeeping Internal Audit Checklist for Multi-Site Teams
• Common OSHA Recordkeeping Errors to Avoid in 2026
• Audit-Ready OSHA Recordkeeping Checklist for Safety Teams
• OSHA Amputation Reporting and Recordkeeping: What Safety Teams Should Do First