
246,000 documents. Six days. A discrimination pattern, surfaced sentence by sentence.
A Prominent Law Firm was preparing depositions in a fair housing case against a city council and its individual members accused of blocking a housing development for discriminatory reasons. Discovery had produced three years of council communications. Manual review estimates ran six weeks. They had one.
One week to depositions. Three years of council members’ communications to review.
The firm represented the plaintiffs in a fair housing case against a city council and its individual members, accused of blocking a proposed housing development through zoning denials, procedural delays, and pretextual objections motivated by the race and family composition of the residents the development was expected to serve. Discovery produced 246,000 documents — emails, internal city memos, text messages, and constituent communications — covering a three-year window across council members and city staff.
Defense counsel had been reviewing for weeks. Manual review of the full corpus would take a 25-attorney team approximately six weeks at standard rates. The litigation team had one week before the first depositions of council members and senior city staff. Anything missed would mean walking into a deposition without the document the witness was about to be asked to authenticate.
- 246,000 documents across email, internal memos, text messages, and constituent communications
- Three-year window across council members and city staff
- First depositions of council members and senior city staff in 7 days
- Manual review estimate: $1.4M and six weeks
HarmCheck ran the corpus at 20,000+ pages per hour.
The firm pointed HarmCheck Rapid Deploy at the document corpus on Sunday evening. By Tuesday morning, the system had completed a full pass across all 246,000 documents — surfacing communications referencing protected classes, coded references to “neighborhood character” and “the wrong kind of resident,” and the pretext patterns documented in prior fair housing matters against municipal defendants.
Every hit was returned with the original document, the precise sentence triggering the classification, the category, and a confidence score. Senior associates worked from a curated subset of ~4,200 documents — a 98.3% reduction in manual review burden — backed by a complete audit trail of what had been reviewed, what had been excluded, and why.

Annotated PDFs. Findings spreadsheet. Deposition-ready evidence.
By the end of day six, the litigation team had a curated set of ~4,200 flagged statements to review — each tied back to the source document, the precise triggering sentence, and the category that surfaced it. The judgment about what mattered, what to use, and how to use it stayed with the attorneys.
Instead of a 25-attorney team spending six weeks combing through 246,000 documents at standard rates, the litigation team spent six days reviewing a focused subset — with citations, source links, and category labels already in front of them. HarmCheck didn’t write the deposition outline, develop the case theory, or decide what to put in front of a witness. It just made sure the right statements were on the table in time for the team to do that work.
- ~4,200 flagged statements surfaced for attorney review out of a 246,000-document corpus
- Each flag linked back to its source document and the exact triggering sentence, grouped by category
- Annotated PDFs and a master findings spreadsheet for attorneys to work from in deposition prep
- Thousands of hours and an estimated $1.2M in manual review saved versus a traditional eDiscovery workflow

“We walked into that deposition having read every document that mattered. Six days for what would have been a six-week review — it saved us thousands of hours of manual review.”
More case studies
What if Citi used HarmCheck before the Lindsey lawsuit?
A 2023 federal complaint alleges years of threats, sexual harassment, and retaliation inside the Equities division. Every category named in the filing is exactly what Active Listening was built to catch — at the moment of draft, before send.
Bulge-bracket bank stops an MNPI leak before send.
An equity research analyst began drafting a market commentary referencing a name on the firm’s restricted list. Restricted List intercepted the message, blocked the send, and routed it for compliance review — before any external party saw it.
See HarmCheck in your environment.
Every case study starts with a conversation. Tell us what you’re trying to protect, and we’ll show you exactly how HarmCheck would have caught it.
Request a Demo