
Rules
How OSHA recordkeeping rules shape process control documentation
Operations process control must carry OSHA recordkeeping duties: 300, 300A and 301 forms, five-year retention, and the criteria that decide what gets logged.
What to take away
- Operations process control and OSHA recordkeeping overlap where a shift log entry becomes evidence about an injury, so both systems must agree on names, times and job titles.
- 29 CFR Part 1904 requires three formsthe OSHA 300 log, the 300A annual summary and the 301 incident report.
- You keep injury and illness records for five years, and the 300A must stay posted through April of the following year.
- Medical treatment beyond first aid and restricted duty are the two criteria that most often turn a minor event into a recordable case.
- California runs its own recordkeeping program, Texas covers private employers under federal OSHA, and Washington adds requirements on top of the federal rule.
- Recordkeeping failures show up in enforcement data as citation items, usually alongside a hazard finding rather than alone.
What 29 CFR 1904 actually requires of an operations manager
The rule is short and the obligations are narrow. If you run a plant, you must record every work-related fatality, every injury and illness that meets a recording criterion, and you must do it on the forms OSHA prescribes.
Start with the scope. 29 CFR Part 1904 covers most private employers in general industry. The 29 CFR 1904 standard places the duties that matter to a plant manager in sections 1904.4 through 1904.11 for recording, 1904.29 through 1904.32 for the forms, and 1904.33 through 1904.40 for retention, access and reporting.
OSHA publishes the recordkeeping rules that govern the forms, the recording criteria and the retention duties in one place, which makes it the cheapest reference to keep bookmarked.
What the rule does not require is a particular process control system. Nothing in 1904 tells you to log a control room alarm, a batch deviation or a shift handoff. Those records exist because your process needs them, and the rule only reaches them when they become the best evidence of what happened to a worker.
That distinction matters for how you assign work. The EHS manager owns the 300 log. The operations manager owns the process records that feed it. A recordable determination made without the shift log is a guess.
Three duties fall on operations specifically. First, tell the recording authority about every work-related injury your crew reports, including the ones that look trivial at the time. Second, preserve the process records that establish exposure, timing and task. Third, keep the two record sets consistent, because a compliance officer will read them side by side.
Deadlines are tight and fixed. A fatality must be reported to OSHA within eight hours. An in-patient hospitalization, amputation or loss of an eye must be reported within twenty-four hours. Everything else goes on the log within seven calendar days of learning about it.
The rule also reaches employee access. Under the 1910.1020 record access requirements, workers and their designated representatives can request exposure and medical records, and you must provide them within fifteen working days.
If you have an OSHA Process Safety Management Checklist, the exposure records it generates fall under that access duty too.
One practical point: the person who decides recordability should not be the same person whose shift performance is being measured. Separate the roles, or the close calls disappear from the log.
The OSHA 300, 300A and 301 forms and where process-control logs intersect them
The three forms do different jobs, and operations staff usually see only one of them.
OSHA Forms and Process Records
OSHA 300 log
- Owner
- EHS manager
- Trigger
- Recordable case within 7 days
- Process control intersects
- Job title, department, shift from roster and shift log
OSHA 300A summary
- Owner
- Plant manager signs
- Trigger
- Posted Feb 1 to Apr 30
- Process control intersects
- Establishment identity must match site scope
OSHA 301 incident report
- Owner
- Supervisor plus EHS
- Trigger
- Within 7 days of case
- Process control intersects
- Task, equipment state and sequence from control room record
Control room shift log
- Owner
- Operations
- Trigger
- Every shift
- Process control intersects
- Supplies timing, alarm sequence
The OSHA 300 log is the running register. It holds one line per case with the employee's name, job title, date, where the event happened, a description, and the classification of the outcome. It stays in the establishment and is updated as cases develop.
The 300A is the annual summary. It aggregates the year's numbers by establishment, gets signed by a company executive, and is posted where employees can see it from February 1 through April 30.
The 301 is the incident report. It captures how the injury happened, what the employee was doing, what equipment or substance was involved, and what the physician or other health care professional said. This is the form where process records earn their keep.
OSHA forms and process-control logs
| Record | Owner | Trigger | Where process control intersects |
|---|---|---|---|
| OSHA 300 log | EHS manager | Recordable case within 7 days | Job title, department and shift come from the roster and the shift log |
| OSHA 300A summary | Plant manager signs | Posted Feb 1 to Apr 30 | Establishment identity must match the site your control system is scoped to |
| OSHA 301 incident report | Supervisor plus EHS | Within 7 days of the case | Task, equipment state and sequence come from the control room record |
| Control room shift log | Operations | Every shift | Supplies timing, alarm state and who was at the board |
| Batch or run record | Operations or quality | Every run | Establishes what the process was doing when the exposure occurred |
Read the table as a chain of custody. The 301 asks what the employee was doing, and the control room log is often the only document that answers it with a timestamp.
That is why the two systems should share identifiers. If the 301 says the operator was clearing a jam on line three at 02:14, the shift log should say the same thing in the same words. Mismatched descriptions are the easiest inconsistency for an investigator to find.
The 300 log itself is not a narrative document, and you should resist the urge to make it one. Keep the description short and factual. Detail belongs on the 301 and in the process records.
A note on privacy. You do not enter the employee's name on the 300 log for a case involving intimate body parts, mental illness or HIV, and you use "privacy case" instead. The 301 still carries the name and stays confidential.
Retention periods: five years, and which control-room records fall outside them
The injury and illness records retention period is five years following the end of the calendar year the records cover. That means a 2026 case stays available into 2032.
Retention Periods for Records
- 5 years after calendar yearOSHA 300, 300A, 301, privacy case list
- 30 yearsEmployee exposure records under 1910.1020
- Employment plus 30 yearsMedical records under 1910.1020
- Life of processProcess safety information under PSM
The five years applies to the 300 log, the 300A summaries and the 301 reports, plus the privacy case list and the annual summary worksheets. If you keep the records on a computer, you must be able to produce a copy for an OSHA representative at the establishment within four business hours.
The 300A posting duty is separate and shorter. Post it by February 1 and leave it up through April 30. Posting is not the same as retention, and a plant that pulls the summary down in May has not destroyed anything.
Now the part operations managers get wrong. Most control-room records are not covered by 1904 at all. Shift logs, alarm histories, trend data, batch records, operator round sheets and maintenance work orders fall under other rules and other retention schedules.
Those other schedules are often longer. Under 1910.1020, employee exposure records are kept for thirty years, and medical records for the duration of employment plus thirty years. Process safety information under the PSM standard has its own life-of-the-process expectation.
So the practical rule is this: the shortest clock is not the one that governs. A shift log that supports an exposure record may need to survive thirty years even though the 300 log entry tied to it only needs five.
Build the retention schedule around the longest applicable requirement, then decide what the operations system keeps for its own purposes. Storage is cheap. Reconstructing a shift from memory is not.
Two housekeeping points. Keep the 300 and 301 records for each establishment separately, because the rule is written per establishment. And if you close a site, the records still have to be retrievable for the remainder of the five years.
Recording criteria: medical treatment, restricted duty and the control-room shift log
Is the Case Recordable?
Is the case work-related and meets a general criterion?
Record on OSHA 300 log
Not recordable under 1904
Medical treatment beyond first aid is the criterion that catches most plants off guard. First aid includes things like a simple bandage, a tetanus shot, over-the-counter pain relief, drinking fluids for heat stress, and using a finger splint. Anything past that list is generally medical treatment.
Restricted duty is the second trap. If you keep a worker on the job but limit their tasks or hours because of the injury, the case is recordable as restricted work, even if they never miss a day.
Both determinations depend on facts that live in the process record. When did the symptoms start? What was the worker doing? Was the exposure continuous or a single event? Was the task a routine part of the job or an exception?
This is where an operational risk assessment matrix helps, because it forces you to name the exposure and the task before an incident happens rather than after.
Here is a worked example. An operator reports a burn on the forearm at 14:20 during a manual valve change on a steam header. The shift log shows the valve change at 14:12 and a high-temperature alarm at 14:14. The clinic debrides the burn and prescribes a topical antibiotic.
Debridement is medical treatment beyond first aid, so the case is recordable. The 300 log gets a line the same week. The 301 describes the task and cites the alarm time. The shift log and the alarm history are preserved under the exposure record schedule, not the five-year schedule.
Now change one fact. If the clinic only cleaned the burn and applied a bandage, the case is first aid and stays off the 300. The process records still exist, but the OSHA duty does not attach.
The lesson is that the same physical event can go either way, and the deciding facts are clinical. Operations supplies the sequence, the clinician supplies the classification, and neither should guess at the other's part.
Keep the shift log structured enough to answer these questions later. Free-text narrative is fine for context, but the timestamp, the equipment tag, the task name and the personnel on shift should be fields, not sentences.
How state plans in California, Texas and Washington change the federal baseline
Roughly half the states run their own occupational safety and health programs, approved and monitored by federal OSHA. The OSHA state plans index lists which states operate their own programs and which rely on federal enforcement.
State Plan Recordkeeping Differences
California
- Program
- Cal/OSHA
- Forms
- State forms required
- Retention
- State instructions
Texas
- Program
- Federal OSHA for private sector
- Forms
- Federal forms
- Retention
- Federal retention
Washington
- Program
- Department of Labor and Industries
- Forms
- State rules generally stricter
- Retention
- Check state additions
California runs Cal/OSHA, which has its own recordkeeping regulation, Title 8 Section 14300. The forms are the same in substance, but the state publishes its own versions and the posting and reporting mechanics follow state instructions. Employers in California should use the state forms, not the federal ones, because the state rule is the operative one.
Texas is different. Private-sector employers in Texas are covered directly by federal OSHA, and the state's program covers public employees only. A Texas manufacturer files federal forms, follows federal retention, and deals with federal area offices.
Washington runs the Department of Labor and Industries, and its safety and health rules are generally stricter than the federal baseline. Washington employers should treat the state rule as the starting point and check for additions rather than assuming the federal text is complete.
The pattern generalizes. A state plan can add reporting triggers, change the posting window, or require the state's own forms. It cannot reduce the federal floor.
For a multi-site operator, that means one corporate standard and three local overlays. Build the corporate standard on 29 CFR 1904, then list the state deviations by site.
Do not assume a state plan is a formality. California and Washington both enforce actively, and a corporate template written in Texas may miss a state-specific posting or reporting step.
Where recordkeeping failures turn into citations: reading OSHA enforcement data
Recordkeeping violations rarely stand alone. In practice they appear as additional citation items attached to a hazard finding, which is why they are easy to underestimate when you scan penalty totals.
The most-cited items are failure to record a recordable case and failure to record it within seven calendar days. Others include a missing 301, an uncertified 300A, and failure to provide access to records on request.
The OSHA enforcement data is published by standard, so you can pull the citation history for 1904 and see which paragraphs are cited most often in your industry. That is a better use of an afternoon than reading a summary of penalties.
Use the data as a diagnostic. If failure to post the 300A shows up repeatedly, your posting calendar is the problem, not your judgment. If failure to record shows up, your reporting culture is the problem.
A quality management checklist approach works here: list the duty, name the owner, name the evidence, and check it on a schedule.
The pattern to watch for is a gap between what the process record shows and what the 300 log says. An inspector who reads both will find it, and it converts a single hazard citation into a recordkeeping citation as well.
Building a documentation map that satisfies 1904 and your process control system
A documentation map is a single table that names every record, who owns it, what triggers it, where it lives and how long it stays. Build one, and the annual audit becomes a checklist rather than a project.
This is also where exceptions, handoffs and watching leave a trace, because the map is where a verbal handoff either gets written down or disappears.
Start with the OSHA records and work outward. Then add the process records that support them. Then add the records that exist for other reasons and note which ones can be pulled into an OSHA response if needed.
Documentation Map Steps
- List every record mentioning person, time, task
- Assign one owner per record as a role
- Write the trigger for each record in one sentence
- Set retention from longest applicable rule
- Define how records link via case number
Then test the map before you need it. Pick a closed case from last year and try to reconstruct it from the records alone, without asking anyone who was there.
If you cannot reconstruct the sequence, the map has a hole. Fix the field, not the narrative.
A few habits keep the map alive. Review it when a process changes, because a new unit means new exposure records. Review it when a state rule changes. Review it after every recordable case, because that is when you learn what the map missed.
The SOP vs Work Instruction distinction matters here. A procedure tells you what the process is. A work instruction tells you how to do one task. The record tells you what actually happened, and only the record answers an OSHA question.
Finally, keep the map short enough to use. If it runs to forty pages, nobody will open it. One page per record type, with the owner and the retention rule, is enough for most plants.
The test of the whole system is simple: when a worker is hurt, can you produce the sequence of events, the exposure record and the completed forms without a debate about whose file they are in? If yes, the process control system and the recordkeeping rule are doing the same job.
- Every recordable case has a 300 log line within seven calendar days
- The 301 is complete, including the task and equipment description
- The 300A is certified and posted from February 1 through April 30
- Injury and illness records are retained for five years after the covered year
- Exposure records are retained for thirty years and medical records for employment plus thirty
- Shift logs capture timestamp, equipment tag, task and personnel as fields
- Case numbers link the 301, the shift log and the maintenance work order
Treat the checklist as a quarterly review, not an annual one. Most recordkeeping citations are timing failures, and timing failures are visible long before an inspector arrives.
Common questions
What is the retention period for OSHA injury and illness records?
Five years following the end of the calendar year the records cover. That applies to the 300 log, the 300A summaries, the 301 reports and the privacy case list.
Does a control room shift log count as an OSHA record?
Usually not. Shift logs are process records and fall under your own retention schedule, though they may become exposure records under 1910.1020 if they document a worker's exposure.
When is an injury recordable if the worker stays on the job?
When the worker is placed on restricted work or transferred to another job because of the injury. Restricted duty is a recording criterion even with no days away.
Do California and Texas follow the same recordkeeping rules?
No. California runs Cal/OSHA with its own recordkeeping regulation and forms, while private employers in Texas are covered directly by federal OSHA.
Who signs the OSHA 300A?
A company executive, which means an owner, a corporate officer or the highest-ranking company official at the establishment. The signature certifies that the summary is accurate.
How fast must you provide records to an OSHA representative?
If the records are kept off site, you must produce a copy at the establishment within four business hours of the request.







