Resources and facilities

School Maintenance Requests: Close the Job, Not Just the Complaint

A classroom fan has been reported three times. One teacher told reception, another sent a photograph to a colleague and a third mentioned it during a meeting. There are plenty of messages, but no single record of who is dealing with the problem. A repair request needs an owner and a next step, not just an audience.

SkoolMatic EditorialUpdated 4 min read
A facilities coordinator and maintenance worker reviewing a school corridor washbasin

Describe the location before the fault

“The upstairs tap” may be obvious to the reporter and meaningless to the person assigned to inspect it. Ask for a building, floor and room or fixture reference. Add a short description of the observed problem and when it occurs. A photograph can help if it avoids students and unnecessary personal information.

Keep the form small. Staff should not need to diagnose the cause or choose a technical repair code. “Water gathers below the basin after use” is a useful observation. The maintenance professional can determine whether the problem is a fitting, a blockage or something else.

Use a separate route for immediate hazards

A routine request queue should not replace the school’s urgent reporting procedure. If a problem presents an immediate risk, staff need a known contact and an appropriate way to keep people away while qualified help is arranged. Do not let an online form become a reason to delay reporting a dangerous condition.

Agree who assesses urgency and who can authorise outside support. Ordinary staff should report what they see rather than attempt electrical, structural or other specialist repairs themselves. The management record can capture the subsequent actions, but it is not a substitute for competent assessment of the physical problem.

Assign one owner even when several people help

A job may involve reception, a caretaker, a contractor and the accounts office. Give one person responsibility for following it through. Their role is to keep the next action visible, not necessarily to perform the repair. Without that owner, everyone can reasonably believe someone else is waiting for a quotation.

Use meaningful states such as awaiting inspection, awaiting approval, scheduled and awaiting confirmation. Add a brief reason when a task is blocked. “Waiting” by itself tells the principal very little; “replacement part ordered, expected Thursday” supports a useful decision about temporary arrangements.

Plan access around the school day

A repair can be technically simple and operationally awkward. Confirm when the room is available, who will open it and whether the work affects nearby classes. Give teachers enough notice to move materials or use another room where necessary.

Keep contractor visits within the school’s visitor and supervision arrangements. The maintenance entry should include the planned attendance and school contact, without replacing the established visitor process. If a visit is postponed, update the affected staff. An unchanged schedule can leave a classroom unnecessarily empty while everyone waits for someone who is no longer coming.

Confirm the result before closing the request

“Contractor attended” and “problem resolved” are different statements. Ask the appropriate person to check the result in normal use. For specialist work, retain the relevant completion information and follow the school’s agreed acceptance process. A teacher can report whether the classroom issue persists without being asked to certify technical safety.

Tell the original reporter when the job is closed or why further work is needed. If the same fault returns, link the new report to the earlier job. That history helps distinguish a recurring issue from several unrelated requests and gives the maintenance provider a clearer account.

Review recurring faults rather than only totals

A report showing twenty closed jobs may look reassuring while the same roof leak keeps returning. Review repeated locations, long waits and work that was reopened. Ask whether the school needs a planned repair, a better description or a clearer approval route.

Use a small weekly review to unblock outstanding tasks. Record the decision and the next check date. If adopting software, test assignment, postponement and reopening with sample requests before relying on its dashboard. A useful maintenance process makes responsibility visible from the first report through the final confirmation.

What schools should check

  • Location

    Identify the exact room or fixture.

  • Urgency

    Use the established urgent-reporting route for hazards.

  • Ownership

    Name one person to follow the job through.

  • Closure

    Confirm the result and notify the reporter.

Related questions

Should every maintenance issue go through an online form?

Routine requests can. Immediate hazards need the school’s urgent reporting and response process first; the record can be completed when it is appropriate to do so.

When should a repair request be closed?

Close it after the responsible person has received suitable confirmation that the reported issue was addressed. A visit or an invoice alone does not establish that the problem is resolved.

Explore the school software behind these workflows

Review the product workflow with your school team, then bring your current records and questions to a live demo.

Explore SkoolMatic school workflowsBook a Demo