Field service

What this category covers

Software for work that happens away from the office: dispatching jobs, planning routes, giving engineers what they need on site, and turning a finished visit into an invoice.

The industries differ wildly. Maintenance, installation, cleaning, inspection, repairs and utilities all buy from this shelf, and a product tuned to one can fit another badly.

Rostering staff by shift belongs in workforce management. Booking appointments where travel is irrelevant is scheduling and booking.

Dispatch is a geography problem

Assigning jobs is not a calendar exercise once travel enters the picture.

The right engineer is the one with the correct skill, the necessary parts, the appropriate certification and a location that makes the journey sensible. Products differ in how many of those constraints they can hold at once, and in whether a dispatcher can override the suggestion when reality intervenes.

Ask what happens when a job overruns. Automatic reshuffling of the rest of the day, with notifications to the customers affected, is the feature that separates serious products from calendars with a map attached.

Emergency work is the other test. A same-day call has to fit into a planned day without dismantling it, and the tool should show the cost of each option rather than silently choosing one.

The mobile side decides adoption

Engineers use this software in vans, plant rooms, lofts and basements. If it is unpleasant there, it will not be used, and the office will go back to phoning people.

• Offline capability, with the job sheet available and updates queued until signal returns.
• Job history for the site, so nobody arrives blind to last month’s visit.
• Photographs and signatures captured as evidence, attached to the record automatically.
• Parts used, recorded on site rather than remembered at the depot.
• Time on site, captured without asking somebody to fill in a timesheet later.

Test with a real engineer rather than a manager. The questions that matter are how many taps a normal job takes and whether the phone’s battery survives a full day of it.

Parts, stock and the van problem

Stock in this category moves constantly and lives in places nobody counts.

Look for stock levels held per van as well as per warehouse, transfers between them, and a way to reserve parts against a scheduled job. Without that, engineers hoard, the count drifts, and someone drives across a county for a component that was already on board.

Purchasing links matter for the same reason. A part consumed on site should reduce stock, appear on the invoice and trigger a reorder without three separate people typing it.

Customers, evidence and getting paid

The visit is only finished when it is billed and accepted.

Check the customer-facing side: appointment confirmations, an arrival window, notification when the engineer is on the way, and a record of what was done. Those reduce failed visits and disputes more than anything internal.

Then check the money path. A completed job should produce an invoice from the labour and parts recorded on site, with payment possible at the door if that suits your trade. Contract and warranty work needs the same path with different rules, and products vary in whether they understand the difference.

How it is priced

Per user per month, commonly with separate rates for office users and field technicians, and sometimes a floor of several seats.

Route optimisation, customer portals, stock control and accounting integration are the features that usually sit above the entry plan, and most trades need at least two of them. Hardware, mobile data and any per-message cost for customer notifications belong in the total as well.

Ask what happens to seasonal headcount, since paying twelve months for a summer crew is a common waste. The broader pattern of quiet meters is set out in what pricing pages hide.

Getting engineers to use it

Adoption decides whether this software delivers anything, and engineers are a demanding audience for good reason.

They are judged on jobs completed, not on data entry, so anything that adds minutes to each visit gets abandoned. Involve two or three of them in the trial and take their objections literally rather than as resistance to change.

The details that matter are small. Whether the job sheet opens with one tap. Whether photographs upload without waiting. Whether the phone works in gloves, in rain, in daylight and in a dark plant room. Whether last month’s visit is visible before knocking on the door.

Then remove the paperwork the system replaces. If engineers still fill in a sheet as well as the application, nothing was gained and everybody noticed.