How to Correct an OSHA 300 Log Entry After New Information

An injury entry can be accurate when it is first made and wrong a month later. A worker may initially receive treatment and then miss several days of work. A diagnosis may change. An employer may discover a recordable case that was omitted from a prior year's Log. Someone reviewing a spreadsheet may also find that a case was entered under the wrong outcome.

For an employer required to keep injury and illness records under OSHA Part 1904, the task is to make the stored Log reflect what is now known. OSHA's retention and updating rule requires the employer to update its stored OSHA 300 Logs during the five-year storage period for newly discovered recordable cases and changes in the classification of previously recorded cases. If a case's description or outcome changes, the rule says to remove or line out the original entry and enter the new information.

That instruction is narrower than a demand to recreate every document connected with the case. OSHA treats the Log, the annual Form 300A summary, the Form 301 incident report and data already sent through the Injury Tracking Application differently. This guide explains those differences and gives a practical review sequence. It is for people managing an employer's records, not for deciding a disputed medical diagnosis or making a case-specific legal determination.

First identify what changed

Do not start by editing a form. Start with the new fact and the case it concerns. The action differs depending on whether the employer has found a new recordable case, learned that an existing case has a different classification, received a changed outcome or discovered a simple transcription error.

| What the employer learned | The immediate recordkeeping question | Likely review path | | --- | --- | --- | | A case from a prior calendar year was never entered | Was it a recordable, work-related new case for that year? | Apply the recording criteria, then add it to the correct year's stored Log if it qualifies. | | An entered case later involved days away from work | Does the new outcome change the Log classification and day count? | Update the existing case on the original year's Log. | | A worker returned earlier or later than estimated | Does the Log's day count now differ from the supported count? | Replace the estimate with the supported count, subject to OSHA's counting rules. | | A description or outcome was entered incorrectly | What wording or classification should the Log now show? | Correct the existing entry in the way section 1904.33 describes. | | A new record appears to relate to an already logged injury | Is this a continuation of the old case or a new case under OSHA's criteria? | Check the new-case rule before deciding whether to update or add an entry. |

The table is an editorial workflow, not an OSHA form or an automatic conclusion that a particular case is recordable. OSHA's general recording rule requires the employer to consider work-relatedness, whether the case is new and whether a recording criterion is met. Where those facts are uncertain, gather the relevant information before classifying the case. If the decision depends on a medical opinion or a contested factual history, obtain appropriate case-specific advice. Do not use a generic example to override the actual evidence.

The OSHA 300 Log is the record that must be updated

The core rule appears in 29 CFR 1904.33. Employers covered by Part 1904 keep the OSHA 300 Log, any privacy case list, the annual summary and OSHA 301 Incident Reports for five years after the end of the calendar year the records cover. During that storage period, the employer must update the stored Log for newly discovered recordable injuries or illnesses and changes to the classification of previously recorded cases. A change in description or outcome calls for the original Log information to be removed or lined out and new information entered.

The phrase stored Log matters. Closing a calendar year or posting the annual summary does not turn the Log into an unchangeable historical snapshot. A later correction belongs on the Log for the year in which the case occurred. It is not generally a new injury in the year the correction was discovered. OSHA's rule on cases that cross calendar years says to record the case once, on the year-of-injury Log, and later update that initial entry when the day count becomes known or reaches the rule's cap.

An employer using paper can follow the regulation's direction to remove or line out the old entry and enter the new information. An employer using an electronic system should ensure the resulting stored Log and any printed equivalent form show the corrected information. OSHA permits computer records if the system can produce equivalent forms when needed. A separate internal note recording when a correction was made, what new fact prompted it and who reviewed it can help the team understand the decision later. That note is a sensible process control, not an extra OSHA form specified by section 1904.33.

A newly discovered case needs a recording decision

An employer may learn after the original entry window that a worker received medical treatment beyond first aid, had a recordable work restriction or sustained another outcome that meets the rule. The new information may show that a case should have been entered on a Log for an earlier year. Section 1904.33 requires newly discovered recordable cases to be added during the Log's storage period. It does not say that every newly discovered incident belongs on the Log.

The decision still begins with the Part 1904 tests: work-relatedness, a new case and a qualifying recording criterion. Section 1904.7 lists general outcomes including death, days away, restricted work or job transfer, medical treatment beyond first aid, loss of consciousness and certain significant diagnosed injuries or illnesses. Other Part 1904 provisions address particular case types. An employer should not infer recordability merely because a worker visited a clinic, submitted a workers' compensation claim or used the word injury in an internal report.

If the new facts establish a recordable case, add it to the Log for the year in which it occurred. Also check the initial Form 301 obligation. Section 1904.29 requires a Form 301 or equivalent incident report for each recordable case entered on the Log. Its seven-calendar-day initial entry rule begins when the employer receives information that a recordable injury or illness has occurred. A newly discovered case is different from an update to an existing Form 301: the initial incident report may still be needed even though section 1904.33 does not require employers to revise previously completed 301 reports during storage.

