The work happens where the signal doesn't
Most field software treats no connection as an error state. This one treats it as the normal condition, because in pest control it is. A cold room is a metal box. A plant room is underground. A warehouse aisle is forty metres of steel racking between you and the nearest window.
On the phone
What the phone holds
Before the shift, the app pulls down what the day needs and keeps it in a database on the handset: the jobs, the full zone tree for each site, every trap in those zones, the question set for each trap type, and the shared reference data — 65 pest species, the chemical list, the material list, the stock locations. Thirteen tables in all.
Signal
What needs a connection, stated plainly
Works with no bars
Everything between the morning download and the client's signature: opening a job, walking the zone tree, scanning a QR code, filling in the form, taking photographs, recording chemicals, confirming installations and capturing the signature.
Needs a connection
Signing in, the first capability check, pulling the day down, and reading live van stock — which falls back to the last reading and shows the time it was taken.
Sync
How the work gets back
Every entry is queued on the device. When signal returns and the app is open, the queue drains itself, and it is careful about why something failed.
No signal
Waits
Not a failure. The item keeps its place in the queue and no attempt is used up.
The server was busy
Retries
Worth another try. The item is retried, backing off from thirty seconds to thirty minutes across eight attempts.
The server said no
Stops
The same record would be refused the same way a hundred times, so it stops at once and asks for a person.
What the technician sees
- The number of records waiting to upload, on the home screen.
- The number that failed, in red, with a retry button.
- In settings, each failed item with the server's own words and a button to copy them for support.
Guarantees
Two guarantees worth stating
Local progress always wins.
A visit signed offline is never reset by a server that has not heard about it yet.
Signing out cannot quietly discard work.
Signing out refuses to run while unsent work exists. It names the number and asks a second time before discarding anything.
Tell us about your sites
How many technicians you have, and what your clients are audited against. We will tell you plainly whether the suite fits.
Talk to us