Just Cause Eviction Documentation: Building the Pre-Eviction Maintenance File

What Maintenance Records Do You Need Before Evicting a Tenant in California?

A pre-eviction maintenance file is the timestamped proof that you met every habitability obligation before, during, and after the lease violation you're acting on.

If you manage 15+ units in California and you've ever had a tenant raise habitability as an eviction defense, this is your starting point. AB 1482's just cause requirements mean you can't just prove the tenant violated the lease. You have to prove you didn't give them a reason to claim you violated yours.

Step 1: Build the Maintenance Request Log Before You Need It

Don't start assembling documentation after you decide to evict. By then it's too late to fill gaps. Most PMs wait until they've already served notice, then scramble to pull records together. That doesn't work.

Every maintenance request from every tenant should land in a single system with a timestamp the moment it arrives. I don't care if it comes in by phone, email, text, or a handwritten note slid under your office door. It gets logged with the date, the tenant's exact words, and who received it.

I got burned on this in my first year managing a 48-unit property. Tenant filed a complaint with the housing authority about a broken window latch. We'd replaced it two months earlier, but the original request came in through a phone call that nobody logged. Our maintenance tech remembered fixing it. The tenant remembered reporting it. We had no record of either. The inspector treated it as an open deficiency because we couldn't prove our own timeline. A $35 latch replacement turned into a $1,800 re-inspection and remediation cycle. All because the intake wasn't timestamped.

Common mistake at this step: Logging the request but not the tenant's original language. "Plumbing issue" in your system doesn't match "water is pouring out of my cabinet" in the tenant's text. Courts compare what the tenant reported against what you logged. If your version sounds milder, it looks like you downplayed the problem.

Step 2: Document Every Response With Timestamps and Evidence

Response documentation is the timestamped proof of what you did after a request came in — acknowledgment, dispatch, arrival, completion, and tenant notification. Courts don't care that you received the request. They care how fast you responded and what steps you took.

For every request, your file should show:

• When you acknowledged receipt to the tenant (date and method)

• When you dispatched a vendor or internal tech

• When the vendor arrived on-site

• When the work was completed, with before/after photos

• When you notified the tenant the work was done

That's five timestamps per request. Sounds like a lot until you're sitting in court and the tenant's lawyer asks "how long did it take you to respond to the mold complaint?" and you can say "fourteen hours from report to vendor on-site, here's the dispatch record."

If your work order system creates an audit trail automatically, this happens without extra effort. If you're doing it manually, you'll miss something -- and the one you miss will be the one the judge asks about.

Step 3: Keep the Violation Notice Chain Airtight

This is where most eviction cases fall apart. The notice chain has a gap somewhere, and the judge finds it before your attorney does.

Under AB 1482, a just cause eviction for lease violations requires:

1. Written notice citing the specific lease clause. Not "tenant violated lease terms." The actual section number and the specific behavior. "Tenant violated Section 12.3 by installing a satellite dish on the building exterior without written landlord consent, observed on March 14, 2026."

2. Proof of service. How you delivered the notice, when, and to whom. Certified mail with return receipt is the gold standard. Hand delivery with a witness and a signed acknowledgment works too. Taping it to the door and hoping for the best doesn't work.

3. Documented cure period. The tenant gets time to fix the violation. Your file needs to show that you gave them the full statutory period and that you checked whether they cured it.

4. Evidence the violation wasn't cured. Photos, inspection notes, or a follow-up visit record showing the problem persists after the cure period expired.

Miss any one of those four links and the chain breaks. I've seen cases dismissed because the PM cited "Section 9" of the lease but the violation was in Section 9.2(b). The judge ruled the notice was insufficiently specific.

Step 4: Build the Communication Trail

A communication trail is every documented interaction between you and the tenant about maintenance or lease compliance — emails, texts, call logs, and follow-up confirmations.

Your file should include:

• Emails (saved, not summarized)

• Text messages (screenshot with timestamps visible)

• Phone call logs (date, time, duration, summary written within 24 hours)

• In-person conversations (documented in a follow-up email: "Per our conversation today at 2pm...")

The communication trail serves two purposes. First, it shows you were responsive and professional. Second, it proves the tenant was aware of the violation and the cure timeline.

I had a tenant claim she never received our violation notice. We produced three emails, two certified mail receipts, and a text message where she acknowledged the issue and asked for an extension. Case closed.

Common mistake at this step: Calling the tenant instead of texting or emailing. Phone calls are faster, but they're invisible in court. If you must call, follow up immediately with a written summary. "Hi Maria, following up on our call at 3:15pm today -- as discussed, the lease violation notice was for the unauthorized pet observed on March 7th, and the cure period runs through March 21st."

Step 5: Cross-Reference Maintenance Against Lease Violations

Most PMs skip this, and it costs them.

Before you file anything, pull the tenant's complete maintenance history and lay it next to your violation timeline. You're looking for two things:

Timing overlap. Did the tenant submit a maintenance request within 30 days before or after you issued a violation notice? If yes, opposing counsel will argue the eviction is retaliatory. Your defense is the maintenance file: you responded to every request within your standard timeline, the response wasn't affected by the violation notice, and you can prove it with timestamps.

Unresolved items. Is there anything the tenant reported that you haven't closed? Anything that took longer than your usual response time? A single open work order can torpedo an eviction case in California. The tenant's attorney will argue you failed your habitability obligations under AB 628 and the eviction is retaliation for the complaint.

Go through every request from the past 12 months. Make sure every one shows a complete cycle: reported, acknowledged, dispatched, completed, tenant notified. If there's a gap, close it before you file.

Step 6: Assemble the Pre-Eviction File

Pull everything into a single file -- digital or physical, but organized and complete. Your attorney should be able to open it and find what they need without calling you.

The file should contain, in order:

• Lease agreement with all amendments and addenda

• Complete maintenance request log for this tenant

• Response and completion records for every request, including photos and timestamps

• All violation notices with proof of service

• Cure period documentation

• Communication trail, chronological

• Inspection reports or photos of current unit condition

• Notes on comparable treatment for similar violations with other tenants

That last item trips up a lot of PMs. If you evicted this tenant for an unauthorized pet but looked the other way when the tenant in Unit 12 had the same breed, opposing counsel will find out. Enforce every violation the same way across every unit. No exceptions.

What This Looks Like When It's Working

You get the call from your attorney: tenant is fighting the eviction, claiming habitability defense and retaliation. Instead of spending a weekend digging through email and text threads, you pull the pre-eviction file. Maintenance requests with timestamps. Response records with photos. Violation notices with proof of service. Communication log going back 18 months.

Your attorney reads it in 20 minutes and says "we're fine."

That's a file your system built while you worked, not something you assembled the night before a hearing. The PMs who build documentation into their daily workflow don't scramble when the eviction gets contested. The ones who treat it as an afterthought settle cases they should've won.

I'd rather spend 10 minutes logging a maintenance response than 10 hours reconstructing one for a judge.