If the facts do not support a recording decision, record what information remains unresolved in the employer's case file and return to the question when the evidence is available. Do not fill a Log with speculative cases simply to make it appear cautious. Equally, do not treat a missing fact as proof that a case cannot be recordable.

Update the outcome when a case gets worse or better

A common correction begins with a case correctly recorded as medical treatment beyond first aid. Later, a clinician recommends days away from work. That may change the Log's most serious outcome and its day count. Conversely, an estimate of days away may need to be replaced with the actual count once the worker returns. The employer needs the facts behind the change and the correct Log year.

OSHA's general recording criteria explain how days away, restricted work and job transfer are counted. The injury day itself is not counted as a day away. Calendar days can include weekends and holidays when the worker was unable to work because of the injury or illness. The standard also addresses recommendations from health care professionals and permits a 180-day cap for the combined days away and restricted or transferred days. Those details make a day-count correction more than a spreadsheet arithmetic exercise.

Consider a worker injured in December who is still away when the annual summary is prepared. The cross-year provision in section 1904.7 directs the employer to estimate the total days away for the summary and later update the initial Log entry when the count is known or reaches the cap. The case stays with the year of injury. Do not create an extra case in January merely because the absence continued. If a restriction or medical recommendation is unclear, resolve that evidence before treating the example as a template for a real person.

For a change to the case description, keep the entry informative enough to identify the event and outcome, while applying the privacy rules discussed below. A vague replacement such as “incident occurred” may make the Log less accurate. An overly detailed description can unnecessarily expose sensitive information. The correct level of detail depends on the information required by the OSHA form and whether the case falls within a privacy category.

Do the 300A and 301 forms need the same change?

OSHA draws an express distinction between the stored Log and the two other forms. Under section 1904.33, an employer is not required to update an already completed Form 300A annual summary or Form 301 Incident Report during the storage period, although it may do so. A company should therefore avoid the blanket instruction “every Log change means you must reissue every form.”

The timing still matters. Before the original annual summary is completed, section 1904.32 requires the employer to review the Log, correct deficiencies, total the columns, certify the summary and post it. A known error found in that review should be corrected before the summary is prepared. After a summary has already been completed, section 1904.33 says that updating it is optional under that retention rule. This is not permission to knowingly certify an inaccurate new summary.

The Form 301 distinction is similar. The employer must prepare an initial 301 or equivalent report for each recordable case entered on the Log under section 1904.29. If later details of an existing case change, section 1904.33 does not require an update to that already completed report. The employer may choose to update it for internal consistency. The choice should take account of how the organization uses its incident records and whether another applicable requirement calls for a different record. Do not confuse that optional existing-report update with the initial report for a newly identified recordable case.

| Record after later information arrives | Federal Part 1904 position | Practical check | | --- | --- | --- | | Stored OSHA 300 Log | Update for a newly discovered recordable case or a relevant change to an existing one during storage. | Find the correct year and case; confirm the change is supported. | | Already completed Form 300A | Not required to update during storage under section 1904.33; an employer may update it. | Separate an old completed summary from one still being prepared and certified. | | Already completed Form 301 | Not required to update during storage under section 1904.33; an employer may update it. | Check whether this is an existing case or a new case that still needs its initial report. | | ITA data already submitted | OSHA's current FAQ says a later update is not required, while the underlying Log still must be updated. | Check the current ITA guidance and whether the edit window is open before promising any portal change. |

This table describes the cited federal rule and OSHA guidance. It is not a substitute for checking a state plan's applicable recordkeeping rules or a particular establishment's reporting duties.

What if the employer already submitted data to OSHA's ITA?

Some establishments submit information from Forms 300A, 300 and 301 electronically through OSHA's Injury Tracking Application. Section 1904.41 sets out categories based on establishment size and designated industry. Not every employer that keeps a Log routinely makes the same annual electronic submission. The correction question should not be answered by assuming that all employers use the portal.

OSHA's ITA FAQ addresses information that changes after an establishment has submitted data. It says the establishment is not required to update information already submitted, though it may do so within the stated submission-year window. It also expressly says that the employer is still required to update the underlying OSHA Form 300. Portal options and collection periods can change. Check OSHA's current instructions if the organization wants to revise a submitted dataset. Do not claim that editing a Log automatically edits or resubmits ITA data.

The distinction is useful when communicating internally. The safety team might have four separate facts to report: a corrected stored Log, whether a completed annual summary was voluntarily updated, whether a completed incident report was voluntarily updated and whether the submitted ITA dataset changed. Calling all four “the OSHA record” invites confusion. Keeping the decisions separate makes later questions easier to answer without inventing a universal resubmission duty.

This article does not replace the separate severe-event notification rules. A work-related fatality, inpatient hospitalization, amputation or loss of an eye can trigger a direct reporting duty under section 1904.39, regardless of the slower Log-correction workflow. If a new fact suggests such an event occurred, check that reporting rule immediately. The existing Complys guide to severe-event reporting explains that separate question.

Protect a privacy concern case while correcting it

