Service specification 4 sections Products named
Bespoke Field Service
Management Software
What field service management software does
Field service management, often shortened to FSM, runs work that happens away from the office. It plans who goes where, sends the job to the engineer’s phone, and records what they did on site. Most systems also handle quotes, parts, certificates and the invoice at the end.
Mostly the words change, not the software. Service and maintenance contractors say field service. Trades say job management. The same FSM tools cover both. Use whichever phrase your team already uses.
This is one type of bespoke software. It often sits beside a bespoke ERP system and customer portal software. It may need API integration services to read customer and stock records.
Off-the-shelf job software against something built for you
There are good products in this market. This is when one of them stops being the right answer.
| What to weigh | The case for building your own | What it costs you |
|---|---|---|
| How the day is planned | Scheduling follows how you really allocate work, including the awkward parts. | You have to write down how you allocate work. Much of it lives in one person head. |
| The engineer on site | The app asks only what your job actually needs, so it gets filled in. | Getting engineers to use anything new is a people job, not a software job. |
| What you pay | No monthly fee per engineer, so a busy season does not cost more. | The build costs money up front, and so does every change afterwards. |
| Joining things up | Jobs, parts, invoices and certificates can share one set of records. | Each connection to an existing system is its own piece of work. |
| Paperwork | Certificates and reports come out in your format, signed on site. | Somebody has to own those documents being right, and keep them right. |
| When to buy instead | If a product fits, buying is faster and cheaper. Most firms should. | Building because a product is nearly right is the expensive mistake. |
What it replaces
Most of this work is being done already. It is just being done on paper, on the phone and in the evening.
The day is planned on a whiteboard
Only the person holding the pen knows the plan. A sick engineer means a morning of phone calls.
The board shows who is free, who is nearby and who holds the right ticket.
Job sheets come back in the van
Paper arrives days later, wet or missing. Somebody types it up again to raise the invoice.
The engineer records the job on site and the office sees it the same minute.
Nobody can say what happened last visit
The history sits in an old file, a different engineer's memory, or nowhere at all.
Every visit to that site and that asset sits on one record with photos and readings.
Invoices go out late
The invoice waits for the paperwork, and the paperwork waits for someone to have time.
The invoice is built from what the engineer entered, as soon as the job is signed off.
The products, and when to buy one
Search for this software and you will find products, not developers. That is the right result. For most businesses one of them is the answer, so here they are.
For a trades business running a few vans, look at Tradify, Powered Now, OnSite7 and ToolTime. For service and maintenance contractors with bigger teams and contract duties, look at Joblogic, Commusoft, BigChange, Simpro, Workever and Fergus. For large firms with heavy compliance rules, the options are Microsoft Dynamics 365 Field Service, IFS and Totalmobile.
Those are mature products with years of work behind them. If one fits, buy it. We would rather tell you that now than take a scoping call that should never have happened.
When a product is the right answer
Buy one when your jobs look like everyone else’s: a quote, a visit, a job sheet, an invoice. Setup is quick. Someone else fixes the faults and keeps the phone app working. Most connect to Xero or QuickBooks with no work from you. If that describes your business, stop reading and go and buy one.
When building one wins
Build when the product keeps saying no to something that matters. In practice it is usually one of four things.
Your certificate or job sheet has to be laid out a set way, because a regulator, an insurer or a large customer says so. Your pricing depends on a contract the product cannot model, so someone corrects every invoice by hand. The job needs a customer, asset or stock record that lives in a system you already run, and the product cannot show a record it does not hold. Or the sum stops working: most products charge for every engineer every month, forever, and you have a lot of engineers.
Try two products before deciding. The things they cannot do become your specification, and that is a far better brief than a blank page. Our guide to writing a software specification covers turning that list into something every supplier can quote against.
What goes in a bespoke build
Three parts do most of the work. The scope names every job type, every document and every system the build has to read.
-
01
Scheduling and dispatch
The board shows who is free, who is nearby and who is trained for the work. Jobs move between engineers without a phone call. Recurring visits and contract commitments are planned once and then repeat on their own, so a missed service shows up before the customer notices it.
-
02
The engineer's phone
The job, the address, the site history and the parts list arrive on the phone. Photos, meter readings, times and a customer signature go back. It has to keep working with no signal and sync when the van reaches coverage, because a job that cannot be closed on site becomes evening paperwork again.
-
03
Proof, certificates and invoicing
Anything that has to leave site as a document is generated from what the engineer entered, in the layout your regulator or customer expects. The invoice follows the job rather than being typed again from a paper sheet, so billing stops waiting on the van coming back.
What drives the cost
The number depends on the jobs, the documents and the systems involved. We do not guess it from a headcount.
-
03.1
How many job types
A single repeat visit is simple. Installs, callouts, services and quoted work each behave differently.
-
03.2
What must work offline
Reading jobs offline is one job. Recording and syncing them safely is a larger one.
-
03.3
What documents come out
A plain job sheet is quick. A regulated certificate with a fixed layout is not.
-
03.4
Which systems it reads
Accounts, stock and customer records each need a link, and one system has to own each number.
- Every job type listed
- Every document named
- Each source system agreed
- A fixed price against that scope
Common questions
What is the best field service management software?
What is the difference between field service and job management software?
Is there free field service management software?
Can engineers use it with no phone signal?
How secure is customer data on an engineer's phone?
Will it connect to Xero or QuickBooks?
Should we buy a product or build our own?
How many engineers do you need before building makes sense?
Who owns the software once it is built?
The parts engineers and customers actually touch: mobile app development, bespoke databases and customer portal software.
Tell us which product nearly worked
Bring the one you tried and the thing it would not do. That is usually the whole specification, and it tells us straight away whether you need a build at all.
- Pontefract, West Yorkshire
- Building for businesses across the UK
- Reply within 1 working day