Your crews are the only people inside every property on a schedule — so they find the snapped hinge, the cracked deck board and the ants before anyone else does. Rinsebase turns what they find into a repair visit with a name, a date and a record, on the same schedule as your cleans.
The incidents feed: what crews filed today, with their photos, and the repair visit already booked for the ones that need one.
It's 11:40 on a Saturday turnover. Your lead sends you a photo of a hot tub cover with the hinge strap snapped and a text: "cover won't latch." You forward it to your handyman. He sends a thumbs-up. Then nothing — no date, no name, nothing anyone else can see.
Two turnovers later a different crew finds the same cover and sends the same photo. Was it fixed and broke again? Was it never fixed? Is it on the property manager's list or yours? Nobody knows, because the only record is a camera roll and a group chat.
That is how small repairs become guest complaints: not because nobody noticed, but because noticing never turned into anyone's job.
Your crew files an incident from the crew app while they're standing in front of the problem: the room, what kind of problem it is, a description and photos. It lands in one feed alongside your lost & found and linen issues, attached to the property and the clean it came from — and, when the calendar has it, the guest who just checked out.
On the incident, Schedule repair opens with the visit already written: the property, the room and the problem in the title, the crew's description and photo in its notes. Pick the day, the start time, how long it takes and who's going — and it's on the schedule.
Schedule repair on a pest report: the title, the property and the crew's photo come from the incident.
The incident shows the visit's progress straight from the visit itself, so nobody updates two places. You mark the incident resolved when the work is done.
A repair visit sits on your Schedule at the property, with your tech's name on it — next to the cleans and the inspections, not in a separate system nobody opens. Repairs and other tasks read teal, inspections magenta, so one look at the week tells you who is where, and why.
Two weeks by crew: the maintenance tech's repair visits and the inspector's visits in their own lanes, beside the cleaning crews.
On the crew app the visit carries the property's address and directions, and when your tech completes it, they're asked what they did. That line is what shows up on the incident and in the log.
When a property manager asks whether the deck board by the grill was ever fixed, the answer is one screen away. The Repairs view lists every visit booked from an incident — open, done, or all of them, filtered by tech — with when it was, who went, and what they wrote when they finished.
The Repairs view for one tech: three visits booked, three done with notes — and one flagged because its incident was resolved while the visit was still on the schedule.
For a property manager, operations means cleaning and maintenance. A cleaning company that only reports problems is a vendor. One that finds them, books the fix and can show the record of every repair is the partner that gets renewed — and gets handed the next twenty units.
"A customer asked me the obvious question: her crews were already finding the problems, so why did the fix still live in her texts? This is the answer. On the call we'll set up your maintenance tech and walk one incident from a crew's phone to a finished repair."
A 30-minute call with the founder: we'll set up your maintenance tech, walk an incident from the crew's phone to a booked repair, and show you the log — on your own properties.
14-day free trial · No credit card · Priced by crew, never per work order · Unlimited properties