Work order management is the process of creating, scheduling, tracking and closing the records that describe each field job. Done well, every work order moves through a defined set of statuses, carries the information the next person needs, and closes with enough detail to invoice, warranty and learn from.
The work order is the spine of field service management. Scheduling reads its duration. Dispatch reads its priority and skill. The technician reads its notes. Billing reads its parts and labor. Next year's tech reads its history. When a work order is thin, every one of those steps guesses.
This guide covers the lifecycle, the fields that matter, how to prioritize, how to measure your backlog, and what a good closeout looks like.
Work order vs service ticket vs job
The terms get used loosely. A useful distinction:
- A service ticket is the request: the customer's problem as reported.
- A work order is the authorized job: what will be done, by whom, with what.
- A visit is one trip to site. One work order can need several visits.
Keeping work orders and visits separate matters. If a job needs a return trip for parts, you want one work order with two visits, not two unrelated jobs. Otherwise your first-time fix rate and job costing are both wrong.
The work order lifecycle
Every company needs a short, fixed list of statuses that everyone uses the same way. More than about ten and nobody uses them correctly. Fewer than six and you can't see where jobs are stuck.
| Status | Meaning | Who moves it forward |
|---|---|---|
| New | Request captured, not yet qualified | Intake / CSR |
| Ready to schedule | Scope, address, access and duration confirmed | Intake / CSR |
| Scheduled | Date and arrival window promised to the customer | Scheduler |
| Dispatched | Assigned to a specific technician for a specific day | Dispatcher |
| In progress | Tech on site | Technician |
| On hold | Waiting on parts, approval, access or another trade | Dispatcher / office |
| Work complete | Tech finished, closeout submitted | Technician |
| Reviewed | Office checked closeout for completeness | Office / service manager |
| Invoiced | Billing done | Accounting |
| Closed | Paid or otherwise finished | Accounting |
Two rules keep the lifecycle honest:
- Every status has an owner. If nobody owns "On hold," jobs live there forever.
- Every hold has a reason code and a date. "Waiting on parts, ETA Thursday" is actionable. "On hold" is a graveyard.
The fields that actually matter
A work order can have dozens of fields. Most companies need about a dozen filled every time.
At creation - Customer, site address and site access notes (gate codes, pets, parking) - Problem description in the customer's words - Job type, which drives the default duration and required skill - Priority (see below) - Equipment on site, if known (make, model, age)
At scheduling - Job duration estimate - Required skill or certification - Promised arrival window
At closeout - What was found (diagnosis) - What was done - Parts used, and parts still needed - Actual time on site - Photos before and after - Recommendations or follow-up needed - Customer sign-off, if your process uses it
The duration field deserves special attention. It's the single field that most affects whether tomorrow's schedule holds. If every job type defaults to "2 hours," your schedule is fiction. Build defaults from actual on-site time by job type, and review them quarterly.
Prioritizing work orders
Priority shouldn't be "whoever called loudest." A simple two-factor matrix works for most companies:
| Low business impact | High business impact | |
|---|---|---|
| Safety or loss risk | P2: within 24 hours | P1: same day / emergency |
| No safety or loss risk | P4: schedule normally | P3: within 2 to 3 days |
High business impact covers things like a commercial client under an SLA, a maintenance-agreement customer, or a system that's completely down. Safety or loss risk covers gas smells, active leaks, no heat in freezing weather, and similar.
Write the rules down so that intake staff can apply them without asking. Then track how many P1s you actually get. If a third of your work orders are P1, your matrix is a mood, not a rule. For true emergencies, see emergency call scheduling.
Measuring your backlog
Backlog is the work you've accepted but haven't done. Counting open work orders tells you little, because a 30-minute filter change and a two-day replacement both count as one. Measure backlog in hours instead.
Backlog days = open labor hours ÷ daily available labor hours
Where daily available labor hours = technicians × on-site hours per tech per day. On-site hours means paid hours minus drive and other non-wrench time. If you use paid hours, you'll overstate capacity by whatever share of the day goes to driving.
The gap between 4.6 and 6.5 days is the difference between telling customers "early next week" and actually reaching them early next week. If your promised lead times keep slipping, check whether your backlog math counts drive time as capacity. The capacity planning guide goes further.
Watch backlog as a trend. Rising backlog with flat demand means you're losing capacity somewhere: callbacks, holds or slower closeouts.
Holds and return trips
Holds are where work orders go to age. The most common reasons:
- Parts. The tech diagnosed it, but the part isn't on the truck.
- Approval. The customer or property manager needs to sign off on a quote.
- Access. Nobody home, gate locked, tenant not notified.
- Another trade. Electrical needed before HVAC can finish.
Each one creates a return trip, and each return trip is a full truck roll with no new revenue. The cost is easy to underestimate:
Cost of a return trip ≈ (drive time + setup time) × loaded labor rate + vehicle cost per trip
Use the truck roll cost calculator to put your own number on it. Then multiply by how many return trips you had last month. Most companies are surprised.
The fixes sit in other parts of the system: better truck stock for parts holds, approval-before-dispatch for quote holds, and confirmation calls for access holds. See field service inventory management and quoting and estimates.
Closeout standards
A work order isn't done when the tech leaves. It's done when the next person can act on it without a phone call. Set a closeout standard and check it.
A practical standard is that a different technician could pick up this file next year and know what's there, what was done and what to watch. That means:
- Diagnosis in plain words, not "fixed"
- Parts listed with quantities
- Photos of the equipment label and the finished work
- Any recommendations recorded as a separate follow-up, not buried in notes
Have the office review a sample of closeouts every week. Score each one pass or fail against the standard. Share the pass rate with techs. It usually rises fast once people know someone is reading.
Good closeouts also build service history, which makes the next visit faster and helps you spot equipment that keeps failing.
Work order metrics worth tracking
Keep the list short:
| Metric | Formula | What it tells you |
|---|---|---|
| Backlog days | Open labor hours ÷ daily on-site capacity | How far out you really are |
| Time to schedule | Scheduled time − created time | Whether intake is a bottleneck |
| Hold rate | Work orders that entered hold ÷ all work orders | How often jobs can't finish first visit |
| First-time fix rate | Jobs completed in one visit ÷ all jobs | Truck stock, diagnosis and skill matching |
| Closeout pass rate | Closeouts meeting standard ÷ closeouts reviewed | Data quality for billing and history |
| Time to invoice | Invoiced time − work complete time | How fast work turns into cash |
The field service reporting guide covers how to review these on a weekly cadence.
Where scheduling fits
Most work order systems treat scheduling as "put it on a calendar." The work order carries a duration, and the calendar finds a free block. What's missing is the drive. A two-hour job that's forty minutes from the previous one doesn't fit in a two-hour gap. CrewLink handles that one step: it checks feasibility before a slot is offered, with travel computed from where the truck will be (the previous job), not from the shop. Your work orders and billing stay wherever they live now.
What to take away
- A work order is the record every other function reads. Thin work orders force everyone downstream to guess.
- Use a short, fixed set of statuses, give each one an owner, and require a reason and date on every hold.
- Build duration defaults from actual on-site time by job type. It's the field that decides whether tomorrow holds.
- Measure backlog in hours divided by on-site capacity, not ticket count and not paid hours.
- Set a closeout standard a different tech could use next year, and review a sample every week.
Common questions
What is work order management?
Work order management is the process of creating, prioritizing, scheduling, tracking and closing the records that describe field jobs. It covers the statuses a job moves through, the information captured at each step, and the review that makes the record usable for billing and future visits.
What should a field service work order include?
At minimum: customer and site details, access notes, the problem as reported, job type, priority, estimated duration, required skill, arrival window, diagnosis, work performed, parts used, time on site, photos and any follow-up needed.
How do you prioritize work orders?
Use written rules rather than judgment calls. A simple matrix scores each job on safety or loss risk and business impact, producing three or four priority levels with target response times. Track how many jobs land in each level to make sure the rules are being applied.
How do you measure a work order backlog?
Add up the estimated labor hours on all open work orders and divide by the on-site hours your technicians have available per day. The result is backlog in days. Use on-site hours rather than paid hours, or drive time will make your capacity look larger than it is.
What causes work orders to get stuck?
Most stuck work orders are waiting on parts, customer approval, site access or another trade. Give each hold a reason code, an owner and a target date, and review the hold list daily. Fixing the cause usually means changes to truck stock, quoting or confirmation steps.