Do field service apps work without internet access?
Last updated 2026-11-05
The short answer
Most field service apps keep working offline for a narrow set of actions — opening the jobs already downloaded to the device, adding notes and photos, and marking a job complete — then sync when the phone reconnects. Pricing lookups, creating customers, raising invoices, taking card payments and reassigning work between technicians usually need a connection.
Full offline operation is rare. So is a vendor saying so plainly, which is why the question keeps getting asked.
What usually works offline
- The schedule already downloaded to that device
- Customer name, address and contact details for those jobs
- Notes, photos, measurements and signatures
- Marking a job complete
- Time tracking on the job you are currently on
What usually does not
- Looking up a price list, parts catalogue or service history
- Creating a new customer or a new job
- Raising, editing or emailing an invoice
- Taking a card payment
- Reassigning work to another technician
- Anything that depends on what a colleague changed
| Action | Typically offline | Why it breaks |
|---|---|---|
| Open today's jobs | Yes | The list is cached when it last synced |
| Add photos and notes | Yes | Queued locally and uploaded later |
| Mark job complete | Usually | Small payload, safe to queue |
| Look up a price | Rarely | Needs the current price list |
| Take a card payment | No | Requires a live authorisation |
| Create a new customer | Rarely | Needs a unique identifier from the server |
Why "offline mode" is a fuzzy claim
Three different things get called offline, and vendors rarely distinguish between them.
The first is cached reading — you can see data that was downloaded earlier. Almost every app does this and it costs nothing to build.
The second is queued writing — you can add new data that uploads later. Fewer apps do it properly, because merging becomes hard when two people edit the same job.
The third is true offline operation — the app is fully functional with no server at all. This is genuinely rare, because things like payment authorisation cannot be faked locally.
A vendor who says "works offline" is usually promising the first, occasionally the second, and almost never the third.
How to test it in twenty minutes
Do this on the trial before you commit, ideally in a basement rather than the office.
- Put the phone in airplane mode, then force-close and reopen the app. If it will not start, offline reading is not real.
- Open today's job, add a photo and a note, and mark it complete.
- Turn airplane mode off and watch for a sync confirmation. Silence is not success — look for an explicit message.
- Do it again, but kill the app between capture and reconnect. This is the test that finds queued work that dies with the process.
- Try to raise an invoice while offline. If it appears to succeed, ask where the invoice number came from — a locally invented number will collide later.
Questions to ask before you buy
- Which actions are queued locally, and which are refused outright?
- How many queued actions can accumulate before the app stops accepting work?
- Does it warn me before discarding queued work?
- What happens if two technicians edit the same job while both are offline?
- Is the price list cached, and if so when does it expire?
FAQ
Can I take a card payment with no signal?
Almost never. Card payments need a live authorisation from the payment processor, and the usual workaround is to record the card details and charge later, which shifts your fraud risk. If payments matter more than offline notes, judge the app on its payment path rather than its offline mode.
Will queued photos and notes survive a dead battery?
Only if the app writes them to storage before the process ends. Some queue in memory and lose everything when the app is killed. The twenty-minute test above — capture, force-close, reconnect — is the only reliable way to find out, because no vendor advertises the difference.
Does offline mode work on tablets as well as phones?
It is not safe to assume so. Offline caching is often implemented per app rather than per platform, and tablet builds sometimes lag the phone build by several versions. Test the specific device your technicians will actually carry.
What happens when two technicians edit the same job offline?
One edit usually wins and the other is discarded, sometimes silently. Ask explicitly which record wins and whether the loser is notified. A sync conflict you never learn about is worse than a sync failure you do.