In July, the two elevators at a 166-unit Washington, D.C. building stopped working. They were still out when the city’s attorney general sued the developer, citing what the complaint calls “extreme and pervasive disrepair,” including nearly 200 unresolved housing code violations, exposed electrical wiring, and unrepaired fire damage. Read the coverage, and the obvious question is why nobody fixed the elevators. That’s the wrong question. Buildings break. Elevators fail. The question that actually decided this case, and every case like it, is whether the owner could produce anything showing they knew and were doing something about it.
They couldn’t. That’s the pattern worth understanding, because it has almost nothing to do with elevators.
Buildings Failing Isn’t the Story. Unprovable Response Is.
Oakland is suing a landlord this year over a separate 98-unit building where a prolonged elevator outage left elderly and disabled tenants stranded, alongside allegations of pest infestations and unrepaired fire, water, and structural damage. Different city, different building, same underlying gap: not that something broke, but that nothing in either case shows the kind of documented, dated response multi-family inspection software is built to produce.
That distinction is the entire legal and financial ballgame, and most operators don’t treat it that way. A property manager who walks a building, spots a failing elevator relay, and mentions it to maintenance has, in their own mind, “handled it.” A court, a regulator, or an insurer reviewing the same situation eighteen months later sees something indistinguishable from a property manager who never noticed at all. Verbal awareness with no record leaves exactly the same evidentiary trail as no awareness. Zero.
The Same Leak, Two Paper Trails, Two Very Different Outcomes
Picture the same slow ceiling leak in two identical buildings. In the first, a resident mentions it in passing. The property manager makes a mental note, tells maintenance verbally, and the leak gets patched three weeks later when someone finally gets to it. Nothing was ever wrong here, exactly, the problem did get fixed. But six months later, when a tenant’s attorney or a city inspector asks what happened, there’s nothing to show them. No date, no photo, no record that anyone treated it as anything other than background noise.
In the second building, the same leak gets photographed and logged the day it’s noticed, flagged with a severity level, assigned a follow-up date, and closed out with a second photo once repaired. Both buildings fixed the leak in roughly the same timeframe. Only one of them can prove it. If either building ends up in front of a judge, an insurer, or a city attorney a year later over an unrelated issue, that difference in provable history is the difference between “an operator managing a building” and “an operator who got lucky so far.”
Insurers Are Asking the Same Question, Just Pricing It Instead of Litigating It
A court isn’t the only party demanding proof. An insurer renewing a policy is running the identical evidentiary test, just translated into a premium instead of a verdict: can this owner show a documented condition history, or only tell one? Multifamily property insurance costs have climbed roughly 58% over the past five years, now consuming close to 4.78% of revenue, up from under 2% in 2000, and carriers don’t publish their exact formulas, but the properties absorbing the steepest increases are disproportionately the ones with open claims or a maintenance history nobody can produce clean records for. Same gap the court is looking for. Different consequence for missing it.
What Multi-Family Inspection Software Actually Needs to Prove
This is the specific gap multi-family inspection software has to close, and it’s a narrower job than “catch more problems.” Any maintenance team eventually notices a failing elevator or a slow leak. The job is turning that moment of noticing into something that survives eighteen months and holds up to someone who wasn’t there: a photo, a timestamp, a status that updates as the issue moves toward resolution, attached to the specific unit or system, not buried in a text thread or a manager’s memory.
Multi-family property inspection software built around that discipline treats every flagged issue as evidence-in-progress, not a task that disappears once someone mentions it’s been handled. Across a 200-unit or 2,000-unit portfolio, that turns “we’re pretty sure we dealt with it” into a record an owner can actually hand to an insurer, a regulator, or opposing counsel, and have it mean something. A deeper look at how standardized multifamily inspections catch problems before they escalate covers the operational side of building that habit across a portfolio; the move-in/move-out inspection discipline most operators already run for unit turns is the same discipline, applied continuously to elevators, roofs, and plumbing instead of only at turnover.
The Real Test for Any Property Right Now
Not a checklist. One question: if a tenant, an insurer, or a city attorney asked about any specific issue in your building today, roof, elevator, plumbing, life safety, could you produce a dated record showing when it was flagged and what happened next? For most operators, the honest answer depends entirely on which property manager gets asked, and how good that person’s memory is on that particular day. That’s the exposure. Not the building’s aging.
If you want to see what a portfolio-wide, evidence-grade inspection record actually looks like in practice, book a demo.
You must be logged in to post a comment.