Why "I Fixed It" Isn't Enough: How Courts Actually Evaluate Maintenance Records

What Do Courts Look For in Maintenance Documentation?

Courts don't ask "did you fix it?" They ask three questions, and most PMs can only answer one.

When were you notified? The clock starts when the work order comes in, not when somebody gets around to reading it. If a tenant submits a request on Tuesday and your coordinator doesn't see it until Thursday, those two days are on you. I've seen landlords lose habitability cases over 48-hour gaps between request submission and first response.

What steps did you take, and when? This is where "I fixed it" falls apart. Saying you dispatched a vendor isn't the same as proving when the vendor arrived, what they did, and when they finished. You need timestamped entries, not a retroactive note someone typed up three weeks later when the attorney's letter arrived.

How fast did you respond relative to the severity? A leaking faucet and a gas smell get different response windows, and courts know the difference. If your documentation shows you treated a potential carbon monoxide issue with the same urgency as a squeaky cabinet hinge, that's going to be a problem.

The "Reasonableness" Standard

Most property managers think the legal question is binary: did I fix it or didn't I?

Courts don't work that way. They use a reasonableness standard, and "reasonable" depends entirely on what you can demonstrate with records.

I learned this during a habitability dispute in 2023. Tenant claimed we'd ignored a recurring mold issue for four months. We hadn't ignored it. We'd sent vendors three times. But our documentation was a mess. One visit was logged in a spreadsheet. Another was in a text thread with the vendor. The third was a handwritten note our maintenance coordinator kept in a spiral notebook.

Three visits, three different systems, zero credibility. That's the kind of documentation breakdown that kills you in court.

The judge didn't say our records were false. She said they were unreliable. Cost us about $18,000 in settlement plus legal fees.

A court-admissible maintenance record needs to come from a consistent system, not scattered notes assembled after someone sues you. Regular entries, timestamped automatically, stored in one place. That's what judges mean when they evaluate whether records are "kept in the ordinary course of business." Ad-hoc documentation created after a dispute starts gets thrown out as self-serving.

Your Verbal Testimony Won't Save You

Your word doesn't carry much weight against a document. A timestamped work order with GPS verification and before/after photos will outweigh your testimony about what you "remember" happening. Every time.

I had a case where my maintenance tech swore he'd replaced a smoke detector battery during a routine check. No photo. No timestamp. No work order entry. The tenant's attorney asked one question: "If the battery was replaced, why isn't it in your records?"

We couldn't answer that without sounding like we were making excuses.

If it's not in the system, it didn't happen. At least not in a courtroom.

The Four Records That Matter in Court

I've been through enough disputes to know which records attorneys grab first.

The intake record. When did the request come in, from whom, and what did they report? Exact words matter. "Leaking faucet" and "water everywhere" are different emergencies, and if your intake log says "plumbing issue," you've already lost context a judge would want.

The dispatch-to-completion chain. This is the audit trail most PMs don't have. A continuous, timestamped sequence from when you assigned the vendor to when they checked in on-site, finished the work, and you verified the result. Gaps in this chain are where attorneys live. I had an HVAC vendor confirm a repair twice by phone but never check in through our system. When the tenant claimed the work wasn't done, we had his verbal promise and nothing else. That verbal promise was worth exactly zero in mediation.

Before-and-after evidence. Photos with metadata — location, timestamp, who took them. Not photos your vendor texted you from an unknown number that you saved to your camera roll. I'm talking about documentation tied to a specific work order, taken at the job site, stored permanently. We use GPS-verified work orders for this, and it's the single best change we've made for defensibility.

Communication logs. Every text, email, and call with the tenant about the issue. Courts want to see that you acknowledged the problem and communicated your plan. Silence between the request and the fix looks like negligence, even when you were actively working on it.

If you've got all four for every work order, you're ahead of 90% of property managers I know.

When Records Are Missing: Adverse Inference

Missing records don't weaken your case. They can destroy it.

Judges can issue what's called an "adverse inference," telling the jury to assume the missing records would've been bad for you. You could have responded in 20 minutes, sent the best vendor in town, fixed the issue perfectly. But if you can't prove it, the court instructs the jury to assume the opposite.

I watched a PM lose a $27,000 habitability claim because his work order system had been offline for two weeks during a software migration. The work got done. His vendors confirmed it, his tenants confirmed it. But the records gap made his entire documentation system look unreliable, and the judge weighed that absence against him.

You can't afford gaps. Not for a day, not during a migration, not for a "we'll enter it later."

The Response Time Trap

Response time documentation trips up more PMs than any other single issue.

You might have a 24-hour SLA for non-emergency requests. You might even meet it consistently. But if your records don't show the timestamp between request received and vendor dispatched, you can't prove it.

And inconsistent response times across units can trigger fair housing scrutiny. If unit 4B's leaky pipe got a same-day response and unit 7A's identical issue took four days, you'd better have a documented reason for the difference. Fair housing investigations look at patterns across your portfolio, not individual incidents.

I track response time by category: emergency (under 2 hours), urgent (under 24 hours), routine (under 72 hours). Every work order gets classified at intake. Last quarter we flagged 11 tickets that missed their SLA window, and 8 of those were vendor no-shows we wouldn't have caught without automatic timestamp tracking. If we miss the target, I want to know why before someone else asks.

Documentation Is Audit Prep

Most PMs I talk to treat documentation as administrative overhead. Something their coordinator handles. Something they'll "get to" later. Something that doesn't generate revenue so it sits at the bottom of the priority list.

That's a $18,000 mistake waiting to happen.

You're building your legal defense on every single work order. Every time your tech finishes a job without uploading photos, every vendor who checks out without a timestamp, every work order that sits open for days without an update, that's the gap an attorney will walk through.

I've stopped thinking of maintenance documentation as a task and started thinking of it as audit preparation. A platform like Revoscape automates the timestamps, GPS verification, and photo requirements so your crew captures evidence without extra steps. But even if you're using spreadsheets, the mindset matters: every work order is a potential exhibit.