Yes. A work order can require signatures from operator, supervisor, and safety officer — configurable per work type and customer.

Customer signatures are PII; treated as such. Retention rules per customer, per region. Right-to-erasure supported with audit-log preservation.

Can the customer get a copy in their portal?

Yes if the customer portal is enabled. Otherwise email. Most B2B customers prefer both.

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 · Customer Sign-off

Done means signed.

Customer signs on the engineer's tablet. The work order closes. The invoice triggers. No back-office step, no paper bridge, no "we will email you the report tomorrow". The cycle from job done to invoice sent is minutes — and customers love it.

Signature with name and role

Name, role, signature, optional photo of the customer signing. Captures who authorised the work — not just an unverifiable squiggle.

Instant customer copy

Customer receives their copy of the signed work order by email within seconds. Branded, dated, including photos. Disputes get answered before they start.

Tamper-evident record

Signature is hashed with the work-order content at the moment of signing. Any retrospective edit shows as such in the audit log. Auditor-friendly.

What you see

The signature is the contract.

A signature on a tablet is more than a digital nicety. It is the moment the customer accepts the work — the legal moment that justifies the invoice. uFieldService treats it accordingly: tamper-evident, audit-logged, sent to the customer with the full work order attached.

On-screen signature with stylus or finger
Customer name and role captured
Optional customer photo at sign-off
Auto-email of signed work order to customer
Tamper-evident hash of order content + signature
Multi-signature support (multiple stakeholders signing)

When this matters

Signals you'd reach for this.

Paper signatures get scanned later

A paper signature scanned the next morning takes the engineer's admin time and delays the invoice. Real-time signature ends both.

Customers cannot remember signing

Without a copy in their inbox, customers genuinely forget. A polite reminder ends most disputes before they grow.

"Who actually signed?"

When you cannot prove who at the customer signed, every dispute is open. Name and role capture closes most of them.

Sign-off paperwork lives in a binder

Paper that lives in a depot binder is unfindable when needed. Digital records are findable in three seconds.

FAQ

The questions everyone asks first.

Still wondering? Ask us directly →

A "no-signature" path with mandatory reason and supervisor notification. The work order closes; the invoice flow may require a manager approval depending on contract. Audit log captures the refusal.

See uFieldService in a 30-minute demo.

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

The uTools suite