Maintenance
From a tenant report to a paid invoice, with the owner able to follow.
Maintenance is where property managers earn their reputation and lose their margin. A tenant reports a broken boiler, and what follows is a chain of calls, quotes, appointments, approvals and invoices that usually lives in someone inbox.
REOS turns that into a ticket on the unit, with priority, tenant, owner, vendor, photos, quote, intervention and invoice. The owner sees the cost and the outcome in the portal, so the annual argument about maintenance spend is replaced by a list of resolved tickets with amounts.
What it does
- Tenant reporting with photos, routed to the right property manager.
- Vendor directory with trades, coverage areas and response history.
- Quotes, approval thresholds and owner authorisation when required.
- Scheduling of interventions with access arrangements.
- Cost tracking per unit and per building, feeding the finance layer.
What it automates
- A ticket above the approval threshold is routed to the owner for authorisation before work is ordered.
- A vendor does not respond within the agreed window and the ticket escalates.
- A ticket closes and the invoice flows to the owner statement with the full history.
Records behind this module
These are the actual tables in the platform. Every other module reads the same rows, which is why nothing needs reconciling.
Metrics it produces
- Open tickets
- Average resolution time
- Cost per unit
- Vendor response rate
Frequently asked questions
Can tenants report issues without an account?
Do vendors get access?
Ready to see it on your own portfolio
A demo runs on a structure that looks like yours: your unit count, your mandate model, your portals. Forty five minutes, no slide deck.