What Manual Document Review Costs
Small Law Firms Per Case

Legal discovery — the pre-trial phase where parties exchange documents, emails, contracts, and other records relevant to a dispute — creates a structural problem for small firms. The volume of electronic documents in even modest civil cases has grown faster than the tools available to firms that can't afford a six-figure e-discovery budget. The American Bar Association's 2024 Legal Technology Survey found that only 27% of solo attorneys use litigation support software, compared to 73% at firms with 100+ lawyers. When a production lands on your desk with 15,000 files and a 30-day response deadline, those solo practitioners aren't choosing to read everything by hand because it's the best approach. They're doing it because the alternative — a full e-discovery platform — costs more than the case is worth.

This article walks through the actual cost of manual document review for a small firm, breaking it down by role, activity, and case size. The goal is not to argue that you should buy e-discovery software. It's to show what you're already spending — so you can decide whether a lighter, cheaper extraction step makes more sense than either extreme.

The Cost of "Just Reading Everything" — A Per-Case Model

Most small firms don't model their discovery costs in advance. They assign the work, track the hours, and find out what it cost when the bill goes out. Here's what that bill actually contains, using real salary and billing data.

Start with the hourly numbers. According to the Bureau of Labor Statistics May 2024 data, paralegals earn a median $29.33 per hour — roughly $61,010 annually. But that's salary, not billing rate. Small-firm paralegal billing rates typically run $100–175 per hour depending on market and practice area. For first- and second-year associates, the billing rate at a small firm ranges from $150–300 per hour — lower than BigLaw but still the largest single cost in a discovery budget. Contract document review attorneys, as one Reddit user on r/Lawyertalk noted, currently earn "$32 is the higher-paying end of remote doc review" — but the firms hiring them charge clients $50–80 per hour for managed review services.

Now apply those rates to a realistic case. Consider a two-attorney firm handling a breach-of-contract dispute. The defendant produces 12,000 pages — roughly 2,000 individual documents spanning emails, contracts, invoices, and internal correspondence. At a sustainable review pace of 50 documents per hour — a rate that accounts for reading, comprehension, and note-taking on heterogeneous document sets — reviewing 2,000 documents takes 40 hours. If a paralegal does the first-pass organization and an associate does the substantive review:

That's $12,625 to review 2,000 documents. For a production of 10,000 documents — not unusual in a commercial dispute — the comparable figure climbs past $60,000. And this assumes a clean set of documents: all readable, all in English, all properly organized. The real world rarely cooperates that way.

Where the Hours Actually Go — Beyond the Billing Line

The $12,625 figure tells you what the client pays. It doesn't tell you where the time is actually spent — and that distinction matters, because understanding where the hours go is the first step to deciding which hours you can eliminate without increasing risk.

In a manual review workflow, the first 15–20% of time doesn't go to legal analysis at all. It goes to basic information triage: opening each file individually, identifying what kind of document it is (email? contract? invoice? handwritten note?), noting the date, sender, and parties involved, and deciding whether it belongs in the "review closely" pile or the "probably irrelevant" pile. This is work a first-year law student could do — but in a small firm, it's often done by the same associate whose time bills at $225 an hour.

What makes this pattern expensive isn't just the rate; it's the cognitive switching cost. An associate who toggles between "reading an email for its sender" and "analyzing a contract clause for liability exposure" is doing two fundamentally different tasks. The first is data extraction — finding facts that exist on the page. The second is legal judgment — evaluating what those facts mean. When the same person does both sequentially across 2,000 documents, the mental context-switching costs time no timesheet captures. Each time you shift from "who wrote this" to "does this create liability," there's a few minutes of reorientation.

Then there's the formatting friction. Discovery productions arrive in whatever format the producing party chooses: clean email PDFs, scanned contracts with crooked pages, Bates-stamped TIFFs, smartphone photos of handwritten notes, spreadsheet exports with truncated columns. In a manual workflow, every format variation requires a few seconds of visual adjustment — long enough to break reading flow, not long enough to appear on a timesheet as a separate task. Over 2,000 documents, those seconds compound into hours of unconscious friction. And the result isn't just slower review — it's review that's more likely to miss things, because the mental energy that should go to analyzing content is instead being consumed by format negotiation.

