Which request is quietly carrying the exposure. Whether anyone walked the building.
A maintenance operation is the requests that come in and the walking that goes out. Your property system keeps the first. The second lives in someone’s head. These two products cover both, and neither one writes a single field into your system of record.
Reads the daily work-order export you already run and hands your coordinator the day in order, with the reason on every line. The request that looks routine and is not is what Order is built to flag, from the first export.
See what Order does →For the field leads who walk a portfolio and the supervisors who need to see that the walking happened. A day built by the drive, one tap on site, and a coverage report that shows the buildings with no visit on record before it shows anything else.
See what Rotation does →It runs on the request your maintenance system already created. Order sits alongside Yardi, RealPage or AppFolio — it never replaces them, and it never writes back to them.
That arrives in your system as an HVAC ticket, filed behind eleven other HVAC tickets, sorted by the day it came in. The building it sits in is not the same as the other eleven. Nothing in the queue is capable of telling you that.
The day already in order, and a plain-language reason for it — one they can act on immediately and repeat to a supervisor without translating anything. Order suggests. Your team decides what gets dispatched.
Nobody on your team has to go looking, property by property, or notice when something changes. Keeping that reference material current is the part we own. It is most of what you are actually buying.
It does not dispatch. It does not close tickets. It does not write a single field back into your system of record — not now, not in a later release. Order produces an identified risk, a suggested tier and a cited basis; a person decides. If Order is down, your maintenance operation runs exactly as it does today. That is the whole design, and it is why it can be trusted with the question it answers.
Every one of these houses someone who cannot simply leave when a repair is slow. That is what turns an ordinary maintenance backlog into something more expensive.
Market-rate, rent-stabilized and subsidized housing. Habitability timelines that shift by city, relocation obligations that attach when a home becomes uninhabitable, and the subsidy-program deadlines that override both. The vertical Order was built in first.
See how it applies →Residence halls and purpose-built communities, on campus and off, where every unit empties and refills in one window and the queue fills overnight. A smoke detector in a building where students sleep is not the same item as one in an office, and the queue does not say so. When the institution asks about a repair from October, the answer should be a record.
See how it applies →Assisted living and memory care, where the maintenance queue and the licensing file turn out to be the same document. A surveyor reads a delayed repair differently than a work-order system does, and the difference does not show up until the survey.
See how it applies →Facilities operating under consent decrees and monitor scrutiny, where cell conditions, heat, water and life-safety faults carry constitutional weight. The population cannot leave, which is exactly why the response window is the whole question.
See how it applies →Not decoration. These are architectural commitments, not settings — which is the only reason they are worth printing.
Order does not price your risk. It tells you which request is quietly carrying it, while there is still time to do something about it.
A daily work-order export out of Yardi, RealPage or AppFolio. Read-only, and mapping your columns is configuration rather than engineering. Nobody has to install anything, and nothing changes inside your system.
Publicly available requirements are tracked per property, and updated as they move. Building that and maintaining it is our job, permanently. Your team never has to go find it, keep it, or notice when it changes.
Each morning: what is running closest to its window, what it may cost, and the reference material behind the flag so your team can check it. Your team decides what gets dispatched. Order has no opinion it can act on.
Send one daily export and a work order you already know was handled too slowly. Inside a week you are looking at your own queue, ranked, with the reason on every line — and you will know whether that one came up.