Work Order Template: 12 Essential Fields and a Filled Service Example

A work order template gives your team one place to record what needs doing, who will do it, and how to confirm the result. It turns a loose request into an assigned job. However, a useful form must also preserve the original scope when the work changes.

Below, you will find twelve essential fields, a copyable blank structure, and a filled service example. This guide also explains how to build a work order template in Excel, manage approvals, and decide when a shared form needs to become a proper job-tracking system.

What a work order should do

A work order tells a person what action to take on a specific site, asset, or service request. It can cover a repair, planned task, installation, or internal maintenance job. Next, it records the work and the result so the office can review the outcome.

IBM’s explanation of work order management places the record within a process of approval, assignment, execution, and review. The form supports that process. It does not replace the person who decides whether a job may proceed.

Keep a work request, quote, work order, and invoice distinct. A request describes a need; a quote proposes scope and price. A work order directs approved work, while an invoice asks for payment under the agreed terms.

For example, a customer may request a leaking valve repair before anyone knows the cause. The office can create a diagnostic work order first. Then it can seek approval for additional work once the technician has evidence.

Twelve essential work order template fields

1. Work order number and version

Give every order a unique number that never changes. Add a revision number when someone changes the scope after issue. Also, keep the date and author of each revision so staff can find the current instruction.

2. Customer and site identity

Record the customer, service address, site contact, and a stable site ID where available. The billing address may differ from the work location. Therefore, give each its own label.

3. Asset or work-area reference

Include an asset ID, room, floor, or work zone. Add a serial number only when it helps identify the item. For instance, “boiler room pump P-04” is clearer than “pump at customer site.”

4. Request and observed problem

State what the requester saw and when it started. Keep that description separate from a confirmed diagnosis. Otherwise, an untested guess may appear to be an established fact.

5. Approved scope and exclusions

Describe the authorized task in plain language. Also, record any limit, such as diagnosis only or a maximum approved amount. List relevant exclusions so the crew knows when to stop and seek a decision.

6. Priority and target date

Use a small set of priority labels with clear meanings. Separate a customer request date from a confirmed appointment. Then record any service target that affects the job.

7. Assigned person and required skills

Name the owner and the crew or technician. Include a reviewer where the job needs a separate acceptance check. In addition, flag required skills so the dispatcher does not assign work based only on availability.

8. Access and task prerequisites

Record entry arrangements, the site contact, and references to required permits or safe work procedures. Avoid turning the form into a substitute for those procedures. The person doing the work still needs the approved instructions for the task.

9. Parts, tools, and materials

List expected items, quantities, and whether the team has them ready. Later, record actual use separately. That distinction helps the office find missing stock and compare the plan with the finished job.

10. Time and cost records

Capture arrival, work, travel, or labor hours under your chosen rules. Keep estimated cost separate from actual cost. Also, distinguish an internal cost from a customer charge.

11. Completion evidence and findings

Record what the technician did, what they found, and which checks they performed. Link photos or readings to the relevant finding. A vague “job done” note rarely helps the next person.

12. Acceptance, follow-up, and billing state

Show who reviewed the outcome and whether more work remains. Separate technical completion from customer acceptance and invoice readiness. Therefore, the office can see a finished repair without assuming every related task has closed.

A blank work order structure you can copy

Use the fields below as a starter form. First, remove anything that does not help your team make or record a decision. Then add trade-specific detail only where your jobs require it.

The table is a structure, not a legal agreement or trade procedure. Tailor approval and acceptance wording to your contract and work process. For another practical format, Jobber’s work order template shows how a service business can present job information.

A filled service example

The following example uses a fictional facilities repair. It shows the level of detail that makes a record useful without adding long paragraphs to every field. In practice, staff could enter the same data through a mobile form.

