Free Work Order Template (Fillable + Example)

A work order is only useful when the person receiving it can understand what to do, where to do it, what “done” means, and who can approve the result. A vague request such as “fix the leak soon” leaves a technician to discover the location, urgency, access rules, materials, and approval limits after arriving. Those gaps cause repeat visits, unsafe work, missed service commitments, and disputed costs.

Use this work order template to define the request before work starts and preserve a record through inspection, approval, execution, and closeout. It works for facilities maintenance, equipment repairs, field service, IT operations, and internal service teams. Adapt the fields to your process; do not treat a general template as a substitute for safety procedures, permits, manufacturer instructions, or local regulations.

What is a work order, and when should you use one?

A work order is a controlled record that describes, authorizes, assigns, and documents a specific piece of work. It connects the original request to the people, resources, safety controls, timing, and evidence needed to complete and verify the job. A work order can be a form, a ticket in a maintenance system, or a task record in an operations platform; the workflow matters more than the file format.

Use one whenever work needs coordination, approval, a traceable history, a safety check, or a clear completion standard. Typical cases include a leaking pipe, a scheduled generator inspection, a replacement of a failed production sensor, or a request to repair a door lock. A trivial task may need only a lightweight ticket, but repeated or consequential work benefits from a structured record.

A work order is not automatically a purchase order, contract, risk assessment, or permit to work. It may reference those records, but each serves a different purpose. A work order defines the job; a purchase order authorizes a supplier purchase; a permit or risk assessment controls specific hazards under your organization’s procedures.

What should a complete work order template include?

A complete template gives the requester an easy way to describe the problem while giving the dispatcher and technician enough detail to plan and execute safely. Make required fields genuinely necessary and use “unknown” or “to be confirmed” where that is more honest than guessing.

How should requester, location, and asset details be recorded?

Capture a named requester and a reliable contact route, not just a department name. For a site job, provide enough location detail that a new technician can find the point without asking three people: “Building C, level 2, east mechanical room, pump P-204” is more useful than “pump room.” Include access windows, security check-in, keys, escort requirements, and whether the area is occupied.

Identify the asset with the organization’s own tag or ID whenever possible. Add model or serial details only when they help distinguish the equipment or obtain parts. If the request concerns an area rather than a particular asset, say so. A correct asset history helps teams notice repeat failures and choose the right maintenance plan; an incorrect asset association can mislead future decisions.

How do you define scope, priority, and acceptance criteria?

Write the scope as observable actions and boundaries. “Inspect the north loading-bay door, identify why it fails to close, adjust the closer if safe, and report any replacement parts needed” is more useful than “repair door.” State exclusions such as “no electrical rewiring without separate approval.”

Priority should reflect impact and urgency under a published local policy. A blocked emergency exit or a leak near energized equipment may require immediate escalation under site rules; a cosmetic defect may wait for planned work. Do not use “urgent” as a substitute for impact details. Define the service target as a target or policy commitment, not a promise the team cannot meet. Separate response time (when someone acknowledges or attends) from restoration time (when service is back), because they are different measures.

Acceptance criteria describe evidence that the requested result has been achieved. Examples include “door closes and latches in three consecutive tests,” “temperature reading is within the manufacturer’s specified range,” or “failed component replaced and post-repair functional test recorded.” If the technician discovers that the requested repair is not safe or possible, an approved alternative or a documented escalation can be the correct outcome.

How should safety, materials, technicians, and service targets work together?

The work order should prompt planning, but a form alone does not make work safe. Require the assigned person to review site procedures, identify job-specific hazards, obtain permits where required, and confirm isolations and controls before beginning. The responsible qualified person must decide whether the job is safe to proceed; stop-work authority should be clear to everyone involved.

Record known hazards and access constraints without pretending the requester has completed a formal risk assessment. Use fields for hazard/control references, required PPE, lockout or isolation verification, permit number, and a pre-start confirmation. If conditions differ from the request, pause, make the area safe under procedure, and seek the right review rather than silently expanding scope.

