
Key Takeaways
- Hotels are not exempt: NAICS 7211 is absent from the partial-exemption list in Appendix A to Subpart B of Part 1904.
- The injury rate says why: traveler accommodation recorded 3.8 total recordable cases per 100 full-time equivalent workers in 2024, against 2.3 for private industry.
- What the rule requires: 29 CFR 1904.29 sets the 300, 300A and 301 forms, and 1904.32 sets the February 1 to April 30 posting.
- Where the mandate stops: Part 1904 requires no corrective action verification and no closed loop.
- What that leaves: a complete log and a hazard somebody reported in March that nobody confirmed was fixed.
A housekeeper reported a loose carpet edge on the fourth floor in March, and 7 months later it is still there for the next guest to catch a heel on. Nobody ignored it, and the report was handled correctly on the day it arrived. Your records are in order too: every recordable injury from the past year is logged, and the annual summary went up on February 1.
Both of those things are true at once, and the gap between them is where most hotel safety programs lose ground. That log is a record of what happened to people. Nothing in it asks whether the hazard that caused the injury was ever repaired.
What OSHA Requires a Hotel to Record
That question of repair follows a prior one, which is whether the log applies to a hotel at all. The answer is in Appendix A to Subpart B of Part 1904, which lists the industries exempt from routine recordkeeping, and NAICS 7211, traveler accommodation, is not among them. Rooming and boarding houses at 7213 are listed, and so are restaurants at 7221, which is where the confusion usually starts.
The injury data behind that list explains the distinction. Accommodation work is more hazardous than the exemption question implies, and BLS recorded 3.8 total recordable cases per 100 full-time equivalent workers in traveler accommodation in 2024, against 2.3 across private industry. A hotel is not a low-hazard workplace in the way the exemption list means it.
What the rule sets | Where it says so |
|---|---|
The 300 Log, the 300A Summary and the 301 Incident Report | 29 CFR 1904.29 |
More than 10 employees in the last calendar year | 29 CFR 1904.1 |
Post the summary by February 1, keep it to April 30 | 29 CFR 1904.32(b)(6) |
Keep the records 5 years after the year they cover | 29 CFR 1904.33(a) |
Report a fatality in 8 hours, a hospitalization in 24 | 29 CFR 1904.39 |
Those 5 rows are the whole recordkeeping obligation, and most properties meet them. The documentation layer is already there at most properties, maintained by people who know the forms and who have been completing them correctly for years.
What the Rule Does Not Ask For
Read those 5 rows again for what is missing from them. Part 1904 requires no root cause analysis, no corrective action record, no verification that a fix worked, and no closed loop from the hazard to its repair. The obligation is to record the injury accurately and keep the record.
Because none of that is required, 2 hotels can meet the identical standard while running quite differently. One of them logs the slip and moves on to the next shift. The other logs the slip, assigns the carpet repair to engineering and checks 30 days later that it held. It can show that history to a regional director. OSHA's recordkeeping rule treats those 2 properties as identical, because the rule measures the record.

