A cleaning schedule for student accommodation has to cover three different jobs at once: the weekly clean of shared kitchens and bathrooms, the deep clean and turnover of rooms between students, and the reactive cleans that come from complaints and inspections. This template covers all three.
The weekly communal cycle is the predictable one: shared kitchens, corridors, bathrooms, laundries and social spaces, cleaned on a fixed rota that repeats through the term. The turnover cycle is driven by the calendar of arrivals and departures, and covers the deep clean, the linen change and the inspection between one student leaving and the next moving in.
The reactive cycle is everything else: a spillage in a kitchen, a complaint from a floor, a failed inspection, a viewing booked at short notice. Most schedules only plan the first cycle properly, which is why the other two end up being handled by whoever happens to be nearby.
Block the rota by building and floor rather than by individual room, so a cleaner walks one route instead of criss-crossing the site. Put kitchens on fixed days, because they are the biggest source of complaints and students behave better when they know the kitchen is checked on a Tuesday. In high-occupancy blocks, shared bathrooms need a daily pass, not a weekly one.
Then publish the rota where students can see it, on the noticeboard and in the resident app. When students know when the cleaner is coming, the space is cleared in advance, the clean takes less time, and the complaints about missed areas mostly stop.
A turnover clean should be triggered by the check-out date in your occupancy data, not by a supervisor noticing that a room is empty. That single change removes most of the delay between a departure and a room being ready to sell again.
Use a standard checklist per room type, so an en-suite studio and a cluster bedroom each have their own defined scope rather than a general instruction to clean the room. Inspect after the clean, not before the next arrival, and record photo evidence of the finished state so a dispute about condition at handover has an answer already on file.
Occupancy changes daily during intake. Students arrive early, defer, swap rooms and leave without telling anyone, so a rota built on Sunday is out of date by Wednesday. Cleaners work from a printout that is already wrong, and there is no way to correct it from the corridor.
Nobody can see what was actually done, only what was planned, so the manager finds out about a missed room when a complaint arrives. In peak weeks the complaints arrive before the rota catches up, and the team spends the term firefighting instead of running the plan.
In a self-planning schedule the plan is generated from occupancy and check-out dates rather than typed out by hand. Each cleaner opens today's list on their phone, works through it, and marks each room done, with inspected and photo states recorded against the room itself. The housekeeping manager sees what is late while there is still time to move somebody, not the following week.
Campus Pilot works this way and cuts the time housekeeping managers spend planning to close to nothing, because the schedule rebuilds itself every night from live occupancy. See every feature, or book a demo to see it running on your own buildings.
Two pages: a weekly communal rota grid from Monday to Sunday by area, with cleaner and sign-off columns, plus a turnover clean checklist per room with an inspection sign-off.
Download the cleaning schedule template (PDF)Most operators clean shared kitchens two or three times a week, and daily in high-occupancy blocks or during intake weeks. The important part is a fixed, published day and time, because students clear the surfaces in advance when they know the clean is coming, and a kitchen on a known schedule generates far fewer complaints than one cleaned whenever there is a gap.
In most tenancy agreements the student cleans their own room during the stay, while the operator cleans communal areas and carries out the turnover clean between tenancies. Some premium and long-stay products include a periodic in-room clean. Whichever model you use, define it in the tenancy pack and reflect it in the rota so expectations and scheduling match.
Drive the schedule from the check-out date on each booking rather than from a single end of term date. Each departure creates a turnover task automatically for the day the room becomes free, the tasks are grouped by floor to keep the route sensible, and the inspection follows the clean. That is exactly what the second page of this template is for.
Yes. Coliving and long-stay accommodation run the same three cycles, usually with a heavier weekly communal load and fewer, larger turnover peaks. Keep the rota grid as it is, adjust the room types on the turnover checklist, and the structure works without further changes.
A live walkthrough of Campus Pilot on your own buildings, reservations and checklists. Live within a week.
Book a demo →