Home / Resources

Template

Work order template: every field a service job ticket needs, and why each one is there

A work order is the one document that follows a job from the phone call to the invoice. If a field is missing, someone has to chase it later. This template lists the fields, with a copy-ready blank form.

6 min readTemplate

A work order gets touched by at least four people: the CSR who books it, the dispatcher who places it, the tech who does it and the person who bills it. Each of them needs different fields. A template that only serves one of them creates work for the other three.

This template is built backwards from those four people. Copy the blank form below the field tables into your paper ticket, spreadsheet or software. Then use the field table to decide what to keep.

The fields, and who needs them

Header

Field Example Who needs it, and why
Work order number WO-24817 Everyone. One number ties the call, the visit, the parts and the invoice together.
Date created 2026-10-12 Office. Measures how long jobs wait between booking and visit.
Created by Front desk, J. Office. Tells you who to ask about the original call.
Job type Repair, maintenance, install, inspection, return visit Dispatcher and reports. Drives planned duration and skills.
Priority Emergency, same day, routine Dispatcher. Decides which open time it takes.
Related work order WO-24502 Office. Flags a return visit or a callback on earlier work.

Customer and site

Field Example Who needs it, and why
Customer name Dana Ruiz Everyone.
Mobile number (555) 010-0142 Tech and office. Texts and on-the-way calls.
Billing address If different from site Billing.
Service address 418 Elm St, Unit 2 Tech. Read back on the call, unit number included.
Access notes Gate code, side door, park on street Tech. Saves the first ten minutes on site.
Pets, hazards Dog in yard, steep attic stairs Tech. Safety.
Adult on site Yes, Dana, 8 to 12 Tech. Who can approve work.

The job

Field Example Who needs it, and why
Problem as reported Furnace runs but blows cold air since Sunday Tech. In the customer's words, not the CSR's diagnosis.
Equipment Gas furnace, brand, approx. age, location Tech. Decides what parts to carry.
Service history Last visit WO-22110, filter changed Tech. See service history.
Warranty or plan Under labor warranty until 2027-03 Tech and billing. Changes who pays.
Skills or license required Gas, refrigerant, backflow Dispatcher. Only qualified techs get it.
Special parts Ordered, arrives Tuesday Dispatcher. Do not book before the part is in hand.

Schedule

Field Example Who needs it, and why
Assigned tech M. Lee Everyone.
Arrival window promised Tue 8 to 10 Tech and office. The promise you are measured on.
Planned duration 90 minutes Dispatcher. Decides whether the next job on the day fits. See job duration estimate.
On my way, arrived, done 7:52, 8:21, 10:05 Reports. Real drive and real time on site.

Work performed

Field Example Who needs it, and why
Diagnosis Failed flame sensor, dirty Billing and the next tech.
Work done Cleaned and tested flame sensor, ran 3 cycles Customer and the next tech.
Recommendations Replace filter within 30 days Sales follow-up.
Photos Before, after, nameplate Callbacks, warranty, disputes.
Follow-up needed None / return visit / quote Office. Creates the next work order.

Parts and labor

Field Example Who needs it, and why
Parts used Part, quantity, from truck or supplier Billing and restocking.
Labor Hours or flat-rate task code Billing. See time and materials and flat-rate pricing.
Price approved before work Yes, $289, 8:40 Disputes. Proves the customer said yes.
Totals Parts, labor, fees, tax, total Billing.

Sign-off

Field Example Who needs it, and why
Customer signature or approval Signed on tablet Disputes.
Payment Paid by card on site / invoice sent Billing.
Tech signature M. Lee Accountability.

Copy-ready blank form

WORK ORDER #__________        Created: ____/____/____  By: __________
Type: [ ] Repair [ ] Maintenance [ ] Install [ ] Inspection [ ] Return visit
Priority: [ ] Emergency [ ] Same day [ ] Routine    Related WO #: ________

CUSTOMER
Name: ______________________   Mobile: ______________________
Service address: ___________________________________ Unit: ____
Billing address (if different): _________________________________
Access notes: ___________________________________________________
Pets / hazards: _________________________________________________
Adult on site (name, times): ____________________________________