An accurate Log is not a reason to disclose a worker's identity where OSHA requires special treatment. Section 1904.29 identifies defined privacy concern categories. For such a case, the employer enters “privacy case” instead of the worker's name on the OSHA 300 Log and keeps a separate confidential list linking case numbers to names. The regulation also allows a description to avoid details of an intimate or private nature where the case could otherwise be identifiable, while retaining enough information about the cause and general severity.

Before correcting a sensitive case, check whether the new wording would inadvertently identify the employee. The confidential identity list and the Log must still allow the case to be tracked correctly. This is especially important when a prior description is being replaced or an old entry is removed or lined out. A correction should improve accuracy without defeating the privacy handling that the rule requires.

Privacy concern status is not a discretionary label for every case an employer considers embarrassing. OSHA lists the categories in section 1904.29. Where the facts are uncertain, review the actual category and the form instructions. Do not use a broad internal confidentiality preference as a reason to leave required Log information out of an ordinary case.

A workable correction review for a multi-person team

OSHA sets the recordkeeping outcomes. The following sequence is an internal process suggestion for employers who need to coordinate safety, HR, supervisors and site managers. It is not a new OSHA-mandated approval process.

1. Locate the original case and year. Confirm the establishment and calendar year to which the case belongs. Avoid placing a continued absence on a second year's Log. 2. Describe the new information. Identify whether it is a new recordable case, a revised classification, a different day count, a changed description or a correction to a transcription error. 3. Check the underlying decision. Use the applicable work-relatedness, new-case and recording criteria. If the evidence is incomplete, seek the facts needed for that decision rather than guessing. 4. Update the stored Log. Apply section 1904.33 to the correct year's entry. Where the description or outcome changes, follow its direction to remove or line out old information and enter the new information. 5. Review connected records separately. Ask whether a newly discovered case needs an initial 301. For an already completed 301 or 300A, distinguish the optional update rule from the initial preparation duty. 6. Check ITA only if relevant. Confirm whether the establishment submitted the affected data and consult current OSHA portal instructions before changing a submission. 7. Protect privacy. Confirm whether the case is within OSHA's privacy categories and whether the corrected description discloses too much. 8. Record the internal reason for the change. Keep a concise note of the new fact, source, review date and person responsible. This helps the team reconstruct the decision. It is an internal good practice, not a separate OSHA form requirement. 9. Use the corrected data in the safety process. If the change reveals a hazard trend or failed control, consider whether the underlying safety assessment needs attention. That is a management follow-up, not a change to the Log rule itself.

The most useful control is a clear route for new facts to reach the person who owns the Log. A physician's revised recommendation may reach HR first. A worker's absence may appear in payroll. A supervisor may learn that a restriction continued longer than estimated. A year-end form review will not catch a change nobody communicates. An internal handoff can keep the record accurate without asserting that OSHA prescribes this exact workflow.

Three examples of corrections that should not be confused

Later days away. A case was initially logged as medical treatment beyond first aid. A later recommendation and the worker's actual absence may change the classification and day count. Review the facts under section 1904.7, then update the original year's Log as needed. Do not add a second case merely because time has passed. If the prior year's 300A was already completed, section 1904.33 does not require its update, though the employer may choose to do so.

A previously missed case. A manager receives information about an injury from last year and realizes it may have met a recording criterion. Apply the work-relatedness, new-case and recording tests first. If it was recordable, add it to the stored Log for that year during the retention period and address the initial 301 requirement. Do not call it an optional 301 revision when no incident report was ever prepared for that case.

An already submitted 300A. An establishment discovers a changed outcome after sending annual data through ITA. Correct the underlying Log if section 1904.33 requires it. OSHA's current ITA FAQ says the employer need not update data already submitted, though an update may be available within its stated window. Keep the local correction and the portal-submission decision separate. Do not promise that a vendor system can perform a resubmission without confirming the actual product and current portal process.

These examples explain the decision path. They do not decide whether an actual medical record, treatment, job restriction or later event meets OSHA's criteria. The case facts, applicable regulation and relevant professional evidence control that result.

Where this sits in the wider recordkeeping process

The correction workflow begins after an employer has established that Part 1904 applies and has made or should have made an entry. It is not a full guide to who is exempt, how each injury category is defined, what an executive must certify or how electronic submission thresholds work. The live Complys OSHA 300 overview covers the wider structure of the three forms. Use the specific OSHA provisions cited above when the actual case turns on a threshold, a privacy category, an unusual medical outcome or a State Plan rule.

For a recordkeeping team, the practical test is simple to state but important to apply carefully: Does the stored Log still tell the truth about the case, in the correct year, under OSHA's recording criteria? If not, determine the supported correction, make it on the Log and document the internal reason. Then separately decide whether any optional update to an old summary, old incident report or already submitted ITA data is useful or available. Keeping those questions distinct is the clearest way to avoid an inaccurate Log and an invented resubmission requirement at the same time.

If your organization is evaluating how to manage incident evidence and follow-up across sites, explore Complys for US businesses and ask to see the current workflow that fits your team. Confirm any OSHA-form functionality in the product itself before relying on it for statutory records or submissions.

Related guides

See also: OSHA 300 Logs for Multiple Establishments and Short-Term Jobsites, OSHA 300 Privacy Concern Cases: the Log and Confidential List.