Resources / Business Office / Work orders

Routing maintenance and facilities work orders

The short answer

A work order is only partly about the repair. The rest is a routing problem: the request has to reach the person who can actually do the work, someone has to decide what gets done first, and the teacher who reported the broken door needs to know it was seen at all. In most districts that routing runs on whatever carries messages, email, a phone call to the front office, a note in the custodian's mailbox, so the work gets tracked in one person's head. Doing it well means the request travels a defined path from report to assignment to completion, the person managing the work can see and direct all of it in one place, and the status of any request is a lookup instead of a question someone has to go ask.

On this page

Why the existing systems don't cover it How districts handle it now Where it goes wrong

What doing it well actually requires Common questions How Flow Forms handles it

Why the existing systems don't cover it

Districts usually have software on either side of this process but nothing in the middle of it. The accounting system records the cost of the repair after the fact. A facilities scheduling tool knows which rooms are booked. Neither one carries a request from the teacher who found the problem to the custodian who fixes it, and neither holds the in-between states that make maintenance manageable: reported but not assigned, assigned but waiting on a part, done but never communicated back. Some larger districts buy dedicated work order software, but in a small district the process usually is not big enough to justify another system with its own logins and licensing, so it defaults to the tools everyone already has open, which is email and memory.

How districts handle it now

The report arrives however it arrives. A teacher mentions the leak to the principal, the principal emails the head custodian, someone else calls the district office about the same leak two days later. The custodian keeps the working list, sometimes on paper, sometimes as a mental queue ordered by whoever asked most recently or most urgently. Assignment happens verbally. Completion is announced by the problem no longer being there. When a business manager or superintendent needs to know what is outstanding, what it will cost, or why something reported in October is still open in January, the answer requires asking the person who holds the list, because the list exists nowhere anyone else can see it.

Where it goes wrong

Requests disappear into the gap between reporting and assignment. The same problem gets reported three times through three channels and treated as three problems, or each reporter assumes another one already sent it and it gets reported zero times. The person who reported something never hears back, concludes reporting doesn't do anything, and starts flagging problems only when they become emergencies, which makes every repair more expensive than it needed to be. And the maintenance staff absorb the disorder as their working conditions: a queue with no order, interruptions as the assignment mechanism, and accountability for delays on requests they never saw.

What doing it well actually requires

A work order process that actually holds together comes down to a defined path from report to completion and one place to run it from, and it has a few specific parts.

One way in, no matter who found the problem

Every report enters the same way and lands in the same queue, whether it came from a teacher, a principal, or the business office. The duplicate reports collapse into one item, and nothing depends on the reporter knowing who the right recipient is, because the routing is the form's job, not theirs.

The way in can be posted where the problems actually happen

Any form can be opened from a printed QR code, which changes where reporting can physically live. A code posted in the break room, the gym, the bus barn, or the boiler room opens the maintenance request on whoever's phone is already in their hand, and the report happens at the moment of noticing instead of surviving the walk back to a desk. Districts lose the most reports in exactly that gap, the space between seeing a problem and being somewhere you can report it, and a posted entry point closes it to thirty seconds. The codes go wherever the district wants that kind of response: printed, taped to the wall, done.

The person running the work directs it from the queue, not from their inbox

At Philipsburg School District No. 1 in Montana, the head custodian uses the maintenance request workflow to delegate the work, communicate with staff, and clarify the status of any request. That is the working shape of a functioning work order process: the queue is the management tool, assignment is explicit instead of verbal, and the person directing the work can see everything open in one place instead of reconstructing it from messages.

The same model carries every kind of physical work the district maintains

Columbia Falls Public Schools in Montana runs building maintenance and its mechanic shop through the same build. The routing does not care whether the subject is a boiler, a bus in the shop, or a door that will not lock; what matters is that each type of request follows the path the district defined for it, to the people responsible for that work.

Everyone in the chain knows what they need to do, without being walked through it

Glendive Public Schools in Montana runs maintenance requests as part of more than a dozen workflows across every department, on a system its superintendent describes as one where every person involved knows exactly what they need to do, whether they are new to the role or have been there for years. For maintenance specifically, that means the process does not depend on the one person who has always handled it remembering how it goes.

Status is visible without asking anyone

Reported, assigned, in progress, waiting, done: the state of any request is something the office can look up, not a question that interrupts the custodian's day. The record of what was reported, when, what it took to resolve, and what it cost accumulates as the process runs, which is the history a business office needs when the budget conversation turns to why maintenance spending looks the way it does.

Common questions

Questions we hear from every business office.

How do school districts track maintenance requests without buying work order software?

Most small districts don't track them so much as absorb them: requests arrive by email and word of mouth, and the head custodian carries the list. It works until volume or turnover breaks it. The alternative isn't necessarily a dedicated facilities platform; it's a routed workflow built around how the district's maintenance actually runs, one entry point, explicit assignment, visible status, which delivers the tracking without another standalone system to license and learn.

Who should a teacher send a maintenance request to?

In a well-built process, the teacher doesn't have to know. They report the problem through the single request form, and the routing delivers it to whoever the district decided handles that kind of work. In buildings where codes are posted, they don't even have to find the form; scanning the code where they're standing is the report. The question itself is a symptom: any process where staff have to know the right recipient will lose requests every time the answer changes.

How does the head custodian assign work without everything going through their inbox?

From the queue. Requests land in one place, the custodian assigns each to the right person from there, and staff see what they've been assigned without a forwarded email chain. Philipsburg's head custodian runs delegation, staff communication, and status questions through the request workflow itself rather than around it.

What happens when the same problem gets reported by three different people?

With one entry point, the duplicates are visible as duplicates and collapse into a single item, instead of becoming three parallel efforts or three unanswered messages. This is one of the quiet costs of email-based reporting: the process has no way to know two reports are the same problem.

Do maintenance requests and vehicle or facility use requests have to be separate processes?

They're different processes with different approvers, and they should stay that way, but they don't need different systems. A repair request routes to maintenance staff; a request to use the gym on Saturday routes to whoever approves facility use. Each follows its own path. What they share is the model: one way in, defined routing, visible status.

How Flow Forms handles it

Flow Forms builds the district's actual maintenance process as a routed workflow: one entry point for every report, assignment run from the queue by whoever directs the work, routing that follows the district's own definition of who handles what, and status anyone authorized can look up without asking. Districts run building maintenance, mechanic shop work, and repair requests through builds shaped to their own operation, and the same team that built the routing stays on to adjust it when the operation changes.

See how it would work for your district →