Field service management is how you organise work carried out at customer sites: booking the job, assigning the right person, recording what happened and getting the work invoiced. It keeps the office, engineer and customer working from consistent job information.
For a heating, electrical or maintenance business, that can mean rearranging a visit when a part has not arrived, getting access to a locked plant room or finding the notes needed to raise an invoice. Those details determine whether the day runs to plan.
This guide explains the process through a practical example, distinguishes it from the software used to support it, and highlights record-keeping considerations for the UK and Ireland. Fieldmotion provides software for these workflows; the principles also apply when you use simpler tools.
An engineer needs more than an address and a time slot. Before they leave, someone needs to confirm the work, check access and make sure the necessary parts and information are available.
After the visit, the office needs enough detail to issue the documents, deal with unfinished work and bill the customer. If that information stays in the engineer’s notebook or memory, the next person has to chase it.
Planned servicing and reactive repairs use many of the same steps, but start differently. A recurring visit begins with an agreed schedule; a breakdown begins with a request that needs assessment. The guide to planned preventative maintenance explains that distinction in more detail.
The handovers become clearer when you follow a single job. Take a commercial customer booking routine maintenance on an air-handling unit.
The example below is hypothetical and concerns job administration, not technical servicing instructions.
The office records the customer, site, asset reference and requested work. It checks whether the visit is covered by a contract, who can approve charges and whether access or a shutdown needs arranging.
If a quote is required, confirm the scope before booking. A request to inspect equipment should not quietly become authorisation to replace components.
Check the engineer has the competence and time for the task. Allow for travel and the site’s access window, and confirm the parts are available before committing to the visit.
The engineer receives the work order, relevant history, site contact and task-specific recording requirements. For recurring work across several locations, a multi-site maintenance schedule helps keep asset references and due dates connected.
The engineer records work completed, relevant readings, materials, limitations and supporting photographs. If another component needs investigation, it becomes a separate finding with a next action.
The booked visit can be complete while that finding remains open. A clear additional-work reporting process helps distinguish an observation from an approved repair.
For example, a useful handover might read: “Unit AHU-02, first-floor plant room: agreed maintenance completed and readings attached. Separate finding: customer reports intermittent noise; cause not established during this visit. Office coordinator to confirm whether a diagnostic visit is authorised.” This is illustrative wording, not a technical assessment.
Before billing, the office checks the work record against the agreed scope and charges. If the parts list or time record is missing, send it back to the person who can supply it. Assign any remaining follow-up to someone by name.
Issue the invoice according to the contract and applicable tax treatment. Keep supporting documents retrievable. The principles in facilities management reporting help make that handover useful to the client as well as your accounts team.
An invoice waiting for a parts list is a useful place to start looking. So is an engineer returning to a site because nobody confirmed access. These are specific problems you can investigate.
Headcount tells you little on its own. A small team handling complicated contracts may have more to coordinate than a larger team doing repeatable work. Look at where information goes missing in your own jobs.
Late invoices: Work is finished, but parts or time records are still missing.
Avoidable return visits: Access, parts or asset details were not confirmed beforehand.
Unclear job status: The office must phone the engineer to understand what remains outstanding.
Lost follow-up: A finding is recorded, but nobody is responsible for reviewing it.
These gaps can also affect margin. The article on field service profit leaks explores the commercial consequences of missed charges, callbacks and duplicated administration.
Field service management software brings scheduling, mobile job information, documents and billing records together. It can save the office from re-entering details and help engineers get the information they need on site.
If you currently copy a customer’s details into a diary, job sheet and invoice, check whether a proposed system can carry them through that whole route. The answer depends on its features, integrations and setup.
Fieldmotion supports scheduling, asset records, mobile forms, photographs and signatures. Engineers can capture information offline, with newly recorded information synchronising when connectivity returns. For urgent findings, use your agreed direct escalation route rather than assuming the office has received an offline update.
Keep supervision and technical review in place. A form can require an answer before submission, but someone still needs to judge whether the recorded work and findings are correct.
Before setting up forms or recurring visits, check which requirements apply to the work and its location. Deal separately with technical records, evidence required by the customer’s contract and tax administration.
The examples below illustrate why those distinctions matter. They are not a complete statement of your trade's obligations or a substitute for competent technical or tax advice.
Identify the forms, results and documents needed for each job type. Confirm who prepares them, who reviews them and how they are retained. Check Great Britain, Northern Ireland and the Republic of Ireland separately where applicable.
Avoid blanket testing assumptions. HSE's PAT guidance explains that, in its Great Britain context, the law does not prescribe annual portable appliance testing. Inspection and testing arrangements depend on the equipment and its use. HSE also distinguishes useful maintenance records from a blanket legal requirement to keep PAT records.
Record why each recurring task is due: a legal requirement, manufacturer instruction, risk-based decision or contract term. Review that basis before copying the same interval to other jobs.
Tax treatment depends on the transaction and parties, not simply the country selected on a job record. Confirm the applicable VAT and any withholding requirements with your accountant or tax adviser.
For example, Revenue explains Relevant Contracts Tax (RCT) as a withholding tax applying to certain payments by principal contractors to subcontractors in construction, forestry and meat processing. It is not a blanket requirement for every Irish service invoice.
For cross-border work, confirm what your job system records, what your accounting package handles and what remains a separate filing task. Currency support alone does not establish the correct tax treatment.
You will come across all three terms when looking at software. Their features overlap, so check the work a system handles as well as the category it sits in.
Job management commonly describes the job lifecycle from quote to invoice. Field service management places additional emphasis on coordinating people working at customer sites. The guide to job management software covers that shared ground.
CAFM, or computer-aided facilities management, typically takes a building or estate perspective. A facilities manager may use it to coordinate assets, maintenance and contractors, while your field service system manages your team's delivery. The CAFM explainer explores the overlap.
If a client uses CAFM, agree how your records will fit with theirs. Establish where instructions are held, where your team submits evidence and who updates the job status. Otherwise, the two systems can show different versions of what remains outstanding.
Choose a recent job that was slow to invoice or needed an avoidable return visit. Follow its messages, notes and records to find where the delay began.
Map the actual route. Include messages, paper notes and spreadsheets, not only the formal procedure.
Mark the gaps. Identify waiting time, repeated entry and missing information.
Agree the handover. Specify the information, responsible person and next action.
Check subsequent jobs. Review whether the same gap still occurs before adding more process.
Choose a measure linked to the problem. For delayed billing, track elapsed days between job completion and invoice issue for jobs billed individually on completion. Review contract-billed work separately, and record disputes or missing purchase orders so the figures do not imply every delay has the same cause.
Take that job to a software demonstration. Ask the presenter to change the booking, record a visit offline and pass it to the office for billing. Check how each step works, including what the team must still do manually.
Field service management is how you organise work performed at customer sites. It connects booking, engineer assignment, site information, work records and invoicing so the office and field team can see what needs to happen next.
Not necessarily. A simple process can work for a small, predictable workload. Consider software when missing information, repeated entry or coordination problems create a measurable burden. Judge the workflow and complexity rather than using engineer headcount as a purchasing rule.
No. Scheduling determines who attends and when. Field service management also covers preparation, customer communication, on-site capture, follow-up and billing. A full diary can still leave incomplete records or unresolved work, so review the whole job lifecycle.
No. A general job record does not replace documentation required for a particular activity. Software can support completing and storing the appropriate documents, but your business must confirm the requirements, competence and review arrangements for the work and jurisdiction.
No. A signature means what the accompanying wording and agreement establish. An attendance acknowledgement should not be treated as approval for extra charges or proof that every defect is resolved. State clearly what the customer is signing and record separate authorisations where needed.