A field service workflow is the sequence every job follows: request, qualify, schedule, dispatch, travel, on-site work, closeout, invoice and follow-up. Each stage has an owner and needs specific information from the stage before it, and most delays and errors happen at the handoffs between stages rather than in the work itself.
If you mapped your company's workflow today, you'd probably find it in three places: the software, the dispatcher's head, and a set of habits nobody wrote down. That works until someone is out sick, a new hire starts, or volume doubles in a hot week. Then the unwritten parts break.
This guide lays out the standard nine-stage workflow, what each stage needs, the most common failure at each handoff, and how to measure the whole thing end to end. It's the process view of field service management.
The nine stages
| # | Stage | Owner | Output |
|---|---|---|---|
| 1 | Request | Customer, CSR | A captured request |
| 2 | Qualify | CSR | A schedulable job: scope, address, duration, priority |
| 3 | Schedule | CSR or scheduler | A promised date and arrival window |
| 4 | Dispatch | Dispatcher | A technician assigned for a specific day and order |
| 5 | Travel | Technician | Arrival on site within the window |
| 6 | On-site work | Technician | Diagnosis, approval, repair |
| 7 | Closeout | Technician, office | A complete work order |
| 8 | Invoice and collect | Office, accounting | Payment received |
| 9 | Follow-up | Office | Review, next visit or maintenance agreement |
Some companies combine stages. A small shop may have one person doing 1 through 4. That's fine. The stages still exist, and the information each one needs still has to be there.
Stage by stage
1. Request
Work arrives by phone, web form, email, a property manager's portal or a maintenance renewal. The goal at this stage is simply to capture it. Missed calls are lost jobs, so every channel needs someone, or something, watching it.
Common failure: requests sit in an inbox or voicemail for hours. Measure time from request to first response.
2. Qualify
Turn the request into a job someone can schedule. That means the address and access details, what equipment is involved, what the customer is seeing, the job type, priority and a realistic job duration estimate.
Common failure: booking a "service call" with a default two-hour duration when the job is really a 30-minute check or a four-hour replacement. Every wrong duration breaks the day it lands on.
3. Schedule
Promise a date and an arrival window. This is the most expensive step in the workflow, because the promise fixes the order of the tech's day and how much of it goes to driving. Change it later and you pay in phone calls, overtime or an unhappy customer.
Common failure: offering a time because the calendar shows a gap, without checking whether the tech can get there from the job before. This is the step CrewLink is built for. It checks feasibility before a slot is offered, using travel from where the truck will be, so the only slots offered are ones a crew can physically reach.
4. Dispatch
Assign the tech, set the day's order and manage changes. A long-running job, an emergency, a no-show. The dispatcher keeps the scheduling board true to what's actually happening. See dispatching.
Common failure: dispatch spends the day repairing a board that was infeasible at booking. If your dispatcher is constantly reshuffling, the problem is usually upstream in stage 3.
5. Travel
The tech drives to the job. It looks like dead time, but it's one of the largest blocks of paid time in the day. See windshield time for how to measure it.
Common failure: the customer isn't told when the tech is late. A delay the customer hears about in advance is an inconvenience. One they discover is a complaint. The customer communication guide covers delay notices.
6. On-site work
Diagnose, present options, get approval, do the work. Most of the trade skill lives here, and most companies are already good at it.
Common failure: the wrong part or not enough time. Both turn into return trips. Better truck stock and better duration estimates at stage 2 fix most of this.
7. Closeout
The tech records diagnosis, work done, parts, photos and recommendations. The office checks the record against a standard. The work order management guide has one you can use.
Common failure: closeouts done the next day or the next week, from memory. Details go missing, invoices get disputed and the next tech starts from scratch.
8. Invoice and collect
Turn the closed work order into an invoice and get paid. Residential work is often paid on site. Commercial work is usually billed on terms.
Common failure: a gap of days between closeout and invoice. Every day in that gap is cash you've earned and don't have.
9. Follow-up
Ask for a review, recommend the next visit, offer a maintenance agreement, schedule any follow-up work. This is where one job turns into the next one.
Common failure: it doesn't happen at all, because nobody owns it.
The handoff checklist
Most workflow failures come from information that didn't make it across a handoff. For each one, write down exactly what has to pass:
| Handoff | What must pass |
|---|---|
| Qualify → Schedule | Address, access notes, job type, duration, required skill, priority |
| Schedule → Dispatch | Promised window, customer contact preference, any constraints |
| Dispatch → Tech | Job order for the day, history at this address, parts to bring |
| Tech → Office | Complete closeout, follow-up needed, parts used |
| Office → Accounting | Approved work order with pricing |
| Accounting → Follow-up | Payment status, customer satisfaction flag |
Print it. Put it where the people who do each handoff can see it. When something goes wrong, check which line was missed.
Measure the whole workflow
The best single measure of a workflow is how long it takes from first request to cash in the bank.
Request-to-cash time = time to schedule + wait for visit + time to close out + time to invoice + time to collect
Measure each piece separately, because each one has a different owner and a different fix.
In this example, six days disappear just by closing out and invoicing on the day of the visit. Nothing about the field work changed. Multiply the days saved by your daily revenue and you have the cash that was sitting in your own process.
Track a few more workflow measures in your field service reporting:
- Return-trip rate: jobs that needed more than one visit
- Schedule changes per job: how often a promised time moved
- Same-day closeout rate: work orders closed out before the tech signed off
How to map your own workflow
You don't need special software to map a workflow. You need a wall and an afternoon.
- Pick five recent jobs of different types: an emergency, a routine repair, a maintenance visit, an install, a commercial job.
- Trace each one through the nine stages. Write down who did each step, when, and what information they had.
- Mark the handoffs where something was missing, late or wrong.
- Count the patterns. If three of five jobs had a wrong duration, that's your first fix.
- Write down the fix as a rule for the handoff, and check it again in a month.
The managing field technicians guide covers the daily rhythm that keeps stages 5 through 7 on track.
Workflow differences by job type
Not every job follows the same path in the same way:
- Emergency calls compress stages 2 to 4 into minutes. Keep a short emergency intake script and reserved capacity. See emergency call scheduling.
- Maintenance visits start from a renewal, not a call, and have flexible windows. See preventive maintenance scheduling.
- Installs and projects add a quoting stage between qualify and schedule, and often need multiple crews or visits.
- Commercial work adds approvals, purchase orders and often an SLA that sets response times.
What to take away
- Every job follows nine stages from request to follow-up. Small companies combine stages but can't skip them.
- Most errors happen at handoffs. Write down exactly what has to pass at each one.
- Scheduling is the most expensive stage to get wrong, because it fixes the shape of the day.
- Measure request-to-cash time in pieces. Same-day closeout and invoicing often recover days of cash without changing field work.
- Map your workflow by tracing five real jobs and counting where the information broke.
Common questions
What is a field service workflow?
It's the sequence of steps a job goes through from the customer's first request to payment and follow-up. A standard workflow has nine stages: request, qualify, schedule, dispatch, travel, on-site work, closeout, invoice and follow-up.
How do I improve my field service workflow?
Trace a handful of real jobs through every stage, note where information was missing or late, and fix the most common handoff failure first. Then measure request-to-cash time in pieces so you can see whether the fix worked.
What is the most important stage of the field service process?
Each stage matters, but scheduling has the most downstream impact. The time promised to the customer fixes the technician's day, the arrival window and the drive time. Errors there show up later as late arrivals, overtime and reshuffled boards.
What is request-to-cash time?
It's the total time from a customer's first request to payment in your account. Breaking it into time to schedule, wait for the visit, close out, invoice and collect shows which part of the process holds the most delay.
Does a small company need a formal workflow?
Yes, even if one person does several stages. Writing down what each stage needs makes it easier to hire, cover absences and grow without the process living in one person's memory.