Legacy load: High · Track: AI Adoption
Landlord-Tenant & Housing
Extremely high volume, low dollar value per matter, and a process that rewards standardization more than almost any other area. adnah's read: this is where legacy load is heaviest and easiest to remove.
Ceremony, safe to remove
- Drafting notices and pleadings by hand for fact patterns that recur nearly identically across hundreds of files
- Manually tracking notice periods and filing deadlines that follow fixed statutory formulas
- Re-entering the same tenant, unit, and lease information across intake, notice, and court filing documents
- Building a case summary from scratch for each hearing when the underlying facts are a small variation on a known pattern
Irreducible, stays with the lawyer
- Judging whether a given fact pattern actually supports the claimed grounds for eviction or defense
- Advocacy at hearing, where the outcome often turns on credibility and framing rather than paperwork
- Negotiating settlement or payment plans where the client's real interests go beyond the strict legal claim
- Spotting the case that looks routine but has a genuine defense or a policy issue that changes the calculus
Primitives most in play
The usual failure mode
The most damaging failure here is speed without a triage layer. Because the volume is so high and the individual stakes so procedural-looking, it is tempting to automate notice and filing generation end to end and consider the job done. But housing matters are exactly where a small number of files hide a real dispute, a habitability defense, or a vulnerable tenant who needs more than a form response, and a fully automated pipeline with no flagging step will process those files at the same speed as the routine ones, which is the wrong outcome for everyone involved.
What changes
- Before: notices and pleadings are drafted individually from a template, filled in by hand. After: they generate directly from case data, and attorney time goes to verifying the small number of atypical entries.
- Before: deadlines are calculated and tracked manually across a large caseload. After: deadlines compute automatically from the statutory formula and the case's actual dates, removing a common source of missed filings.
- Before: every file gets the same manual intake regardless of complexity. After: intake is structured so files with a potential defense or habitability issue are flagged early instead of surfacing at the hearing.
- Before: hearing prep means rebuilding the case summary from the file each time. After: the summary exists continuously as the file develops, and prep time goes to the specific argument for that hearing.
What a working transformation looks like here
A working transformation looks like a caseload where the purely procedural files move through notice, filing, and resolution with minimal manual touch, while the files with a genuine dispute get identified early and receive real attorney attention rather than being lost in volume. The clearest sign it is working is that the rate of contested or defended cases identified goes up, not down, even as overall processing time per file drops.
Next practice area
In-House Legal Operations →