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.

Every job, with full context.
Customer history, addresses, equipment serials, prior issues, required materials, access notes — bundled into the work order before it leaves dispatch. The engineer arrives knowing what they need to know.
A work order that does the homework.
A first-time-fix rate is largely a function of preparation. An engineer who arrives knowing the asset history, with the right parts loaded, and the right access route, fixes it on the first visit. An engineer who arrives blind does not. The work order is where preparation gets institutionalised.
- Customer profile with service history
- Asset/equipment record: serial, model, install date, warranty status
- Previous visit notes — what was found, what was done
- Materials added by the engineer — by scan, by search, or from van stock
- Order notes for access, parking, on-site contact and anything else worth flagging

Signals you'd reach for this.
See uFieldService in a 30-minute demo.
A real screen-share with someone who built it. No slides.