Skip to content
Offline Mode & Multi-Person Collaboration

Offline safety app: the signal dies, the record doesn't.

US construction crews still need to inspect the work and follow their OSHA safety program when a basement, steel deck, or remote site has no reception. SALUS keeps field forms, photos, signatures, and inspection records available through offline workflows, with local capture and synchronization when a connection returns. A foreman can document the condition where it happens instead of rebuilding the account in the trailer. The office receives the connected record after sync, while the crew follows the site’s normal communication and emergency procedures for anything that needs attention immediately.

Offline safety software for the places work actually happens.

Within a month or so of us starting to use SALUS, some of the comments were that if we were to take it away and go back to paper, that they would quit.

WestUrban Developments · Customer story
View customer story
Incident report on a phone at Subterranean Parking Level P3 with a red offline-mode banner, two active contributors, a witness statement being recorded by Officer A. Miller, evidence photos, and a 'Signal Detected — syncing 3 records' card
Full offline workflows
Keystroke-level autosave
Clean sync when signal returns
Sync complete - zero gaps
LeaderEasiest To UseUsers Most Likely To Recommend
01Act 1 · In the field

Offline should mean working, not waiting.

Offline-first architecture

If it lives in SALUS, it works in the basement.

Offline-capable software tolerates a dead zone. Offline-first software is built for one. SALUS runs your workflows locally, with zero signal — forms, inspections, certificates, documents, SDS sheets, equipment profiles — in concrete basements, elevator cores, ventilation shafts, steel decks, and remote sites the towers have not reached.

Heading to a site with limited reception? Download the SALUS app for iOS or Android before you go.

Field Ops quick-access screen at Subterranean Parking Level P3 in offline mode, with tiles for Certificates, Documents, Forms, Machinery, SDS, and Assets
→

Certificates

Verify a credential at the point of work - no signal required.

→

Documents & SDS

The data sheet is readable where the chemical actually is.

→

Forms & inspections

Every workflow runs in the dead zone, start to finish.

→

Equipment & assets

Full profiles travel with the crew, not the coverage map.

The highest-risk spaces are the worst connected. SALUS documents them anyway.

Offline media capture

SALUS does not have a "Save" button. It does not need one.

In SALUS, every keystroke is saved to the device as it is written. Not at save points - every single character, exactly the way Google Docs works, except built for a job site where offline is the default state, not the exception.

Read the field adoption guide for ways to make photo and note capture easier for crews.

Nothing to save. Nothing to lose. No reason to stop reporting.

Phone showing an incident report under a red banner reading 'Offline mode — every keystroke is auto-saved locally,' with 'Saved offline' chips on the location field, the witness statement, and the evidence photos
02Act 2 · The record

Every field entry is protected.

Multi-person collaboration

One form. Two authors. Zero version conflicts.

In SALUS, two workers open the same form from different floors, in different signal conditions, and their entries merge at the field level: nothing overwritten, nothing duplicated. Any role can contribute - and when the field needs help, the right person can be invited straight into the live form.

Nobody asks "who overwrote my notes?" Nobody has to.

Two partially filled report cards — Marcus Chen's with the title, date, and a critical severity flag; Priya Nair's with the detailed description — combined into a single merged result with every field present
Full workflows

Forms, inspections, permits, incidents, and SDS keep working offline.

The offline story is not just forms. The field needs inspections, permits, incidents, certificates, training, SDS, photos, signatures, witness statements, and notes to keep moving.

Offline across the safety record.

Incident detail cards — the location at Level B4 Ventilation Shaft 12, a witness statement, and evidence photos — each marked 'Saved offline' under a banner noting every keystroke is auto-saved locally, with two active contributors
03Act 3 · In the office

Sync cleanly and prove it.

Five-second sync

A five-second signal burst is a complete sync.

Job-site coverage comes in flickers - at the ramp, the gate, the hoist. Offline modes that need minutes of stable connection never catch up. SALUS stores every record locally and moves it the instant any signal appears: even a brief burst is enough for a complete sync. Crews never babysit an upload bar, and the office never waits for end of shift.

Saved in the dead zone. Delivered at the ramp.

Field Forms screen with an offline-mode banner and three records waiting to sync — an incident report, a safety inspection, and an equipment check — beside a 'Signal Detected' card syncing all three
Sync audit trail

The sync audit trail proves what happened.

The data arrives complete from places with zero reception, so nothing is reconstructed from memory at the end of the day. The record the safety director can verify and stand behind is the record the field actually wrote.

Four captured offline. Four delivered. Zero follow-up calls.

A reports panel with a dead-zone log showing four records captured offline — a waypoint location, an inspection, and a damage report — each marked synced, above a 'Sync complete — 4 of 4 records delivered' bar
US construction safety

