←
BACK_TO_BLOG

How a Work Order System Works: One Job From Call to Invoice

Share
X_/_TwitterLinkedInCopy_Link
TL;DR
  • A work order system turns each repair request into one record that moves from triage to dispatch, the site visit and close-out. Each stage adds to that record, so the closed work order holds the whole job.
  • Jobs slip at the handoffs, when the person dispatching doesn't know what the technician needs on the van. Capture the asset and the symptom at intake, so the dispatcher can work out the likely part before the van leaves.
  • Close-out decides whether the system is worth having. A work order closed with the cause, parts and hours recorded becomes the invoice, the job cost and the asset's service history.
  • Buy software when your process matches your trade's usual flow, and build when dispatch or pricing is part of how you win work. Either way, walk one real job through the system before you sign up or start a build.
A paper ticket tape running from an old telephone handset, past a wrench and a small fan motor, into a stack of blue paper record cards, with a bright green strip where it enters the stack.

At 7:40 on a Saturday morning, a restaurant's head chef calls a refrigeration company: the walk-in cooler is reading 9°C and the fish delivery arrives at ten. A work order system is what turns that call into a single record, then carries the record from the person who answered the phone to the technician who fixes the cooler, to the invoice, to the cooler's service history.

Every work order system, from a shared spreadsheet to a full maintenance suite, does this with the same few parts. The easiest way to see them is to follow one job through. The cooler call below is an example we've made up to walk the stages, so the business, times and parts are illustrative.

The Request: How a Work Order Starts

A work order starts as a request: a phone call, an email, a message or a form, from a customer or from your own staff. The system's first job is to turn it into a record before the details get lost.

For the cooler call, the person answering needs five things from the chef:

  • Who and where: the restaurant, the site address, a contact who'll be there.
  • Which asset: the walk-in cooler, ideally matched to a record you already hold, with its make and model.
  • The symptom, in the caller's words: "reading 9°C, compressor running, fan noisy since Thursday."
  • What's at stake: a food delivery at ten.
  • Access: the back door code, the kitchen opens at seven.

The asset line matters more than it looks. If the cooler already has a record, the person on the phone can see it was serviced in August and had its evaporator fan motor replaced last year. That replacement is what tells the dispatcher which part to send.

In a work order process run on calls and a notebook, the request is where the first details vanish. "Fan noisy since Thursday" is exactly the sort of line that never makes it from the phone to the technician.

Triage: Priority, Category and Due Time

Triage gives the request a priority, a category and a time it must be done by. Those three fields decide where it sits in the queue.

The cooler is urgent: stock is at risk within hours. A dripping tap in the same restaurant's staff toilet would be routine and could wait for the next scheduled visit. Keep the levels few, and give each one a response time you've agreed with customers.

Triage is also where the request becomes a work order. A request is someone asking. A work order is your business committing to do the job, with a number, a status and an owner. Some requests never become work orders, such as a second call about the same cooler or a job you don't do.

The U.S. Department of Energy's O&M Best Practices Guide puts "work order generation, prioritization, and tracking by equipment/component" first in its list of typical CMMS functions. Triage is the generation and prioritization part. The equipment part is the asset record from the request.

Dispatch: Matching the Technician, the Time and the Parts

Dispatch assigns the work order to a technician and a time slot, and checks they'll arrive with what the job needs. The parts check is the step that gets skipped.

For the cooler, the dispatcher looks for a technician certified for refrigeration who can reach the restaurant before ten. Then the parts question: given a noisy fan and a warm box, the likely culprit is the evaporator fan motor again, so the van needs one that fits this model.

In a January 2026 Deloitte Digital report on a 2025 survey of 900 field service leaders, 59% said they do not confirm predicted parts are on their trucks. Those leaders work at organisations with 1,000 or more employees and field service teams of 50 or more. The survey didn't cover small firms, but a five-van business runs the same check with fewer people to catch a miss.

A paper work order pinned to a blue board, an empty service van with its rear doors open, and an electric motor left on the floor with a bright green strip across it

A missing part costs a second trip, and for this restaurant a lost morning of stock. The work order is where the dispatcher writes down which part the technician should carry, and where the technician confirms it's on the van before driving off.

On Site: What the Technician Records

On site, the technician works the job and adds their part of the record: arrival time, what they found, what they did, parts used, time spent, photos, and the customer's sign-off. It's also the stage a technician fills in last, standing in a cold kitchen with the next job waiting.

At the restaurant, the technician finds the evaporator fan motor seized, swaps it for the one on the van, checks the defrost cycle, and watches the box drop to 3°C before leaving. On the work order that becomes a cause (seized fan motor), an action (replaced), one part with its serial number, an hour and twenty minutes on site, two photos, and the chef's signature.

Whether that happens in one visit shows up in the first-time fix rate, the share of jobs finished on the first trip. In the same Deloitte survey, the organisations it rated as highly mature reported a first-time fix rate of 73%, against 64% for the least mature.

Where do your jobs slip?

  • REQUEST??
  • TRIAGE??
  • DISPATCH??
  • PARTS??
  • SITE RECORD??
  • CLOSE-OUT??

