How are conflicts resolved?

Field-level merge with conflict markers shown to the user. Most edits never collide — different engineers work on different work orders, and within a work order the engineer's device is the only writer while the job is live. The rare collision (a back-office edit to a work order the engineer is also touching) is handled with a clear "this changed in the office" prompt and a side-by-side compare.

A typical day caches under 200MB. The app evicts old cached work orders on a rolling basis. Battery use is dominated by screen-on time, not by the sync engine.

Field Service

uFieldService

Engineer execution, native to Business Central.

Field service operations are often split across multiple systems and manual steps. uFieldService centralises the engineer-execution side of that workflow. Engineers receive digital work orders with customer details, asset history, work instructions and required materials — sourced from either the Project module or the Service module of Business Central, whichever fits the job. Engineers register their own time and time for coworkers, add materials by scan, work fully offline, communicate with customers from the app, and capture a customer signature on-site. Everything posts straight back to Business Central — no re-keying, no paper bridge.

Functionalities · 10

uFieldService · Offline Mode

A full shift offline is a supported scenario.

Basements. Tunnels. Rural blackspots. Industrial sites where the customer Wi-Fi is "rebooting all morning". The engineer does a complete day's work — work orders, materials, photos, signatures, time — without a signal, and the app syncs cleanly the moment connection returns.

Local-first by design

Every action writes to a local store first, then syncs. Offline is not a degraded mode; it is the same mode, minus the network.

Conflict-aware sync

When two engineers update the same record offline, the merge is structured (line-level, not file-level). The engineer sees what conflicted; the resolution is one tap.

Sync status the engineer trusts

A clear pending-count, a "last synced" timestamp, a warning if anything failed. Engineers never wonder whether their day is safely captured.

What you see

The day you cannot afford to lose.

An engineer who finished eight jobs offline and lost them on the drive home is a quitting engineer. uFieldService treats the offline cache as durable, encrypted, and recoverable — the engineer's day survives a dropped tablet, a flat battery, a corrupted file. The sync engine is the most-tested part of the product.

Encrypted local store on the device (work orders, forms, photos)
Outbound queue with retry, conflict detection and audit
Pre-cache of the day's work orders, forms and reference photos
Sync indicator: pending count, last-synced time, failure surface
Cross-device hand-off (start on tablet, finish on phone)
Tamper-evident timestamps — signatures and times preserved through sync

When this matters

Signals you'd reach for this.

Engineers refuse to start work offline

If the app cannot be trusted offline, engineers fall back to paper "just in case". The paper becomes the workflow; the app becomes a copy step.

Sync failures are silent

A failed upload that nobody sees is a job that never happened in the system. An obvious sync indicator turns silent failure into a tap to retry.

Photos go missing on the drive home

A device that loses photos because the cache was unbounded is a device the engineer stops trusting. Bounded, durable cache is table stakes.

"It synced — but did it?"

When sync state is fuzzy, engineers re-enter data. The indicator must be clear enough to end the doubt.

FAQ

The questions everyone asks first.

Still wondering? Ask us directly →

Days. The cache holds the engineer's assigned work orders and their associated forms. We have customers running multi-day remote installations entirely offline.

See uFieldService in a 30-minute demo.

A real screen-share with someone who built it. No slides.

The uTools suite