Work Order Template: Every Field, Every Type, and When to Use Each - eWorkOrders CMMS: Maintenance Management Software

Work Order Template: Every Field, Every Type, and When to Use Each

Reference Guide Updated March 2026 · 12 min read

Work Order Template: Every Field, Every Type, and When to Use Each

A work order template is only as useful as the fields it captures — and most templates used in the field are missing the fields that make maintenance data actionable. A form that collects what was requested but not what was found, what parts were used, or how long it took creates a paper trail without a knowledge trail. This guide covers every required field in a complete work order template, the seven template types maintenance operations use, what compliance-sensitive industries need in their templates, and the difference between a static Excel template and a CMMS digital template that generates, assigns, and tracks work automatically.

44%+
of FM teams say WO status tracking is their most time-consuming task
JLL Technologies (2024)
326 hrs
average annual unplanned downtime — what incomplete templates and deferred PMs cost
Siemens (2024)
25–35%
technician wrench time in average operations — most time lost to admin, not maintenance
Industry research
3–5×
reactive vs. planned maintenance cost — what undocumented, unscheduled work leads to
U.S. Dept. of Energy

The Required Fields: What Every Work Order Template Must Capture

A complete work order template is organized around three parties — the person requesting the work, the person doing the work, and the asset being worked on — plus the transaction that connects them: what was requested, what was found, what was done, and what it cost. Miss any of those four, and the template creates a record without creating useful data.

Section 1 — Request Information
Work Order Number
Required. A unique, sequential identifier assigned at creation. The WO number is the primary key that links every downstream record — parts used, labor hours, findings, costs — to this specific job. Without it, maintenance history cannot be searched, reported, or audited. In CMMS, this generates automatically; on paper, it requires a numbering system (e.g., WO-2026-0001).
Request Date & Time
Required. When the request was submitted. Used to calculate response time and to establish the timeline for compliance documentation. For emergency work orders, timestamp precision matters — MTTR is measured from failure detection, not from technician dispatch.
Requester Name & Contact
Required. Who submitted the request and how to reach them. Needed for follow-up questions, status updates, and confirmation of completion. For facilities with tenant-submitted requests, this field also tracks requester accountability — who is generating the most requests, and for which areas.
Work Description
Required. What is the issue or task? The requester describes what they observed; the technician later documents what they found and what they did. These are two separate fields — the request description tells you what was reported; the completion notes tell you what was real. Conflating them produces records that can’t be analyzed for recurring failure modes.
Work Order Type
Required. Corrective, preventive maintenance, emergency, inspection, service request, changeover, or project. Type determines the template variant used, the priority default, the required fields, and which KPI bucket the closed work order feeds (planned vs. reactive, PM compliance, emergency rate).
Section 2 — Asset & Location
Asset ID
Required. The unique identifier that links this work order to the asset’s maintenance history in the CMMS or asset registry. This is the most underused required field in paper templates — requesters often describe equipment colloquially (“the big compressor in Building 3”) rather than by ID, making the record unsearchable. In CMMS, asset QR code scanning populates this automatically at the equipment.
Asset Name & Description
Required. Equipment name, make, model, and serial number. The serial number is particularly important for warranty documentation — a repair performed on the wrong asset’s record is invisible during a warranty claim dispute.
Location
Required. Site, building, floor, room, and sub-location. For mobile technicians, this is how they find the equipment. For multi-site operations, location is required for site-level filtering in reports. “Building A” is not a useful location; “Building A / Floor 2 / Mechanical Room 2A / AHU-07” is.
Equipment Criticality
Recommended. A-class (production-critical or safety-critical), B-class (important, has redundancy), or C-class (non-critical). Criticality populates automatically in CMMS from the asset record. On paper templates, it requires a lookup. This field drives priority assignment — a C-class asset with a failure report shouldn’t receive the same urgency as an A-class asset with the same issue.
Section 3 — Scheduling & Assignment
Priority Level
Required. The most common four-tier system: Emergency (immediate), High (same shift), Medium (within 48 hours), Low (scheduled). Some operations use a five-tier system adding Critical for life-safety issues. Priority must be defined consistently — ambiguous labels like “ASAP” or “when you get a chance” produce scheduling chaos. In CMMS, priority defaults based on WO type and asset criticality, with manual override.
Assigned Technician
Required. Named person or skill category responsible for execution. Unassigned work orders are the primary cause of backlog — they sit in “open” status indefinitely with no one accountable. For compliance-sensitive work (electrical, high-voltage, confined space), the assigned technician must hold the required certification. CMMS skill matching prevents uncertified assignment.
Scheduled Date / Due Date
Required. When the work is expected to be completed. Without a due date, completion rate KPIs cannot be calculated, overdue alerts cannot fire, and backlog aging cannot be measured. For PM work orders, the due date is generated from the PM schedule trigger.
Estimated Labor Hours
Recommended. Expected time to complete. Used for workload planning — if this week’s PM schedule requires 47 hours and the team has 40 hours available, something needs to be rescheduled before the week starts, not after three PMs are deferred.
Section 4 — Completion & Documentation
Completion Date & Time
Required. When the work was finished. With the request timestamp, this calculates response time and MTTR — two of the most actionable maintenance KPIs. In CMMS, this is captured automatically when the technician closes the work order on mobile.
Work Performed / Findings
Required. What the technician found and what they did. Not what was requested — what was actually discovered and how it was addressed. “Replaced belt” is a record. “Belt at 40% wear, replaced, also found bearing temp elevated — logged corrective WO #847” is a maintenance history. Findings that generate follow-up work orders are the mechanism by which proactive maintenance programs catch failures before they become breakdowns.
Parts Used
Required. Part number, description, and quantity consumed. This field serves three functions: it charges parts cost to the asset and work order, it deducts from inventory, and it creates the parts consumption history that drives reorder points and min/max level optimization. Parts used without part numbers are untrackable by inventory and uncountable by asset.
Actual Labor Hours
Required. Hours charged to this work order. With estimated hours, this calculates estimation accuracy — PMs that consistently take twice the estimated hours need their estimates recalibrated. Total labor hours across all work orders per asset reveals the assets consuming disproportionate technician time.
Total Work Order Cost
Required. Labor cost plus parts cost plus contractor cost (if applicable). Cumulative work order costs per asset is the primary input for repair-or-replace decisions — when a single asset’s annual maintenance cost exceeds a defined percentage of replacement value, the economic case for replacement is established.
Technician Signature & Date
Required. Confirmation that the work was performed, by whom, and when. For compliance-sensitive industries, the signature is the audit evidence. In CMMS, digital signatures are captured with automatic timestamps on mobile at point of completion — no paper form required, no after-the-fact reconstruction.
Supervisor Review & Approval
Recommended. Management verification that the work was completed satisfactorily before the record is closed. The review step is where incomplete or inaccurate work order documentation is caught — a work order closed without a findings description or with parts missing can be returned for completion before it becomes a permanent record.

