Field service management (FSM) is the system a company uses to take in service requests, schedule and dispatch technicians, do and document the work, and get paid for it. It covers the people, the process and the software that move a job from the first phone call to a closed, paid work order.
Every company with trucks already does field service management, whether it calls it that or not. A five-truck plumbing shop running on a whiteboard and a notebook has an FSM system. So does a 50-truck HVAC company on a full software suite. The difference is not whether you manage the field. It's how many of the steps are written down, how many depend on one person's memory, and where the expensive mistakes get made.
This guide covers what FSM includes, how the pieces depend on each other, and how companies at 5 to 50 trucks typically put it together. Each section links to a deeper guide.
What field service management actually includes
The short glossary definition of field service management lists the stages. In practice, almost every service company runs the same nine functions. Some are a phone and a spreadsheet. Some are software. All of them exist.
1. Intake
Intake is how work arrives: phone calls, web forms, emails, referrals, maintenance renewals, warranty returns. The job of intake is to turn a vague request ("the AC is making a noise") into a job someone can schedule: who, where, what equipment, how urgent, and roughly how long.
Intake quality decides everything downstream. A job booked with the wrong duration or missing an address detail breaks the schedule before the truck leaves the yard.
2. Scheduling
Scheduling decides which times you can offer and which one the customer gets. It's where the promise is made. That makes it the most expensive decision in the whole system, because the time you promise locks in the arrival window, the order of the technician's day and how much of that day is driving.
3. Dispatch
Dispatch is running the day after it's booked: assigning techs, handling emergencies, moving jobs when something runs long, and keeping the board honest. A good dispatcher is a problem-solver. A dispatcher who spends all day repairing an infeasible board is a symptom. See dispatching for the mechanics.
4. Work orders
The work order is the record of the job: what was requested, what was found, what was done, which parts were used, how long it took, and what's still open. It's the spine that every other function reads from. The work order management guide covers the full lifecycle.
5. Inventory
Inventory is the parts in the warehouse and on the trucks. The cost of getting it wrong isn't the part. It's the second trip. A tech who arrives without a $14 capacitor turns one visit into two. The field service inventory management guide covers truck stock, reorder points and counts.
6. Quoting, invoicing and payments
This is everything that turns work into money: estimates, approvals, invoices, collections. The quoting and estimates guide covers the front end. Pricing sits underneath all of it, and the field service pricing guide shows how to build a rate from your real costs.
7. Reporting
Reporting tells you whether the system is working: jobs per day, first-time fix rate, callback rate, revenue per technician, utilization. Most companies have too many reports and too few decisions. The field service reporting guide covers which numbers to watch and how often.
8. Customer communication
Confirmations, reminders, on-the-way notices, delay warnings, completion summaries and follow-ups. Customers rarely complain about the work. They complain about not knowing when you'll arrive. The customer communication guide has a touchpoint-by-touchpoint playbook.
9. Maintenance contracts
Recurring agreements are the most predictable revenue a service company has, and the most neglected scheduling problem. Hundreds of visits have to fit into a few shoulder-season months. See the preventive maintenance scheduling guide and the guide to service level agreements for commercial work.
How the parts depend on each other
The nine functions aren't independent. They form a chain, and errors travel down it.
| If this goes wrong | This breaks downstream |
|---|---|
| Intake records the wrong duration | The schedule overbooks, the afternoon runs late |
| Scheduling ignores travel | Arrival windows widen, overtime appears, dispatch spends the day repairing |
| Work order notes are thin | The next tech repeats diagnosis, invoices get disputed |
| Truck stock is wrong | Return trips, lower first-time fix, lost capacity |
| Customer isn't told about a delay | Inbound "where's my tech" calls, bad reviews, no-shows |
The pattern is that upstream decisions are cheap to get right and expensive to fix later. A correct job duration costs a dispatcher thirty seconds at intake. A wrong one costs a late arrival, a phone call, a rescheduled job and sometimes a lost customer. The field service workflow guide walks through each handoff and what has to pass across it.
Where the money is made and lost
Every FSM function eventually shows up in one equation. For a technician-day:
Revenue per tech-day = jobs completed per day × average ticket
And for the company per year:
Annual revenue = T × J × A × D, where T is technicians, J is completed jobs per tech per day, A is average ticket and D is working days.
Most FSM decisions move J. Better scheduling, less windshield time, fewer return trips and better truck stock all add completed jobs to a day that already has the same paid hours.
The numbers are made up. The shape isn't. Run it on your own figures with the jobs per day calculator. Half a job per tech per day is usually not hiding in faster wrench work. It's hiding in drive time, return trips and gaps in the board.
How companies at 5 to 50 trucks assemble FSM
There are three common ways to put the system together. None is right for everyone.
Option A: an all-in-one FSM suite
One product handles intake, scheduling, dispatch, work orders, invoicing, payments, customer messaging and reporting. Most of the large field service platforms are built this way.
- Strengths: one customer record, one login, data flows from work order to invoice without re-entry, one vendor to call.
- Trade-offs: you take the suite's approach to every function, including the ones you care most about. Switching later is a big project. Setup and training are real costs.
- Fits when: you're replacing paper or a patchwork, your processes are fairly standard for your trade, and you want one system of record.
Option B: focused tools connected together
Accounting software for invoicing, a dedicated scheduling and dispatch tool, a CRM or phone system for intake, maybe a separate inventory tool.
- Strengths: each tool is chosen for the job it does. You can replace one piece without replacing everything.
- Trade-offs: data has to move between systems. Someone owns those connections, and gaps between tools are where information gets lost.
- Fits when: one function is clearly the bottleneck and the suite version of it isn't good enough for you.
Option C: a suite plus one specialist
The most common pattern in practice. A company runs a suite for records and billing, then adds a specialist tool for the function that drives its economics. For trades where travel is a big share of the day, that function is usually scheduling. That's the gap CrewLink is built for: it builds live travel time into availability, so the only slots offered are ones a crew can physically reach. It's a scheduling and dispatch product, not an FSM suite, so it sits alongside whatever handles your invoicing and records.
Our comparison of field service management software covers the suites honestly, including when a suite is the better fit.
What changes as you grow
| Fleet size | What usually breaks first | What to fix |
|---|---|---|
| 5 to 10 trucks | The owner is the scheduler, dispatcher and estimator | Write down durations, territories and job types. Get scheduling out of one head. |
| 10 to 25 trucks | One dispatcher can't hold the whole board in memory | Standardize work order closeout, measure jobs per day and drive time per tech |
| 25 to 50 trucks | Territories, skills and maintenance volume collide | Capacity planning, zone scheduling, formal reporting cadence |
The guide to scaling a field service business covers each step in more depth.
A 30-day FSM audit
Before buying anything, spend a month finding where your system leaks. This framework works on paper.
- Week 1: trace ten jobs end to end. Pick ten closed jobs. For each, write down when the request came in, when it was scheduled, when the tech arrived, when the work order was closed and when the invoice was paid. Note every handoff where information was missing.
- Week 2: measure the day. For three technicians, log arrival and departure at every job for five days. Total the gaps. That's drive plus slack, and it's usually larger than anyone thinks. The windshield time cost calculator turns it into dollars.
- Week 3: count the return trips. How many jobs needed a second visit, and why? Parts, diagnosis, wrong skill, customer not home? Each cause points to a different function: inventory, intake, dispatch or communication.
- Week 4: rank the leaks. Put a dollar figure on each one, roughly. Fix the largest first, and only then decide what software it needs.
Most companies find their biggest leak is upstream of where they were looking: in intake and scheduling rather than in the field.
The people side
Software doesn't run a field service company. Technicians do. Two guides cover the human side: managing field technicians covers daily rhythm, scorecards and coaching, and field technician retention covers why good techs leave and what keeps them. If you're earlier than that, see how to start a field service business. If your mix is shifting between homeowners and facilities, see commercial vs residential field service.
What to take away
- Field service management is nine functions: intake, scheduling, dispatch, work orders, inventory, quoting and invoicing, reporting, customer communication and maintenance contracts.
- The functions form a chain. Upstream errors in intake and scheduling are cheap to prevent and expensive to fix.
- Most FSM improvements show up as more completed jobs per technician per day, at the same payroll hours.
- Companies at 5 to 50 trucks choose between an all-in-one suite, focused tools or a suite plus one specialist. Pick based on which function drives your economics.
- Audit before you buy: trace real jobs, measure the day, count return trips, then rank the leaks.
Common questions
What is field service management in simple terms?
Field service management is how a company runs work done at customer locations. It covers taking the request, scheduling a time, sending the right technician, recording the work and getting paid. The term also describes software suites that handle those steps in one product.
What are the main components of a field service management system?
Most systems cover intake, scheduling, dispatch, work orders, inventory, quoting and invoicing, reporting, customer communication and maintenance contracts. Not every company needs software for all nine, but every company performs all nine in some form.
Do I need field service management software?
Not always. A small shop can run well on a calendar, a spreadsheet and accounting software. Software starts to pay when scheduling no longer fits in one person's head, when information is lost between steps, or when you can't measure jobs per day and return trips. Usually that happens somewhere between 5 and 15 trucks.
Is an all-in-one FSM suite better than separate tools?
It depends on where your economics are decided. A suite gives one record and less re-entry. Separate tools let you pick the best option for the function that matters most. Many companies run a suite for records and billing and add a specialist for scheduling or another bottleneck.
What is the difference between FSM and field service scheduling?
Scheduling is one part of FSM: deciding which times to offer and who goes where. FSM is the whole system around it. Scheduling is small in scope but decides a large share of the cost, because it fixes arrival windows, drive time and the order of every technician's day.