Can a field be internal-only?

Yes. Every block has a visibility toggle with two options: engineer-only, or engineer and customer PDF. Internal-only fields show up on the engineer's tablet and in Business Central reporting, but never on the PDF sent to the customer.

Can different work types have different forms?

Yes — that is the point. Each work type in Business Central points to its own form template; the engineer sees the right form when they open the work order. Generic fallback forms exist for one-off work types.

What about conditional logic — show field B only if field A is ticked?

Supported. Conditional visibility and conditional required-ness, driven by other fields on the same form. Keeps forms short by hiding everything that does not apply yet.

Can we go back to an old, filled-in form?

Yes. Every completed form is stored against the work order it belongs to — you can always open a past work order and see exactly what the engineer filled in, what they ticked, the photos they attached and the signature they captured. The completed form is a permanent part of the work-order record.

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 · Form Builder

Build the engineer's form. Build the customer's report. From the same place.

A drag-and-drop builder for the forms engineers fill in on the job — order details, materials used, time clocked, photos, custom checklists, free text. Decide per field whether it stays internal or shows up on the PDF that goes out to the customer. No code, no Business Central report layouts, no developer ticket.

Drag-and-drop form builder

Assemble forms from blocks: header, customer details, work-order lines, time, materials, photos, signatures, free text, checklists, dropdowns, numeric inputs. Reorder, duplicate, conditionally show or hide. The result is what the engineer sees on the tablet.

Internal or customer-facing per field

Every block carries a toggle: shown to the engineer only, or shown to both the engineer and the customer (on the signed PDF). The internal damage-assessment notes stay internal; the work summary, materials and signature land on the customer copy.

A form per work type

Different jobs need different forms. A heat-pump install captures refrigerant volume and pressure; a printer service captures the page count. Each work type points to its own form, so engineers never see fields that do not apply.

What you see

A form that matches the job.

Off-the-shelf service apps give you one generic form for every situation. uFieldService lets you build the exact form your engineers need for each kind of work — and decide, field by field, what the customer is allowed to see. The result is shorter forms, faster sign-off, and a customer report that says exactly what you want it to say.

Drag-and-drop builder; no code, no developer needed
Field types: text, number, dropdown, checkbox, date, photo, signature, free text
Pre-built blocks: order header, materials, time, customer details, asset details
Per-field visibility: engineer-only, or engineer and customer PDF
Conditional fields (show "refrigerant type" only when "refrigerant added" is ticked)
Per-work-type forms — engineers see the right form automatically
Required fields and validation — sign-off blocked until completed
Live preview of both the engineer view and the customer PDF as you build

When this matters

Signals you'd reach for this.

"Can we add a field to the report?"

A question that should not need a developer. A form builder is the difference between "we will scope it in Q3" and "done by the end of the meeting".

Customers see fields they should not

A report that leaks an internal note, a cost figure, or a damage assessment is the bad kind of transparency. Per-field visibility prevents it.

Engineers fill in fields that do not apply

A generic form with twelve sections for every job is twelve sections of "N/A". Work-type-specific forms cut the noise.

Forms drift across teams

Without one source of truth, "the form" becomes "Mark's form", "Sven's form" and "what we used last year". A central builder ends the drift.

FAQ

The questions everyone asks first.

Still wondering? Ask us directly →

You, with a drag-and-drop builder. It is designed for an operations manager or service lead, not an IT specialist. Most companies build their first few forms in an afternoon, then iterate from real engineer feedback.

See uFieldService in a 30-minute demo.

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

The uTools suite