The 7 Work Order Template Types

The same template structure doesn’t work for all work. A preventive maintenance work order needs a checklist and measurement fields; an emergency work order needs a dispatch timestamp and MTTR field; a service request needs an approval gate before it becomes a work order at all. Template types exist to ensure each category of work captures the right data for that work’s specific purpose.

🔧

General / Corrective Work Order

The standard template for repairs, fixes, and unscheduled maintenance tasks. Used when something needs to be corrected — a fault identified during inspection, a reported malfunction, or a degraded component that hasn’t failed yet. Core fields: all Section 1–4 fields above. Additional: failure code (for root cause analysis), follow-up work order generated (yes/no), root cause category.

Best for: reactive repairs, corrective maintenance, and any unscheduled task not driven by a PM schedule
📅

Preventive Maintenance Work Order

Generated automatically by the PM schedule on a time or meter trigger. Contains the PM checklist specific to this asset and task — each item must be marked completed or flagged as finding before the work order can close. Additional fields: PM interval trigger (time-based or meter-based), last completed date, next due date, checklist line items with pass/fail, measurement fields (temps, pressures, amp draw, vibration readings), PM compliance timestamp.

Best for: scheduled recurring maintenance — filters, lubrication, inspections, calibration, safety checks
🚨

Emergency / Breakdown Work Order

Triggered by an unplanned equipment failure requiring immediate response. Speed of creation matters — every minute between failure and work order creation is a minute of untracked downtime. Additional required fields: failure detection timestamp (separate from WO creation time), dispatch time, arrival time, equipment-down-to-up timeline, root cause, production impact, and whether a PM deferral contributed to the failure. This template feeds MTTR, emergency work order rate, and the data that optimizes PM intervals.

Best for: unplanned breakdowns, safety incidents, utility failures, equipment failure mid-production
🔍

Inspection Work Order

A structured condition assessment with a defined checklist. Unlike a PM, the primary purpose is observation rather than action — but findings generate corrective work orders. Additional fields: inspection type (visual, thermographic, vibration, oil sample, etc.), condition rating per item (good / monitor / action required), corrective WO numbers generated from findings, inspector certification. Compliance-sensitive industries require inspection work orders as proof of a functioning maintenance program.

