Overtime, weekend, night rates?

Driven by the engineer's contract and the job's rate card. The engineer captures their time; the system applies the rates.

How is travel time handled when one engineer drives multiple coworkers?

The lead engineer captures the travel leg once, and the system records the same travel time for each coworker logged on the job. Whether passengers' travel is paid, paid at a reduced rate, or unpaid is driven by their contract and the customer's rate card — both apply automatically when time posts to Business Central.

How are breaks handled? Are they automatic or manual?

Both are supported, driven by the engineer's contract. A break can be manually started and stopped from the app, or auto-deducted on shifts that pass a configured length. Either way, break time is excluded from on-site time, so what the customer sees on their signed report and what the planner sees on the work order match the engineer's actual hands-on work.

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 · Time Registration

Time captured at the moment it happens.

Travel, on-site, work, break — registered as the engineer moves through the day. And the engineer can register time for coworkers on the same job, so a two-person team does not need two tablets and four taps to log the same hour. Time lands directly on the Project or Service order in Business Central.

One-tap state changes

Travelling → Arrived → Working → Break → Working → Done. Every transition stamps the time. No timesheet to write up at 7 PM.

Time for coworkers

On a two- or three-person job, the lead engineer logs time for the team. Each coworker shows up on the time-sheet with their own rate, role, and project line.

Posted to Business Central Project or Service

Engineer time hits the right project-task or service-line in Business Central directly. No re-keying, no end-of-week reconciliation, no spreadsheet bridge.

What you see

A timesheet that writes itself.

A timesheet filled in on Friday for the past five days is a guess. uFieldService captures time as it happens — and lets the lead engineer log time for their coworkers in the same flow, so a crew of three does not become a tax on the lead engineer's evening. The hours are accurate, the payroll is on time, the invoice is defendable.

State-based time tracking (travel, on-site, work, break)
Per-coworker time entry from the lead engineer's app
Per-engineer rates and overtime rules from Business Central
Per-project or per-service-order posting in Business Central
Edits with audit trail (who changed, why, when)
Daily and weekly summary visible to the engineer before submit

When this matters

Signals you'd reach for this.

Friday-evening timesheets

Time written from memory at the end of the week is the worst kind of data. Real-time capture ends it.

Lead engineers re-enter the team's time

A lead who logs their own and then re-enters their two coworkers' hours on a separate form is doing unpaid admin. The team flow gives the time back.

Payroll variances per engineer

When timesheets are guesses, payroll over- or under-pays. Real-time, signed-off time is what payroll needs.

Project margins missing labour

A project that under-reports labour over-states margin. A two-week mis-estimate compounds across a quarter. Accurate time is the floor.

FAQ

The questions everyone asks first.

Still wondering? Ask us directly →

Both. Time on a project job posts to the Business Central Project module against the right task; time on a service order posts to the Business Central Service module against the right service line. The engineer does not choose — the work order does.

See uFieldService in a 30-minute demo.

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

The uTools suite