Skip to content

Working offline

Verifline is built for places with no signal: basements, cold rooms, underground parking, dead zones. The principle takes three beats: preload before, capture during, sync after.

Open the Inspections screen — or the phone’s home — with network: the published templates you can use are put on the device on their own. The Start an inspection sheet says how many are ready: 3 of 4 templates available offline. Offline, a template not yet on the device stays in the list, grayed out, with Not on this phone yet: open it once online — open the Inspections screen at the office, not at the bottom of the basement.

Without network, the app keeps going. On a phone, the cloud in the top bar is crossed out and counts the entries waiting; on a computer, the Offline badge shows in the top band. Capture works identically — answers, notes, photos, actions, and the occurrences of a repeatable section you add, rename or delete. Everything writes to the device, in order, waiting for the network to come back.

The interface contracts rather than lying: screens that live off the server show “Available online only”, and the dashboard freezes on its last numbers — dated “Numbers as of {time}”, so you know what you are reading.

Usable offline Online only
The dashboard (numbers frozen) The template editor
Inspections — list and preloaded capture The organization: members, sites, groups, roles
Actions — view, create, Mark complete Settings — Account settings, Organization settings
The More screen, including Appearance Reports
An action’s messages and photos — to add again once the network is back
Support — the button and the bubble go away, and come back with the network

The theme (Light, Dark, System) follows the same rule: on a phone, More → Appearance stays adjustable offline; on a computer it lives in Account settings, so online only.

When the network returns, the app replays your writes in order. On a phone, the number on the cloud in the bar melts to zero, and the cloud gets its check mark: Everything is saved. Tap it to retry the sending if you would rather not wait. On a computer, it is the “{n} unsynced” counter in the top band, and Sync now forces the pass right away.

Syncing is replayable without duplicates: an inspection sent twice (hiccuping network, app relaunched) exists once. Notifications do not ring twice either.

If your access changed while you were working offline — a role changed, a site removed — the server may refuse an entry. It is not lost: it waits, and the app counts it apart, “{n} entry not saved”. Tap it to see it:

  • Retry sends it again, in the order you made it — useful as soon as an administrator has given the access back;
  • Remove drops it, once you have talked it over with them if this work matters.

The app also reads your access again: the menu no longer offers what was just refused.