A service work order is an internal pre-job brief for a visit that has already been booked. Use it to give the assigned technician or crew the confirmed customer, site, scope and preparation context they need before arrival. It is not a booking form, a completed-work record or a payment document.
Copy the template below into a document, spreadsheet or digital job form. Keep the core fields short enough that the person preparing the visit can complete it consistently.
Copyable service work order template
Use: Internal pre-job work order or job brief
Purpose: Prepare an already-booked service visit for technician or crew handoff
| Section | Field | Use | Priority |
|---|---|---|---|
| Job reference | Work order number or job reference | Use one consistent identifier to connect the brief to the visit record. | Required |
| Job reference | Date created | Record when the brief was prepared or updated. | Required |
| Customer | Customer name and preferred contact method | Identify the customer and the best contact route if the technician needs to reach the office or customer. | Required |
| Site | Service address and relevant location details | State the location clearly, including a unit, building, gate or site contact where relevant. | Required |
| Visit | Scheduled date and arrival window | Record the confirmed visit timing. | Required |
| Visit | Priority | Use a simple internal label such as routine, priority or urgent if it helps the team prepare. | Recommended |
| Assignment | Assigned technician or crew | Name the person or team expected to carry out the visit. | Recommended |
| Scope | Confirmed scope or job summary | Write a concise description of the requested work and the agreed visit purpose. | Required |
| Access | Access, parking or arrival instructions | Include practical site context the technician needs before arrival. | Recommended |
| Preparation | Expected materials, equipment or documents | List what may be needed to prepare for the visit. This is an expectation, not a record of items actually used. | Optional |
| Internal notes | Office or team instructions | Add concise internal context, such as a related job reference or a point to confirm on arrival. | Optional |
| Status | Job status | Use a small internal set, such as draft, ready, assigned, in progress or complete. | Required |
Compact version for a solo operator
If one person books, prepares and completes most visits, start with these fields: job reference, customer, service address, scheduled visit, confirmed scope, access details, expected preparation items and status. Add priority only when it changes how you prepare for the visit.
Office-team add-on block
For an office-managed team or multi-technician job, add assigned technician or crew, internal instructions, office-only notes and a related approved-scope reference. These fields help the office transfer context without turning the work order into a long general-purpose form.
What a pre-job work order is for
The work order is the bridge between a booked visit and field execution. It consolidates the practical context that should be ready before the technician arrives: where to go, what the visit is for, when it is scheduled, who is assigned and what preparation may be needed.
Digital work-order records commonly bring together identifiers, job address, technicians, appointments, job summaries and instructions. For example, ServiceTitan documents these as available work-order document components. That supports the structure above, but it does not create a universal industry rule about which fields every business must use.
Keep this document focused on before-arrival preparation. It should state the confirmed scope, not narrate completed work. It may reference an approved scope where useful, but it should not become an estimate, quote or invoice.
Required and optional fields explained
The best template is not the longest one. A field belongs in the pre-job brief only if it helps someone locate, understand, access, assign or prepare for the visit before work begins.
Required fields
- Job reference: prevents confusion when similar jobs or customers exist.
- Customer and site: gives the technician the correct person and location.
- Scheduled visit: records the agreed timing for the prepared job.
- Confirmed scope: makes the purpose of the visit clear.
- Status: shows whether the brief is still being prepared or is ready for handoff.
Recommended fields
- Priority: useful when it affects preparation or internal attention.
- Assigned technician or crew: especially useful when an office hands jobs to field staff.
- Access instructions: helps avoid preventable arrival issues.
- Internal preparation notes: captures concise operational context that should not be lost in messages or separate notes.
Optional fields
- Expected materials or equipment: a planning prompt, not an actual-usage record.
- Related approved-scope reference: useful where the visit follows an approved estimate or quote.
- Office-only notes: useful for teams that need a clear distinction between field-facing and internal context.
Do not put actual labor, final materials, completed-work notes, photos, customer acknowledgement or charges in the core pre-job brief. Those are downstream records. If your work order needs only a scope reference, see the separate estimate, quote and invoice workflow guide for the distinction between commercial documents.
Use the same structure on paper, in a spreadsheet or digitally
The fields can stay the same even when the delivery format changes. Choose the format that makes handoff reliable for your team rather than assuming one format suits every business.
| Format | How to apply the template | Useful control |
|---|---|---|
| Paper | Use a fixed printed layout and ensure one person owns preparation before the form reaches the technician. | Keep a visible job reference and status field. |
| Spreadsheet | Use one row or linked record for each work order, with the full brief stored in consistent columns or a connected sheet. | Use one standard status column and avoid free-form status wording. |
| Digital job record | Create reusable fields or forms that attach to the job where the chosen system supports them. | Separate field-facing instructions from office-only notes where needed. |
Some field service platforms support reusable job-linked forms with text, dropdown, checkbox, date and image fields; FieldPulse describes these capabilities for its reusable job-linked forms. Capabilities vary by system, so use the template structure as a design guide rather than assuming every tool has the same options.
Paper and PDF versions can be practical for a simple handoff, but they are static. ServiceTitan notes that static PDF work orders do not provide real-time updates. If the scope, assignment or access information changes often, make sure the team has one clear current version.
Keep the work order separate from adjacent documents
| Document | Primary role | Where this template fits |
|---|---|---|
| Booking form | Captures the incoming request and initial appointment information. | Use the booking details as an upstream source, then prepare the work order after the visit is booked. See the field service booking template. |
| Pre-job work order | Prepares the confirmed visit and technician handoff. | This article’s template: scope, site context, assignment, access, preparation and status. |
| Field service report | Records completed or paused work, outcomes and next steps during or after the visit. | Move visit evidence and follow-up details to the field service report template. |
| Estimate, quote or invoice | Handles commercial scope confirmation or payment documentation. | Reference approved scope only when needed; do not turn the work order into a pricing or payment document. |
Simple handoff sequence for each visit
- Start with the booked visit. Bring forward the confirmed customer, site and appointment information already captured.
- Create or complete the pre-job work order. Add the job reference, scope, access details, preparation context and current status.
- Confirm assignment and readiness. Record the technician or crew and make sure the brief is ready before arrival.
- Use the work order as the pre-arrival reference. Keep it focused on what the technician needs to know and prepare for.
- Move outcome information downstream. Record work performed, evidence and next steps in the post-visit service report rather than adding them to the pre-job brief.
Template boundary: This is an internal operational template, not legal authorization, a contract, a safety or compliance form, a service report or an invoice. Status labels and field choices are practical internal conventions, not universal standards.
Evidence checked 2026-08-01. Official sources support examples of digital job records and forms, but they do not define a universal “pre-job work order” or “job brief” standard.
Frequently asked questions
What should be included in a service work order template?
For a pre-job service work order, include a job reference, customer name, service address, scheduled visit, confirmed scope, status and relevant access details. Priority, assigned technician or crew, preparation notes and expected materials are useful additions when they help the team prepare before arrival.
What is the difference between a work order and a service report?
A pre-job work order prepares the visit before arrival. A service report records what happened during or after the visit, including completed or paused work and next steps. Keeping them separate reduces duplicate entry and prevents the work order from becoming an incomplete outcome record.
Can I use a service work order template in a spreadsheet?
Yes. Use the same field structure in a spreadsheet, paper form or digital job record. A spreadsheet can give each job one consistent record and status field. Unlike a live digital job system, a static document or PDF will not update in real time when details change.