Walk us through one job from the phone call to the invoice. In one call, we'll scope a first sprint around the handoff that loses the most.

MAP_MY_WORK_ORDERS→

Close-Out: When a Work Order Is Actually Done

A work order is closed when the work is finished, the record is complete, and someone has checked it. Closing it early, or closing it empty, is how a work order system quietly stops being useful.

For the cooler, close-out means the office reviews the technician's notes, confirms the part and hours, and sets the status to complete. If the technician had found a cracked door seal as well, close-out is where a follow-up work order gets created for it, rather than a line in someone's memory.

My take: the close-out screen is the one to design first. A technician finishing a job at 9:45 on a Saturday will fill in what takes thirty seconds and skip the rest, so the fields that feed the invoice and the asset history have to be the quick ones.

What a Closed Work Order Feeds: Invoice, Job Cost and Asset History

The invoice, the job cost and the asset history all come straight off the lines the technician and the office filled in at close-out.

The invoice comes from the hours and parts on the record. The job cost comes from the same lines at your cost price, which is the comparison our post on how job costing software works walks through.

The asset history is the part that pays off later. The DOE guide's checklist for deciding whether you need maintenance software asks: "Are you able to access historical information on the last time a system was serviced, by whom, and for what condition?" With the cooler's record, the answer is yes, and it shows the evaporator fan motor failing twice in fourteen months. That's a reason to offer the restaurant a preventive maintenance visit every quarter.

The same guide, in its 2010 edition, puts the savings of preventive maintenance over a purely reactive approach at an estimated 12% to 18%.

The Parts Every Work Order System Has

Following the cooler job through gives the parts list that every work order system shares, whatever it's built on:

1. Requests: the inbox for calls, emails and forms, before anyone commits to the work. 2. Work orders: one record per job, with a number, status, priority, due time and owner. 3. Assets and sites: what you service and where it is, so every job attaches to a history. 4. People and schedule: technicians, their skills and their time, for dispatch. 5. Parts: what's needed, what's on each van and what was used. 6. The site record: notes, photos, time and sign-off, usually captured on a phone. 7. Status history: who changed what and when, from request to close.

A spreadsheet can hold the first two and part of the third. It struggles with the rest, because they need a phone screen in the field and a record that several people update at once. In Plant Engineering's 2020 Industrial Maintenance Report, a survey of 171 people responsible for plant maintenance, 47% used in-house spreadsheets and schedules to manage it and 46% used clipboards and paper records, while 50% used a CMMS. Respondents could pick more than one, and plenty did. The respondents run industrial plants, a different world from a five-van service firm. Even there, spreadsheets and paper sat next to the software.

Buying or Building a Work Order System

Off-the-shelf work order management software, the kind sold as work order software for small business, suits a business whose jobs look like the trade's usual flow: request, dispatch, fix, invoice. It's quick to start, and you pay per technician as you grow.

A custom work order system earns its cost when your flow is unusual and the difference is commercial. Examples include contract pricing with a priority uplift, dispatch rules that depend on which customer holds which service agreement, or a parts process tied to your own warehouse. Our post on the signs a business has outgrown spreadsheets covers how to tell whether dispatch has reached that point.

If you build, we'd start where we started this post: one real job, walked through as a clickable prototype of every screen it touches, from the call log to the close-out, before anyone writes the dispatch board or the reports. Off-the-shelf is often the right answer, and we'll say so when it is.

Which stage of your last job had the least written down?

FAQs

// QUESTIONS //
Q.

What is the difference between a work order and a purchase order?

A work order authorises a job to be done, such as a repair or an installation. A purchase order authorises buying something from a supplier, and a work order may trigger one when a part has to be ordered.

Q.

What is the difference between a work order system and a CMMS?

A work order system manages jobs from request to close. A CMMS (computerised maintenance management system) includes work orders and adds asset registers, preventive maintenance schedules, parts inventory and maintenance reporting.

Q.

Can one work order cover more than one visit?

Yes. Keep one work order for the job and log each visit against it, so a return trip for a part shows up as a second visit on the same record.

Q.

Should customers be able to raise their own work orders?

Customers can submit requests through a form or portal, which saves a phone call and captures the asset and symptom in their words. A portal works best when it shows the customer each asset you already hold for them, so they pick the cooler from a list.

2-WEEK SPRINTS
//
$2,500 FLAT
//
LIVE IN 90 DAYS
//
THE CODE IS YOURS
//
ZERO LOCK-IN
//
2-WEEK SPRINTS
//
$2,500 FLAT
//
LIVE IN 90 DAYS
//
THE CODE IS YOURS
//
ZERO LOCK-IN
//
2-WEEK SPRINTS
//
$2,500 FLAT
//
LIVE IN 90 DAYS
//
THE CODE IS YOURS
//
ZERO LOCK-IN
//
2-WEEK SPRINTS
//
$2,500 FLAT
//
LIVE IN 90 DAYS
//
THE CODE IS YOURS
//
ZERO LOCK-IN
//

Every job, [closed properly.]

START_PROJECT
→