- Home
- Filling Out Safety Forms Offline
Filling out safety forms where there is no signal
Reading a safety data sheet without a connection is a solved problem, and OSHA has said what it requires. Writing the record is the other half, and it is the half that decides what an inspector finds. A permit closed out inside a tank, eleven signatures at a tailgate, an inspection filed from a basement: the standards ask for those records to exist and to be kept. They say nothing about when a record is allowed to reach a server.
That silence is not permission. It means the gap between writing and uploading belongs to whoever built the tool, and it is where records quietly stop existing.
Four places it happens
A hot work permit is signed and closed out where there is no signal.
29 CFR 1926.352 requires the permit conditions to be met before and during the work. The record is the proof they were.
Eleven workers complete a HazCom refresher at the tailgate.
1910.1200(h)(1) makes training due at initial assignment and whenever a new chemical hazard arrives. The certification record has to exist.
One worker files an inspection, then hands the tablet to the next.
A record attributed to the wrong person is a recordkeeping problem, not a display problem.
Everything the crew wrote that day tries to upload at once.
If one entry is rejected, what happens to the twenty behind it decides whether the day survives.
What HazComFast does
- The entry is written to the device. For the forms it covers, a submission made without a connection is stored locally and confirmed on screen, then carried forward when the signal returns.
- One rejected record does not hold up the rest. Entries that fail permanently are set aside with the reason and an attempt count; the queue keeps moving instead of stopping at the first failure.
- The record keeps the person who wrote it. The owner is fixed at the moment of entry, so a shared device does not reassign the morning crew work to whoever is logged in later.
- One upload at a time. Two tabs, or a manual retry during an automatic one, cannot start two uploads of the same queue at once.
The clocks that keep running with no signal
Part 1904 never mentions a server, and that is why the deadlines get missed. The clocks it does set start when something happens or when you learn of it, and none of them pauses because a crew is underground.
- Seven calendar days to enter the case. 29 CFR 1904.29(b)(3): you must enter each recordable injury or illness on the OSHA 300 Log and the 301 Incident Report “within seven (7) calendar days of receiving information that a recordable injury or illness has occurred.” The clock starts when you learn of it, not on the day it happened, and not on the day the tablet finds Wi-Fi.
- Seven more to move it to the central location. 29 CFR 1904.30(b)(2)(i) lets you keep the records at headquarters only if you can “transmit information about the injuries and illnesses from the establishment to the central location within seven (7) calendar days.” A short-term jobsite with no coverage is exactly the case the paragraph was written for.
- Eight or twenty-four hours for the worst outcomes. 29 CFR 1904.39(a)(1) gives eight hours after a work-related death; (a)(2) gives twenty-four after an in-patient hospitalization, an amputation or the loss of an eye. Those are reported by phone, by the 1-800-321-OSHA line or through OSHA’s reporting application, and (b)(1) says that if the Area Office is closed you use the 800 number or the application. No form on a device discharges that call.
- And the signature at the end of the year. 29 CFR 1904.32(b)(3) has a company executive certify the annual summary “based on his or her knowledge of the process by which the information was recorded.” A day of entries that never left a phone is a hole in that process, and it is the executive who signs over it.
So the question to ask a vendor is not whether forms work offline. It is what the queue does on day three: whether the entry still carries the date it was written, whether a second tap made a second record, and whether one rejected form took the rest of the day with it.
Wi-Fi bars, no internet: the third state
Every vendor talks about “offline”, meaning no signal. The case that actually eats a day on a jobsite is the other one: the phone shows full bars on the site trailer’s Wi-Fi, and nothing reaches the server. A captive portal nobody signed into, an access point with no uplink, a router someone unplugged. The phone says connected. It is not reachable.
Connected is not reachable
The app tracks three states rather than two: online, offline, and degraded, which is what it calls a connection the browser reports as live while the server does not answer. Screens that queue an entry decide on that state, not on the browser’s flag.
Why a form should wait instead of trying
In the degraded state the banner says so, and an entry goes into the queue without an upload being attempted. That matters for a reason that is not obvious: an entry whose upload is tried and fails burns an attempt, and enough failed attempts put a record in quarantine for review. Not trying is how a form written on a dead Wi-Fi stays a normal entry instead of becoming an exception somebody has to clear.
Signatures and photos wait on the phone
Attachments stay on the device until the entry replays: the signature, the photo of the deficiency, the training attestation. They are not uploaded ahead of the record, which is the arrangement that used to keep an entry out of the queue when its attachment failed.
What you see when access comes back
The state returns to online on the next reachability probe, not at the instant the Wi-Fi does: the probe runs every 30 seconds, backs off on each failure up to five minutes, and restarts when the network changes or when you come back to the screen. Then the queue goes when you next open the app in coverage. Try it on an Android phone: join a Wi-Fi with no uplink and create a corrective action, and the banner names the degraded state while the badge counts the entry waiting.
Frequently Asked Questions
Not about the server, and that is the half people hear. The standards require records to be created and kept: 29 CFR 1904.33(a) sets five years for the OSHA 300 Log, the privacy case list, the annual summary and the 301 forms, and 29 CFR 1910.1020 sets thirty years for exposure records. Nothing in the text speaks to the moment a record leaves the device it was written on. But Part 1904 does put clocks on the work itself, and they run on the calendar whatever the signal is doing — seven calendar days to enter a recordable case under 1904.29(b)(3), seven more to move it from the establishment to the central location under 1904.30(b)(2)(i), and eight or twenty-four hours to report the worst outcomes under 1904.39(a). The gap between writing and uploading is yours to manage, not OSHA's to excuse.
Yes. The field forms write the entry to the device, confirm it on screen, and send it when the connection returns.
One. The entry gets its identifier when you fill it in, not when it uploads, so a second tap — or a resend during a half-returned signal — lands on the same record instead of creating a new one. That holds for the screens the offline queue covers: the hot work and confined space permits, adding a product, the safety plan, the 301 form, the training record with its attachment, the toolbox talk and the incident investigation. Try it: in airplane mode, fill in a hot work permit, tap Submit twice, come back online, then open the permit list.
Yes, and the form says which one it is. An inspection answered to question twelve of twenty comes back with those twelve answers under a banner naming the form you had open. Submit it and the draft disappears. One limit worth knowing rather than discovering: clearing the browser's data clears the draft with it, because the draft lives on the device.
No. Opened cold and still offline, with the sign-in token already expired for more than an hour, the app opens on the kept session rather than on the login screen. That is the question the buyer checklists tell you to run — leave the device offline and see whether it demands re-authentication — and it is the one nobody answers in print.
No. When the signal returns the queue sends each entry for itself. One the server refuses stays on the device, marked for review in the offline manager, and the ones behind it go up anyway. A full queue never drops the oldest entry quietly. Try it: in airplane mode fill in two forms, come back online, then open the offline manager — the queue is empty and both forms are in their lists.
The others still go through. A single malformed entry used to stop the whole queue and stay at the front of it, which meant everything written behind it never went up. Entries that fail permanently are set aside with the reason and an attempt count, and the queue keeps moving.
The person who wrote it. The owner is fixed when the entry is created, not when it uploads, so a record written by the morning crew is not reassigned to whoever is logged in at the end of the shift. The OSHA interpretation letter of August 14, 1997 makes the same point about badge-scanned attendance: the condition is that the record identifies the right person.
Yes. In an interpretation letter dated April 10, 2000, OSHA stated it would have no objection to electronic capture satisfying training certification requirements. A 1997 letter had already reported that a search of all OSHA standards found no standard requiring the employer to obtain the employee signature. What the standards ask for is a certification record identifying who was trained.
Get the Binder in Order Before the Inspector Arrives. Are You Ready?
OSHA does not give advance notice of inspections (29 CFR 1903.6). Get the binder in order before the opening conference, not during it.
Serious Violation
$16,550
per violation (max)
HazComFast Pro
$199/mo
10 jobsites, unlimited chemicals, unlimited workers
New sign-ups are paused. The free tools below need no account, and customers can log in as usual.
Your account keeps working as usual. Cancel anytime.