Skip to content

Planning for work away from a connection · 4 min read

What should your business app do when there’s no signal?

When staff lose signal on a job, decide what they still need to read or record, and what should wait until they can check with the office.

Start here.

Start with the task that stops when the connection drops. A readable job pack may be enough. If staff need to record work, test whether it stays on the device and reaches the office later. Keep decisions that rely on current shared information pending until someone can check.

  • Follow a real job to see what stops when the connection drops.
  • Distinguish work saved on the phone from work the office has received.
  • Test one change from the field and another from the office before reconnecting.

Find the moment the work stops

Imagine a company that inspects commercial kitchen equipment. A technician opens a job on their phone in the car park, then loses signal in the basement. They still need the equipment checklist, a way to record what they found and somewhere to put a photo. Back at the office, a colleague may be updating the same job.

Ask someone who does the work to walk you through a recent visit. Where did they lose signal, what did they need at that moment, and what did they do instead? If they only needed the address and access instructions, a job pack they can open without signal might be enough. If they kept notes on paper and typed them again that evening, saving the notes on the phone may be the better investment.

Decide what people can read, record or confirm

Make a short list of the information that must be on the phone before someone leaves. In the inspection example, that could mean the assigned jobs, the checklist and the previous service note. Agree how staff can tell whether those details are ready and when they were last updated.

Then decide what they can record. Give someone a way to check that their notes or photos were saved on the device, and a separate indication once the office has received them. If the inspection requires a current instruction from a supervisor, agree what staff should do until they can reach one.

Three ways to handle a lost connection in the hypothetical inspection business
NeedWhat to ask forWhat to check
Read the job detailsA job pack prepared before the visit.Can staff open the right checklist and tell when it was last updated?
Record work to send laterNotes and photos saved on the phone until it reconnects.Can staff see what is waiting and what the office has received?
Make a promise that depends on shared informationA way to check with the office or wait for a connection.Does the app make clear that the promise is still pending?

Agree what happens when two people change a job

Suppose the technician records the inspection as complete while out of signal. In the meantime, the office learns that a second unit needs checking and adds it to the job. When the phone reconnects, the office should get the inspection notes and still see that the second unit needs attention.

Try that example with your supplier. Ask what the technician sees, what the office sees, and who settles the difference if the app cannot. Discuss the actions that need current information to be safe or useful. Reserving the last replacement part or promising a time to a customer may need to wait until someone can check the shared schedule or stock.

Test it with the connection switched off

Use a sample job and devices like the ones staff carry. Prepare the phone as you normally would before a visit. Switch off Wi-Fi and mobile data, open the job, enter a note, take a photo, and close and reopen the app. Ask someone at the office to change one instruction while the phone is still disconnected.

Turn the connection back on and check both screens. Can the technician tell the note and photo reached the office? Is the newer instruction still there? Try a weak or interrupted connection too. A useful demonstration includes what staff see when a photo has not made it through and what they do next.

Buy the part your staff will use

Try the smallest useful option on a few representative jobs. Ask staff whether they could finish the agreed task, whether they still had to type anything twice, and whether the office could tell what was waiting to come through. If staff can carry on with a job pack and a clear phone fallback, you can stop there.

If you need the app to keep information on a phone, agree which records belong there and what happens on a shared or lost device. Keep the first trial narrow enough that you can check those rules with the people who will use it.

Give your supplier a job to demonstrate

Use a recent example to agree on the work staff should be able to finish.

Before the visit
Which jobs, files and instructions should be ready on the device?
During the visit
What can staff do without a connection, and what should wait for confirmation?
After reconnecting
How will both sides know their changes arrived and what still needs attention?

Planning something with a similar workflow?

Discuss your project with us

A couple of common questions.

Is a downloadable app enough to work without signal?

Ask to see the specific task with the connection off. Test what opens, what saves and what reaches the office once the connection returns.

What if someone goes to a job that was never loaded on their phone?

Agree on a fallback and show it clearly. Staff may need to call the office or wait for a connection before starting if the job requires information they do not have.

Can we test offline access with one team first?

Yes. Pick a team and a representative set of jobs. Include a changed instruction, a photo and a reconnection so you see how work moves between the phone and the office.

Have something in mind?

Tell us what you want to build or improve. We’ll work out a useful first step together.

Discuss a project