Every repair in your building,
on one record
Tenants report it. You assign it. The crew checks in on site. Every step lands in the same place.
- Reported
- Booked
- Attended
- Closed
Tenants report it themselves
A code in the lobby opens a form in ten languages. Eight questions, one at a time. The form reads what the tenant typed and picks the category for them, so the request arrives sorted.
A screenshot of the tenant request form on step 2 of 8, asking what kind of problem it is. The heating option is pre-selected and tagged as the closest match to what the tenant typed. One queue, split by what is wrong with it
Work nobody has taken sits apart from work that has run late. Those are different failures and they need different answers. Assign or schedule from the row you noticed it in.
A screenshot of the resident manager’s queue. Two bands group the work: four unassigned jobs, then eight overdue ones. Each row shows the apartment, what is wrong, how late it is, and a single button to assign or schedule it. Visits book into fixed slots
Five two-hour slots a day, in the building calendar rather than a separate tool. Book one while the tenant is still on the phone. Anything without a time sits beside the week so it cannot be forgotten.
A screenshot of the building’s week calendar. Five fixed two-hour slots run down the left, Monday to Friday across the top, and four booked visits sit in the grid tinted by urgency — red for the emergency in 9F, amber for the leak in 12A, green for routine work. The crew checks in and out
One press on arrival, one on the way out, with a result: done, or nobody home. You can see which apartments have somebody in them right now.
A screenshot of a handyman’s phone. Two jobs for today: the first is in progress with a Check out button and a call button, the second is booked for 10am with a Check in button. Every job closes as a record
Who was told, who went, when they stood in the apartment, what they found, and what the tenant said afterwards. It gets written as the work happens, so nobody reconstructs it later.
A screenshot of a finished work order’s history: assigned by the resident manager on Monday, checked in and checked out by the handyman on Tuesday with a note about the valve, and confirmed by the tenant that evening.
What it takes to run it
Nothing to migrate
The record starts the day you begin. Load your units and your crew, and the first request can be filed that afternoon.
No account for tenants
They scan a code and fill in a form. The status link they get back answers most of the calls your desk takes.
A screen for each role
Managers, crew, front desk and view-only oversight each get their own. Adding somebody to the crew does not change what you pay.
Put a building on it and see
Every screen on this page is the running product. Watch one repair travel six of them, from the tenant’s first message to the closed record, or write to us and we will set your building up and walk your team through it.
Or write to [email protected]. A person reads it.
Lucas is built by Couwed, which is the name on that inbox.