FieldCred caches data opportunistically on each device: the first time a worker's record is successfully loaded online on a given tablet or phone, it's saved locally on that device. If that same worker is scanned again later with no signal, the device falls back to the cached copy automatically.

What you'll see offline

  • A clearance banner (green "Cleared" or red "Not cleared") still shows, computed against the cached worker record and cached site requirements.
  • An "Offline — showing cached data from …" notice appears above it, so it's never mistaken for a live result.
  • If that cached data is over 24 hours old, the notice specifically flags it as stale and suggests confirming another way if possible.
The scan still counts. A gate scan attempted with no signal is queued on the device rather than dropped. As soon as the device regains a connection — checked on app open and automatically whenever the browser detects it's back online — every queued scan is sent to the real audit log, with clearance re-derived from the worker's current record at that time (not the possibly-stale cached snapshot that was on screen during the scan).

The app itself (not just worker data) also loads with no signal — its own pages/JS/CSS are cached separately, so a gate tablet with zero bars can still open FieldCred at all, not just use cached records inside it.

For the one real limitation of this system, see Why a first-time worker can't be checked with no signal.