The Business Records Doctrine: Why Your Documentation System Determines Admissibility

What Is the Business Records Doctrine in Property Management?

The business records doctrine is the legal rule that determines whether your maintenance logs, work orders, and vendor records are admissible as evidence or excluded as hearsay.

Under federal law (FRE 803(6)) and state equivalents like California Evidence Code §1271, a record qualifies as a business record only if it meets four elements: it was made at or near the time of the event, by someone with direct knowledge, as part of a regularly conducted business activity, and kept as a regular practice of that business. Miss any one of those four, and your records are hearsay. Inadmissible, no matter how accurate they are.

This matters more than most PMs realize. I've talked to attorneys who estimate that 60-70% of property management records they see in litigation wouldn't survive a hearsay objection. The records exist. The information is correct. But the system that created them doesn't meet the four-element test.

The Four Elements That Make Your Records Admissible

Courts evaluate four things when deciding whether your maintenance documentation gets in.

1. Timeliness: "at or near the time of the event"

Your work order has to be created when the event happens, not reconstructed later. A dispatch log generated by your maintenance platform at 9:47am on March 12 qualifies. A timeline your office manager typed up in April for the attorney? Hearsay.

I've seen PMs keep detailed records of everything that happened, then dump it all into the system days or weeks later during "catch-up" sessions. Those records look thorough. They might even be accurate. But a hearsay objection knocks them out because they weren't contemporaneous.

The fix is simple: your system should timestamp entries automatically when they're created. If your coordinators are logging work orders the same day they come in, you're fine. If there's a 72-hour gap between the event and the record, you've got a problem.

2. Knowledge: "by a person with knowledge of the event"

The person creating the record needs firsthand information. Your maintenance coordinator who took the tenant's call and dispatched the vendor? Their log entry qualifies. Your office administrator who heard about the job secondhand and entered it a week later? Different story.

This is where scattered documentation kills you. I had a contractor's liability insurance lapse for three months and nobody caught it. During that window, his crew damaged a tenant's car and we were looking at $200K in potential exposure. When we pulled our records to see how the lapse happened, there was no record. The person who tracked vendor credentials had left, and her replacement was working from a spreadsheet she'd inherited but didn't understand. No single person with knowledge of the vendor's insurance status had created or maintained the tracking record.

3. Regular activity: "in the course of a regularly conducted business"

Courts want to see that recording maintenance activity is something you do as part of normal operations, not something you started doing because a lawsuit showed up. If you've been using the same work order system for two years and every job flows through it, that's a regular business activity. If you created a tracking spreadsheet the week after you got served, opposing counsel is going to have a field day.

This is the element that rewards consistency. The PM who logs every $75 garbage disposal swap the same way they log a $6,000 HVAC replacement builds a record courts trust. The PM who only documents "big" jobs and handles the small stuff over text messages has a system with gaps. And gaps invite challenge.

4. Regular practice: "kept as a regular practice"

Different from element three, and most PMs miss the distinction. Regular activity means you do the work routinely. Regular practice means you keep the records routinely. You might dispatch vendors every day (regular activity) but only formally log the jobs when your office manager has time (irregular record-keeping practice).

Courts look for evidence that your record-keeping is systematic, not selective. Do all work orders go through the same system? Do all vendor invoices get matched to work orders? Is there a consistent process, or does it depend on who's working that day?

I ran this test on our own system and the answer was embarrassing. Emergency calls went straight into our platform. Routine requests? About half of them lived in somebody's text thread for a day or two before getting logged. Same team, same buildings, two completely different documentation practices. That's the kind of inconsistency courts notice.

Where Most Property Management Records Fail

I've reviewed our own documentation system twice in the past four years, once after that $34,000 loss and once when we switched platforms. Both times, the same gaps showed up.

Text message maintenance. Half our vendor communication happened over text. Dispatch confirmations, arrival updates, completion photos, all in text threads that live on someone's personal phone. None of that qualifies as a business record unless it's captured into your system of record. We had a plumber billing 4 hours for jobs that took 2, and we only caught it because we'd started pulling timestamped check-in and check-out data into our work order system. The $3,400 we recovered over six months came from records that were systematic, not from the text messages that preceded them.

Email-based work orders. If your "system" is a shared inbox where tenants email requests and your coordinator forwards them to vendors, you don't have a documentation system. You have an email chain. Email threads aren't created "in the course of a regularly conducted business activity." They're ad hoc communications. Stop using email for work orders. It's non-negotiable in 2026. Route everything through a work order platform that timestamps each stage automatically.

Selective documentation. You log the big jobs but handle small repairs informally. Maybe the handyman texts you "done" and you move on. Then six months later, that tenant files a habitability complaint and your records show a gap, a two-month window where nothing was documented. You did the work. You didn't record it in your system. And that gap is what opposing counsel points to when they argue your documentation practice isn't "regular."

How to Build a System That Passes the Four-Element Test

You don't need expensive software. You need consistency. A court-defensible documentation system comes down to four practices.

Every request enters the same way. Phone call, email, tenant portal, walk-in. Doesn't matter how the request arrives. It all goes into one system and gets a timestamp. No exceptions for "quick" fixes or "minor" issues. Every job, every time.

Every work order follows the same lifecycle. Request, triage, dispatch, vendor arrival, completion, verification, closeout. Each stage gets a timestamp and an actor, who did what, when. This is what courts mean by "regular practice." The lifecycle is the same whether it's a $45 P-trap or a $6,000 roof repair.

I learned this the hard way with a tenant who put in a request for a "small leak under the sink." We scheduled it for the following week because it sounded minor. By the time our guy got there, the subfloor was rotted through. $4,200 repair that would've been $120 if we'd treated it like every other work order and dispatched within 48 hours. That work order sat in someone's email for four days before it entered our system. Under the business records doctrine, those four days don't exist.

Every record is created by the person doing the work. Your coordinator logs the dispatch. Your vendor logs the arrival. Your inspector logs the verification. Courts evaluate who created each record, and if the same person is logging events they didn't witness, the "knowledge" element fails.

Nothing gets deleted or overwritten. An audit trail means every version of a record is preserved. If a work order gets updated (scope changes, vendor swaps, timeline shifts), the original entries stay and the changes are logged separately. Courts are suspicious of records that look "too clean." A real business record has corrections, notes, and updates. A fabricated one is perfect.

What Changes When You Get This Right

A documentation system that qualifies under the business records doctrine means your records walk into court without a fight. The opposing attorney can challenge the content, whether your response time was adequate, whether your repair was sufficient. But they can't challenge the records themselves. That's a different case to defend.

Your audit prep gets simpler too. Auditors and insurance adjusters apply the same logic courts do. They want to see systematic records, not cherry-picked documentation assembled after the fact.

And your operations get better without you trying. A system that creates timestamped, actor-identified records at every stage shows you where your process breaks down. You'll catch the vendor who bills 4 hours for a 2-hour job. You'll spot the coordinator who lets requests sit for three days before dispatching.

We caught about $8,200 in vendor overbilling in our first year after rebuilding our documentation system for admissibility. Wasn't the goal. But when every record has a timestamp, an actor, and a consistent lifecycle, the discrepancies surface on their own.