Service Work Order Template
One form for a visit to a customer's site. It carries the service call reference and the SLA response window, the fault in the customer's own words, technician arrival and departure times, the parts fitted and labour booked, the decision about who pays, and the customer's signature taken on site rather than chased afterwards.
- Response and fix due times against the SLA
- Arrival and departure logged per visit
- Every part marked billable, warranty or contract
- Customer signs on site, having seen the charges
Service Work Order
Customer site visit, charges and sign-off
| # | Work performed | Done | Hrs | Notes |
|---|---|---|---|---|
| 1 | Log the call and set response and fix due times | |||
| 2 | Record the fault in the customer's own words | |||
| 3 | Log technician arrival and departure | |||
| 4 | Record fault found, root cause and work carried out | |||
| 5 | List parts fitted, each marked billable, warranty or contract | |||
| 6 | Agree the charges and take the customer's signature |
A preview of the real document. The download is the complete file.
Download the service work order template
Free, editable and yours to rebrand. Pick a format — you'll get all three, so you have the printable version too.
- Word (.docx) for editing the SLA wording and adding your own terms of service.
- Excel (.xlsx) where parts, labour and the charge split total themselves per visit.
- PDF print-ready, for the customer signature taken on site.
What is a service work order?
A service work order is the record of a field service visit to a customer's site, from the call being logged through to the customer signing on site. It carries the customer and account, the SLA response window, the fault as reported, the technician's attendance times, the diagnosis and work carried out, the parts and labour, and the decision about who pays for each of them.
It differs from an internal maintenance work order in who is on the other side of it. An internal job ends with a supervisor's sign-off. A service work order ends with a customer's signature, and that signature is what makes the invoice defensible.
What should a service work order include?
Ten fields decide whether the visit can be billed and whether the SLA can be evidenced. Each one below is a field that gets queried when it is missing.
| Field | What goes in it | Why it earns its place |
|---|---|---|
| Service call reference | The reference the call was logged under | What the customer quotes when they ring back. It should survive across visits for the same fault. |
| Contract or SLA | Which agreement covers this customer | Determines the response window, the rates, and whether the visit is chargeable at all. |
| Response due by | The time you are contractually committed to | An SLA you cannot evidence is an SLA you cannot claim to have met. Record the target and the actual. |
| Reported fault, in the customer's words | The complaint verbatim, before diagnosis | Written up as a diagnosis, the same recurring fault looks like three different faults across three visits. |
| Equipment still in use | Yes, no, or partially | Changes the priority and, on some contracts, the response obligation. It also tells the technician what to expect. |
| Arrival and departure | Per visit, with travel hours separate | The basis for labour charging and the evidence for response time. Reconstructed later, it is an estimate. |
| Fault found and root cause | What was actually wrong, and why | The gap between reported and found is the most useful diagnostic data a service business collects. |
| Parts fitted | Part number, qty, unit price, charge to | Every line needs a charge-to. A blank here is an unbilled part discovered at month end. |
| Charge to | Billable, warranty or contract | The commercial decision. Made on site with the customer present, or made in the office three days later by someone guessing. |
| Customer signature | Name, position, signature, date and time | Taken after the charges have been explained. It is what turns the visit into an invoice that will be paid. |
If you cut the form down, keep the charge-to column. A visit with parts and labour recorded but no charge decision is a visit that has to be reconstructed by someone who was not there. That reconstruction happens at month end, under time pressure, and it consistently resolves in the customer's favour because nobody can prove otherwise.
How do you fill in a service work order?
Fill Part A when the call comes in, Part B on site, and Part C before you leave the customer's premises. Six steps, and the last one is the one that cannot be done later.
Log the call against a contract, not just a customer
The contract determines the response window and the rates. Setting response due and fix due at the point of logging is what makes the SLA measurable rather than a claim made afterwards.
Write the fault in the customer's words first
Record the complaint verbatim, then diagnose separately. If the technician writes 'condenser fan seized' where the customer said 'it's making a noise and cutting out', you have lost the only version that lets you spot the same complaint recurring.
Log arrival and departure as they happen
Time on site and travel time, per visit. These are the numbers that get estimated if they are not written down, and estimates favour whoever is doing the estimating.
Separate fault found from work carried out
What was wrong, why it was wrong, and what you did about it. Root cause is what turns a series of visits into an argument for replacement rather than another repair.
Mark every part and labour line billable, warranty or contract
Do it line by line as you record them. A blank charge-to is not a neutral state — it becomes a decision made later by someone with less information.
Explain the charges, then take the signature on site
Work complete, site left safe, charges explained, customer name, position, signature, date and time. A signature obtained after the visit, by email, three days later, is not the same instrument and does not resolve disputes the same way.
Billable, warranty or contract — deciding who pays
Every part and every labour line on the form needs one of three answers. Getting this right on site is the difference between an invoice that goes out and one that gets written off.
| Billable | Warranty | Contract | |
|---|---|---|---|
| Who pays | The customer, on this invoice | The manufacturer or the installer | Nobody separately — it is covered by the agreement |
| Typical trigger | Work outside any agreement, or customer-caused | Component failure inside the warranty period | Work explicitly listed in the service contract |
| Evidence needed | Signed acceptance of the charges | Serial number, install date, failure description | The contract reference and its scope |
| What goes wrong | Charges not explained, so payment is disputed | Claim submitted late or without the serial number | Chargeable work absorbed as contract work by default |
| Where it is decided | On site, with the customer present | On site, then submitted afterwards | At the point of logging, from the contract |
The default is the expensive one. When the charge decision is left blank, it is almost always resolved later as contract or warranty work, because that is the answer nobody has to justify to the customer. Deciding on site — with the customer looking at the same sheet — is what stops the margin quietly leaving.
Where a document stops working
A form handles one visit. It handles a service operation badly, and the gaps are the ones that cost margin.
SLA is measured after the fact
Response due and actual sit on a sheet in a van. Nothing warns you an hour before a P1 breaches, which is the only moment the information is useful.
Recurring faults stay invisible
The third visit to the same unit looks like a first visit unless somebody remembers. Asset history exists on paper only if every previous sheet is filed against the same asset ID, which they rarely are.
Unbilled work is found at month end
A blank charge-to is discovered during invoicing, weeks later, by someone who cannot ask the technician what happened without interrupting another job.
The signature is stuck in a van
A signed sheet is evidence only once it comes back to the office. Until it does, the invoice waits, and the customer's memory of what was agreed drifts.
Running service work in Facilio
The template is the paper version of a service call. Facilio runs the same call as live state, from intake through to the charge decision, across every job rather than one sheet at a time.
Atom Copilot
Ask the intake and status questions instead of assembling them
What is breaching today, which calls are still unassigned, what has this customer had done this year. On paper each of those is a search through filed sheets. Atom Copilot answers from live data in natural language and can trigger the follow-up action in the same step.
Work Completion Validator
Check the visit is actually complete before it closes
On this form, a missing charge-to or an unrecorded departure time only surfaces at invoicing. Work Completion Validator checks the completion record against what the job required, so the gaps are caught while the technician is still on site rather than at month end.
Ops Performance Intelligence
See SLA and recurrence as a pattern, not a stack of sheets
Response and fix performance by contract, and the same asset appearing for the third time in a quarter. Neither is visible from individual forms. Ops Performance Intelligence surfaces both while there is still time to act on them.
- ~80%end-to-end resolution on service intake at Berkeley
Use the template while one or two engineers are covering a handful of calls a week. A signed sheet per visit is perfectly adequate there. Look at a connected CMMS when SLA breaches are discovered after the fact, or when unbilled parts start surfacing at month end.
Live in production across portfolios including Dunnes, CBRE, Brookfield, Charter Hall and Berkeley.
Frequently asked questions
What is a service work order?
A service work order is the record of a field service visit to a customer's site. It captures the call reference and SLA, the customer and asset, the fault as the customer reported it, the technician's arrival and departure, the diagnosis and work carried out, the parts and labour, the decision about who pays, and the customer's signature.
It differs from an internal maintenance work order mainly in how it ends: with a customer signature and a charge decision rather than a supervisor's sign-off.
What is the difference between a service work order and a maintenance work order?
A maintenance work order is internal: your team, your asset, your cost. A service work order is external: someone else's site, someone else's equipment, and an invoice at the end of it.
That difference adds four things to the form — a contract or SLA, arrival and departure times, a billable-warranty-contract decision on every line, and a customer signature taken on site.
Why record the fault in the customer's own words?
Because the customer's description and the technician's diagnosis are different pieces of information, and both are useful. The complaint is how the customer will describe it when they ring back; the diagnosis is what was actually wrong.
If the two are merged, a recurring fault gets written up differently on each visit and never shows up as recurring — which is exactly the pattern that justifies replacing a unit instead of repairing it a fourth time.
How should billable, warranty and contract work be decided?
Line by line, on site, with the customer present. Every part and every labour line needs one of the three, and the decision should be explained before the signature is taken.
Left blank, the line gets resolved weeks later by someone who was not there, and it is almost always resolved as contract or warranty work because that answer requires no conversation with the customer.
Does the customer have to sign on site?
It is strongly preferable. A signature taken on site, immediately after the charges have been explained, records agreement at the moment both parties saw the same information.
A signature chased afterwards is a different instrument. The work is already done, the charges are already fixed, and the customer is being asked to endorse a summary rather than agree to something in front of them.
How do I evidence an SLA response time?
Record the time the call was logged, the response due time derived from the contract, and the technician's actual arrival time. All three need to be on the same record.
An arrival time reconstructed at the end of the week is an estimate, and an estimate is not evidence if the response window is ever challenged.
What should happen when a return visit is needed?
Record it before leaving: the reason, any parts on order and their expected date, the target date for the return, and the new work order reference if one has been raised.
Also record what the customer was told about limitations or risks. If the equipment is left operational with limitations, that conversation is the one that gets disputed if something fails before the return visit.
In one paragraph
A service work order records a visit to a customer's site from the logged call through to the signature. Log it against a contract so the response window is set at intake rather than argued afterwards, write the fault in the customer's own words before diagnosing it, and record arrival and departure as they happen. Mark every part and labour line billable, warranty or contract while the technician is still there, then explain the charges and take the signature on site. A charge decision left blank does not stay neutral — it resolves later, in the customer's favour, because nobody can prove otherwise.
The template is the floor, not the ceiling
A document records one visit. A connected CMMS runs the service operation: SLAs that warn before they breach, asset history that makes a recurring fault obvious, and charge decisions captured on site rather than reconstructed at month end.
