Most maintenance in student housing does not fail because nobody fixed it. It fails because nobody ever saw the request. A resident mentions a dripping tap to whoever is on the desk, the desk staff member goes off shift, and the tap keeps dripping until it becomes a ceiling repair three floors down.
This page sets out what a maintenance request actually needs to contain, how to triage requests once they arrive, and how to close the loop with the resident. There is a printable form template at the bottom you can use tomorrow morning.
In a typical residence a request can arrive through at least five channels: the front desk, a shared email inbox, a text message to a manager, a comment to a cleaner in the hallway, or a message in a resident group chat. None of those channels talk to each other, none of them timestamp anything, and none of them survive a shift change.
The result is not a maintenance problem, it is a routing problem. Work gets done quickly when it reaches the right technician with the right information. It sits for weeks when it reaches a person rather than a queue.
A request that can be actioned without a follow up call contains seven things. Anything less and a technician has to chase the resident before any work can start, which is where most of the delay actually lives.
Once requests are in one queue, sort them into three bands with published response targets, so residents and staff share the same expectations. Emergencies are anything involving safety, security, water or heat loss: no hot water, a failed door lock, a flood, a gas smell, no power. Respond within four hours and attend the same day.
Urgent requests affect habitability without being dangerous: a broken fridge, a blocked shower drain, a failed light in a stairwell. Respond within 24 hours, complete within three days. Routine requests are everything else, including cosmetic damage and slow drains. Acknowledge within 24 hours, complete within seven days. Publish those targets and then measure yourself against them.
The single biggest driver of complaints is not repair time, it is silence. A resident who is told the ticket was received, then told when someone is coming, then told it is done, will accept a slower fix than a resident who hears nothing for four days and reports it again through a different channel.
Send three updates per ticket at minimum: received with a reference, scheduled with a window, and completed with a note on what was done. If a part is on order, say so and give a revised date. Duplicate reports drop sharply once residents can see that the first one landed.
Four numbers tell you whether maintenance is under control. Open tickets, tracked by age rather than count, because 40 tickets all opened this week is a healthy building and six tickets open for a month is not. Average time to close, split by priority band, so an emergency response target that is quietly being missed becomes visible.
Then repeat issues per unit, which surfaces the shower that has been fixed four times and needs replacing, and first time fix rate, which tells you whether technicians are arriving with the right part. Those four numbers turn maintenance from a stream of complaints into a budget conversation you can win.
A paper form is a good start and a poor system, because someone still has to type it up. In Campus Pilot every asset carries a QR code, so a resident scans the boiler, the fridge or the shower and the request already knows the building, the unit, the room and the asset before they type a word. They add a photo and a sentence, with no app download required.
The request is routed automatically to the right team at the right priority, the resident gets updates as the ticket moves, and repeat issues are visible against the individual asset rather than buried in a list of tickets. See every Campus Pilot feature, or book a demo and we will run it on your own buildings.
One page: a printable resident request form covering unit, location, issue, urgency, photo reference, permission to enter and contact details, plus a triage table with response targets for your staff.
Download the maintenance request form (PDF)Thanks. Here is your template, and a copy is on its way to the team.
Download the maintenance request form (PDF)Unit and building, the location inside the unit, a plain description of the issue with the asset named, the urgency, a photo, permission to enter when the resident is out, and contact details. Those seven fields let a technician arrive prepared instead of calling the resident back first, which is where most of the delay in student housing maintenance actually sits.
Anything involving safety, security, water or heat: a flood, a gas smell, a failed door lock, no power, no hot water in winter. These should be responded to within four hours and attended the same day. Everything else falls into urgent, meaning habitability is affected, or routine, which covers cosmetic and non-blocking issues.
Acknowledge every request with a reference and then send updates when it is scheduled and when it is done. Duplicate reports are almost always a symptom of silence rather than impatience. Once residents can see that the first report landed and is moving, the second and third reports through other channels stop arriving.
It is better than a hallway conversation, but someone still has to transcribe it and route it, and that step is where requests disappear. A QR code on the asset removes the transcription entirely, because the building, unit, room and asset are already attached before the resident types anything.
A live walkthrough of Campus Pilot on your own buildings, reservations and checklists. Live within a week.
Book a demo →