Materials should include a description, quantity, unit if useful, stock or purchase source, and status: available, reserved, ordered, or pending approval. Include tools, specialist equipment, vendor support, and prerequisite work. A part listed on the form is not necessarily available; the dispatcher should verify availability before promising a schedule.

Assignment should name one accountable owner, even when several people contribute. Add a crew or specialist where needed, expected labor hours, and the skill or qualification requirement. Service targets should match the team’s actual capacity, operating hours, travel constraints, and contract. A priority matrix is useful only if staff understand its definitions and can escalate exceptions.

What is the approval lifecycle from request to closeout?

A reliable lifecycle prevents unapproved work and ensures the final record is more than a checked box. Your system may use different status names, but each transition should have an owner and a clear condition.

1. Requested: The requester submits the issue, location, impact, and available evidence. The record receives an ID and timestamp.
2. Triaged: A dispatcher checks completeness, duplicate requests, work type, risk indicators, and priority. Missing critical information is returned for clarification.
3. Reviewed and approved: The correct manager, asset owner, or budget holder approves work according to policy. Safety review or a permit process is completed when applicable. Approval does not replace technical authorization.
4. Planned and assigned: The coordinator confirms scope, materials, access, skills, service target, and schedule, then assigns one accountable technician or crew.
5. Ready to start: The technician reviews the order on site, verifies actual conditions, and completes required pre-work checks. If scope, hazards, or cost changes materially, the job is paused and routed for approval.
6. In progress: Work notes record meaningful actions, readings, parts, time, and any delay or deviation. Use timestamps when they help reconstruct the sequence.
7. Technically complete: The technician records the result and tests against acceptance criteria. Failed tests, unresolved defects, and temporary fixes are explicit; they are not reported as complete repairs.
8. Verified and closed: The requester or designated reviewer confirms the outcome where appropriate. The closeout captures evidence, actual labor/materials, follow-up tasks, and the final status. The record is closed only when required documentation is present.

For low-risk routine maintenance, approval may be a standing authorization or a pre-approved schedule. For unplanned work, establish who can authorize the job and the spending limit before dispatch. Changes to scope, cost, or risk need a documented decision. A time-stamped approval in a system, email, or signed form is better than an undocumented verbal “go ahead.”

How do preventive and corrective work orders differ?

Preventive work orders are generated from a schedule, condition trigger, or maintenance plan before a known failure occurs. Corrective work orders respond to a defect, breakdown, inspection finding, or service request. Both need ownership, scope, safety review, evidence, and closeout, but their planning questions differ.

A preventive order can uncover corrective work. Record the inspection as completed, then create a linked corrective order for the repair if it needs separate parts, expertise, approval, or downtime. This keeps the scheduled task’s history honest and avoids burying substantial repair work inside a routine checklist.

How do you fill out and use this work order template?

Start with the request and the result the requester needs; then let the dispatcher and technician add planning and execution details. Do not ask a requester to guess technical diagnoses, labor estimates, or controls they are not qualified to set. Assign responsibility for completing each section so “everyone’s form” does not become nobody’s form.

Copyable work order template

WORK ORDER

Work order ID:
Status: Requested / Triaged / Approved / Planned / In progress / Complete / Closed
Work type: Preventive / Corrective / Inspection / Installation / Other
Request date and time:
Requested by (name, team, contact):
Approving owner / approval date / reference:

SITE AND ASSET
Site / building / floor / room / zone:
Access window, escort, keys, or restrictions:
Asset name and ID (model/serial if useful):

REQUEST AND SCOPE
Reported issue or scheduled task:
Observed impact and symptoms:
Work included:
Work excluded or requiring separate approval:
Acceptance criteria / required test:

PRIORITY AND PLAN
Priority under local policy / reason:
Response target / restoration target / due date:
Assigned accountable technician / crew:
Estimated labor / cost limit / funding reference:
Materials and quantities / availability:
Tools, vendor, and prerequisites:

SAFETY AND ACCESS
Known hazards / hazard review reference:
Required controls, PPE, isolation, or permit:
Pre-start verification and person confirming:
Stop-work or escalation contact:

EXECUTION AND CLOSEOUT
Actual start / finish / labor hours:
Work performed and findings:
Parts used / quantities / asset changes:
Measurements, functional test, and result:
Photos or document links (before / during / after):
Outstanding issue, workaround, or follow-up order:
Requester / reviewer sign-off and date:
Closed by / close date:

In a paper or spreadsheet version, use dropdowns for controlled values such as status, priority, work type, and site. Avoid dropdowns for nuanced observations; give people space to explain. In a digital system, make fields conditional where appropriate: a permit reference may be required for certain work types, while a serial number may not apply to a room-level service request.

How should photos and other evidence be handled?

Photos help document a condition, identify a component, show before-and-after work, or support a remote review. They do not replace measurements, a functional test, or a safety inspection. Add a short caption stating what the image shows and when it was taken; an unlabeled close-up can be impossible to interpret later.

Follow site rules for photography, privacy, security, and retention. Avoid capturing people, badges, screens, or sensitive areas unless there is a legitimate, authorized reason. Store files in the approved record system and link them to the work order, rather than leaving important evidence in a technician’s personal camera roll. For a critical repair, record instrument readings and test conditions in addition to a photo.

What does a filled work order example look like?

This illustrative example shows the level of detail that makes a request actionable. The names, target, and figures are hypothetical; they are not an industry service standard. Adapt the priority and approval rules to your organization.

The example deliberately separates a symptom from a diagnosis. It defines a safe boundary, names what the technician can do under the authorization, and states what happens if the acceptance test fails. This prevents “repair pump” from becoming an unlimited instruction.

Which metrics show whether the work order process is improving?

Measure the flow and quality of work orders, not just the number marked closed. Select a small set that supports a decision, define the numerator and denominator, and review exceptions by work type or asset criticality. Metrics are diagnostic signals; they do not prove that a team is safe or effective on their own.

Example: if 42 of 50 due preventive orders were completed by their planned date, schedule compliance is 84% for that period. That is a calculation, not a universal benchmark. Review the eight exceptions: were parts unavailable, access denied, or work deliberately deferred after a risk review? The right response differs for each cause. Likewise, if 6 of 40 corrective jobs required a repeat visit within 30 days, investigate those six records before concluding that the team has a quality problem.

Use a trend over several comparable periods and segment by site, asset class, urgency, or work type. Publish metric definitions so teams do not change the denominator to improve a score. Pair speed measures with quality and safety indicators; rewarding closure volume alone can encourage premature closeout or unnecessary work.

What are the common work order mistakes to avoid?

• Writing a symptom as a confirmed cause: Record “water under the unit” unless a qualified person has identified the failed seal. Diagnosis can change the scope.
• Using vague scope: “Check and fix” is not an acceptance criterion. State what to inspect, what is authorized, and how completion will be tested.
• Making every job urgent: If everything is critical, dispatch cannot distinguish immediate hazards from routine inconvenience. Use impact and urgency definitions.
• Leaving safety as a checkbox: A checked field cannot confirm actual isolation or safe conditions. Require an on-site review under the applicable procedure.
• Assigning a team but no owner: Name one accountable technician or coordinator and identify collaborators separately.
• Approving a blank cost or scope: Set an authorization limit and a clear change process. Escalate when actual conditions exceed it.
• Closing without a test or next action: If the equipment remains unavailable or the temporary fix needs replacement, record that and link the follow-up.
• Keeping evidence outside the record: Photos and readings that cannot be found later do not support maintenance history or review.
• Treating preventive maintenance as proof of reliability: A completed checklist is useful, but repeat faults, condition findings, and deferred work still need analysis.

A template can become bureaucratic if it asks every requester for technical detail they cannot know. Keep the intake short, then let dispatch and qualified workers complete the planning fields. Review the form periodically: remove fields that add no decision value, but do not remove a required safety or audit control simply because it takes effort.

