Technicians work with or without signal.

Offline by default, not by exception

Syncs on its own when the signal returns

With the app open, the queue is processed on launch, on reconnect and every few seconds. Technicians can also force a send with the “Sync” button.

With the app closed, the operating system takes over. On Android, a native job is scheduled to fire the moment the device reconnects — even if the app was killed or the phone rebooted. On Android and iOS, a periodic background task acts as a safety net.

• On reconnect — on Android, the upload happens seconds after the signal returns, without opening the app.
• In the background — a periodic system task on Android and iOS that only runs when there is a connection.
• On demand — technicians sync manually whenever they want, for example before leaving the site.

What the technician has at hand with no internet

The app keeps a useful slice of the work on the device: between 50 and 80 records from each list — work orders, assets, execution phases and the maintenance agenda. Enough for a whole shift without signal, without turning the phone into a heavy archive that is slow to open.

The work order the technician opened is always available, even outside that slice. Inside it, everything needed to do the job works offline: checklists with evidence, before and after photos, parts used, diagnosis, execution notes, signatures and, when the module is enabled, calibration sheets.

Nothing gets lost halfway through a job

The most fragile moment of a visit is completion: after photos, diagnosis, notes, parts and the customer's signature piled into a single form. If the battery dies or the system kills the app while the camera is open, the technician would lose all of it — and have to ask the customer to sign again.

So the start and completion forms are continuously mirrored to the device as drafts, and the app restores what was being filled in on its next launch. Photos still in the queue show up in the work order gallery separately from the ones already uploaded, so the technician never thinks a piece of evidence went missing.

Technicians know what has not landed yet

Without a connection, the app shows a banner with the number of pending changes. The sync queue screen lists every item: what is waiting, what the server has confirmed and what failed.

If the session expires while the technician is offline, they choose between logging in again or carrying on offline. Nothing already queued is discarded because of the session.

Office rules apply in the field

The app applies the same operation preferences set in the dashboard: mandatory photos, technical diagnosis, execution notes, parts used and signatures. If the company caps open work orders per technician, the app blocks starting another one and says how many are already in progress.

Permissions apply too: creating work orders or customers from the app only appears for people the company allowed, and a work order's calibrations can only be recorded by the technician assigned to it.