Work Order Process: From Maintenance Request to Close-Out, Step by Step
By Kirill Stolbushkin
Short answer: A work order process is the path a job follows from the moment someone reports a problem to the moment the fix is confirmed and recorded. For most facilities, property management, and field service teams it runs in eight steps: capture the request, triage it, approve it, plan and schedule it, keep the requester updated, do the work, verify and close it, and review what it tells you. The work itself is usually the easy part. The delays come from missing information, unclear approvals, and jobs that are done but never closed.
Requests arrive by phone, text, email, a form, and a conversation in the hallway. A technician shows up without the access code. A tenant calls twice to ask if anyone is coming. A repair costs more than expected and nobody knows who can say yes. Most of these problems come from the process, not the people.
This guide is about the process, whatever tool you use to track jobs today.
Work request vs work order
A work request is the report of a problem: "the heating in unit 4B is not working." Anyone can submit one.
A work order is the authorized job created from it: what will be done, by whom, by when, at what cost limit. Someone with authority creates or approves it.
Keeping the two apart matters. Not every request becomes a work order. Some are duplicates, some are out of scope, some are the tenant's responsibility, and some get answered with a quick instruction over the phone.
Who is involved
Requester: a tenant, an employee, or a customer. Reports the problem and confirms the fix.
Coordinator or dispatcher: triages requests, creates work orders, and schedules the work.
Approver: a facilities manager, property manager, or owner who authorizes spend above a limit.
Technician or vendor: does the work and records what was done.
Supervisor: checks quality on jobs that need inspection.
In a small team one person may hold the first three roles. Write them down anyway.
The work order process, step by step
Step 1: Capture the request
Use one intake point for every request, and ask for what the technician will need:
Location, down to the room, unit, or asset.
What is wrong, in the requester's words, with photos if possible.
How urgent it seems and whether anyone is at risk.
Access details: when someone can get in, keys, codes, pets, site contacts.
Contact details for updates.
Every request gets a reference number.
Step 2: Triage
The coordinator decides what kind of job it is:
Duplicate or already known: link it to the open work order and tell the requester.
Out of scope: explain who is responsible instead.
Can be solved remotely: a reset, an instruction, or a quick answer, then close it.
Real job: set a priority and create a work order.
Step 3: Approve the work
Small, routine jobs should not need anyone's sign-off. Larger ones should. Set a cost limit for each role, sometimes called a not-to-exceed amount, and route anything above it for approval before work starts. In property management this is often the owner or asset manager. In facilities it might be the facilities manager or finance. For field service, approval may come from the customer, through a quote they accept.
Step 4: Plan and schedule
Assign an internal technician or a vendor, confirm the parts and tools, arrange access with the requester, and check any safety requirements such as permits, lockout procedures, or working at height. Then put the job on the schedule. If you manage several properties, each can have its own preferred vendors and approval limit, so keep those lists per property.
Step 5: Update the requester at every status change
Do not wait for the requester to call. Send a short update each time the status changes: received, scheduled with a date and time window, and done. Add an update if the job is delayed, for example while waiting on parts. Proactive updates cut the follow-up calls that eat a coordinator's day.
Step 6: Do the work and record it
The technician updates the status when they start, records what they found and what they did, the time spent and parts used, and adds photos of the finished work. If the job turns out bigger than expected, they stop and flag it instead of carrying on.
Step 7: Verify and close
A job is not done when the technician leaves. Confirm with the requester that the problem is solved, or have a supervisor inspect it for jobs that need a quality check. If the fix did not hold, reopen the work order rather than starting a new one, so the history stays together. Then close it, with costs recorded.
Step 8: Review and follow up
Closed work orders are information. Once a month, look at them as a set:
Which assets or locations keep coming back?
Which jobs should become scheduled preventive maintenance instead of reactive repairs?
Where did jobs wait the longest, and why?
What needs billing, such as a tenant chargeback or a customer invoice?
Set priorities before you need them
Define a few priority levels and a target response time for each, set to fit your team and any lease, contract, or service terms:
Emergency: safety risk or serious damage in progress, such as a gas smell, flooding, or no heat in freezing weather.
Urgent: something important is broken, but nobody is at risk.
Routine: a normal repair that can be scheduled.
Planned: preventive maintenance and improvement work.
Decide who can declare an emergency, and what happens after hours. After-hours emergencies should route to that property's emergency vendor list, not to whoever happens to answer the phone. Name a backup for that too.
The exceptions that stall work orders
Waiting on parts: put the job in a waiting status with an expected date, and tell the requester.
No access: record the attempt, contact the requester to rebook, and set a limit on how many attempts before escalating.
Scope grows: the technician flags it, the job pauses, and the new cost goes back through approval if it crosses the limit.
Vendor does not show: a reminder at the scheduled time, then reassignment to a backup vendor.
Failed verification: reopen and send back to the technician.
Each of these is a branch in the process, so write it down.
How it differs by sector
Facilities teams handle requests from employees in buildings the company runs. Approvals usually follow internal budgets.
Property managers sit between tenants, owners, and vendors. Owner approval limits and tenant communication are the heart of the process, and access arrangements cause most of the delays.
Field service teams do the work at the customer's site. Quotes, customer approval, and billing after completion become part of the process.
If you document maintenance processes for clients, see process mapping for consultants.
The work order process flowchart in BPMN
The work order process maps cleanly to a BPMN flowchart. The BPMN symbols cheat sheet covers each shape.
Message start event: a request arrives.
Lanes: requester, coordinator, approver, technician or vendor, and supervisor, drawn as swimlanes.
Exclusive gateways: triage outcome, priority, and whether the estimate is above the cost limit.
Timer boundary events: an emergency job not started within its target alerts the manager. A vendor who has not confirmed by the scheduled time triggers reassignment.
Message intermediate events: waiting for parts or for the requester to confirm access, plus the status updates sent to the requester.
Loop: failed verification sends the job back to the technician.
End event: work order closed with costs recorded.
The flowchart shows the flow of the job. The step-by-step instructions for the repair itself belong in work instructions. Our post on SOPs, work instructions, process maps, and policies explains which document does what.
How to model and automate this in Vevos
Describe how your team handles requests today, and Vevos generates a BPMN 2.0 model with lanes, gateways, and timers, along with process documentation for coordinators and new hires. If your procedure already exists as a document, you can start from that instead, as described in our guide to converting PDFs to BPMN. For example:
"A tenant submits a maintenance request with photos and access times. The coordinator checks for duplicates and sets a priority. Jobs estimated above our cost limit go to the property owner for approval. The coordinator assigns a technician or vendor and confirms access with the tenant. The technician records the work and photos. The tenant confirms the fix within two days, or the coordinator follows up. Then the work order is closed."
Walk through the model with a coordinator and a technician, adjust it, and keep each revision as a version so changes to the rules are easy to follow. Make sure the person who owns the process has signed off. Our guide to process ownership and RACI helps if that is unclear.
Try it with the free AI process mapper, no account needed. You can start free, with $9 and $29 plans for more room. When you want a working request and work order app, Conductor Agents, the Vevos agents that build apps from a model, can build and deploy one after you review the model, starting on Tempo at $199/month. See the pricing page.
FAQ
What are the steps in a work order process?
Capture the request, triage it, approve the work if it is above a cost limit, plan and schedule it, update the requester at each status change, do the work and record it, verify and close it, and review closed work orders for patterns and follow-up work.
What is the difference between a work request and a work order?
A work request reports a problem and can come from anyone. A work order is the authorized job created from that request, with an assignee, a schedule, and a cost limit. Some requests never become work orders because they are duplicates, out of scope, or solved on the spot.
Who approves a work order?
Routine jobs under a set cost limit usually need no separate approval. Above it, the facilities manager, property owner, asset manager, or customer approves, depending on who pays.
What should a work order include?
The location and asset, a description of the problem, priority, the assigned technician or vendor, scheduled date, access details, cost limit, and, once complete, the work done, time and parts used, photos, and the requester's confirmation.
When should we move from email and spreadsheets to work order software?
Once jobs start getting lost, requesters chase you for status, or nobody is sure who approved a repair. Map the process first, so the tool you pick follows your rules instead of you adapting to its defaults.
How do you prioritize work orders?
Use a small number of levels, such as emergency, urgent, routine, and planned, each with a target response time. Emergencies are safety risks or damage in progress. Decide in advance who can declare an emergency and how after-hours requests are handled.
Related blog posts
- Purchase Requisition Approval Process: Thresholds, Approval Chains, and Workflow — A practical guide to the purchase requisition approval process: the steps from request to approved requisition, how to set spend thresholds and approval chains, which duties to keep apart, and how to handle urgent and over-budget requests.
- Client Onboarding Process: A Step-by-Step Workflow for Agencies and Service Firms — A practical client onboarding process for agencies, consultants, and B2B service teams: seven steps from signed contract to first delivery, which steps every client gets, which depend on the service, and how to map it so nothing gets dropped.
- Customer Support Escalation Process: How to Build a Ticket Escalation Workflow — How to design a customer support escalation process: support tiers, severity levels, clear triggers, handoffs that carry context, an escalation matrix, and how it all maps to a ticket escalation workflow.