How can a team keep work orders organized as volume grows?

At low volume, a controlled spreadsheet and shared folder may be enough, provided the team manages unique IDs, permissions, version history, and backups. The trade-off is that reminders, approval trails, asset histories, and reporting often require manual work. A dedicated maintenance management system can connect work orders to assets, schedules, parts, and service history, but it may take time to configure and train people. Choose the lightest process that reliably controls your operational risk and reporting needs.

Keep one source of truth for each active order. Define who may submit, prioritize, approve, assign, change scope, and close work. Use standard status definitions and a short dispatch review cadence. Link related requests rather than copying the same details into separate records. For recurring work, create a controlled task list and review it when equipment, manufacturer guidance, or site conditions change.

For work that spans several teams, break execution into assigned tasks while preserving one parent order and one accountable coordinator. Dependencies matter: a shutdown window, permit, part delivery, and specialist visit may all need to happen before a final test. A project or work-management platform can make these dependencies, owners, dates, and progress visible, but it is not automatically a maintenance system of record. Confirm that the chosen tool fits asset-history, safety, compliance, and integration requirements before adopting it.

Conclusion

A useful work order template does more than capture a request: it connects the requester and location to a clear scope, priority, safety review, materials, accountable technician, service target, evidence, approvals, and verified closeout. The work order template above can be copied into a form or adapted to a system, but tailor priorities, safety controls, approval limits, and retention to local policy.

Start with the essential fields, test the form on a routine preventive job and a real corrective repair, and ask technicians where ambiguity caused delay or rework. Track a few consistently defined measures—such as schedule compliance, repeat work, and complete closeout—and use exceptions to improve planning rather than to reward fast closure alone. A record is complete when the work result and any remaining risk or follow-up are clear to the next person.

SEO (Final Output)

1. SEO Title: Work Order Template: Free Form & Example
2. Meta Description: Use this work order template to capture scope, priority, safety, approvals, materials, and closeout. See a filled example and practical metrics.
3. URL Slug: work-order
4. Primary Keyword: work order template
5. Secondary Keywords: work order form, maintenance work order, work order example, preventive maintenance work order, corrective work order
6. Featured Snippet Suggestion: A work order is a controlled record that defines, authorizes, assigns, and documents a specific job, including its scope, owner, safety controls, timing, and completion evidence.
7. Internal Linking Suggestion: Link “project management KPIs” to https://doitify.com/planning/project-management-kpis/ and “project risk management” to https://doitify.com/planning/project-risk-management/.
8. Featured Image Suggestion: A facilities technician reviewing a digital maintenance work order beside tagged equipment, with no visible personal or confidential information.
9. Alt Text Suggestions: “Technician checking an equipment maintenance work order”; “Work order lifecycle from request through verified closeout.”
10. Chart Title Suggestion: “Work order lifecycle: request, review, approval, execution, and closeout” (process diagram; no invented performance data).
11. FAQ Questions: Work request vs work order; work order vs purchase order; who approves; cost estimates; incomplete repairs; photos; retention; spreadsheet use.
12. Schema Suggestion: Article; FAQPage only if the visible FAQ content and current search-engine requirements support it.

Admin Actions (Manual Completion)

Images

• Add a featured image illustrating a technician reviewing an equipment work order. Alt: “Technician checking an equipment maintenance work order.”
• Optional lifecycle diagram near the approval section. Alt: “Work order lifecycle from request through verified closeout.”

CTA

• Use the approved English Doitify CTA after the conclusion (publisher-managed).

SEO

• Preserve the live slug `work-order`; set Rank Math title, description, and focus keyword from the SEO block.

Links

• Verify the internal links to the published project management KPI and project risk management pages.

Schema

• Article; FAQPage only where eligible and consistent with visible FAQ content.

Table of contents

• Add a table of contents if supported by the site’s standard article layout.

If this post on work order template was helpful, you might also enjoy Project Prioritization Frameworks Explained (With Examples) and Free Kanban Board Template (Excel, Google Sheets & Apps).