How to build a school maintenance and facilities request tracker

In most schools, a broken heater gets reported in a hallway conversation, a leaking sink gets an email to the custodian, and a projector that will not turn on goes on a sticky note. The facilities team works hard, but the requests arrive through five channels, nobody can see what is already reported, and teachers have no idea whether anyone heard them. The same problem gets reported four times, and the one that matters most waits behind the one that was mentioned loudest.

A facilities request tracker brings every request into one queue. This guide covers what the current way costs, exactly what the tracker should include, an example request you could hand to FORGE, a rollout plan for a school or a district, mistakes to avoid and how to measure progress.

What the current way costs you

• Requests get lost. Emails sit in one person's inbox. Hallway requests depend on memory. When the custodian is out, nobody knows what was promised.
• Duplicates waste time. Without a shared view, three teachers report the same broken water fountain and the team chases three tickets for one problem.
• No priority. The urgent and the cosmetic arrive the same way. A loose stair rail can sit behind a request to move a bookshelf.
• No feedback loop. Teachers never hear back, so they assume nothing happened and ask again, or stop asking at all.
• No history. When the same roof leak returns every spring, there is no record of how many times it was patched or what it cost. That makes the case for a real repair hard to argue at budget time.
• Heavy software for a small team. District-scale facilities systems can be expensive, complex and built for a staff much larger than a typical school's custodial and maintenance crew.

What the tracker should contain

The request form

The form has to be quicker than an email, or staff will keep emailing. Keep it to:

• What is wrong, in a sentence
• Category: plumbing, electrical, heating and cooling, custodial, grounds, furniture, technology, safety, event setup, other
• Location: school, building, floor and room, chosen from a list, not typed
• A photo, taken right from the phone
• Whether it is a safety issue, with a short explanation of what counts
• The requester's name and contact, filled in automatically

Before the form submits, it can show open requests for the same room so a teacher can add "me too" instead of filing a duplicate.

The work order queue

Every request becomes a work order with:

• A priority level, set by the facilities lead or suggested from the category and safety flag
• An assigned technician or custodian
• A target date based on priority
• A status
• Notes, parts used, time spent and after photos
• A link to any related requests for the same room or asset

Priorities that work for most schools:

Statuses

1. New: submitted, waiting for review
2. Assigned: has a technician and a target date
3. In progress: work has started
4. Waiting on parts or vendor: paused for a known reason, with the reason shown
5. Completed: work done, after photo attached
6. Closed: requester confirmed or the facilities lead closed it
7. Not approved: outside scope or needs a different process, with an explanation

The requester sees every status change. That one feature does more for staff trust than anything else in the tool.

Event setups and room needs

Schools also run on setups: chairs for an assembly, tables for a science fair, a gym ready for a game. These are requests with a date, start and end time, room, layout, equipment and number of people. The facilities team sees them on a calendar next to repair work so they can plan staffing, especially for evenings and weekends.

Assets and recurring work

For the equipment that matters most, such as boilers, rooftop units, fire extinguishers, playground equipment and kitchen appliances, keep an asset record with location, install date and service history. Recurring checks, like monthly extinguisher inspections or filter changes, can generate work orders on a schedule so they never depend on memory. Inspection and safety requirements vary by state and district, so confirm which apply to you with your district office or local authority and build those checks into the schedule.

Roles

Notifications

• Requester: when the request is assigned, when it is done, and if it is paused or not approved
• Facilities lead: immediately on any emergency or safety flag
• Technician: when a new order is assigned to them
• Principal: a weekly summary of open requests at their school

Reports

• Open requests by school, priority and age
• Average time to close by priority and category
• Requests per room and per asset, to spot repeat problems
• Work by technician, for fair workload planning
• Setups scheduled for the coming week
• Labor and parts by building, for budget conversations

Example request

Here is an example of a plain-words request a district facilities director could hand to FORGE. Change the schools and rules to match yours.

"We have four schools: two elementary, one middle and one high school. Build a maintenance and facilities request tracker. Any staff member can submit a request from their phone or computer by choosing the school, building and room from a list, picking a category, describing the problem and adding a photo. Before they submit, show any open requests for that room so they can add on instead of duplicating. If they mark it as a safety issue, text the facilities lead for that school right away. The facilities lead sets the priority (emergency, urgent, standard, low or planned) and assigns it to a custodian or technician, who sees their queue on their phone, adds notes and an after photo, and marks it done. The person who asked gets a message at every step. Event setups are a separate request type with a date, times, room and layout, shown on a calendar. Principals see everything at their school. I see every school, with reports on open requests by age, average time to close by priority, and rooms with more than three requests in 90 days."

Rolling it out

1. Map your locations. List every building and room in a clean list. Room numbers that match the signs on the doors save a lot of confusion.
2. Agree on categories and priorities. Write two or three real examples for each priority level. Share them with principals.
3. Load your current open work. Put every known open request into the tracker so it starts with the truth.
4. Train the facilities team first. They need to be comfortable with their phone queue before requests start arriving.
5. Launch at one school. Tell staff in a short meeting and an email with a link. Show the photo button and the status updates.
6. Answer every request through the tracker. When someone emails or stops a custodian in the hall, the custodian enters it or points them to the form. Consistency is what makes it stick.
7. Add the other schools. Bring each principal and facilities lead on with their own walk-through.
8. Add recurring work and assets. Once requests are running smoothly, schedule the recurring checks.

Mistakes to avoid

• A long form. Every extra required field sends teachers back to email.
• Typed locations. Free text gives you "Rm 12," "room twelve" and "Mrs. Lee's room" for the same place. Use a picklist.
• Silent tickets. If the requester never hears back, the tool has failed even if the work got done.
• No emergency path. The tracker is not a replacement for calling someone when there is a gas smell. Put the emergency phone number right on the form.
• Closing without proof. An after photo settles "was it really fixed" in seconds.
• Ignoring patterns. The reports on repeat rooms and assets are where the budget case for real repairs comes from. Review them each term.

How to measure that it works

Launch checklist

1. Clean list of schools, buildings and rooms
2. Categories and priorities with written examples
3. Emergency phone number on the request form
4. Facilities team invited with roles and trained on their phone queue
5. Existing open work entered
6. Requester notifications tested end to end
7. Pilot school launched with a staff walk-through
8. Principals shown their school view
9. Other schools added one at a time
10. Recurring checks and key assets loaded
11. Reports reviewed at the end of the first term

How FORGE handles it

With FORGE, your facilities director describes the buildings, categories and priorities in plain words and gets a working tracker back, and most teams have their first real tool the same day. A panel of top AI models plans it around your schools and roles, a dedicated AI crew builds it, and every piece is checked for quality and security before it is saved. Staff submit from a phone or a laptop, custodians work their queue on their phones, and the district office sees every site on the web.

The tracker lives inside your organization. People join only by invite, each role sees only what it should, and there is a complete record of every change. Teachers and staff who only use the app are free, so you can open it to everyone on campus without adding per-user fees. When you add a building or a new request type, you describe it and the tool follows; changes cost a small fraction of a build and only count when something changes. Our team onboards every school or district ourselves, starting with a workflow workshop. Talk to us or see use cases.

Questions people ask