A Safety App That Works When the Jobsite Has No Signal

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.

A Progressive Web App gives construction crews offline access to their safety data sheets, so the sheets stay within reach, as 29 CFR 1910.1200(g)(8) requires, even in a basement or dead zone where a cloud-only app has no connection.

What a PWA gives you

The crew opens it from the home screen like any other app. It works in a basement, it takes the photo of the deficiency, and nobody is two versions behind the foreman. 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

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 has nothing to show.
• Rural pipeline, 40 miles from a tower. A safety manager completes the weekly inspection, photographs deficiencies, signs digitally, and everything goes out the moment the app is open in coverage.
• 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, an SDS due for review, permit expiring) keep the right person informed without alert fatigue.

Expiry alerts checked when the app opens, signal or not

A fit test that runs out on Thursday matters most to the superintendent who's on site Thursday morning, often below grade. For admins and managers, HazComFast compares the phone's date with the expiry dates kept on the device every time the app opens or comes back to the front: training, respirator fit tests, forklift operator certifications, competent person designations, equipment and permits. It alerts at 30 days, at 7 days, on the day, and once the date has passed. It does that with no signal, from the last list the phone received while online.

If notifications are allowed for the app, each deadline shows as its own notification, three at most, with the rest summed up. If not, a "Deadlines to watch" banner names them inside the app. Each deadline alerts once per step, so opening the app ten times on Monday doesn't repeat it, and moving from 30 days to 7 days alerts again. The dates are the ones your company entered on each record, and the alert shows the date you set.

What still works with no signal

• The compliance steps themselves. In a tank, a basement or a dead zone, the crew can still apply a lock, log an O₂/LEL reading, sign a toolbox talk or close a hot work permit. Each goes out once the app is open in coverage.
• One bar of signal doesn't eat the entry. If a send fails, the entry waits in its list as Pending sync and the draft is kept.
• A product added at the jobsite arrives whole. Add one with its SDS PDF and no signal, and once the app is open in coverage it lands with its sheet, its revision date and its jobsite. Add it without the PDF and the line reads "SDS to complete" until someone attaches the sheet.
• An edit changes only what you edited. Fix a product's name offline and its SDS link, its first-aid and PPE sections stay exactly as they were.
• A shared tablet keeps accounts apart. Sign out and the inventory kept on the tablet for you goes with you. The next person, even offline, never sees it.
• Nobody overwrites anybody. If the office corrected a record while you were offline, your older edit doesn't replace it. You see both and you choose.
• The date is the date of the work. Training taken offline on Friday at 2 p.m. is recorded as Friday at 2 p.m., not the day the phone found signal.
• A dead battery doesn't cost the inspection. Twelve answers into a twenty-question form, reopen it and the draft is there, named. And nobody gets logged out after an hour offline.
• Two injury reports, one second, two case numbers. Two foremen whose reports go out at the same moment get two case numbers, in order, and neither report is dropped.
• An update never eats unsent work. When a new version is ready, the app says how many entries haven't gone out yet and asks you to send them first. "Ready for offline use" tells you the phone has what it needs.
• Room for 300 sheets. One phone holds the SDS for 300 products, the access 29 CFR 1910.1200(g)(8) asks for during each shift, and the app tells you when the phone is full.
• The waiting list reads in Spanish too, and a screen reader announces what's still waiting to be sent.
• No outside service to open a sheet. The SDS opens inside the app.

Four documents the rules want at the point of work

The SDS gets all the attention because 1910.1200(g)(8) names a shift. Three other paragraphs put a document where the work is.

The emergency action plan. It is required when an OSHA standard calls for one (29 CFR 1910.38(a), 1926.35(a)). 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.” An employer with 10 or fewer employees may communicate the plan orally under both paragraphs.

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 often where the signal is not.

The fall protection plan. It exists only where 29 CFR 1926.502(k) allows one: leading edge work, precast concrete erection or residential construction, by an employer who can show that conventional fall protection is infeasible or creates a greater hazard. 29 CFR 1926.502(k)(1) then requires it to be prepared by a qualified person, developed specifically for the site, and “maintained up to date,” and (k)(3) requires a copy with all approved changes at the job site. 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, a duty to hand it over when asked rather than to keep it at each work area, 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.

All four say the same thing: available where the employee is. HazComFast loads these onto the device at sign-in and again each time the network comes back.

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 setting 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 app picks up the new version on its own, without wiping anything that hasn't gone out yet, 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" decides whether the program is used on site or exists only on the org chart.

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 written to the device's own storage, so a browser cache being cleared does not take them. 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.