Working offline

Installing as an app

RopeLogix runs in your browser but can be installed as a standalone app on your phone or tablet — no app store required. It works on iOS, Android, and desktop.

What works offline

• ✓
  Logbook drafts — start and save a new hours entry, including photos, voice notes, and gear tags. The draft saves locally.
• ✓
  Pre-start checklists — run a pre-start and collect crew signatures. The GPS stamp is captured from the device; the record syncs when you're connected again.
• ✓
  Viewing recent records — logbook entries and SWMS documents you've recently opened are cached for viewing offline.
• ✓
  Photos and voice notes — attach from your camera roll or record a memo. Both save locally with the draft.

What needs signal

• ○
  Live review queue — supervisors need a connection to receive and sign pending entries.
• ○
  AI SWMS suggestions — the AI canvas requires a connection. The rest of SWMS drafting works offline once the template has loaded.
• ○
  Team credential dashboard — live data requires a connection.

The sync chip

When you're offline, a small sync indicator appears at the top of the screen. It shows how many local changes are waiting to be sent.

When you reconnect — back in the truck, at the site office, wherever signal returns — RopeLogix syncs automatically. The chip disappears. No manual action required, no data lost.

Submitting twice doesn't double up

Each draft you save offline is given a unique reference ID by the app. When it reaches the server, the server uses that ID to detect and reject duplicates — so if the network retries the upload, only one copy ever lands. You won't end up with two identical entries.

Practically: tap save once, then forget about it. The sync chip will show your queue draining. Don't try to "help" by re-sending — it's already handled.

When an item fails to sync

If an item in the sync queue fails after several retry attempts, the sync chip turns red. Tap it to see the failed items and retry manually.

Persistent failures usually mean the record's data conflicted with a server-side change (for example, the same entry was edited online while you were offline). Open the entry, review it against the current version, re-make any changes, and save again.

If someone edits the same record while you're offline

Rare, but possible: you edit a logbook entry on your phone offline, and your supervisor edits the same entry online before you reconnect. When you're back in range, RopeLogix detects the version mismatch.

You'll see a toast at the top of the screen letting you know the server has a newer version of that record, and your offline change wasn't applied. The newer version stays as the source of truth — no silent overwrite, no lost data on the server side.

If you still want your offline change applied, open the entry, re-make the edit on top of the current version, and save again. The supervisor's changes are preserved; your fresh edit lands cleanly.

Storage limits on the device

RopeLogix caches your recent records and any active drafts on the device. Photos and voice notes are kept too — they're the largest files, so the cache may evict older versions of those first when storage gets tight. Your text drafts (the entry itself, fields, tags) are kept in priority.

If you're heading remote for an extended job, open every document you might need to view while you have signal. Once cached, they're available offline.