Keep OSHA inspection work moving through dead zones

OSHA’s construction inspection requirement does not depend on a mobile signal. The designated competent person still needs to examine the jobsite, materials, and equipment as required by the work. A lost connection should not turn a site walk into a memory exercise at the end of the shift.

Before heading into a low-signal area, confirm that the crew has the current forms and reference documents it needs. During the walk, capture the location, observations, photographs, and assigned follow-up while the details are available. SALUS stores supported field records locally and synchronizes them when connectivity returns, keeping the evidence connected to the inspection.

Plan separately for urgent communication. An offline record is not a live alert to someone whose device has not received it. If a condition calls for stopping work, protecting an area, or contacting emergency services, follow the site procedure immediately. At the next connection, check synchronization and review any outstanding action with the supervisor. That separates the time of field capture from the time the office could actually see the information.

Use the dated OSHA for Construction field guide for current penalties, inspection steps, recordkeeping, and heat-rule status.

Adoption

Keep the field workflow available through the dead zones crews encounter during the shift.

Completeness

Autosave protects every field entry before reception can decide what survives.

Proof

Sync audit trails show where the record came from and when it arrived.

Feature grid

Everything an offline construction app should have been doing all along.

01 ·

Keystroke-level autosave

Every character saved locally as it is typed - no save points, no Save button.

02 ·

Full offline workflows

Forms, inspections, certificates, SDS sheets, and equipment profiles - all with zero signal.

03 ·

Offline media capture

Photos, signatures, and voice notes captured in place - Rosie structures voice at sync.

04 ·

Multi-person collaboration

Two workers, one form, different floors - entries merge with nothing overwritten.

05 ·

Five-second sync

Even a brief signal burst is enough for a complete sync.

06 ·

Sync audit trail

Every record logged as captured offline and confirmed delivered, with timestamps.

Go deeper

Go deeper where offline matters most.

Offline mode is the proof layer every field workflow should inherit.

FAQ

Offline Mode: questions from US construction teams

Can a superintendent document an OSHA-related site walk without reception?
Yes. Supported inspection forms, photos, notes, and signatures can be captured locally and synced when service returns. Confirm the required forms are available before the walk and use the site’s communication procedure for hazards that need immediate intervention.
Will an offline incident record alert the office immediately?
An unsynced record should not be treated as a delivered alert. Use your emergency and escalation procedures for urgent incidents, then confirm the SALUS record has synchronized when connectivity returns.
Does everything really work offline, or just forms?
Everything. Forms, photos, voice notes, signatures, and inspections all work with zero signal - and certificates, documents, SDS sheets, and equipment profiles are readable offline too. The workflow in the basement is the workflow in the trailer.
Is there a Save button?
No. Every keystroke is auto-saved locally as it is typed, not at save points. Walk through a dead zone mid-form and nothing is lost; the record merges and uploads the moment a signal appears.
What happens when two people edit the same form offline?
Their entries merge at the field level - no version conflicts, no overwritten data. Two workers can document the same event from different locations and different signal conditions, and the office receives one complete record with one audit trail.
How long does the device need a connection to sync?
About five seconds. Even a brief signal burst - at the ramp, the gate, the hoist - is enough for a complete sync. Nobody stands still holding a phone in the air.
What happens to photos and voice notes captured offline?
They are held on the device with the rest of the form and delivered in the same sync - nothing uploads piecemeal, so photos never orphan from their record. Voice notes ride along too, and Rosie, the AI Admin & Risk Assistant, structures them into the form's fields for the author to confirm.
Won't offline mode fill the phone and burn the data plan?
No. SALUS downloads only what your sites and your work actually need - current protocols, active forms, the assets your crews touch - not years of archives. Loading stays fast, local storage stays lean, and limited data plans are not spent syncing dead records.
How does the office know a record was captured offline?
Every record is logged as captured offline and confirmed synced, with timestamps - a clean audit trail from local save to dashboard. What arrives is what the field wrote.
How is SALUS different from partial offline mode?
Partial offline mode usually caches a narrow slice of the workflow. SALUS is built around the full field record: forms, inspections, incidents, SDS, photos, signatures, witness statements, collaboration, sync, and proof.
What should we bring to an offline demo?
Bring the workflow that breaks first when reception disappears: a form, inspection, incident, SDS lookup, certificate check, or remote-site record. If HammerTech is in the comparison set, bring the same dead-zone workflow so the demo can show local capture, autosave, merge behavior, and sync proof side by side.
Offline demo

Show us your worst dead zone.
We will show the workflow that still works.

Walk through offline capture, autosave, media, witness statements, sync, and audit trail.

Bring the current workflow. We will map the live version from field action to proof.