Best for: regulatory inspections, pre-overhaul assessments, new-asset baseline assessments
📬

Service Request Template

Submitted by non-maintenance staff — building occupants, production operators, facility tenants. The service request template collects the minimum information needed for maintenance to triage and assign the request: location, issue description, preferred contact, and urgency. Critically, the service request is NOT yet a work order — it goes to a manager review queue first. Approved requests become work orders; duplicates, invalid requests, and out-of-scope items are rejected without cluttering the work order queue.

Best for: tenant-submitted requests, operator maintenance reports, general facility issues
⚙️

Changeover / Setup Work Order

Equipment reconfiguration between production runs, product specifications, or seasonal operation modes. Often overlooked in maintenance tracking because changeovers feel like operations rather than maintenance — but they consume technician time, require parts or tooling, produce compliance documentation, and directly affect OEE availability scores. Additional fields: from-configuration, to-configuration, changeover duration, tooling used, verification checklist, sign-off by both maintenance and production.

Best for: manufacturing line changeovers, seasonal HVAC switchovers, equipment reconfigurations
📋

Project Work Order

Multi-task, multi-technician efforts that don’t fit the single-event model — a major overhaul, a capital installation, a facility retrofit. Project work orders have subtasks (each with their own assigned technician, due date, and completion requirements), milestone tracking, and a budget that spans multiple resource categories. Additional fields: project code, phase/milestone, subtask list with individual assignments and statuses, total budget vs. actual spend, project manager approval at each milestone.

Best for: major overhauls, capital installations, multi-week planned shutdowns, facility retrofits

Compliance-Required Fields by Industry

For regulated industries, work order templates are not just operational tools — they are the documentary evidence an auditor inspects. Missing a required field isn’t a documentation gap; it’s a compliance failure. CMMS systems can require these fields before a work order closes, making compliance automatic rather than dependent on every technician remembering every requirement.

Industry / Standard
Applies To
Required template fields
OSHA 1910 Subpart S / 1910.147
General industry
Lockout/tagout procedure reference, technician certification verification, permit number (if required), equipment isolation confirmation, electrical hazard category, completion verification by qualified person
ISO 9001:2015 (Clause 7.1.3)
All manufacturers
Equipment calibration status at time of maintenance, documented completion by competent person (name + qualification), calibration record number for measurement tools used, next calibration due date
FDA 21 CFR Part 11 / cGMP
Pharma / med devices
Electronic signature with timestamp (immutable), audit trail showing every field change with who/when, equipment qualification status (IQ/OQ/PQ), batch record cross-reference, system validation documentation reference
FDA FSMA / HACCP
Food and beverage
Food contact zone clearance (yes/no), sanitation completion before return-to-service, lubricant type (food-grade confirmation), foreign material prevention checklist, qualified person sign-off specific to FSMA preventive controls
Joint Commission / DNV
Healthcare
Documented PM interval source (ASHE/AAHE, manufacturer recommendation, or risk-based), completion within compliance window, safety risk assessment, life safety system documentation, qualified person certification
AS9100 / AS9110
Aerospace / defense
Equipment configuration at time of maintenance, part number and serial number traceability, work authorization (job card or traveler reference), first article inspection (if applicable), return-to-service authorization
NFPA 25 / NFPA 10
All facilities
Inspector certification number, inspection date within required window, pass/fail by system component, deficiency correction tracking, authority having jurisdiction (AHJ) notification if required, testing method and results
CMMS

In eWorkOrders, compliance-required fields can be configured as mandatory before closure — the work order literally cannot be closed without the LOTO reference number, the electronic signature, or the food contact zone clearance. This makes compliance documentation automatic rather than reliant on every technician remembering every regulatory requirement for every work order type.

Paper vs. Excel vs. CMMS Work Order Templates

Every maintenance operation uses one of these three template formats. Each has a natural limit — the size and complexity at which it stops working reliably. Understanding where those limits are is the basis for a rational decision about when to change systems.

