The conversation about school facilities management usually starts with preventative maintenance — schedules, asset tracking, deferred work backlogs. Those things matter. But there's a step that comes before all of them that almost never gets the attention it deserves: how problems get reported in the first place.

Work order intake — the process by which a teacher, administrator, or kitchen staff member reports a facilities problem — is the entry point for the entire reactive maintenance operation. And in most schools, that entry point is broken. Not catastrophically broken, not obviously broken, but chronically broken in ways that accumulate into real operational and financial costs that almost nobody is tracking.

How most schools actually handle work order intake

Walk into the average school building and ask how someone reports a facilities problem. The answer will usually involve some combination of: telling someone in the front office, calling or texting the facilities department directly (if they have the number), sending an email that may or may not reach the right person, or just waiting until the issue becomes bad enough that it can't be ignored. In some cases, the problem gets written on a sticky note on a door. In others, it gets mentioned in passing at a staff meeting.

What doesn't happen: a structured submission through a consistent channel that creates a logged, timestamped record, routes the request to the right person, and gives the reporter visibility into what happens next.

"A facilities problem that gets reported informally is a problem on a timer. Every day between the report and the work order is a day the issue gets worse — and a day no one is officially tracking it."

The informal system creates several compounding problems. First, reports get lost. A text to the facilities tech's personal phone doesn't create a work order. An email to the front office that gets forwarded doesn't generate a tracked ticket. Problems fall through the cracks not because anyone is careless, but because the system has no structure to catch them.

Second, problems get reported late. When the reporting mechanism is inconvenient — when it requires finding a specific person, knowing a phone number, or navigating a clunky online form — people delay. They wait until the leak is more than a nuisance, until the light fixture is fully dead rather than just flickering, until the HVAC problem has been mentioned three times before anyone submits it. By then, the small preventable issue has often become a larger one.

The three costs of bad intake

The costs of poor work order intake are real but scattered across a facilities budget in ways that make them hard to attribute to the root cause.

The first cost is issue severity. Problems that get reported quickly tend to be small. Problems that get reported late tend to be large. A refrigerant leak reported the day a teacher notices a warm classroom is a service call. The same leak reported three weeks later — after it's been mentioned informally to a few people but never formally submitted — is a compressor replacement. The actual maintenance cost of the issue scales directly with how long it goes unaddressed, and intake quality controls how long that is.

The second cost is technician efficiency. When work arrives through informal channels, technicians spend significant time just processing intake: figuring out what the actual problem is, where it's located, how long it's been happening, and who to call back with questions. A well-structured work order answers all of those questions before the technician leaves the facilities office. An informal report often doesn't.

31%
of technician time in school facilities is spent on administrative tasks related to work order processing — finding information, following up on vague reports, and resolving routing errors — rather than on actual maintenance work.

The third cost is invisible backlog. When work orders aren't logged consistently, facilities leadership has no accurate picture of what's actually pending, how long issues have been open, or which buildings are generating the most reactive work. The backlog is real — it's just invisible. It lives in texts, emails, sticky notes, and people's heads rather than in a system where it can be seen and managed.

What good intake actually looks like

A good work order intake system has three properties. It's accessible, structured, and visible.

Accessible means that anyone in the school building — teacher, custodian, kitchen staff, office administrator — can submit a work order easily from wherever they are. A QR code posted in each room that opens a submission form on a phone. A link on the school intranet. Frictionless enough that reporting a problem takes less time than writing a sticky note about it.

Structured means the submission form captures the information that actually matters for routing and resolution: the location (specific room, not just "the gym"), the nature of the problem (a brief description plus a category), and the reporter's contact information for follow-up. Not a lengthy form that discourages submission — four or five fields that take thirty seconds to complete.

Visible means that once submitted, the work order exists in a tracked system that both the reporter and the facilities team can see. The teacher who reported a leaking ceiling knows the issue was received and is pending. The facilities director can see all open tickets by building, by category, by age. Nothing falls through the cracks because the cracks don't exist — every report has a record.

Work Order Intake Checklist

What a functional intake system requires

  • Submission accessible by phone without requiring login or app download
  • Form captures: location, problem type, description, submitter contact
  • Automatic confirmation sent to submitter with ticket number
  • Work orders route to the right person automatically by category or building
  • Facilities team has a single queue — no reports living in email or text
  • Submitter can check status without calling the facilities office
  • Director has visibility into open orders by building, age, and type

Intake as the foundation for everything else

Here's why intake matters beyond its immediate operational value: it's the data layer for everything else in facilities management. Every trend analysis, every budget justification, every assessment of whether a PM program is working — all of it depends on having accurate records of what maintenance work is actually being done and why. If a significant portion of reactive work arrives through informal channels and never gets logged, that data doesn't exist. The picture of the operation is incomplete.

A school that has solid work order intake for two years has something genuinely valuable: a record of which buildings generate the most reactive work, which equipment categories account for the most service calls, which months are historically busiest, and which locations have chronic problems that haven't been addressed at the root cause. That data is the foundation for making the case for capital repairs, for prioritizing PM investment, and for demonstrating the ROI of a maintenance operation to a school board.

None of that is possible if the intake system is broken. The work is still happening — the technicians are still fixing things — but the record isn't being kept. The operation remains invisible to everyone except the people doing the work.

Getting intake right isn't glamorous. It doesn't get mentioned in vendor demos the way asset tracking dashboards do. But for most school facilities teams, fixing how work gets reported would do more to improve operational outcomes than almost any other single change.