Multi-Location OSHA 300 Logs: How to Keep Establishment Records Straight

Keep a separate OSHA 300 Log for each establishment expected to operate a year or more, even when one central team manages all of them. Central tracking is fine as long as every case lands on the right establishment's log and each site's records can be produced on time.

Centralized software helps only if each injury still lands on the correct establishment log.

Keep a separate 300 Log for each establishment expected to operate for a year or longer (29 CFR 1904.30). An establishment is a single physical location where business is conducted; for mobile work such as construction or transportation, it is the office or terminal that supervises the work. Short-term establishments (under a year) still need records, but they can share one log per company, division, or region. Records may be kept centrally if case information reaches the central office within 7 calendar days and records can be produced in time for employee and government requests. Every employee must be linked to one establishment.

Keep a separate OSHA 300 Log for each establishment expected to operate for at least one year. A company-wide spreadsheet feels efficient until someone needs one site's log by the next business day, or one site's 300A for posting. The fix is an explicit establishment model: every employee has a home establishment, every case lands on exactly one log, and each site's forms can be produced on their own.

Whatever you use should make these easy to keep and retrieve:

• An establishment list with addresses, NAICS codes, and expected duration
• The home establishment for each employee, including remote and traveling staff
• The rule used to place cases that happen away from the home site
• The retrieval procedure for next-business-day and 4-business-hour requests

1. Map every employee to an establishment.
2. Set central reporting rules.
3. Review transfers and new sites monthly.
4. Test site-level exports before year end.

At the director level the question is less about one case and more about whether every site applies the rule the same way, with evidence you could show an inspector.

Keep these in mind when you compare approaches:

• Teams often build one corporate log and later struggle to produce site-specific records.
• Short-term establishments can be handled differently but still need recordkeeping coverage.
• A remote employee's home is not an establishment. Link telecommuters to the establishment they report to.

Spreadsheets fail quietly: a sort that renumbers rows, a tab copied for the new year, a formula that misses a new column. None of that shows on the printed form, which is why any system, including a spreadsheet, should be tested on real historical cases before it is trusted.

A home services company with 14 branches runs one central safety team. Each technician's profile names a home branch, every incident is entered against a branch, and each branch has its own 300 Log and 300A. When the Tulsa branch receives an employee's request for its log, it prints the Tulsa log alone, not a company-wide list with a location column.

300log is organized by establishment: each site has its own log, 300A, and exports, while one team can review every site from the same workspace.

• New Establishments and OSHA Logs: When to Start Separate Records
• Short-Term Establishment OSHA Logs: Projects, Sites, and Seasonal Work
• Centralized OSHA Recordkeeping: What Headquarters Can Manage and What Each Site Still Needs
• OSHA 300 Log Software Buyer's Guide: Features That Actually Matter