Problem guide
Safety and compliance paperwork is always behind
Safety paperwork runs behind because the facts happen where the work is done, on a jobsite, a dock, a kitchen or an exam room, and the record is built later in the office from a text, a call or a skipped form. The legal clocks do not wait. An employer has seven calendar days from learning of a recordable injury to enter it on the OSHA 300 Log and 301 report (29 CFR 1904.29(b)(3)). Capture the facts at the source and start that clock the day the report arrives.

How it actually happens
A tech slips on a ladder on a Tuesday. He finishes the call, mentions it to the foreman, and keeps working. The foreman texts the office manager that evening. Nobody writes down that the office heard about it on Tuesday. That date is the start of a legal clock, and it is already lost. Swap the ladder for a wet dock plate, a hot pan or a patient transfer and the story is the same.
Here is how the rest of a typical case runs, as an example. On Thursday the injured worker sees a doctor and gets a prescription. That makes it medical treatment beyond first aid, one of the recording criteria in 29 CFR 1904.7. The office manager does not know about the doctor visit until the following week, when a workers' comp form arrives. Now the question of whether it is recordable gets decided late, the 301 gets written from a phone call, and the 300 Log entry waits for the next quiet afternoon. In January, someone prepares the annual summary and finds two cases that were never entered.
None of the people in that chain did anything careless. The worker reported it. The supervisor passed it on. The office manager is also running payroll and answering the phones. The problem is the shape of the handoff: the facts are created where the work happens, the record lives in the office, and the only bridge between them is a text message with no date, no form and no owner.
Software narrows that gap less than people expect. In ServiceTitan, a required form fires in the mobile app at completion, but not when the office closes the job, and not when the tag is added afterward. In Procore, the Incidents tool holds the detail, but the recordable call is a toggle and the CSV export is a six-column summary. In both, a person still has to make the judgment and move it onto an OSHA form or an equivalent.
The same pattern repeats for every compliance stream that starts away from the office. Refrigerant service records on larger systems, copies of each tech's Section 608 certificate, weekly certified payroll on federal construction work, equipment inspection logs on a warehouse floor: each is created by someone doing the work and kept by someone in the office, and each falls behind for the same reason.
Why the clocks matter more than the forms
The forms themselves are not hard. What makes this paperwork dangerous is that each one has a short deadline measured from an event the office may not hear about in time: eight hours for a death, twenty-four for a hospitalization, seven days to log a recordable case, four business hours to produce records. A process that relies on someone remembering to call the office cannot meet a deadline measured in hours. A dated intake list, kept every day, can.
Signs you have this problem
- An injury reaches the office as a text from a supervisor, and nobody writes down the date it arrived
- The OSHA 300 Log gets filled in during January, from memory, so the annual summary can be posted
- Required safety or arrival forms are missing on work that shows as completed
- When an inspector or insurer asks for last year's injury records, gathering them takes a day or more
- Service records, certificate copies and inspection logs live in three different places
What usually causes it
- Incident facts are captured where the work happens by phone, text or paper, then rebuilt in the office days laterThe field-to-office split
- Owed forms and undecided recordable cases sit in no list anyone checks, so nobody sees them ageThe invisible queue
- The supervisor, the office manager and the executive who certifies the annual summary each hold part of the record, and nobody owns it end to endThe handoff gap
Find your cause
Ask these in order. The first yes is usually where yours starts.
- Does the office learn about injuries by text or phone, with no date recorded?If yes: the seven-day clock is running without anyone watching it. Start with the dated intake list.
- Is work closed from the office instead of by the person who did it?If yes: required forms are being skipped by design. Find who closes the work and why.
- Is the 300 Log written up once a year instead of case by case?If yes: the log is a reconstruction. Move the entry to the week the case is decided.
- Would producing last year's records take more than an afternoon?If yes: the forms are not where the rule assumes they are. Run the four-hour drill and fix what it finds.
How it breaks in each industry
- HVAC and refrigeration service
- Besides injury records, the company carries refrigerant paperwork. On appliances holding 50 pounds or more of an ozone-depleting refrigerant, each service produces a record for the owner that is kept at least three years, and every certified tech's certificate copy stays at the place of business until three years after that tech stops working. Those records usually live in the field app, the parts system and a filing cabinet.
- Roofing and other short-duration crews
- Crews move every few days, so the question of which log an injury belongs on comes up constantly. Sites expected to last under a year share one log. Temp and leased workers the company supervises day to day go on that log too, which is easy to miss when the staffing agency also keeps records.
- Logistics and third-party warehousing
- An injury on the dock is reported to a shift lead, often on a different shift from the office staff who keep the log. Many workers come through a staffing agency, and the question of whose log the case goes on gets settled late, if at all.
- Healthcare practices and clinics
- A needlestick or a patient-handling strain is reported to the practice manager in the hallway. The follow-up visit, the incident form and the log entry each wait for a quieter day, and the date the practice first heard about it is the one fact nobody wrote down.
Where it breaks between systems
- ServiceTitan (office app and field mobile app)
- Form triggers are set up in the office application but fire only in the mobile experience. A job completed from the office does not pull up the required form at all.[14]
- ServiceTitan required forms
- The check for required forms runs only at the moment of completion. A trigger tag added afterward does not make the form required, and by default only one of the techs assigned to an appointment has to complete a required arrival form.[15]
- Procore Incidents (CSV export)
- The CSV export carries six columns: number, title, incident date, location, status and record count, and only for the tab you are on. Anything else recorded on an incident stays inside that incident.[16]
- Procore Incidents (injury record)
- Whether a case is recordable is a manual toggle the user switches on. The injury record page does not mention OSHA forms, so the recordability decision and the 300 Log entry remain separate jobs for a person.[17]
- Procore and Sage 300 CRE
- Procore's published list of objects that sync with Sage 300 CRE covers budgets, commitments, invoices, job costs and vendor insurance. It lists no incident, inspection or daily log objects, so safety records do not travel with the financial sync.[18]
By the numbers
| Figure | What it measures |
|---|---|
| 7 calendar days[1] | Time allowed to enter a recordable injury or illness on the OSHA 300 Log and 301 Incident Report, counted from receiving the information. A company keeping records centrally must get case details to that location within the same seven days. |
| 4 business hours[2] | Time allowed to hand over the required injury and illness records once a government representative asks for them. |
| 8 hours and 24 hours[3] | Deadlines to report to OSHA a work-related death (8 hours) and an in-patient hospitalization, amputation or loss of an eye (24 hours). These apply to all employers, including those that do not have to keep logs. |
| 5 years[4] | How long the 300 Log, the privacy case list, the 300A summary and the 301 reports are kept after the end of the year they cover. |
| 3 years[10] | Minimum retention for refrigerant service records on appliances in scope of 40 CFR 82.157, in paper or electronic form. |
Rules that apply
- 29 CFR 1904.1, partial exemption by size[5]
- A company with 10 or fewer employees at all times during the last calendar year does not keep OSHA injury and illness records unless OSHA or the Bureau of Labor Statistics tells it to in writing. Count company-wide. Construction is not on the low-hazard industry exemption list, so a contractor above the line keeps logs.
- 29 CFR 1904.29(b)(4) and (b)(5), equivalent forms and computer records[1]
- An insurance form or a software record can stand in for the OSHA forms only if it carries the same information, reads as clearly, and the system can produce the forms when they are needed. A field app that cannot print an equivalent 301 in time does not satisfy the rule.
- 29 CFR 1904.30(b)(1), short-term establishments[6]
- Establishments that will exist for less than a year may share one 300 Log. Locations expected to operate a year or longer each need their own.
- 29 CFR 1904.32, annual summary[7]
- At year end the employer reviews the log for completeness, builds the 300A, has a company executive certify it, and posts it no later than February 1, leaving it up until April 30. The office manager can prepare it but cannot be the one who certifies unless they qualify as an executive under 1904.32(b)(4).
- 29 CFR 1904.41(a)(1)(i), electronic submission[8]
- Establishments with 20 to 249 employees at any time in the prior year, in an industry listed in Appendix A to Subpart E (which includes construction, NAICS 23), submit 300A information electronically by March 2.
- OSHA Directive CPL 02-00-172[9]
- OSHA's current Part 1904 Recordkeeping Policies and Procedures Directive, effective January 13, 2025, restates the four-business-hour rule for producing records and replaced the older recordkeeping manual.
- 40 CFR 82.157(l) and 82.161(a)(4), refrigerant records and technician certificates[11]
- Refrigerant service records required under 82.157 are kept at least three years. Technicians certified under Section 608 keep a copy of their certificate at the place of business until three years after they stop working as a technician.
- 29 CFR 5.5(a)(3)(ii)(A), certified payroll[13]
- On Davis-Bacon and Related Acts covered work only, the contractor submits certified payrolls weekly for every week covered work is performed. It is a separate compliance stream that tends to land on the same office desk.
Measure it in your own shop
From: Your injury reports, texts or emails from supervisors, the OSHA 300 Log and 301 forms, and the completed work in your operating system with its required forms.
- For each recordable case in the last two years, write down the date the office first heard of it and the date it went on the 300 Log.
- Count the cases where the gap was more than seven calendar days.
- From your operating system, pull last month's completed work that should have carried a required safety form, and count how many have it.
- Time a mock request for last year's 300, 300A and 301s from ask to hand-over.
Reading it: The share of cases logged late shows how wide the gap is between the work and the office. The missing-form count on completed work shows whether your software is enforcing anything. The drill time tells you whether you could meet a four-hour request today.
What does not fix it
- A safety software subscription by itself
- OSHA accepts computer records only if they can produce the forms on demand, and the recordable decision is still a person's toggle. If injuries are still reported by text, the software holds the same late data in a nicer place.
- A weekly safety paperwork meeting
- The reporting deadlines run in hours and the log entry in days. A weekly review finds a case after some of those windows have already closed.
- Making every form required
- In ServiceTitan the requirement is checked only at completion and only when the trigger tag was already on the job. Required forms that the office can bypass by closing work itself mostly add friction for the people who do comply.
What to try this week
- Date-stamp every report on arrivalKeep one injury intake list. Each line gets the date the office heard about it, who reported it, and the decision on recordability with its date. The seven-day entry window counts from the day you received the information, so that first date is the one that matters.
- Settle which log each location keepsEach location expected to run a year or longer keeps its own 300 Log. Short-term locations, such as jobsites expected to last under a year, can share a single log under 29 CFR 1904.30(b)(1). Write the list down once and stop deciding it case by case.
- Make forms fire where the work closesWhatever system closes the work should require the form at that moment. If you use ServiceTitan form triggers, tag the job when it is booked, not after. Triggers fire in the mobile app only, and a tag added after completion does not make the form required.
- Run a four-hour drillOnce a quarter, have someone ask for last year's 300 Log, 300A and every 301, and time how long it takes to hand them over. The regulation allows four business hours.
- Put the fixed dates on the calendarThe annual summary is certified by a company executive and posted from February 1 to April 30. Establishments with 20 to 249 employees in the industries OSHA lists, which include construction, submit 300A data electronically by March 2. Schedule the review in early January, not the last week.
Where do-it-yourself stops
These steps get the backlog under control, but the record is still rebuilt in the office from whatever the people doing the work sent. The lasting fix is a capture step built into the systems you already run, so the incident, the form and the date arrive together and the open items show themselves. That is what a Workflow Spec designs.
Questions people ask
Does a small business have to keep an OSHA 300 Log?
Not if the company had 10 or fewer employees at all times during the last calendar year, counted company-wide, unless OSHA or BLS asks in writing. Above that line it depends on the industry: some low-hazard industries are partially exempt, and construction is not on that list.
How fast does an injury have to go on the log?
Within seven calendar days of receiving information that a recordable injury or illness occurred, under 29 CFR 1904.29(b)(3). The clock starts when the company learns of it, which is why the date the office hears about it matters.
Do we need a separate OSHA log for every location?
Each location expected to operate a year or longer keeps its own. Short-term establishments, such as jobsites expected to last under a year, can share one 300 Log.
Can we keep OSHA records in software instead of on paper?
Yes, if the system can produce equivalent forms when they are needed, including within four business hours of a government request. An equivalent form must carry the same information and be as readable as the OSHA form.
Who has to sign the annual 300A summary?
A company executive, as defined in 29 CFR 1904.32(b)(4), certifies that they examined the log and believe the summary is correct and complete. It is posted from February 1 through April 30.
Next step
How we fix this
This guide is how to find it and work around it. If it keeps coming back, it is rarely the only thing costing you. We come on site, find the issues costing you the most, and fix them, starting with the most pressing.
Fox & Santiago, Genesee, Idaho. We work nationwide, for clients across the United States, from our headquarters in Genesee, Idaho.
