Yes, the 300 Form must stay updated during the five-year Cal/OSHA storage period, while the 300A and 301 forms may rest.
Key takeaways
- You must add newly discovered recordable injuries or illnesses to the stored 300 Form.
- You must reflect any change in the classification of an injury or illness already recorded.
- The 300A Annual Summary does not have to be updated during storage, though you may update it if you wish.
- The 301 Incident Report also stays optional to refresh, with the same freedom to update if you wish.
- You touch only the affected line on the log, not the whole file, and note what changed and why.
What the storage period asks of you
You keep closed job files because you may need them. That same logic applies to your Cal/OSHA records. Once the year closes and the annual summary goes up, the logs move into storage. They stay there for five years.
That storage window is active, not passive. One form in the folder still needs attention while it sits there. The California Department of Industrial Relations states the question plainly in its guide to Title 8, Section 14300.33 on Retention and Updating: do you have to update the Cal/OSHA 300 Form during the five-year storage period?
The answer is yes. The same section tells you what that update covers. You must bring stored 300 forms up to date for newly discovered recordable injuries or illnesses, and you must reflect any change in the classification of an injury or illness you already recorded.
Read that again with your own files in mind. A record that sat untouched for three years can still change. A doctor's final report may arrive late. A supervisor's correction may reclassify an entry. A claim adjuster's note may confirm something your first pass missed. When that happens, the stored 300 form needs the edit.
That is the whole point of the rule. The log is the living record. Everything around it can freeze. The log cannot.
Estimators and owners feel this most when they buy or sell a book of work, close out a long-running job, or hand a folder to counsel. A dusty 300 log with stale classifications is a liability in the making. A current one tells the story the way it actually unfolded.
The three Cal/OSHA records you store
Your stored set typically holds three pieces. Each one plays a different role during the storage period.
The 300 Log. This is your running list of recordable injuries and illnesses for the year. It carries the detail for each entry. It is the form that must stay updated while in storage.
The 300A Annual Summary. This is the year-end roll-up, and it goes into the folder. The rules let it rest.
The 301 Incident Report. This is the detail sheet for a single incident. It captures the specifics of one case. The rules let it rest too.
The 300 Log stands apart because it is the record of record. When a new fact surfaces about an old entry, the log carries it forward. The summary and the incident report do not carry that burden during storage.
The update rules side by side
Here is the short comparison you can tape inside the storage box lid.
Source for all three rows: California Code of Regulations, Title 8, Section 14300.33.
What "update" means in practice
The rule gives you two triggers. Both are concrete.
Newly discovered recordable injury or illness. Something you did not capture before now shows up as recordable. Maybe a case that looked minor turns serious. Maybe a record from a crew you no longer run gets found in an old folder. When it meets the recordable standard, it belongs on the 300 log for its year.
Classification change. An entry you already logged moves categories. The detail behind the entry shifts. The stored log must show the new classification, not the old one.
Neither trigger asks you to reopen the whole year. You touch the affected line. You keep the rest as it stands. The goal is accuracy on the line, not a redo of the file.
Keep your correction trail clean. Note what changed and why, inside the file. If the update comes from a late doctor's note, clip it in. If it comes from a supervisor's correction, note the date. The stored file should show its own history.
Why this matters to estimators and owners
Your stored Cal/OSHA file supports more than compliance. It sits behind bids, behind claims, and behind diligence when a deal moves.
If you keep closed job files for years, you already know the pattern. Old numbers resurface. Old facts get tested. The same holds for your Cal/OSHA logs.
A 300 log frozen at year-end may not match what the file shows later. A classification that should have changed sits unchanged. When someone pulls that folder, the gap shows.
Updating the 300 log during storage closes that gap. It keeps the story straight without reopening the whole record set.
For owners selling a firm, a current 300 log shows a clean maintenance habit. For estimators supporting a bid package, a current log means the safety record you cite matches the underlying detail. For a wider check of bid inputs, see construction estimate audit.
You also avoid the awkward conversation. Nobody wants to explain why a stored log still shows an old classification that the file itself contradicts.
Setting a review rhythm
The rule does not hand you a calendar. It tells you what must stay true during storage. You decide how often to check.
Pick a rhythm that fits your file flow. Some teams review stored logs when a late claim letter arrives. Others review on a set schedule tied to their closeout process. Others review when a folder gets pulled for any reason.
Whatever rhythm you choose, assign it to a name. A log with no owner drifts. A log with an owner stays current.
If you keep files across several offices or several years, put a one-line note in the front of each folder. Note who checks the 300 log and when. That line saves time later.
If your firm has a safety lead, that person is a natural fit. If the owner holds the hat, build the check into your own closeout routine. Either way, make the habit visible.
Ask your own compliance contact what rhythm fits your file volume and claim pattern.
What you can leave alone
Two forms get a rest during storage. Knowing which ones keeps your effort focused.
The 300A Annual Summary does not need to stay current. The rules say you are not required to update the annual summary, and you may do so if you wish. The summary reflects its year as closed.
The 301 Incident Report also does not need to stay current. The rules say you are not required to update the Cal/OSHA 301 Incident Reports, and you may do so if you wish.
You may still choose to refresh either one. Some teams update the summary when a late entry changes the year's picture. Some update an incident report when new detail arrives. That choice is yours.
The burden sits on the 300 log. Your effort goes there first.
This split keeps the workload sane. You protect the record that must stay true. You leave the supporting pieces as they were filed.
Building a simple stored-file check
A short pass through a stored folder keeps the log honest. Use this as your working order.
- Confirm the log belongs to the right year. Match it to the summary in the same folder.
- Scan for late arrivals. Look for claim letters, doctor notes, or adjuster mail that arrived after close.
- Check classifications. Confirm each logged entry still carries the right classification.
- Apply only the needed edits. Touch the affected line and leave the rest alone.
- Note what changed. Date the change and say why it landed.
- Re-file the log in its place. Keep the summary and incident reports alongside, untouched.
Run this pass when a folder gets pulled, when a late notice shows up, or on the rhythm you chose. The order works the same either way.
Where other record rules fit
Your Cal/OSHA logs live alongside other stored records. They follow their own rules. Do not blend them. For entry forms and deadlines, see OSHA injury records.
Federal audit rules can reach into your files when a negotiation or award is in play. The clause at FAR 52.215-2 on Audit and Records names who may look. One entry lists the Comptroller General of the United States, or an appropriate Inspector General appointed under section 3 or 8G of the Inspector General Act of 1978. That is a different doorway from a Cal/OSHA review, with its own scope.
Construction timelines run on their own clock too. Under RCW 4.16.310 in Washington, a cause of action that has not accrued within six years after substantial completion of construction, or within six years after termination of services, whichever is later, is barred, with a stated exception for an owner, tenant, or person in possession and control of the improvement when the action accrues. That rule is about claim windows, not record logs, and it sits outside California.
Keep these threads separate. Your Cal/OSHA storage duty stays focused on the 300 log. Other record rules answer other questions.
Next step today: pull a stored folder, open its 300 log, and compare each classification with any late claim letter or doctor's note in that file.
Related guides: Late freight: 4 steps to update posted material cost · Check 7 material storage rules for site safety compliance.
Questions you may hit
What if the late case belongs to an older year's file? You still bring that year's stored 300 log up to date. The rule covers newly discovered recordable injuries or illnesses during storage, so the log in that file gets the edit.
What if the classification change comes from outside your firm? Yes. The trigger is the change itself, so reflect it on the stored 300 log when it lands. A doctor, adjuster, or agency may drive the change.
Do I update the summary to match the new log entry? No requirement to do so. You may update the annual summary if you wish. The summary rests unless you choose otherwise.
Does the incident report need the same edit? No requirement to update the Cal/OSHA 301 Incident Reports. You may do so if you wish. Your log carries the duty.
What if two entries in the same year change at once? Both changes belong on that year's stored 300 log. Each line gets its own correction. Keep a note on each edit.
Who should I ask about my own file rhythm? Your own compliance contact knows your claim pattern and file volume. Ask them what review rhythm fits your firm.
The one-line takeaway
During storage, your 300 log stays alive. Your summary and incident reports can rest. Update the log when a late recordable case shows up or a classification moves. Keep the file ready for whatever pulls it next.
General information, not legal or tax advice.