Skip to main content

Inspections that finish without reception

Pits, basements, tunnels, plant rooms and remote sites are where this work actually happens. Forms complete on the device, loaded work orders record their results there, and both sync when it reconnects, photos included.

Lachlan McRitchie

Lachlan McRitchie

Co-Founder & GM of Operations

Published 3 September 2026Updated 27 September 2026

Trusted by construction, mining and field service teams

Saunders InternationalMineral ResourcesSupagasHacer GroupMetro TunnelUltrabuilt
G2 rating 4.9 out of 5
Capterra rating 5.0 out of 5GetApp rating 5.0 out of 5Software Advice rating 5.0 out of 5
15 reviews on G2 · the same 17 reviews on Capterra, GetApp and Software AdviceCapterra Best Value 2026 badgeCapterra Best Ease of Use 2026 badgeAll MapTrack reviews

Include the reconnection in your field trial

An offline demonstration should finish with a saved result the office can reopen. Use a representative job with several assets and an attachment, on the actual device the crew will take to site.

  1. 1. Check the complete job before departure

    Open the job and its procedures while connected. Give the field crew a clear scope so the office is not editing the same record during the offline visit.

  2. 2. Verify the return to coverage

    After the device reconnects, inspect the completed job, each asset outcome and uploaded photos from a connected session. Keep incomplete uploads or conflicting changes visible until resolved.

Setup and limits

  • A job first created after the device lost reception cannot already be loaded on that device.

What does offline actually mean here?

It means the crew can complete forms and inspections with no connection, and can work through an already-loaded work order, recording its procedures and per-asset pass or fail outcomes. Those sync when the device reconnects. The boundary is specific: the work order must be loaded before signal is lost, and adding costs, moving it to Completed, creating a new work order, imports, exports and server-side automations need a connection. On pull, server state wins if a record changed while the device was away.

  • Works offline: Forms, inspections, photos, and a loaded work order end to end.
  • Needs a connection: Creating new work orders, setup, imports, exports, server-side automations.
  • Conflict rule: Server state wins on pull. Worth knowing before you depend on it.

Why is "works offline" usually not a real answer?

Because it is said by almost everyone and defined by almost no one. Offline covers everything from caching a read-only list to completing a full job and reconciling it later, and the difference only shows up on a site with no coverage, halfway through a shift. The useful question to ask any vendor, including us, is narrower: what exactly can be completed, what cannot, and what happens when the same record changed on the server while the device was away.

The problem

Field work happens where the coverage is not. Pits, tunnels, basements, plant rooms, prisons and remote sites all break an app that assumes a connection, and the failure is expensive because it happens after the crew has driven there. Teams work around it the old way: paper in the ute, photos on a personal phone, and someone typing it all up that evening from memory. That is where the evidence gets thin and the timestamps stop meaning anything.

How MapTrack addresses it

MapTrack has no separate offline mode to switch on, so nobody has to remember to change modes before driving into a pit. Forms and inspections complete on the device, photos included. On a work order that was loaded before signal was lost, procedures and per-asset pass or fail outcomes are recorded on the device; adding costs and moving it to Completed wait for the connection. Everything pushes when the device reconnects. Where a record changed on the server while the device was offline, server state wins on pull, and we would rather you knew that rule up front than discovered it.

How it works

  • 1

    Load the work before the crew leaves

    Open the jobs and assets they will need while there is still signal. The most common offline failure is a job raised after the ute left the highway.

  • 2

    Work normally on site

    Complete forms and inspections, record per-asset results, capture photos. There is no separate mode to enable.

  • 3

    Capture the evidence at the time

    Photos and notes go on the record as the work happens, rather than being reconstructed that evening from memory.

  • 4

    Reconnect and sync

    Submissions and completed work push automatically once the device is back in coverage.

  • 5

    Know the conflict rule

    Server state wins on pull. Give one person ownership of a job while it is out of coverage and this never bites.

Why we publish the boundary instead of the word

Offline is the single most common must-have we hear, and the most loosely defined claim in the category.

A specific capability, not a slogan

Loaded work orders record procedures and per-asset outcomes offline. Completing them and creating new ones need a connection. Both halves are stated.

A published conflict rule

Server state wins on pull. Ask any other vendor in this category for their rule in writing and see what comes back.

Photos survive the gap

Evidence is captured at the time and uploads later, rather than living on a personal phone until someone remembers to send it.

No mode to remember

The app does not need to be switched into an offline state, because nobody does that at the top of the ramp on the way down.

Finish the job where the signal ends

Forms, photos and loaded work orders complete on the device and sync when it comes back into coverage.

  • No credit card required
  • 30 days free trial
  • Cancel anytime

Frequently asked questions

Yes, for forms, inspections and loaded work orders. With no reception, crews complete forms and inspections and work through a work order loaded before they lost signal, recording its procedures and each asset's pass or fail, and it all syncs when the device reconnects.

Complete forms and inspections, and work through an already-loaded work order, recording its procedures and per-asset pass or fail outcomes. Submissions and results push when the device is back online, where costs are added and the work order is moved to Completed. The job has to be loaded onto the device before signal is lost.

Creating a new work order, setup, imports, exports and server-side automations. We would rather be specific about the boundary than say "works offline" and let you discover the edge on a site with no coverage.

On pull, server state wins. That is the rule, and it is worth knowing before you rely on it: if a record changed on the server while a device was offline, the server version is what the device ends up with. Design your process around one person owning a job while it is out of coverage.

Yes. Photos captured against a form or an asset are held on the device and upload when the connection returns. Photo evidence is attached to a large share of inspection and damage conversations, so it has to survive the coverage gap rather than being the thing that fails.

No. The app works the same way whether or not there is a connection, which matters because nobody remembers to flip a switch before they drive into a pit. What changes is when data moves, not what the person on site does.

Load the work before you leave. Open the jobs and assets the crew will need while you still have signal, so they are on the device. The most common cause of a lost afternoon is a job that was raised after the crew had already left the highway.

Try it on your worst site

Join construction, mining and field service teams across Australia.

4.9 on G2 · 5.0 on Capterra, GetApp & Software Advice

  • No credit card required
  • 30 days free trial
  • Cancel anytime