Work Order Template for Field Crews (the One-Page Version That Actually Gets Filled Out)

A work order is the document that authorizes a specific job, tells the crew what to do, and records what actually happened on site: work performed, materials used, hours spent, and who signed off. It is created before the truck rolls and completed in the field, and it feeds the invoice.

That last part is why the template matters. The work order is where field reality becomes billing reality. Every line the tech does not write down is margin you gave away.

Here is the one-page version, then a filled-in HVAC example, then the honest talk about paper vs digital.

Why one page

Long-form work orders look thorough in the office and die in the truck. A tech finishing his fifth call at 4:30 PM will not flip through three pages of fields. He will skip to the signature line.

A one-page work order gets filled out because it can be filled out in four minutes. Everything on it earns its spot:

• Work order number: the job’s identity across dispatch, the field, and billing. No number, no trail.
• Requested by / authorized by: who asked, and who has authority to approve payment. On commercial and property-management work these are different people, and billing the wrong one costs you 60 days.
• Work requested vs work performed: two separate boxes, on purpose. More on this below.
• Materials table: every part that left the truck.
• Labor table: who was on site and for how long.
• Two sign-offs: crew lead confirms the record is accurate, customer confirms the work happened.
• Billing status: so the office knows at a glance whether this page is done or still owes someone money.

The work order template

Copy this into a doc, drop your logo on top, print a pad of them. The top half is filled out by the office before dispatch; the bottom half by the crew lead on site.

WORK ORDER

Work Order #: __________          Date: __________
Priority:  [ ] Emergency  [ ] Same week  [ ] Scheduled

CUSTOMER / SITE
Customer name: _______________________________
Site address:  _______________________________
Contact on site: _____________  Phone: _________
Requested by:  _______________________________
Authorized by: _______________  Title: _________

WORK REQUESTED (office fills in before dispatch)
________________________________________________
________________________________________________

WORK PERFORMED (tech fills in on site)
________________________________________________
________________________________________________
Additional work found? [ ] No [ ] Yes (describe, get initials):
________________________________  Customer initials: ____

MATERIALS USED
| Qty | Item / part #        | Unit price | Total |
|-----|----------------------|------------|-------|
|     |                      |            |       |
|     |                      |            |       |
|     |                      |            |       |

LABOR
| Tech name      | Time in | Time out | Hours | Rate | Total |
|----------------|---------|----------|-------|------|-------|
|                |         |          |       |      |       |
|                |         |          |       |      |       |

SIGN-OFF
Crew lead signature: _______________  Date: ______
Customer signature:  _______________  Date: ______

BILLING STATUS
[ ] Ready to invoice   [ ] Change order needed
[ ] Warranty / no charge   [ ] Invoiced: #________

Two design decisions worth defending:

The “additional work found” line with customer initials. This is the single highest-value line on the page. When the tech finds a seized blower motor on a call booked for a thermostat swap, this line turns that discovery into an initialed change order on the spot instead of an argument when the invoice lands.

Billing status as checkboxes, not a blank. A blank gets skipped. Checkboxes get checked. The office can sort a stack of these in thirty seconds.

Filled-in example: an HVAC service call

Here is what the page looks like after a real afternoon. Names and numbers are illustrative.

Work Order # 2417. Date: 08/03/2026. Priority: Same week.

Work requested: Tenant reports AC blowing warm air, unit runs but does not cool. Diagnose and repair rooftop package unit.

Work performed: Found failed run capacitor (45/5 MFD) and dirty condenser coil restricting airflow. Replaced capacitor, chemically cleaned condenser coil, verified refrigerant pressures within spec, confirmed 19 degree delta-T at supply register.

Additional work found: Yes. Contactor pitted, recommend replacement within 60 days. Quoted separately, not performed today. Customer initials: DM

Materials used

Labor

Sign-off: Crew lead M. Ortiz, 08/03. Customer D. Marsh (by phone approval, noted), 08/03.

Billing status: Ready to invoice.

Notice what this page just did. It documented a diagnosis, priced the fix, captured an upsell lead (the contactor) with the customer’s initials on the record, and handed billing a complete invoice. Four minutes of writing.

Where the money leaks

We build software for home-services operators, and when a shop shows us their books, the leaks almost always trace back to this document. Three patterns repeat:

The materials table is empty. The capacitor got replaced. It just never got written down, so it never got billed. One unbilled part per truck per day, across a year, is real money leaving in five-dollar and sixty-dollar increments. The tech is not stealing; he is busy, and the form was in the other truck.

“Work performed” says “fixed AC.” Three words where forty belonged. Now the invoice has no story behind the number, the customer calls to ask what they are paying for, and the callback six months later has no service history to check against.

The gap between requested and performed was never initialed. The customer asked for one thing, the crew did more because the job needed it, and nobody captured the approval. That gap is where change orders and disputes live. Every contested invoice we have ever seen an operator fight started in that gap.

If your crews consistently skip fields, the fix is usually not another training meeting. It is a form that matches how the work actually flows, which sometimes means a work order flow built around your jobs rather than a generic pad from the supply house.

Paper vs digital, honestly

Paper is not embarrassing. A two-truck shop running a printed pad of the template above, with the office keying invoices weekly, is running a fine system. Zero subscription, zero training, works without a signal.

Paper dies at dispatch scale. Somewhere around the third truck, the failure modes compound: forms lost between the truck and the office, handwriting nobody can read, invoices going out a week late because the paperwork rode around in a cab, and an office person re-keying every line into the billing system, which is the same work done twice.

The mainstream platforms handle the digital work order natively, and they do it well for standard workflows. Per Jobber’s own feature documentation (2026), its job forms and checklists let techs fill out custom fields, attach photos on site, and email the completed form to the client as a PDF. Housecall Pro’s work order tools (2026) cover custom forms, photo attachments, and job details that sync to the office in real time, with offline viewing for dead zones. ServiceTitan’s mobile app (2026) gives techs job details, photo capture, and estimates in the field, syncing to the cloud when the truck gets signal back. If you are shopping that tier, our HVAC dispatch software guide covers the honest tradeoffs.

When a custom work order flow is worth building

The platforms’ form builders cover most shops. They stop covering you when the work order needs to do things their data model was not built for:

• Photo-driven punch lists. A coatings or install crew that must document surface prep, mid-job, and final state, with photos required per stage before the job can close, not optional attachments.
• Piece-rate tracking. If crews are paid per square foot or per unit installed, the work order is also the payroll record, and no mainstream form builder computes piece-rate pay off form fields.
• Multi-crew, multi-day jobs. One work order, three crews, four days: platform work orders are mostly built for one tech, one visit.
• Requested-vs-performed as a change-order trigger. When the performed box diverges from the requested box past a dollar threshold, the system should generate a change order for signature automatically, not rely on the tech remembering.

We build these flows on top of Jobber, Housecall Pro, and ServiceTitan through their APIs, so the office keeps the CRM they know and the field gets a form that matches the actual work. If your work order needs to do more than the form builder allows, tell us what the page needs to capture and we will tell you whether it is a build or a workaround, usually in one call.

Start with the template above either way. The one-page version, filled out every time, beats the perfect system nobody uses.