Australian student accommodation runs on a calendar nobody else uses, under tenancy rules that vary by state, and with a bond process that is decided almost entirely on the quality of your condition report. Operations software that was designed for a northern hemisphere September intake and a UK deposit scheme will get the shape of the year wrong from day one.
This guide covers what operations software has to do for an Australian operator, how bond claims actually get won, and what to check before you buy.
The main intake sits in late February, with a substantial second intake in July and a growing third in November. That gives you two large turnover waves rather than one, plus a summer over Christmas and January when domestic students leave and short stay and conference guests often move in.
Any system you buy has to generate turnover work from the actual lease dates in your portfolio, not from a fixed academic year assumption. If the cleaning plan is built around one annual turn, half your operational year is being managed by hand.
The condition report is the whole bond case. In most states the tenant is given a condition report at the start of the tenancy, has a short window to comment on it, and any later claim on the bond is judged against that document. If the entry report is thin, the claim is over before it is lodged.
That means photographs of every room and every priced asset at entry, signed off by the resident, and the same template used again at exit so the two records line up item by item. Fair wear and tear is expected and cannot be charged. A worn carpet after a year of ordinary use is not damage. A burn mark in it is, and the difference has to be visible in the photos.
Weekly communal and kitchen rotas run continuously, while room turnover cleans spike hard in February and again in July. A rota built by hand each week absorbs a supervisor's morning and still cannot answer which rooms were finished by mid afternoon.
Look for rotas generated automatically from occupancy and departure dates, live per room completion status on a phone, photo sign off on communal areas, and the ability to reassign a cleaner's list mid shift without rebuilding the day from scratch.
Australian operators frequently run buildings across several cities, with a small central team and contractors on the ground. That makes routing more important than volume. Every request should carry the building, unit, room and asset, a photo, and a priority band with a published response time, so a contractor in another state arrives prepared.
Urgent repairs are defined in state tenancy legislation and carry their own response obligations. Keeping those tickets in a separate, visibly tracked band is the simplest way to stay on the right side of them.
Students will not install an app to report a broken kettle. QR codes in the room that open in the phone browser, attach a photo and already know the asset are what actually get used. Early reports are cheap reports, and they arrive during the tenancy rather than surfacing at exit when nobody can be charged for them.
For the operator, the payoff is one weekly view across the portfolio: rooms ready by building, open jobs by age, and damage recovered against target, without anyone assembling a spreadsheet on Monday morning.
Campus Pilot is the operations layer next to whatever you already run for reservations, including RMS, Mews, a university housing system or a live Google Sheet. It does not hold your leases or your money, and it does not ask you to migrate them.
It generates cleaning rotas from real occupancy, runs maintenance and inspections on a phone, produces entry and exit condition records with paired photos, prices damage from your own asset list, and gives residents QR based reporting with no download. Pricing is per bed per month with everything included. See every feature and pricing, or book a demo and we will run it on your own buildings.
It is the system that runs the daily operation of a residence: cleaning rotas, maintenance requests, condition reports, damage and bond claims, and student communication. It sits next to the reservations or tenancy system, which holds the leases and the money, and manages everything that happens to the building and the staff.
By making the entry condition report complete and photographic, then using the identical template at exit so the two records compare line by line. Bond claims are decided on evidence, and most failed claims fail because the entry report was thin or the exit inspection used a different form. Published asset prices also stop the amount being argued over at exit.
No. It reads occupancy and departure dates from RMS, Mews, a university housing system or even a live Google Sheet, and manages the operational work that follows. The reservations system stays where it is, and there is no migration of leases, rent or student records.
Yes. Turnover work is generated from the actual lease dates in your portfolio rather than a fixed academic year, so both major intakes and the November intake are handled the same way, along with short stay and conference occupancy over the summer break.
A live walkthrough of Campus Pilot on your own buildings, reservations and checklists. Live within a week.
Book a demo →