JOB
Problem as reported (customer's words): _________________________
Equipment (type, brand, age, location): _________________________
Last visit / history: ____________   Warranty or plan: __________
Skill or license required: ________   Special parts: ____________

SCHEDULE
Tech: ____________  Window promised: ____ to ____  Planned: ___ min
On my way: _____   Arrived: _____   Done: _____

WORK PERFORMED
Diagnosis: ______________________________________________________
Work done: ______________________________________________________
Recommendations: ________________________________________________
Photos taken: [ ] Before [ ] After [ ] Nameplate
Follow-up: [ ] None [ ] Return visit [ ] Quote   Notes: __________

PARTS AND LABOR
Part / qty / source: ____________________________________________
Labor (hours or task code): _____________________________________
Price approved before work: $________ at ____:____ by __________
Parts $______ Labor $______ Fees $______ Tax $______ TOTAL $______

SIGN-OFF
Customer approval: ______________  Payment: [ ] Paid [ ] Invoiced
Tech: ______________

Why these fields and not others

"Problem as reported" is in the customer's words because CSR shorthand loses detail. "No heat" and "blows cold air" point to different parts.

Planned duration sits next to the window because the two together decide the rest of the day. A window is only as good as the planned durations of the jobs before it. If yours are guesses, every later window on that tech's day is a guess too.

On my way, arrived and done are three fields, not one because together they split the day into drive and time on site. Without them you cannot tell a slow job from a long drive, which is the first question in any job costing review.

Price approved before work has a time stamp because a billing dispute is often less about the price than about whether the customer agreed to it.

How to adapt it

  • Cut by trade. A cleaning or pest control company can drop equipment and diagnosis and add a recurring-service field. An install crew needs multi-day dates and a crew list instead of one tech.
  • Make fields required in the right place. The CSR must fill the customer, site and problem fields before booking. The tech must fill work performed, photos and parts before marking done.
  • Keep the related work order field. It is the only reliable way to count callbacks.
  • Let software fill what it can. Many scheduling apps record timestamps when the tech taps on my way, arrived and done. CrewLink's tech app, for example, records those taps plus notes, photos and parts, and the recorded time on site feeds future bookings. The work order management guide covers the full lifecycle from request to invoice.

What to take away

  • Build the work order for all four people who touch it: CSR, dispatcher, tech and billing.
  • Record the problem in the customer's words, the planned duration, and on my way, arrived and done as separate times.
  • Time-stamp the customer's price approval before work starts.
  • Link return visits to the original work order so callbacks can be counted.

Common questions

What should be included on a work order?

At minimum: a work order number, customer and service address, the problem as reported, the assigned tech and arrival window, the planned duration, the work done, parts and labor, the approved price and the customer's sign-off. The template above adds access notes, equipment, service history and timestamps.

What is the difference between a work order and a service ticket?

Many shops use the terms interchangeably. Where they differ, a service ticket is often the customer's request and a work order is the job record that the tech works from and billing invoices from. See the service ticket glossary entry for more.

Should a work order include pricing?

Yes, at least the price the customer approved before work and the final totals. That record settles most disputes. If you use flat-rate pricing, record the task code as well as the price.

Can I use a spreadsheet as a work order system?

For a very small shop, yes. The problem appears when several people need to update the same job at the same time and when you want to count callbacks or measure time on site. That is usually the point where shops move to software.

See your own day on it

CrewLink offers only the times a crew can actually reach, from where the truck will be. Plug in your trucks, services and city and see how your week would run, then walk through it with your own territory. CrewLink is in early access.

Set up your CrewLinkIndependent contractor? Join CrewConnect

Keep reading

  • Work orderWork order definition for field service. What a work order contains, how to measure work order cycle time, and the fields that prevent return trips.
  • Work order management for field service companiesWork order management explained: the lifecycle, the fields that matter, priority rules, backlog math and closeout standards for field service teams.
  • Service ticketService ticket definition for field service. What a service ticket records, how it differs from a work order, and how to measure ticket backlog and age.
  • Job costingJob costing definition and formula for field service. How to calculate the true cost and margin of each job, including drive time and return visits.