Capability
Paper / Excel
CMMS Digital Template
PM auto-generation
Manual — someone must remember to create the PM work order, fill in the template, and assign it
Automatic — PM triggers generate work orders from the template on the configured schedule, assigned and delivered without intervention
Mobile access
None native — paper requires return to filing location; Excel requires laptop or desktop with shared drive access
Native iOS/Android — technician receives, completes, and closes work orders from the equipment without returning to a desk
Required field enforcement
None — blank fields stay blank; no mechanism to prevent incomplete records from being filed
Configurable — required fields must be completed before closure; compliance fields enforced automatically
Asset history linkage
Manual — finding past work orders for a specific asset requires searching through files by asset name or date
Automatic — every closed work order attaches to the asset record; full history visible instantly on any new work order for that asset
KPI calculation
Manual formula application to raw data — MTTR, completion rate, EMG%, and backlog age require spreadsheet analysis
Automatic — all KPIs calculated from closed work order data and displayed on live dashboards without manual compilation
Inventory integration
None — parts used on work orders require separate inventory deduction; mismatches are common
Automatic — parts selected from inventory on work order close deduct from stock automatically; reorder alerts fire when minimums are reached
Compliance signatures
Wet signatures on paper, or honor system on Excel — easily challenged as incomplete or after-the-fact
Digital signatures with automatic timestamps — immutable, audit-defensible records meeting FDA 21 CFR Part 11 and ISO requirements
Knowledge retention
Leaves when the person leaves — work order history tied to whoever managed the files and folders
Permanent — all work order history stays in the system regardless of staff changes; searchable by any authorized user
When to upgrade from Excel to CMMS

Excel templates work reasonably well up to approximately 20–30 assets and one dedicated maintenance person. At that scale, the overhead of manual PM tracking, status updates, and report compilation is manageable. Beyond that threshold, the overhead grows faster than the asset base — 50 assets with two technicians on two shifts produce more work order volume and more tracking burden than a single spreadsheet can handle reliably. The clearest signal to switch: if someone’s primary job function includes maintaining the maintenance spreadsheet, the spreadsheet has become the problem.

CMMS Work Order Templates in eWorkOrders

In eWorkOrders, a work order template is a pre-configured record that defines all the fields, default values, checklist items, assigned technician, and required parts for a specific type of work on a specific asset. When a PM schedule trigger fires or a work order is manually created, the system populates the template automatically — the technician receives a complete work package, not a blank form.

⚙️

Configure once, generate automatically

Build the PM template for an asset once — define the checklist, the interval, the assigned technician or skill category, the estimated labor hours, and the required parts. Every subsequent PM on that asset auto-generates from that template on the configured schedule. No manual scheduling. No missed PMs because someone was on vacation.

📋

Checklists embedded in every work order

The PM checklist is part of the template — it auto-populates every generated work order. Technicians complete each item, enter measurements into structured fields, and flag findings. Any finding can generate a corrective work order directly from the checklist item. Nothing gets lost between the inspection and the follow-up.

📦

Parts auto-reserved from inventory

Template-defined parts are reserved from inventory when the work order generates. If stock is below the required quantity, a procurement alert fires before the PM date — not after the technician arrives to find empty shelves. The PM doesn’t get deferred because of a missing filter.

🔒

Required fields enforced before closure

Configure any field as required for closure. Compliance-critical fields — LOTO reference, electronic signature, food contact clearance, calibration confirmation — cannot be bypassed. The work order cannot be marked complete without them. This turns compliance from a training problem into a system constraint.

📱

Delivered to mobile — completed at the equipment

Technicians receive work orders on iOS or Android. They complete the template fields, mark checklist items, record measurements, log parts, photograph findings, and sign off — all from the equipment location. Status updates are real-time. The manager’s dashboard reflects completions the moment they happen.

📈

Closed work orders build the asset history

Every closed work order becomes a permanent record on the asset — labor hours, parts used, findings, measurements, cost. After 12–18 months, this dataset reveals which assets consume the most maintenance resources, which failure modes recur, and whether PM intervals are right-sized. Template data compounds in value over time.

The 5 Most Common Work Order Template Mistakes

1

No asset ID field — or it’s optional

The asset ID is the primary key that makes maintenance history searchable. A work order without an asset ID creates a record that can be filed but not found. Making it optional guarantees that a significant percentage of work orders will be submitted without it — especially service requests from non-maintenance staff who don’t know the asset ID. In CMMS, QR code scanning makes it the easiest field to complete; on paper, it requires deliberate enforcement.

2

Request description and completion notes in the same field

What was requested and what was found are different data. “Fixed the pump” tells you nothing about what failed, what was replaced, or whether the root cause was addressed. Separate fields for (a) the issue reported and (b) the work performed and findings are required to produce maintenance histories that can be analyzed for recurring failure modes and optimized PM intervals.

3

No parts field — or parts recorded without part numbers

Parts recorded as “filter” or “belt” without part numbers cannot be linked to inventory, cannot be used to calculate accurate cost per asset, and cannot drive reorder automation. The parts field in a work order template needs: part number, description, quantity, and unit cost. Without part numbers, the parts record is human-readable documentation — not machine-readable data.

4

One template for all work order types

