Field service management is the way a business plans, sends, tracks and gets paid for work its people carry out at customers' sites, from the first call to the final invoice. Field service management connects the office, the engineers in vans and the customer, so jobs don't stall on retyped details, wasted visits or late invoices.
The usual abbreviation is FSM. One UK guide for small and midsized firms describes it as the coordination of jobs, people, information, and equipment to allow tasks to be efficiently completed away from an organisation's main site, which for most firms means engineers installing, servicing or repairing equipment at customers' sites. It isn't the same as facilities management (FM), which looks after buildings, though FM contractors can use it too.
Each job passes through six stages, and each one leaves a record:
With a few vans, start with the request, completion and invoice rows: one shared diary, job sheets back the same day, invoices raised from the job. Contract and subcontractor work puts more weight on scheduling and review.
Key takeaways
- FSM is how you run jobs from request to payment, with or without software. Done well, it means fewer wasted visits, faster invoicing and evidence when a customer disputes a visit.
- Enter each job once: retyping is where errors start.
- Proof of work protects revenue: photos, signatures and certificates captured on site help settle disputes and speed up invoicing.
- Software helps most when it connects the stages, so map your own process first.
What Does Field Service Management Involve?
In practice, field service management involves six stages: taking the request, scheduling and dispatching an engineer, managing the job on site, tracking assets and parts, completing the job with proof and an invoice, and reviewing performance. Each stage depends on information captured in the one before, so an early gap shows up later as a wasted visit or late invoice.
Managing Customer Requests and Work Orders
Every job starts as a request: a call, an email, a web form or a planned visit. Good field service management captures it once, as a job (some firms call it a work order) linked to the customer, the site and any equipment there, so nobody types the same details again.
Picture a heating customer ringing about a boiler fault. The office opens the customer record and sees the address, the boiler's service history and any access notes, then creates the job from that record with the fault, the priority and the likely parts. If a quote comes first, it'll convert into the job when the customer accepts. For managing agents and multi-site clients, keep a client, site and asset structure so every job lands against the right site and order number.
Scheduling and Dispatching Field Teams
Scheduling decides who does the job and when, and dispatching gets the details to that engineer. The right choice weighs skills and certificates, location and travel time, availability, and whether the van already carries the parts.
Reactive call-outs also have to fit around planned preventative maintenance, from annual boiler services to alarm checks. Generate those visits from each customer's due dates or contract schedule, so a missed visit shows as overdue instead of disappearing. If you run contracts, rank reactive work by their attendance and fix deadlines. Whoever dispatches needs a live view of every engineer to move work quickly.
Once the slot is set, confirm it with the customer and message them when the engineer is on the way. Before you use subcontractors, check their accreditations and insurance. They need the job details and deadlines your own engineers get, and they should return the same times, photos and certificates against the same job, or their work falls outside the record.
Managing Jobs and Communication in the Field
On site, the engineer needs the job details, the site and equipment history, the risk assessment and method statement (RAMS), and a way to report progress without ringing the office. A mobile job sheet does this. Status changes, notes, photos and signatures flow back as the work happens, so the office can tell a customer where their engineer is from the screen.
Job tracking software gives managers that live view of jobs and engineers, and alerts can flag a job running late before the customer has to chase it.
Field engineers often work alone, and the law expects you to manage that risk. HSE describes lone workers as those who work by themselves without close or direct supervision, with engineers among its examples, and employers must manage the risks before anyone works alone. You also must monitor your lone workers and keep in touch with them. Status updates from the job sheet and agreed check-in times make that routine.
Safety paperwork belongs in the same flow as the job. Clare, an HSEQ Manager at a UK construction firm, described on Capterra's BigChange listing how her team designed its own policies, procedures and health and safety worksheets in the system, without needing developers.
Tracking Assets, Parts and Resources
FSM tracks three kinds of resource: the customer equipment you maintain (the boilers, alarms or air conditioning units on each site), the parts you use, and your own vans and tools. Each asset needs a history of visits, faults, parts fitted and certificates, so the next engineer arrives knowing what happened last time.
Record parts against the job they were used on and keep a view of what each van carries. That'll save trips to the merchant and put the parts cost on the right invoice.
Your own kit has rules too. PUWER requires that all work equipment be maintained in an efficient state, in efficient order and in good repair, and that any machinery maintenance log is kept up to date.
Vehicle tracking shows where engineers are and helps route planning, but it's a form of monitoring. The ICO says you must inform workers and passengers of any vehicle monitoring, so tell drivers before you switch it on.
Completing Jobs, Capturing Proof of Work and Invoicing
A job isn't finished until you can prove it was done and you've billed for it. Proof of work, often called proof of service, means timestamped photos, customer signatures, completed job sheets and any certificates, captured on site and stored against both the job and the asset.
Know the retention period for each certificate type you issue. For landlord gas safety checks, for example, HSE tells landlords you have to keep records for at least two years, and those records can be stored electronically if they can be reproduced in hard copy and kept secure.
Future Group, an Essex-based electrical services company, made that move off paper. Its BigChange customer story describes office staff typing up engineers' paper reports before sending them to clients, until job cards with time and date stamped photographs replaced them and fed customer reports, invoices and payroll automatically. By its own account, the company reported an 80% boost in efficiency underpinned by virtually paperless management of mobile operation.
Log any defect on a planned visit against the asset before the engineer leaves, then raise the remedial quote for client approval. Raise the invoice on sign-off, or the day the period closes if the contract bills in arrears, with the client's order number and job evidence attached. Where you agree a payment date, it must usually be within 30 days for public authorities or 60 days for business transactions.
Monitoring Performance and Improving Field Operations
You'll improve operations by reviewing the data each job produces. Useful measures include first-time fix rate (jobs finished on the first visit), response time against what you promised, jobs completed per engineer per day, job cost against the quote, and the gap between completing a job and invoicing it.
Check margin while jobs are running so you can act before an overrun becomes a loss. Regular field service reporting turns those records into decisions: which jobs to price differently, where another engineer would pay for itself and which customers generate repeat call-outs.
How Does Field Service Management Software Support FSM?
Software for field service management is one system that connects every stage of FSM: the customer record, the schedule, the engineer's mobile job sheet, proof of work, invoicing and reporting. Each stage reuses what the previous one captured, so the office and the field work from the same record of every job, customer and site.
If you're VAT-registered, Making Tax Digital means you must now use compatible software to keep your VAT records and file your VAT Returns, and as announced at Budget 2025, the UK will introduce mandatory e-invoicing for all VAT invoices from 2029. That makes field service integrations part of the decision, so check that any system connects to your accounting package, such as Sage or Xero.
When you compare options, look for:
- A mobile app that works with poor signal. Engineers should be able to view their schedule, open job details, complete forms, capture photos and collect signatures without signal, then sync.
- Scheduling that understands your work. Route optimisation should account for traffic, engineer skills and vehicle equipment, and schedule changes should reach the engineer without a phone call.
- Sign-off that triggers certificates and billing. Sign-off files the certificate against the asset and queues the invoice.
- Contracts and planned maintenance. Visits generated from assets and contract schedules, response deadlines per client, and a way to import the asset register you already keep in spreadsheets.
- Time to go live. Ask how long until you're running, and who moves your customer and asset data across.
- Ease of use in the field. Ask whether an engineer can learn the app in a day, and test it with one of yours.
- Room to grow. Ask whether it still fits as you grow from a few vans to a team with subcontractors.
- If you have multi-site clients or subcontractors: client, site and asset structure, per-client reporting, and subcontractor access returning evidence to the same record.
- Reporting you'll actually use. Response and fix times per contract, job cost and first-time fix, by client, site and engineer.
Field Service Management Best Practices
The best field service management practices are simple habits applied to every job: capture work once, schedule on skills and location, finish paperwork at the job, invoice on completion, review the numbers regularly and bring engineers into any change early. Together they keep information moving from request to payment without gaps.
- Map your workflow before you change tools. Write down how a job moves from first call to paid invoice today, then judge any system against that.
- Capture once, use everywhere. The details taken at the first call should feed the schedule, the job sheet, the certificate and the invoice.
- Schedule on skills, location and stock. Sending the engineer with the right certificate and parts is one of the simplest ways to avoid a second visit.
- Finish the paperwork on site. Photos, signatures and certificates captured at the job are stronger evidence than notes you've written up later.
- Automate the routine. Confirmations, reminders, late-job alerts and recurring maintenance visits shouldn't need someone to remember them. Field service automation takes that admin off the office.
- Roll out in stages and bring engineers with you. Begin with jobs, scheduling and mobile job sheets, then add invoicing and reporting. If the app slows engineers down on site, they'll go back to paper. Expect the first weeks to take extra office time while records move across. Trial it with one willing engineer, keep on-site forms short, then run paper alongside for a few weeks and stop accepting paper sheets on a set date.
Is Field Service Management Right for Your Business?
Every business that sends people to customer sites already does field service management, formally or not. The question is whether the way you're doing it today still copes. If several of the signs below sound familiar, your process is costing you time, cash or evidence, and a more structured approach to field service management is worth the effort.
- Job details are typed more than once, by more than one person.
- Only one person really knows the schedule, and holidays cause chaos.
- Job sheets come back days after the work, or not at all.
- Planned visits live in a spreadsheet and slip without anyone noticing.
- A customer disputes a visit and you can't produce photos, times or a signature.
- A new contract, site or type of work is coming that the current setup can't absorb.
Worried it's overkill for your size? A sole trader with a few jobs a week may manage with a diary and accounting software. Once you're coordinating several engineers, reactive and planned work, and customer records, the cost of re-keying and missing evidence grows with every job.
Skilled people are scarce too: in BESA's labour market research among building services employers, 66% report ongoing shortages of skilled installation and maintenance personnel, so every engineer's day needs to count.
Pick one call-out from last week. Write down who took the call, where it was noted, when the job sheet came back and when the invoice went out. The stage where details were retyped or sat longest is your weakest, so fix it first.
For a wider view of what good looks like, read our guide to field service excellence. When you're ready to see the six stages connected in one system, take a look at how BigChange approaches it.
Frequently asked questions
What is the difference between CRM and FSM?
CRM manages your relationship with customers; FSM manages the work you carry out at their sites. CRM holds enquiries, contacts and account history, while FSM covers scheduling, engineers, proof of work and invoicing. The two meet in the customer record: a field service CRM keeps customer details, contact information, job histories and financial documents in one place.
What does field service management software do?
FSM software runs scheduling, dispatch, job records and billing from one system the office and engineers share. The office can track engineers' location in real time and assign jobs to them accordingly, while engineers update jobs, add photos and capture signatures from a phone or tablet. Linked to accounting software, it turns finished jobs into invoices.
What is the difference between job management software and field service management software?
Job management software centres on the job itself: booking it, sending it to an engineer, recording the work and invoicing it. FSM is broader: it covers the coordination of jobs, people, information, and equipment across the business, from dispatch and scheduling to parts, contracts and customer records. The two labels overlap, so compare features rather than names.
What should I look for in field service management software?
Look for an engineer app that works offline, scheduling that weighs skills, location and van stock, and sign-off that files certificates and raises the invoice. Check it will work on your fleet of devices and that data can be transferred between systems, including your accounting package, and that one of your engineers can learn it quickly.
Can field management software work without a constant internet connection?
Yes, if its mobile app is built for offline use. Engineers should be able to view their schedule, open job details, complete forms, capture photos and collect signatures without signal, then sync when coverage returns. Ask each supplier to show this, and test it somewhere with no signal, such as a basement plant room, before you commit.
