Offline Check-In for NDIS Carers: How It Works and What the Audit Trail Looks Like
How Teiro handles check-ins when carers have no mobile signal -- what gets stored on-device, when it syncs, and whether offline check-ins satisfy NDIS audit requirements.
How does offline check-in work in Teiro?
When a carer has no mobile signal, Teiro's mobile app stores the check-in locally on the device -- recording the timestamp, the job reference, and the GPS coordinates if the device can obtain them without a network connection. When connectivity is restored, the app automatically syncs the cached check-in to the server. The audit trail on the job record shows the original check-in timestamp captured on-device, not the time the sync occurred.
Why remote and regional NDIS service delivery often lacks connectivity
Australia's disability support sector operates across an enormous geographic range. A registered provider in a major city may have some carers working in inner-suburban apartments with strong 5G coverage and others working in outer suburbs or satellite towns with intermittent connectivity at best.
For providers operating in regional or remote areas -- including providers delivering supports to Aboriginal and Torres Strait Islander communities, rural aged care recipients, or participants in regional SIL houses -- reliable mobile connectivity during a shift is not a given.
Common scenarios where connectivity is absent or unreliable:
- Residential facilities in regional towns where internal signal is blocked by building materials
- Rural properties where the nearest tower is 30 or more kilometres away
- Underground car parks and basement facilities in metropolitan areas
- Hospitals and medical facilities with restricted or congested networks
- Homes in areas underserved by mobile infrastructure
An app that requires a network connection to check in is an app that fails in these environments. Teiro's offline mode ensures that check-ins are captured regardless of connectivity, and that the record created is as complete as possible given what the device can access at that moment.
What gets cached locally when a carer checks in offline
When the device cannot reach the Teiro server, the app stores the following locally:
- The check-in or check-out timestamp (taken from the device clock at the moment the carer taps the button)
- The job reference (the specific job the check-in relates to)
- The GPS coordinates, if the device can obtain them independently of the network (most modern iOS and Android devices can acquire GPS without a mobile data connection, using satellite signals directly)
- The action type (check-in or check-out)
- The user identifier (so the record is attributed to the correct carer on sync)
The cached record is stored securely on-device and is not accessible to other apps or users.
GPS availability when offline
GPS acquisition does not require a mobile data connection on most modern devices. The device communicates directly with GPS satellites to determine its position. However, GPS cold-start time (the time it takes a device to acquire satellite signals after being in a location without GPS use) can be longer without the assistance of network-based location services, which use cell tower and Wi-Fi triangulation to speed up the process.
In practice, this means:
- If the device has been used recently in a GPS-active state (navigation, recent check-in), it will typically obtain coordinates quickly even without a data connection.
- If the device has been off or in airplane mode for an extended period, GPS acquisition may take 30-60 seconds in an area with clear sky visibility.
- Indoor environments with no sky visibility may prevent GPS acquisition entirely, regardless of connectivity.
Teiro records whatever the device can provide. If GPS coordinates are obtained, they are stored. If they are not available, the check-in is still captured with the timestamp and job reference.
Sync behaviour when connectivity restores
When the device re-establishes a network connection -- whether Wi-Fi or mobile data -- Teiro automatically syncs any pending offline check-in records to the server in the background. The carer does not need to take any action.
The sync process:
- 1.The app detects that connectivity has been restored.
- 2.Any pending cached check-ins are transmitted to the server.
- 3.The server records the check-in with the original on-device timestamp, not the sync time.
- 4.A sync metadata field records when the data was received by the server, distinct from when the check-in occurred.
- 5.The job activity feed on the coordinator's view updates to show the check-in once sync completes.
This means the audit trail accurately reflects when the carer checked in, not when their phone happened to find a signal. A carer who checks in at 9:00 am in a building with no signal and whose phone syncs at 9:45 am when they step outside will have a check-in time of 9:00 am on their job record.
GPS-available vs GPS-unavailable vs fully offline: what the record looks like
| Scenario | Timestamp | GPS coordinates | Distance from job address | Sync note |
|---|---|---|---|---|
| Online check-in, GPS available | Captured at check-in | Captured at check-in | Calculated on server | No offline sync needed |
| Offline check-in, GPS available | Captured on-device | Captured on-device | Calculated on server at sync | Sync timestamp recorded separately |
| Offline check-in, GPS not available | Captured on-device | Not available | Not calculated | Sync timestamp recorded; no distance shown |
| Fully offline, no GPS | Captured on-device | Not available | Not calculated | Check-in marked as offline; coordinator notified |
In all scenarios, the check-in timestamp is recorded. The presence or absence of GPS coordinates affects the distance calculation but does not prevent the check-in from being logged.
Does an offline check-in satisfy NDIS audit requirements?
The NDIS Quality and Safeguards Commission requires providers to maintain records that demonstrate support was delivered as planned. The Commission does not prescribe the specific technology used to create those records, but it does require that records be accurate, contemporaneous, and attributable to the worker who delivered the support.
An offline check-in captured by Teiro satisfies the contemporaneous requirement because the timestamp is recorded at the moment of the check-in, not at the time of sync. The record is attributable because it is linked to the carer's account and device. The sync metadata provides an additional audit layer showing when the data was transmitted to the server and confirming the two timestamps are consistent with a plausible offline period.
For providers in regional and remote areas, this is important. A Commission auditor reviewing records for a participant in a location with known connectivity limitations should not penalise a provider for using offline check-ins if the records are otherwise complete and consistent.
The practical standard is: can the provider demonstrate that a specific carer attended a specific job at a specific time? An offline check-in with a device timestamp, job reference, and carer identifier satisfies that standard. The absence of GPS coordinates in a genuinely offline environment does not undermine the record -- it is consistent with the documented connectivity conditions.
Providers should include a brief description of their offline check-in capability in their quality management documentation so that auditors understand how the system handles low-connectivity environments.
What coordinators see when a check-in was offline
The job activity feed in Teiro shows check-in events as normal. Where a check-in was captured offline and synced later, the record includes:
- The check-in timestamp (on-device time)
- An offline indicator noting the check-in was captured without connectivity
- The sync timestamp (when the server received the data)
- GPS coordinates and distance, if available
Coordinators do not need to do anything with this information in normal operations. The offline indicator is there for transparency -- if a coordinator sees a check-in that was logged offline and synced three hours later, they can follow up if that seems inconsistent with what they know about the shift.
Frequently Asked Questions
Can a carer manipulate the check-in timestamp by changing their device clock?
Teiro records the device timestamp but also records server-side metadata on sync. A significant discrepancy between the on-device timestamp and the sync time -- beyond what is plausible given connectivity conditions -- is flagged. Coordinators can see both timestamps. Device clock manipulation is possible in theory, but the dual-timestamp record makes it detectable on review.
What happens if a carer's phone dies before the offline check-in syncs?
If the app is closed or the device runs out of battery before the pending check-in syncs, the cached data may be lost depending on whether it was written to persistent storage. Teiro writes cached check-ins to persistent local storage immediately on capture, so they survive app restarts and brief power interruptions. A full device wipe or factory reset would lose unsynced data.
Does offline mode work for check-out as well as check-in?
Yes. Offline mode applies to both check-in and check-out. The same caching and sync behaviour applies to both events.
Are offline check-ins treated differently in payroll processing?
Teiro passes the on-device timestamp to payroll calculations, not the sync timestamp. So a carer who checks in offline at 9:00 am will have a shift start time of 9:00 am in the payroll record, even if the sync happened later. Coordinators can review offline check-ins before payroll is finalised if they want to verify any anomalies.
For more on how Teiro handles check-ins in all conditions, book a demo or create a free account.