What about job software on sites with no signal?

Last updated: September 2026

Start with the honest bit

Dispatch needs a connection. There is no local cache, no queue of changes waiting to upload, and no way to keep using it when the signal goes. If that is a deal breaker for your work, this is the paragraph that saves you a fortnight.

We say it plainly because the alternative is worse. A product that implies otherwise, and then loses an engineer write-up in a plant room, has cost that business more than the subscription ever saved.

What follows is the useful part: what connection-free working actually involves, and what most trades businesses need instead of it.

What it really takes to work without a connection

It is not a setting. Software that genuinely keeps working with no signal has to store your data on the device, let you change it, and then reconcile those changes with the server later, which raises hard questions.

What happens if two people changed the same job? What happens if a job was cancelled while you were underground? What happens to an invoice number allocated on a device that has not spoken to the server for two days?

Products that handle this well have usually built their whole architecture around it. Products that bolt it on tend to produce quiet data loss, which is worse than an honest error message, because nobody notices until it matters.

What most trades businesses actually need

Be specific about the problem before buying a solution to it. In most trades, the signal-free part of the job is short: fifteen minutes in a basement, an hour in a plant room, a morning at a rural property.

And the tasks that matter during that window are usually reading rather than writing: what is the fault, what is the history, what does the certificate say. Reading can be handled by looking before you go in.

The writing part, the notes, the photographs and the write-up, does not have to happen at the exact moment. Photographs are taken with the phone camera and attached afterwards. Notes can be written when you come back up.

A working routine for signal-free sites

1. Read the job before you go in. Fault, history, access, previous photographs. Ten seconds at the door.
2. Take photographs with the phone camera as normal. They are on the device regardless of signal.
3. Write the important details in your phone notes if you must, then move them across when you are back in signal.
4. Write the job up before you drive off, in the van, where the signal usually returns.
5. Never let the write-up wait until the evening. That is the failure that gets blamed on signal and is actually about timing.

Businesses that work in genuinely remote places also tend to keep a paper fallback for the worst sites, and that is a perfectly respectable answer rather than a defeat.

Where this leaves the choice

If most of your work is in houses, shops, offices and flats, the connection problem is a nuisance rather than a constraint, and you should choose on the rest of the criteria instead.

If most of your work is in basements, tunnels, rural estates or steel-framed industrial buildings, then connection-free operation is a genuine requirement and you should test it properly: put a candidate in flight mode, write up a job, then reconnect and confirm nothing was lost.

That test is worth doing even where a product claims support, because the claim and the behaviour are not always the same thing.

What Dispatch does instead

It is built mobile first for the phone in a van: large thumb targets, layouts designed for a small screen, nothing to install, and an engineer view that shows the job, the history and the documents in one place.

It is deliberately quick to read on arrival and quick to write up on departure, which is the shape most trades work actually has. Firestore, Storage and all compute run in the UK, in London, which is a different question people often ask in the same breath.

And it is honest about the gap. If you want the rest of the mobile picture, job details on your phone covers what an engineer sees, and installing it on your phone takes about thirty seconds.