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.

uFieldService image 1
Functionalities · 10
uFieldService · Overview

Field service execution, native to Business Central.

Digital work orders, on-site execution, time and materials capture, digital signatures — all flowing directly into Business Central, on either the Project module or the Service module. Engineers spend their day on the work; the back office sees clean, signed data the moment it happens.

Built for the van
Works fully offline. Big buttons. Photo capture. Signature capture. Time registration for the engineer and their coworkers. Built by people who shadowed engineers for a week before they wrote a line of code.
Done means signed
Customer signs on the engineer's tablet. The work order closes. The signed report is sent. The back office sees a completed, defendable record — not a pile of paper waiting to be typed up.
Native to Business Central — Project and Service
Work orders, time and materials land directly in Business Central's Project or Service module. Use the one that fits the job; both are first-class.
What you see

The cycle time conversation.

A field-service business lives and dies on cycle time — work order to cash. Paper-driven shops measure it in weeks. Digital-but-disjointed shops measure it in days. uFieldService brings the engineer-execution side to hours: signed data hits Business Central the moment the engineer leaves the site, so the back office can invoice from it without re-keying anything.

  • Digital work orders with full customer and asset context
  • Engineer app with offline support, photo and signature
  • Time registration for the engineer and their coworkers on the job
  • Materials added on the order — by scan, by search, or from van stock
  • Customer communication from inside the app (ETA, status, signed report)
  • Van stock tracked as a first-class location
  • Posts to Business Central Project or Service — your choice per job
uFieldService image 2
When this matters

Signals you'd reach for this.

01
Engineers type up reports in the evening
A field service business with an evening admin shift is paying its engineers twice and frustrating them once. Real-time capture solves it.
02
Back office re-keys engineer paperwork
A back-office team that retypes engineer time, materials and signatures into Business Central is doing the same work twice. Direct capture ends the duplicate.
03
Engineers run out of parts mid-job
Without van-stock tracking, restock is reactive. Engineers come back to the depot for one part. Productivity drops.
04
Service knowledge lives in heads
When the engineer who knows the customer retires, the customer becomes a guess. A per-asset timeline prevents the loss.
FAQ

The questions everyone asks first.

Still wondering? Ask us directly →

Both. uFieldService writes to whichever module fits the work — Projects for installation, refit and longer-running jobs; Service for break-fix and recurring maintenance. The engineer sees one app; the back office sees the right module for each job.

See uFieldService in a 30-minute demo.

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

The uTools suite

Other apps that pair well with uFieldService