• Order: WO-1048, revision 1, issued 14 October.
• Site: Example Building, ground-floor plant room.
• Asset: Pump P-04.
• Reported issue: Site contact reports water below the pump after the morning check.
• Scope: Inspect and diagnose the leak. Seek approval before replacement work beyond the agreed diagnostic visit.
• Assignment: Maintenance technician, with site supervisor as reviewer.
• Access: Contact the site supervisor before arrival and follow the site’s access process.
• Findings: Technician identifies leakage at a connection and records a photo against the asset.
• Additional approval: Supervisor authorizes the quoted connection repair at 11:10.
• Work performed: Technician completes the approved repair and records the check result.
• Outcome: Supervisor accepts the repair record; office prepares the invoice.
• Follow-up: Site team to report any recurrence under the existing service process.

Notice that diagnosis and approved repair remain separate steps. Also, the record shows who made the scope decision and when. That helps the office answer questions without relying on the technician’s memory.

How to build a work order template in Excel

If you search for “work order template excel,” start by choosing the workbook’s purpose. A printable job sheet and a tracker for hundreds of jobs need different layouts. You can use both, but they should share the same order ID.

Use one row per order in the tracker

Create columns for order ID, site, asset, scope, owner, status, dates, and follow-up. Keep each field in its own column. Avoid merged cells in the tracker because they make sorting and filtering harder.

Use drop-down lists for status and priority. Also, set a clear date format and use one time zone per defined reporting view. This reduces the risk of staff entering several different labels for the same state.

Keep line items in a separate sheet

One order may use several parts and labor entries. Put those items in a second sheet with the order ID on each row. Then total them for the print view or job review.

Do not hide actual cost inside a free-text note. A separate amount and unit makes the record easier to check. If taxes or customer charges apply, use the rules for your business and location.

Protect formulas and check a sample

Lock calculation cells where appropriate and leave input cells clear. Test one normal job, one cancelled job, and one order with added work. Next, check totals and status filters before the team uses the workbook.

Keep a clean master copy. Give staff a clear route to the current version instead of asking them to find last month’s attachment. Also, back up the tracker and assign one person to manage changes.

Make status changes explicit

A simple sequence might use Requested, Approved, Assigned, In Progress, Awaiting Action, Completed, and Closed. Define what each state means. For example, Completed can mean the technician has finished, while Closed means the office has reviewed the required records.

When a job pauses, record the reason and next owner. “Awaiting parts” should identify which part and who will follow up. Otherwise, the label merely hides work in another queue.

Our guide to work order programs covers tools that help manage these states. Use the template first to define the workflow you need the software to support.

Connect the work order to scheduling and billing

The dispatcher needs skills, location, duration, and access details. The technician needs scope, asset history, and relevant documents. Meanwhile, the office needs approved charges and enough evidence to prepare a correct invoice.

A field service CRM can connect these views around the customer and job. However, do not overwrite an approved quote simply because the technician enters more time. Route extra work through the agreed approval process.

Use a billing-ready check for missing time, parts, or acceptance records. Then keep invoice status separate from job status. A disputed charge should not erase the technical history of the repair.

When a template is no longer enough

A shared workbook can work well for a small queue with a clear owner. It becomes harder to manage when several people edit it at once, crews work offline, or one job creates many related visits. In addition, spreadsheets need careful controls to prevent accidental changes.

Consider a system when duplicate versions, missed assignments, and lost attachments become common. Our article on custom field service software explains how to plan a workflow around your team’s actual needs. Keep the original field definitions as a starting point.

If the gap concerns customer and job links, custom crm development may fit. Start with one real handoff that fails today. Then test the proposed system with staff who create, complete, and review the work.

Check a changed job without losing the original scope

Use a real change during your template trial. Suppose a technician arrives to inspect one asset and finds a second issue nearby. First, record the new finding separately from the approved task.

Next, identify who can approve additional work and how the approval reaches the technician. Keep the original scope, the proposed addition, and the decision time. Do not replace the first instruction with a larger task description that hides the sequence.

Once someone approves the change, issue the current revision and confirm that the crew can see it. Also, update any parts, time, or scheduling needs. The office should use the same revision when it checks the finished job.

Finally, test the opposite outcome: the customer declines the extra work. The order should still show the finding and declined proposal without treating it as an incomplete original repair. This protects the history and gives the office a clear next step.

Start with one real job

Test your work order template from request through closure using a recent service job. Check whether every handoff has the information it needs. Then remove unused fields, clarify approvals, and make the current record easy for the team to find.