Where the Report Stalls
The stall is rarely in the reporting itself. A housekeeper tells a supervisor, the supervisor completes the 301, and the incident enters the log correctly. What happens next usually leaves the system entirely, into an email to engineering, a line in a shift handover, or a verbal instruction at the morning meeting.
None of those 3 places is retrievable 3 months later. When a regional director asks which corrective actions from the second quarter are still open, somebody reconstructs the answer from inboxes. That reconstruction is how an open action becomes a repeat incident at the same location.
Before you buy anything to fix that, test the current process on 3 real incidents:
- Name the corrective action each one produced.
- Find who owned it and the date it was due.
- Show the evidence it was completed.
- Check whether anybody confirmed it still held a month later.
Run that test on incidents from last year, where memory has already faded. A recent action is still in somebody's memory, which hides the problem. If the 4 answers for a 9-month-old incident come from an inbox search, the loop is open and nobody knows it.
Connect the incident to a verified fix.
KC Safety connects incident intake to a corrective action with an owner, a due date and a verification step.
What a CAPA Workflow Adds to the Same Incident
Corrective action tracking software puts that second half in the same record as the incident itself, through a corrective and preventive action workflow. That incident produces an action, the action carries an owner and a due date, and a verification step asks later whether it worked. The OSHA form is still generated, and now a verified repair is attached to it.
That verification step is the part most properties skip, and it is where repeat incidents come from. A carpet repaired in March can lift again in June, and a procedure changed after that incident can revert when the supervisor who changed it moves property. A 30, 60 and 90 day verification cycle is what catches both.
Multi-Property Groups Have a Second Problem
A portfolio adds a question that a single property never faces. The 300 Log is kept per establishment, so a hazard pattern that appears across 8 hotels is invisible in 8 separate logs, each of which looks unremarkable. Nobody at any single property is looking at the same hazard twice.
A system that holds every property's incidents with a location on each one answers that pattern question directly. One corrective action workflow then runs at every site, and a regional safety manager filters by location to see which hazard type keeps recurring where. How hotel departments define ready covers the training side of the same consistency problem.
What KC Safety Gives a Hotel Safety Team
That cross-property view starts at intake, which is where KC Safety begins, and the OSHA forms come out of the intake without being typed again. It generates the 300, 300A and 301 from the incident data, which removes the manual transfer between an incident form and the log that produces transcription errors. The record an auditor asks for is a by-product of the work.
The corrective action lives on that same incident record. Each one carries a classification, an owner and a verification step at 30, 60 and 90 days. The question of whether a fix held then has an answer with a date on it. Nothing in that chain depends on an email thread surviving a change of staff, a change of system, or the departure of the manager who sent it.
Those locations are configured once and used everywhere after that. Each of those incidents carries its property, routing rules assign by location, and reporting filters by it.
That filter is what gives a group the cross-property view 8 separate logs cannot produce. Where one of those corrective actions is a training gap, the KC LMS integration turns it into an assignment with a completion record. Training courses for hotel employees covers choosing that content.
Run that 4-question test on 3 incidents from last year this week. Count how many of the 12 answers come out of a system, and how many come out of an inbox. That count is the business case for changing the process, and producing it costs an afternoon of somebody's time against the procurement cycle it replaces.
Frequently Asked Questions
1. Are hotels required to keep an OSHA 300 log?
Yes, in most cases. NAICS 7211, traveler accommodation, does not appear on the partial-exemption list in Appendix A to Subpart B of Part 1904, so a hotel with more than 10 employees at any time in the last calendar year keeps the records. 29 CFR 1904.29 sets the 300 Log, the 300A Summary and the 301 Incident Report.
2. Does OSHA require corrective action tracking?
No. Part 1904 is a recordkeeping rule: it prescribes what to record, on which form, how long to keep it and what to report. It requires no root cause documentation, no corrective action record and no verification that a fix worked. Two hotels can meet the same standard with very different safety outcomes.
3. When does the annual summary have to be posted?
29 CFR 1904.32(b)(6) requires the summary to be posted no later than February 1 of the year following the records it covers, and kept in place until April 30. Under 29 CFR 1904.33(a) the log, the annual summary and the 301 forms are kept for 5 years following the end of the calendar year they cover.
4. How hazardous is hotel work compared with other industries?
More than the exemption question suggests. BLS recorded 3.8 total recordable cases per 100 full-time equivalent workers in traveler accommodation in 2024, against 2.3 across private industry. That difference is the practical reason 7211 sits outside the low-hazard exemption list.
References
- Legal Information Institute. Appendix A to Subpart B of Part 1904, Partially Exempt Industries. law.cornell.edu
- Legal Information Institute. 29 CFR 1904.29, Forms. law.cornell.edu
- Legal Information Institute. 29 CFR 1904.32, Annual Summary. law.cornell.edu
- Legal Information Institute. 29 CFR 1904.33, Retention and Updating. law.cornell.edu
- Bureau of Labor Statistics. Table 1, Incidence Rates of Nonfatal Occupational Injuries and Illnesses by Industry, 2024. bls.gov