Construction workers don't sit at desks. They're on scaffolds, in trenches, on rooftops, and inside concrete structures. Safety software that only works on a desktop — or needs a reliable connection — doesn't work for construction. A Progressive Web App (PWA) delivers native-app performance through the browser: no app-store download, no IT approval, no separate iOS and Android builds. And on a jobsite, that architecture is what makes an OSHA requirement actually achievable.
The OSHA rule behind offline access
29 CFR 1910.1200(g)(8) requires safety data sheets to be “readily accessible during each work shift.” Electronic access is allowed if it is immediate, barrier-free, and backed up for power/system failures. An offline-first app is how you meet that rule in a basement or 40 miles from a cell tower.
A Progressive Web App gives construction crews offline access to their safety data sheets, so a worker can meet OSHA's readily-accessible requirement under 29 CFR 1910.1200(g)(8) even in a basement or dead zone where a cloud-only app would fail.
What a PWA gives you
A Progressive Web App is a website that behaves like a native app: it installs to the home screen, keeps working when the network does not, uses the camera for inspection and near-miss photos, opens from what is already on the device, and updates itself so the crew is not split across versions. HazComFast uses in-app notifications for the deadlines that matter (training expiring, inspection due, a sheet revised, a permit about to lapse).
Why a PWA beats a native app on a jobsite
| Factor | Native app | PWA |
|---|---|---|
| Installation | App-store download, IT approval | Open URL, "Add to Home Screen" |
| Updates | Manual app-store updates | Automatic, transparent |
| Device compatibility | Separate iOS + Android builds | Any device with a browser |
| Offline | Depends on implementation | The documents are stored on the device |
| Deployment | Weeks via enterprise MDM | Minutes, URL-based |
Offline-first is the whole point
The jobsite packs store each site's sheets on the device, and the app shows how many are ready (17 of 20, 20 of 20), so the jobsite's SDS open where the signal drops. The forms the offline queue covers are kept on the device until the app is open and back online. The offline manager lists what is still waiting to be sent and what needs your attention, so a form that could not be sent does not wait in silence. What the device itself can lose, and how to check it before the crew leaves, is covered in our guide to paperless SDS and device failure.
What this looks like in the field
- Basement concrete pour, three floors down, no signal. A worker checks the SDS for a curing compound, reads Section 8 for PPE, and keeps working safely: the sheet is already stored on the device, which is how 1910.1200(g)(8) gets satisfied where a cloud-only app simply fails.
- Rural pipeline, 40 miles from a tower. A safety manager completes the weekly inspection, photographs deficiencies, signs digitally, and everything syncs on the drive back.
- Multi-trade coordination. A GC director filters the dashboard by jobsite, spots one crew with expired HazCom training, and notifies them before they start.
Targeted in-app notifications (training expiring, inspection due, SDS expiring, permit expiring) keep the right person informed without alert fatigue.
Four documents the rules want at the point of work
The SDS gets all the attention because 1910.1200(g)(8) names a shift. It is not the only paragraph that puts a document where the work is, and once you line them up the phone stops looking like a convenience.
The emergency action plan. For general industry, 29 CFR 1910.38(b): the plan “must be in writing, kept in the workplace, and available to employees for review.” In construction the duty sits in 29 CFR 1926.35(e)(3), in almost the same words: “The written plan shall be kept at the workplace and made available for employee review.” A jobsite trailer counts as the workplace. So does the excavation, and the worker in it.
The confined space entry permit. 29 CFR 1926.1205(c) requires the completed permit to be “made available at the time of entry to all authorized entrants or their authorized representatives, by posting it at the entry portal or by any other equally effective means.” The entry portal of a vault or a tank is, as a rule, where the signal is not.
The fall protection plan. 29 CFR 1926.502(k)(1) requires it to be prepared by a qualified person, developed specifically for the site, and “maintained up to date.” A plan that is up to date in the office and three revisions behind on the roof is not the same document.
The written HazCom program. 29 CFR 1910.1200(e)(4) makes the employer produce it on request to employees, their designated representatives, the Assistant Secretary and the Director, in accordance with 29 CFR 1910.1020(e). For construction, all of 1910.1200 arrives through 29 CFR 1926.59.
Four paragraphs, four documents, one common clause: available where the employee is. That is the case for the phone, and it is a stronger one than offline SDS access alone. HazComFast loads these onto the device when you sign in and when the network comes back. The gesture that matters is the simple one: open the app before the crew leaves coverage.
The deployment math nobody counts
The architecture has a second payoff that only shows up at scale: getting the app into workers' hands. Construction crews rotate, use their own mixed devices, and change from job to job — the worst possible environment for a native app that needs an app-store download, a login provisioned in advance, and IT approval per device. A PWA collapses that to a URL: a foreman texts a link, the worker taps "Add to Home Screen," and the tool is live in under a minute, on whatever phone they already carry. Multiply that across a 40-person crew and the difference between "deployed by Friday" and "deployed next quarter" is the whole point. Updates work the same way — the service worker refreshes silently, so there is no version drift where half the crew is running last month's chemical list. For a safety tool, "everyone has the current version, today" is not a convenience; it is the difference between a program that is actually in use and one that exists only on the org chart.
Put the whole program in every worker's pocket
HazComFast is a PWA built for jobsites where the signal drops: it installs by URL and loads the jobsite's SDS onto the phone. No signal? Log it anyway. Near-misses, inspections and permits save on the phone and send themselves the moment you're back online. No app store, no MDM.
Related: Offline SDS Access — Why It Matters · Why Cloud-Only SDS Apps Fail · Are Digital SDSs Legal? · How Much Does HazCom Software Cost?
Sources & verification (verified 2026-07-14): SDS access requirement per 29 CFR 1910.1200(g)(8) — safety data sheets "readily accessible" to employees during each work shift; OSHA permits electronic access when it is immediate, barrier-free, and backed up for power/system failures. PWA capabilities (home-screen install, on-device storage, camera) are standard web-platform features; the documents HazComFast puts offline are stored on the device, not in a service-worker cache. Emergency plan, entry permit, fall protection plan and written program re-read 2026-10-08 on the eCFR, title 29 up to date as of 2026-10-06. Not legal advice.
Frequently Asked Questions
Does OSHA allow electronic or offline SDS access?
Yes. 29 CFR 1910.1200(g)(8) requires safety data sheets to be 'readily accessible during each work shift' to employees in their work area. OSHA permits electronic access as long as employees have immediate access with no barriers and there is a reliable backup for power or system failures. Offline-capable access satisfies both requirements precisely where they are hardest to meet — basements, tunnels, and remote sites with no signal — which is why an offline-first design is a compliance feature, not just a convenience.
What is the difference between a PWA and a native app for construction?
A Progressive Web App runs through the browser but installs to the home screen, keeps working without a connection, and uses the camera, with no app-store download, no IT approval and no separate iOS and Android builds. For a rotating crew on mixed devices that means deployment by URL in minutes rather than weeks through mobile-device management. The reason it matters for compliance rather than for convenience: 29 CFR 1910.1200(g)(8) requires the sheets to be “readily accessible during each work shift to employees when they are in their work area(s)”, and the work area is where the phone is.
Does OSHA care which phone the crew carries?
No. 29 CFR 1910.1200(g)(8) is written about access, not about hardware: the sheets must be kept in the workplace and be readily accessible during each work shift to employees in their work area, and the parenthetical allows electronic access so long as it creates “no barriers to immediate employee access in each workplace.” A PWA installs from a URL on Safari, Chrome and every modern mobile browser, with no separate download per platform, which is why it suits a crew that brings its own phones. What you have to be able to show is the access itself, plus the thing 1910.1200(h)(2)(iii) asks for: that each employee was informed of the location and availability of the written program, the chemical list and the sheets.
How much storage does the offline cache use?
It depends on how many sheets the jobsite packs you download contain. The offline manager shows the space used and whether the browser reports that storage as protected from automatic cleanup, as best-effort storage the browser may clear if space runs low, or as not reported at all. Check it before the crew leaves coverage, because the duty does not bend to a full device: 29 CFR 1910.1200(g)(8) wants the sheets accessible during each work shift, and (g)(9) is the only allowance in the paragraph, for employees who work at more than one geographical location in a shift, whose sheets may be kept at the primary workplace facility.
What happens to data captured offline?
For the forms the offline queue covers, an entry made without a connection is kept on the device and sent when you next open the app in coverage. The offline manager shows what is still waiting to be sent and flags what could not be sent so you can act on it. Keep one date in mind while a form sits in that queue: 29 CFR 1904.29(b)(3) gives you seven calendar days from receiving information that a recordable injury or illness has occurred to enter it on the 300 Log and the 301, and that clock runs on the calendar, not on the signal.
OSHA figures and citations here come from our regulatory source-of-truth modules, last checked against the eCFR, OSHA.gov, and the Federal Register on October 5, 2026. Last reviewed July 7, 2026.
About This Article
Published by: HazComFast
Published: February 23, 2026
Last Updated: July 7, 2026
This content is for informational purposes only and does not constitute legal advice.