A work order status workflow gives every job a clear answer to three questions: what has happened, who acts next, and whether the work can genuinely close. Without those rules, a job can be marked complete after a technician leaves even though notes need review, a part is outstanding, or another visit is required.
This guide provides a practical lifecycle for solo operators and small office-managed service teams. It works on paper, in a spreadsheet, or in field service software. The labels are configurable; the important part is that each status has a defined meaning, owner, and next action.
Why a work order needs more than open and complete
“Open” and “complete” are often too vague for service work. A job may be planned but not started, actively being worked, paused for a decision, finished in the field, awaiting office review, or fully closed. Combining those situations under one open status makes follow-up difficult. Combining them under complete can make unfinished work disappear.
The most useful distinction is between Work Complete and Closed:
- Work Complete means the relevant field activity or visit is finished and the team has captured the local evidence it needs.
- Closed means all related work and associated activity are complete, with no unresolved follow-up remaining in that work order.
This distinction reflects a common lifecycle pattern in field service systems. For example, Salesforce work-order status definitions distinguish New, In Progress, On Hold, Cannot Complete, Completed, Closed, and Canceled, and define Closed as the point when all work and associated activity are complete. Those are platform-specific examples, not a required universal taxonomy.
Also keep the work-order lifecycle separate from visit, booking, or appointment progress where your system uses separate records. Some systems allow those records to have different statuses, and an update to one does not necessarily update the other. Salesforce documents this distinction between separate work-order and appointment statuses. A scheduled visit is therefore not proof that the overall work order is active or ready to close.
Use a simple work order status model from new to closed
Start with the smallest status set that distinguishes planned, active, paused, field-complete, closed, and canceled work. A small team does not need every possible label. It does need a visible path for work that cannot proceed.
| Status | Meaning | Typical next status |
|---|---|---|
| New or Unscheduled | The work order exists, but it has not yet entered active field work. It needs a next owner and action. | Scheduled or Assigned, Paused, Canceled |
| Scheduled or Assigned | A visit is planned or allocated. This is a planning state, not evidence that field work has begun. | In Progress, Paused, Canceled |
| In Progress | Active field work has started on the work order or relevant visit. | Work Complete, Paused, Return Visit Needed, Canceled where appropriate |
| Paused or On Hold | Work cannot progress until a stated event, decision, item, or contact occurs. | Scheduled or Assigned, In Progress, Return Visit Needed, Canceled |
| Return Visit Needed | The current visit ended, but the same work order needs another field action. | Scheduled or Assigned, In Progress, Canceled |
| Work Complete | The relevant field work is finished and the required local job record has been captured. | Ready for Review, Closed, Return Visit Needed |
| Ready for Review | An optional handoff status for office-managed teams before administrative closure. | Closed, Return Visit Needed, Paused |
| Closed | All work and associated activity on the work order are complete. | Reopened only under a local exception rule |
| Canceled | The work will not proceed. Retain the business’s chosen reason category where useful. | Usually final |
Ready for Review and Return Visit Needed are useful local labels, not universal system states. If your software supports custom labels, map them to broad status categories so reports remain understandable. Salesforce similarly documents that custom values can retain a standard category through status categories for custom labels.
Before a work order moves to Scheduled or Assigned, make sure the job record contains the information your team needs to act. If you need a pre-job record format, start each job with a complete work order.
Define the rule for every status change
A label alone does not control a workflow. For every status, define five items: the entry condition, accountable owner, record required at the change, permitted next statuses, and the next action.
| Status | Entry condition | Accountable owner | Record or evidence | Control rule |
|---|---|---|---|---|
| New or Unscheduled | Work order is created. | Owner, office coordinator, or dispatcher | Customer and job details appropriate to the business | No work order remains here without a named next action. |
| Scheduled or Assigned | A planned field action exists. | Dispatcher, coordinator, or solo operator | Current owner and planned action | Do not use this as a substitute for In Progress. |
| In Progress | Field work has started. | Technician or solo operator | Start note where the team uses one | Move out only to complete or a visible exception path. |
| Paused or On Hold | Progress is blocked. | Person who can remove the block | Reason, next action, and review date | A paused job without an owner is not controlled. |
| Return Visit Needed | The current visit ended with more work required. | Coordinator, dispatcher, or owner | Reason for return and required next action | Keep the work order visible until the next field action occurs. |
| Work Complete | The relevant field activity is finished. | Technician or solo operator | Notes and other local evidence where relevant | Do not use if an unresolved exception remains. |
| Ready for Review | Field work is complete and an office check is used. | Office reviewer or owner | Review outcome and any follow-up instruction | Return the job to an exception status if more action is needed. |
| Closed | All work and associated activity are complete. | Owner or office reviewer for managed teams | Confirmation that no work-order follow-up remains | Use a reopening rule rather than silently editing history. |
The evidence column should reflect your local process, not an assumed compliance requirement. Depending on the job, useful evidence may include job notes, photos, materials used, customer acknowledgement where the team uses it, or a follow-up instruction. Do not make every item mandatory for every job. Signatures, images, and service reports can be supported by some field service platforms, but availability depends on configuration, access, and mobile-app conditions.
Assign ownership for solo operators and office-managed teams
Status ownership prevents a work order from becoming everyone’s problem and nobody’s responsibility.
Solo operator
One person may update every stage, but the same lifecycle still helps. Record a next action whenever work pauses or needs another visit. Before marking Closed, take a separate moment to confirm that no service follow-up remains. That brief review reduces the risk of treating “I left the site” as “the work order is finished.”
Office-managed team
- Technician: usually owns In Progress updates, work-complete evidence, and notes explaining incomplete work.
- Dispatcher or coordinator: may own visibility for Scheduled, Paused, and Return Visit Needed statuses.
- Office reviewer or owner: may own Ready for Review and Closed, particularly when a second person checks the work-order record.
Set a review interval that fits the business, such as a daily or weekly exception review. The rule is simple: every paused, incomplete, or review-ready job should have a named owner, next action, and date for the next check.
Scheduled or Assigned is only upstream context in this workflow. For the mechanics of office visibility during the service day, use a separate process to assign and monitor scheduled work on a dispatch board.
Separate completed field work from a closed work order
Work Complete is a field result. Closed is an administrative end state. Keeping them separate is especially useful when one person performs the work and another person reviews the record.
A technician can mark Work Complete when the visit is done and the team’s relevant record is captured. That may include job notes, a materials reference, photos where useful, an acknowledgement where the business uses one, or instructions for a remaining follow-up. The work order can then move to Ready for Review rather than disappearing into Closed.
A completed visit may still need a record check, a follow-up task, an exception decision, or another visit. If you use a post-visit record, you can document the completed visit in a field service report. The report can support Work Complete or review status; it is not automatically a universal requirement for closure.
Once the work order is Closed, any downstream handoff should occur only after the team’s closure criteria are met. Keep that handoff separate from the status model rather than adding billing stages to the work-order lifecycle.
Keep exceptions visible instead of falsely closing work
Exception statuses are where a work order status workflow earns its value. They stop unfinished jobs from being labeled complete merely because a visit ended.
Parts pending
Move the work order to Paused or Return Visit Needed. Record the required item or decision, who owns the next action, and the next review date. The key is not the wording of the label; it is that the job remains visible.
Customer approval pending
Use a paused local label if further work depends on a customer response. Record what response is needed and who will check back. This is a work-order visibility rule, not an estimate-approval process.
Inaccessible site or cannot complete
Use Paused, Cannot Complete, or Return Visit Needed according to your local model. Capture a concise reason, relevant follow-up need, and next owner. Do not close the overall work order just because the current visit could not finish.
Incomplete work and return visits
Keep the same work-order context where practical. The completed portion of a visit can be recorded, while the overall work order remains in a visible follow-up status. Move it back to In Progress when the next field action begins.
Canceled jobs
Use Canceled when work will not proceed. Keep the final disposition and the reason category your business uses for reporting. Avoid leaving canceled work in New, Scheduled, or Paused, where it can distort the active backlog.
Run the same lifecycle on paper, in a spreadsheet, or in software
You do not need automation to use status controls. The same logic works in any record system if the current status and next action are easy to find.
Paper log
Keep one current-status line for each work order. Include the work-order ID, current status, owner, date updated, and next action. When the status changes, update the line or maintain a short history on the job record.
Spreadsheet
Create columns for:
- Work-order ID
- Current status
- Current owner
- Last update date
- Next action
- Next review date
- Evidence reference, where used
Filter the sheet for Paused, Return Visit Needed, and Ready for Review. Those views become an exception list for the owner or office team.
Field service software
First confirm which record carries the work-order status and whether appointment, booking, or line-item statuses are separate. Then test any automation with a sample job before relying on it. Relationships, mappings, and permissions vary by platform configuration, and status changes may not cascade across related records.
Set up your status rules before changing labels
- Choose the smallest status set that distinguishes planned, active, paused, field-complete, reviewed, closed, and canceled work.
- Write a one-sentence definition for every status.
- List the permitted next statuses so a job cannot jump from active work to closed without a deliberate decision.
- Assign an owner and next-action requirement to every exception status.
- Decide what local documentation supports Work Complete for each type of job.
- Decide whether an office review stage adds value for your team.
- Test the workflow with a normal job, an incomplete visit, a return visit, and a cancellation before rolling it out.
A good work order status flow is not the one with the most labels. It is the one that makes the current state, responsible person, and next action clear—especially when the job is not yet ready to close.
Frequently asked questions
What is the difference between completed and closed on a work order?
Completed can mean the relevant field work is finished. Closed should be reserved for the point when all work and associated activity on the work order are complete. A completed visit may still require review, follow-up, or another visit. Exact labels and permissions vary by system.
What work order statuses does a small service business need?
A practical minimum is New or Unscheduled, Scheduled or Assigned, In Progress, Paused or Return Visit Needed, Work Complete, Closed, and Canceled. Add Ready for Review when a technician-to-office handoff makes that stage useful.
Should scheduled and in progress be separate statuses?
Yes, where practical. Scheduled or Assigned means work is planned or allocated. In Progress means active field work has begun. Separating them avoids treating a planned visit as proof that work is underway.
How should a work order be handled when a technician cannot finish the visit?
Move it to a visible Paused, Cannot Complete, or Return Visit Needed status. Record the reason, owner, next action, and next review date. Do not mark the overall work order closed while follow-up work remains.