Skip to main content
Buyer's Guide

How to Test Whether a Field Service App Really Works Offline

Every app says it works offline. A 20-minute airplane-mode test shows what that means before your technicians depend on it: what to try without signal, what to check in the office and which red flags mean lost work.

Published October 29, 2026 6 min read

Every field service app says it works offline. You find out what that means at 4pm on a Thursday, in a basement, when a technician's notes and photos don't show up in the office and the customer is waiting for an invoice.

You don't have to find out that way. A field service app offline test takes about 20 minutes, one phone and one person in the office. Run it during the trial, before anyone in your shop depends on the app.

Why "works offline" means different things to different vendors

"Offline" covers a wide range. At one end are apps that show what you looked at earlier but won't let you change anything until signal returns. At the other are offline-first apps that work from the phone all the time and sync in the background. In between are apps with an offline setting you have to switch on before you lose signal, which your techs will forget to do.

The differences that matter in the field:

  • Can the tech change things offline, or only read them?
  • Do photos and completed forms survive if the app is closed or the phone restarts?
  • What happens when the office and the tech edit the same job?
  • Does anything need to be prepared in advance, like downloading the day's jobs?

Trade work happens where signal is worst. Federal researchers have pointed out that modern building materials such as aluminum, steel and coated glass can significantly reduce or block wireless signals. Your test should assume the same.

Before you start: set up a real test

You need:

  • One phone with the app installed and signed in as a technician
  • One person in the office signed in to the office side
  • A real-looking job assigned to that technician: a customer, an address, a checklist if the app supports forms, and some service history
  • Twenty minutes where nobody needs that phone

Use a test customer, not a real one. You're going to create a conflict on purpose.

The field service app offline test, step by step

Step 1: Load the day, then cut everything

Open the app with signal and look at today's job once. Then turn on airplane mode.

Here's the catch most testers miss: airplane mode doesn't always turn off Wi-Fi. On an iPhone, Apple notes you can still use Wi-Fi and Bluetooth in Airplane Mode, and many phones remember your Wi-Fi choice. Turn Wi-Fi off separately, and check that the status bar shows no Wi-Fi icon. On Android, the steps vary by phone; Google's Pixel help page shows the settings path.

If you skip this, you're testing the app on the office Wi-Fi, which tells you nothing.

Pass: the app opens to something useful, not a spinner or an error screen.

Step 2: Work the job start to finish

Do everything a technician does on a normal call, with no signal:

  1. Open the job and read the customer's notes and service history.
  2. Change the status to on the way, then arrived, then working.
  3. Fill in the checklist or job form.
  4. Take three photos: before, during, after.
  5. Add a note.
  6. Collect the customer's signature, if the app supports it.
  7. Mark the job complete.

Pass: every step works without a warning that you need a connection. Write down any step that's blocked.

Step 3: Close the app and reopen it

Still offline, force-quit the app. Swipe it away; switching to another app doesn't count. Then open it again.

This step separates offline-first apps from apps that hold your work in memory. If the photos, form answers or status changes are gone after a restart, a dead phone battery in a crawl space will cost you the same work.

Pass: everything from Step 2 is still there.

Step 4: Make a conflict on purpose

Ask the person in the office to change something on the same job while the phone is still offline: edit the job notes, or change the status of a piece of equipment on it.

Real days produce this all the time. The office updates a gate code while the tech is underground, or marks a unit as replaced.

You'll check the result in Step 5. What you want to learn is how the app decides whose change wins, and whether it tells anyone.

Step 5: Reconnect and check the office

Turn Wi-Fi and cellular back on. Don't open anything special on the phone; a good app syncs in the background.

Then, in the office, check:

  • Is the job marked complete, with the right times?
  • Are all three photos attached, in full quality?
  • Is the form filled in, with every answer?
  • Is the signature there?
  • What happened to the conflict? Did one change silently overwrite the other, or did someone get asked?

Pass: everything arrives without the tech doing anything, and the conflict is handled in a way you can explain to your team.

Red flags

Stop the trial and ask hard questions if you see any of these:

  • The app needs you to switch on an offline setting or download jobs first
  • Photos or forms disappear after a restart
  • The app blocks completing a job without signal
  • Sync only starts when the tech opens a specific screen or taps a button
  • A conflicting change disappears without anyone being told
  • The vendor can't tell you in one sentence what happens when two people edit the same job

What to ask the vendor

Bring these to the call:

  1. Is there anything a technician can't do without signal?
  2. Does anything have to be downloaded before the tech loses signal?
  3. What happens when the office and the tech change the same record?
  4. Which plan includes offline use?

For reference, here's how FSM Navigator answers. The iOS and Android app is offline-first on every plan, Free included, so there's no setting to turn on. Technicians keep working without signal and changes sync automatically when the device reconnects. Some of the steps above depend on your plan: job photos, forms, signatures and time tracking are on Pro, and parts used from van stock are on Enterprise. On Enterprise, if a technician's queued asset status change is rejected because the asset changed in the meantime, the app opens a conflict sheet that shows both values and lets the technician keep theirs, keep the server's or merge. Details are on the offline field service app page.

Run the same test on every app you're comparing. The results will tell you more than any feature list. If mileage matters to you, also read how offline mileage tracking handles trips logged without signal, and what good job photo documentation looks like once photos arrive. To compare the rest of the mobile app, start at the mobile app page.

Start free with up to 5 users and run this test on your own phone this week.

Frequently asked questions

How do I test if a field service app works offline?

Put a technician's phone in airplane mode with Wi-Fi off, work a job start to finish, force-quit and reopen the app, then reconnect and check that everything arrived in the office.

Does airplane mode turn off Wi-Fi?

Not always. iPhones and many Android phones let Wi-Fi stay on in airplane mode. Turn Wi-Fi off separately for a real offline test.

What happens to offline data if the app closes?

In an offline-first app, it's saved on the phone and survives a restart. Test it: force-quit the app while offline and reopen it.

How do I know if data synced after reconnecting?

Check the job in the office: status, times, photos, form answers and signature should all be there without the technician doing anything.

Is an offline setting the same as an offline-first app?

No. An offline setting has to be turned on before you lose signal. An offline-first app works from the phone all the time and syncs in the background.

Try FSM Navigator free for up to 5 users

No credit card. iOS & Android included. Set up in under 5 minutes.