A single generic template creates one of two problems: it includes so many fields that simple requests feel like paperwork, discouraging compliance; or it omits fields required for specific work types, leaving compliance-critical records incomplete. PM work orders need checklists. Emergency work orders need dispatch timestamps. Inspection work orders need condition ratings. One template for everything serves none of them well.

5

No closure review step

A work order that goes directly from “completed by technician” to “closed” without a supervisor review step allows incomplete records to become permanent history. The review step is where blank fields are flagged, implausible entries are questioned, and follow-up work orders are created for findings that weren’t captured. It adds one step and produces dramatically better records — which, 18 months later, is the maintenance program’s institutional knowledge.

Frequently Asked Questions

What fields does a work order template need?
Every work order template requires: WO number (unique), request date/time, requester name and contact, asset ID and location, work description, work order type, priority level, assigned technician, due date, completion date/time, work performed and findings, parts used with part numbers and quantities, actual labor hours, total cost, and technician signature with timestamp. The three fields most commonly missing that most undermine data quality are: asset ID (makes history searchable), findings/work performed (separate from the request description), and parts with part numbers (connects to inventory).
What are the different types of work order templates?
Seven main types: (1) General/corrective — standard repair or fix; (2) Preventive maintenance — recurring scheduled work with asset-specific checklist; (3) Emergency/breakdown — immediate response with MTTR tracking; (4) Inspection — condition assessment that may generate a corrective WO; (5) Service request — submitted by non-maintenance staff, requires approval before becoming a work order; (6) Changeover/setup — equipment reconfiguration; (7) Project work order — multi-task effort with subtask tracking. Each type needs different required fields and different completion documentation.
What is the difference between a work order template and a work order?
A template defines the structure — all the fields, default values, required items, and checklist for a type of work. A work order is a specific instance of that template, populated with actual data for a particular job on a particular asset at a particular time. In CMMS, PM templates automatically generate work orders on schedule, pre-filling the checklist, assigned technician, and parts list. The template is the blueprint; the work order is the record of one execution of that blueprint.
Should I use paper, Excel, or CMMS work order templates?
Paper works up to about 10–15 assets with infrequent maintenance. Excel works for slightly larger operations but lacks mobile access, PM auto-generation, version control, and required-field enforcement. CMMS digital templates add all of those capabilities and produce asset history automatically. The practical threshold: around 20–30 assets or two-plus technicians, the overhead of manual template management exceeds the effort to implement CMMS. If someone’s primary job is maintaining the maintenance spreadsheet, the spreadsheet has become the problem.
What compliance fields does a work order template need?
It depends on your industry. OSHA 1910 requires LOTO documentation and technician certification. ISO 9001 requires calibration status and qualified completion sign-off. FDA 21 CFR Part 11 requires immutable electronic signatures with timestamps and full audit trails. FSMA requires food contact zone clearance and food-grade material documentation. Joint Commission requires PM interval documentation and completion within defined windows. AS9100 requires configuration traceability and return-to-service authorization. CMMS systems can require all of these fields before a work order closes.
How do CMMS work order templates differ from Excel templates?
Excel templates are static documents — someone fills them in and files them. CMMS templates are active — they auto-generate PM work orders on schedule, enforce required fields before closure, link every closed record to the asset’s permanent history, calculate KPIs from closed records, deliver work orders to technicians on mobile at the equipment, and integrate with inventory to reserve parts automatically. The fundamental difference: Excel templates document what happened; CMMS templates drive what happens next.

CMMS Work Order Templates That Generate, Assign, and Track Automatically

Configure your work order templates once — eWorkOrders generates PM work orders on schedule, enforces required fields, delivers to technicians on mobile, and builds the asset history that makes your maintenance program smarter over time. 4.9 stars on Capterra. 30+ years serving maintenance teams. Setup in 24 hours.

Book a Free 90-Min Demo Work Order Guide →

Related Resources

Pillar

Work Order Management Guide

The complete work order guide — lifecycle, types, priority, KPIs, and how CMMS automates the full program.

Read the guide →

Cluster

Work Order Tracking

Status workflow design, escalation rules, and real-time visibility — how templates produce trackable records.

Read the guide →

Cluster

PM Checklist Templates

The checklist items that belong inside each PM work order template — organized by equipment type across 7 categories.

Browse templates →

Cluster

Free Excel Templates

Downloadable Excel work order templates — general, PM, and emergency — for operations not yet using CMMS.

Download templates →

Industry

Manufacturing Work Order Software

Templates tuned for manufacturing — 5 WO types, OEE impact, shift handover, and compliance for plant operations.

Read the guide →

Tool

CMMS ROI Calculator

Quantify what switching from Excel templates to CMMS is worth in your operation.

Calculate ROI →

Book A Demo Click to Call Now