A work order is the record that turns a request into an assigned, tracked job. It names the work, the owner, and the deadline, then collects the time and parts. The request comes first; once it's accepted, a work order goes to the team that does the job.
If you searched "what is a work order" because facilities requests started landing in your IT queue, this guide is for you. It comes from the team behind SherpaDesk, a helpdesk and PSA (professional services automation) a small IT team can run alone.
Key takeaways
ITIL's 2011 glossary defines a work order as "a formal request to carry out a defined activity." In IT service management, change and release teams often use work orders to hand jobs to the technical teams that do them. Once it's closed, the work order becomes the history: who did what, how long it took, and what it cost.
The request comes first. At the University of Florida's engineering college, repair and maintenance requests go to Facilities Services as work requests. Once the request arrives, a work order goes to the right shop to do the repair.
A request can be a duplicate, out of scope, or the wrong team's job. A work order should only exist for work someone has agreed to do.
In federal contracting, a purchase order is an offer to buy supplies or services on specified terms. A failed rooftop unit needs a work order for the repair, and may also need a purchase order if the compressor is bought.
| Record | What it does | Badge reader example |
|---|---|---|
| Work request | Asks for work and describes the problem | Staff email: the east door reader is dead |
| Work order | Hands an accepted job to the people who will do it | The accepted repair, assigned to one technician |
| Ticket | Holds the request and the work in one helpdesk record | One ticket tracks the emailed request through repair and closure |
| Purchase order | Offers to buy supplies or services from a seller | A new reader, if you buy one |
In a helpdesk, one ticket can carry the first two rows: the coordinator's review turns it into a work order.
Work that isn't written down risks being done late, done twice, or forgotten. A work order gives each job an owner and a date someone can check. The Government Accountability Office surveyed a national sample of public school districts from November 2025 to January 2026. For the 2024-25 school year, it found:
| Finding | Share of districts |
|---|---|
| Canceled school at least once due to an emergency facility issue | 19% |
| Had chronic facility issues in at least one school | 47% |
| Had limited or no capacity for preventive maintenance on recommended schedules | About 1 in 5 |
Districts in that last row had more chronic facility problems and more disruptions to instruction. Use recurring work orders to keep jobs like boiler servicing on the schedule between emergencies.
Some building systems have already moved to IT, as one r/k12sysadmin member noted. "I remember when phone, security cameras, and intercom/clocks were all Facilities items. As things moved to IP based, these all got handed over to I/T."
For an MSP, work order management is also billing: hours that never reach a record never reach an invoice.
Good work order management starts with a process everyone follows. The work order process below is one we recommend, built on the flow Ohio University's facilities team publishes. It has three roles: the requester, the coordinator who accepts, prioritizes, and assigns the work, and the technician. On a small team, the coordinator is often the IT lead. One badge reader runs through every step.
Someone reports a problem by phone, email, walk-in, or web form. Accept whatever channel people will use, and confirm receipt.
Example: a staff member emails that the badge reader at the east entrance won't open the door.
The coordinator checks the request and either accepts it or turns it down with a reason. Our ticket triage guide covers the routing rules.
Example: a second email about the same door is merged, and the request accepted.
The accepted request becomes a work order with a priority and a due date.
Example: staff can't badge in at the only staffed entrance, so the coordinator marks it urgent and agrees on a next-day fix with the requester.
The coordinator picks a technician by skill and current load, then books the time. Ohio's shop managers handle this step. If the fault is already diagnosed, order parts now.
Example: the technician who knows the access system gets it for that afternoon.
The technician records the work on a log sheet: hours, notes, and parts. Ohio's managers update the status, such as "progressing" or "parts on order."
Example: the reader has failed. The technician logs 45 minutes and puts the job on hold for a part, and the coordinator gives the requester a new date.
At Ohio University, technicians can't close a work order; managers close it after a quality review. A small team can drop the second person, but not the check.
Example: two days later, the technician fits the part and logs time and parts; the coordinator tests and closes the job.
This guide groups work orders by what starts them: a schedule, a failure, or a request for something new. Urgency is a separate question, covered by the priority levels below.
| Type | Where it comes from | IT or school example |
|---|---|---|
| Preventive | A schedule, to catch failures early | Quarterly filter change on a server room AC unit |
| Inspection | A periodic check within a preventive program | A monthly walk-through of network closets |
| Corrective | A failure, reported by a user or found on an inspection | A classroom display that won't power on |
| Install or move | A request for something new | Mount and connect 30 new door-access readers |
The University of Central Florida's maintenance policy describes preventive maintenance as scheduled inspection, cleaning, adjustment, and minor repair, meant to stop failures that would need corrective work. In this guide, a maintenance work order is one of the first three rows: work on existing buildings or equipment. An install is new work.
Here, emergency is a priority rather than a type, usually on a corrective job, such as a water leak above a switch rack.
Priorities are the other half of work order management: they tell you how fast someone must respond. The University of Kansas facilities office publishes four levels with response targets.
| Priority | Covers | Response |
|---|---|---|
| 1, Emergency | Immediate or imminent danger to life, health, safety, or security, or significant property damage | Immediate |
| 2, Urgent | Unscheduled, reactive work that may cause injury, damage, or serious disruption of service | Within 48 hours |
| 3, Scheduled | Date-sensitive requests, including preventive maintenance | Within 5 days |
| 4, Routine | Requests with no threat to life, property, or operations, worked in order received | Within 10 days |
Note where preventive maintenance sits: priority 3, with a date. Our guide to incident priority levels sets the same kind of scale for IT tickets.
Work order management is the practice of moving every work order through those six steps, on time, and learning from the closed ones. A work order management system is the software that holds the queue, the schedule, and the history.
For a team of three, it's mostly four numbers, checked once a month, each with a next move:
Start your work order management review with backlog, using your own numbers.
Weeks of work order backlog
Open hours ÷ weekly hours. Your numbers stay in the browser.
Example: a three-person team has 96 estimated hours in open work orders and spends 60 hours a week on them. That's 96 ÷ 60 = 1.6 weeks of backlog.
Watch the trend monthly. If backlog grows, check whether preventive jobs are slipping despite having no user complaints.
Subscribe to the SherpaDesk Blog.
Get Tips for Running IT With a Small Team.
Loading form…
The form couldn’t load. Please try again.
Or start your free trial →SHERPADESK · FREE TRIAL
Resolve tickets.
Turn time into revenue.
Bring support tickets, billable time, and invoicing into one place. Built for small IT teams and MSPs.
After your trial, keep your first agent free forever.
SHERPADESK · LIVE DEMO
See tickets, time,
and billing work together.
Walk through ticketing, time tracking, and billing with a product specialist. See how SherpaDesk fits the way your team works.
A live walkthrough tailored to your team.
Work order management systems range from maintenance suites to the queue inside a helpdesk. Pick by the work you do most. If you run a plant or a large equipment program, a computerized maintenance management system (CMMS) fits. An IT team that also takes facilities requests may do better with work orders in its helpdesk. Check for:
Schools that want dedicated work order management software can compare options in our guide to school facilities maintenance software.
Check your own work order management against this list.
As one r/k12sysadmin member put it, "Let the end user type in the issue, hoping you get some details. Allow your IT staff to select the category."
Skip review, and three reports of one outage can become three work orders, with three technicians chasing one fault.
Marking everything urgent hides the real emergencies. If a projector and a leak above the server rack both arrive as urgent, the leak can end up waiting. Save urgent for a risk of injury, damage, or serious disruption of service, as Kansas does.
Closed counts alone reward easy jobs. Pair them with backlog and repeat work.
A work order should only exist for work someone has agreed to do.
How this works in SherpaDesk
Each work order is a ticket. You log time against it with a timer or the timesheet, and uninvoiced time collects in "Ready to Invoice" by contract.
Scheduled maintenance work orders live under Tickets > Scheduled, with days, time, recurrence, and a To Do template for the checklist. Routing rules send each class to the right technician, and custom forms show only the fields that class needs. Users can request a service date, and printed tickets can carry a signature block for sign-off.
A helpdesk and PSA a small IT team can run alone, for your own staff or your clients. No contract. No implementation project. No dedicated admin.
Base Camp is $45 per agent per month ($40 billed annually). The first agent is free, forever, so a team of three pays $90 a month ($80 billed annually). The trial is 14 days free with no card.
Who this isn't for
Maintenance teams choosing a CMMS for heavy equipment and preventive-maintenance programs.
A maintenance work order is a job to inspect, service, or repair an existing building system or piece of equipment. Preventive work is scheduled to head off failures; corrective work fixes them. Installing something new is a separate job.
Start from an accepted request. Give it a priority and a due date, and assign one owner. If the fault is already diagnosed, order parts before the first visit. In a helpdesk, the reviewed ticket can be the work order.
No. In federal contracting, a purchase order is an offer to buy supplies or services on specified terms. A work order assigns a job to your own team or a contractor. One repair can need both, so link them and keep the job's cost in one place.
Enough for someone else to do the job without calling back: what needs doing, where, who owns it, and by when. As the work happens, the technician adds notes, hours, and parts, and someone checks the result before closing.
Close, and often the same record. A ticket is how IT tracks a request and the work on it; see our guide to what an IT ticket is. Facilities teams call the accepted job a work order. If the same people handle IT and facilities jobs, one queue with categories keeps work order management in one place.
In the process above, the coordinator does: often a facilities supervisor, IT lead, or service manager. On a small team, one lead can approve and close.
Patrick co-founded SherpaDesk and has led it as CEO since 2013. He has worked with IT service providers since 1998, first on network projects for schools and government offices, then on the helpdesk software their technicians use every day.