The Alternative That's Not an E-Discovery Platform

The assumption most small firms operate under is binary: either review everything manually, or buy an e-discovery platform. But there's a third option that short-circuits the most expensive part of the manual workflow without requiring a platform contract.

Batch extraction works like this: instead of opening 2,000 documents one at a time to identify basic facts, you upload them all at once into a tool that reads every file and extracts the structural data you need into a single spreadsheet. You define the columns — "Date," "Document Type," "Sender," "Recipient," "Parties Mentioned," "Dollar Amount," "Key Terms" — and the AI reads each document, locates the relevant values, and populates a row in your output table. This is column-name extraction: you specify what you want to extract by naming the fields, and the AI finds them regardless of where they appear on each page or what format the document uses.

The output isn't a finished privilege review. It's a sortable index that replaces the first 15–20 hours of manual triage — the part where a $225/hr associate is opening files and building a mental map of what's in the production. With a spreadsheet where each row is a document and each column is a field you requested, the associate opens the review already knowing which documents contain dollar figures, which mention key parties, and which are contracts rather than emails.

This approach doesn't replace what an e-discovery platform does. Platforms like Relativity, Everlaw, and Logikcull handle the full EDRM pipeline: collection, deduplication, email threading, near-duplicate detection, privilege logging, redaction, and production. For cases involving millions of documents, hundreds of privilege calls, or multi-party review teams, that full pipeline is necessary. But for the small firm handling a 2,000–20,000 document production where the primary question is "what's in here, and what do I need to read first," a batch-extracted spreadsheet answers the question without the platform overhead.

And it answers it before you spend a dime on associate time. If a ACEDS analysis shows that document review consumes 64% of discovery spend, the fast-extraction pass is the tool that lets you redirect the other 36% into the subset of documents that actually warrant it — rather than spreading it across the entire production evenly.

Our companion article on batch extraction for legal discovery covers the full workflow — from column design to spreadsheet triage — in detail. The focus here is the cost comparison: what changes in your bill when you add that extraction step.

Manual Review vs E-Discovery vs Batch Extraction — Cost at Three Case Sizes

The numbers below compare three approaches across three typical small-firm case volumes. "Manual" assumes the associate + paralegal workflow modeled earlier. "E-Discovery Platform" assumes per-GB hosting at $15–25/month plus platform subscription ($25,000–$50,000+ annually for Relativity) or per-matter pricing ($3,000–$15,000 for smaller platforms like GoldFynch and Nextpoint). "Batch Extraction" assumes the extraction tool cost plus reduced review hours — the triage step replaces manual document-by-document opening and sorting.

Two patterns stand out. First, at every case size, batch extraction + targeted review is cheaper than full manual review — and the savings grow with volume. Second, batch extraction competes with entry-level e-discovery platforms on cost while providing a fundamentally different capability: it doesn't host a review database, but it gives you a spreadsheet you can sort, filter, and annotate in tools your team already uses. For small firms, the spreadsheet is often the more useful output — because it integrates with the Excel-based workflows that paralegals and associates already run for case management, deposition tracking, and exhibit lists.

The batch extraction approach also eliminates the steepest hidden cost of e-discovery platforms: the onboarding time. Relativity, for all its power, requires training. Logikcull and Everlaw are more accessible but still introduce a new interface into a workflow where every new tool is a friction point. Batch extraction asks the tool to produce a spreadsheet — and your team already knows how to use spreadsheets.

Calculating ROI — When the Math Tips Toward Extraction

The economics of adding a batch extraction step depend on how many of the manual review hours it eliminates. The extraction itself doesn't replace substantive legal analysis — it replaces the triage and sorting phase. In a typical small-firm workflow, that phase consumes roughly 15–20 hours per 2,000-document production.

Here's the breakeven math for a firm handling one moderate-sized discovery matter per month:

Across 12 matters per year, that's roughly $46,000 in recovered billable time — time the associate now spends on case strategy, motion practice, and client development instead of opening PDFs. The math improves further if the firm handles higher-volume productions: at 10,000 documents, the triage hours that extraction replaces multiply, and the savings per case approach $15,000.

