A general contractor based in Chicago runs fourteen active job sites simultaneously across Illinois, Indiana, and Wisconsin. On a Wednesday afternoon in mid-July, a worker at the Indianapolis site slips on a wet concrete pad while carrying a sheet of plywood. He falls hard, lands on his right wrist, hears the snap. Within an hour he’s at the urgent care clinic, his hand wrapped in a temporary splint, and the X-ray confirms a displaced distal radius fracture. The clinic doctor calls in the orthopedic surgeon. The worker won’t be back on a site for ten weeks.
OSHA gets the call. The Indianapolis Area Office assigns a compliance officer who arrives at the site Thursday morning at 8:30 AM. The site superintendent meets him at the gate. The officer’s first three questions: who was present at this site between 6 AM and the time of the injury, what tasks were they performing, and where are the OSHA 300 and 301 forms for this site and the past three sites in your portfolio that had recordable incidents in the past twelve months. The superintendent opens a spreadsheet on his laptop. Then a paper binder from the trailer. Then makes phone calls to the head office in Chicago. The OSHA officer notes the phrase “delayed production of recordkeeping” in his preliminary report, which is the auditor’s polite way of describing a documentation failure.
OSHA Form 300, the Log of Work-Related Injuries and Illnesses, together with Form 300A, the Annual Summary, and Form 301, the Injury and Illness Incident Report, constitute the backbone of OSHA recordkeeping under 29 CFR §1904. They’re required for employers with more than ten employees in non-exempt industries, which covers nearly all of construction, manufacturing, and field service. Many general contractors and field service operators fall into the “delayed production” category not because they don’t have the underlying data, but because the data lives across too many systems, paper binders, spreadsheets, and trailer files. The compliance officer doesn’t care where the data lives. He cares whether you can produce it within a reasonable time after the request.
Pull a sample OSHA 300 with linked GPS site logs in two clicks, and see whether the four-hour rule turns harmless.
No credit card, up and running in 2 minutes.
Open your trialWhat OSHA actually wants on Form 301
Form 301 requires eight discrete pieces of information for every recordable incident: the employee’s name and identifier, the job title at the time of the incident, the establishment where the employee normally works, the address of the incident location if different, the time of incident, what the employee was doing immediately before, what happened, and what factors contributed. GPS clock-in data answers four of these eight fields directly and without human intervention. The other four require human input, but they’re typically clearer and easier to write when the GPS log is the starting point. The investigator sees the same scene the safety manager saw when reconstructing the incident.
The “what the employee was doing immediately before” field is the one investigators scrutinize most carefully. If the answer is vague, “performing assigned duties”, the investigator marks it as inadequate. If the answer is specific, “carrying a sheet of plywood from the materials drop on the west side of the foundation to the framing crew on the east side, walking across the recently-poured slab that had been hosed down for cleaning”, the investigator marks it as compliant. Specificity is the difference between a citation for inadequate recordkeeping and clean continuation of the inspection.
The seven-day recording window
OSHA requires that a recordable incident be entered on Form 300 within seven calendar days of the employer learning of the incident. Multi-site operations frequently miss this deadline because reporting chains break under volume. A worker at site A reports an injury to his foreman; the foreman calls the safety officer; the safety officer is on vacation; the email sits in an inbox until the following Monday; by the time the form gets filled out, ten days have passed since the incident.
A GPS-tracked workforce with incident reporting in the same mobile app eliminates the chain breakage. The worker reports the incident from the field directly in the app, date, time, location (already auto-captured by GPS), description, photographs if appropriate. The safety officer gets an automatic notification. The entry hits Form 300 the same day, regardless of who’s on vacation. The seven-day window becomes a non-event because the workflow is real-time.
The Form 300A annual posting requirement
Every February 1, employers covered by the recordkeeping rule must post the previous year’s Form 300A summary in a workplace location visible to all employees. The posting must remain in place through April 30. For multi-site contractors, this means physical posting at every site, not a single posting in the home office. A digital alternative is not legally sufficient under the current rule. But the source data for 300A, total hours worked by all employees during the year, broken down by establishment, comes directly from time tracking. If hours data is fragmented across systems, 300A becomes a forensic reconstruction project every January.
The 300A’s value goes beyond compliance. Worker safety incidence rates calculated on accurate hours data become a competitive bidding asset. General contractors with low recordable incidence rates win bid weighting on government and large private projects. The same data that satisfies OSHA also helps the company qualify for safer, higher-margin contracts. The investment in clean time tracking pays dividends in business development, not just compliance.