The savings don't come from replacing the associate. They come from compressing the part of the workflow where the associate adds the least value — the mechanical step of opening files and identifying basic metadata — while preserving the part where the associate's legal judgment is irreplaceable. A batch-extracted spreadsheet tells the associate that document #47 is a March 2024 email from the HR director referencing a "termination discussion." The associate still reads document #47. But the associate didn't spend 30 seconds opening it, scanning for a date, scanning for sender and recipient, and deciding whether to read it. The spreadsheet already answered those questions. The 30 seconds of mechanical work is replaced by 3 seconds of reading a spreadsheet cell — and the 10 minutes of substantive analysis that follows is where the money should be going all along.

Frequently Asked Questions

Is AI extraction defensible if challenged by opposing counsel?

Batch extraction for triage purposes — building an internal index of what's in a production — is analogous to a paralegal preparing a document index by hand. It does not make privilege determinations or relevance judgments, and the output spreadsheet is an internal work product, not a filing. If the extraction is used solely to guide which documents receive substantive attorney review, the method is no different in principle from manual indexing — just faster. For firms concerned about work product protection, FRCP 26(b)(3) addresses the discoverability of materials prepared in anticipation of litigation.

What's the accuracy of AI extraction on legal documents — especially scanned PDFs and handwritten notes?

Print text on clean PDFs achieves roughly 99% accuracy. Scanned documents with moderate quality drop to 90–95%. Handwritten notes — common in margin annotations, deposition notes, and internal memos — range from 85–95% depending on handwriting legibility. This is why the extraction functions as a triage tool, not a final work product. If the spreadsheet lists "Smith settlement offer $45K" from a handwritten note, and the actual note says "$47K," the value is that you now know to pull that document and read it yourself — you would not have known it existed otherwise. The extraction doesn't need to be perfect; it needs to be good enough to tell you where to look.

Does batch extraction handle native file formats like .msg or .docx?

Currently, the tool accepts PDF, JPG, PNG, WebP, and AVIF files. Most discovery productions are already delivered as PDF or TIFF files, so this is rarely a practical limitation. Native files (.msg, .docx, .xlsx) should be converted to PDF before upload — most practice management platforms can batch-convert these formats. The conversion step adds a few minutes to the workflow but doesn't change the cost equation meaningfully.

How is this different from just using Ctrl+F on a document folder?

Ctrl+F searches for text strings within the text layer of a PDF. It cannot read text from scanned image-based PDFs, handwritten notes, or photographs of documents — all common in discovery productions. It also cannot extract structured data into a spreadsheet: you can find the word "termination" in 200 documents, but you can't easily see which of those documents also contain a date, a dollar amount, and the name of a specific custodian. Batch extraction outputs a structured table where each column is a field you defined, making the relationships between data points visible and sortable.

What happens to privileged documents during batch extraction?

The extraction tool reads documents to identify the data points you specified — dates, parties, amounts, document types. It does not make privilege determinations. If a document contains privileged communication, the extraction will still populate the spreadsheet row with the structural data you requested (date, sender, recipient), but the privilege determination — whether the communication is protected — remains with the reviewing attorney. The batch extraction step does not alter or redistribute the underlying documents. It creates an index that helps you find potentially privileged documents faster, so your privilege review is more targeted and less exhaustive.

What You're Really Paying For — and What You Can Stop Paying For

When a small firm bills $12,625 for document review on a 2,000-document production, the client is paying for two distinct things: the legal judgment required to evaluate relevance and privilege, and the mechanical labor required to open, sort, and catalog the production. The first is worth every dollar. The second is worth almost nothing — and it's the larger portion of the bill.

Batch extraction doesn't eliminate the need for legal judgment. It eliminates the need to spend legal judgment hours on tasks that don't require it. A paralegal who spent 3 hours building a spreadsheet index rather than 15 hours opening files one by one has recovered 12 hours of capacity. An associate who begins document review with a pre-sorted, pre-filtered index reads fewer irrelevant documents, spots patterns faster, and spends less time context-switching between mechanical triage and substantive analysis.

The firms that benefit most from this approach aren't the ones with the biggest discovery budgets. They're the ones where every hour of associate time is directly felt on the firm's bottom line — and where the difference between a $12,625 review bill and a $7,050 review bill is the difference between a case that's profitable and one that isn't.