Build a budget estimate for legal-discovery compliance work using document volume, average handling time, labor rate, technology cost, outside support, and contingency. The calculator turns review volume into labor hours, combines variable and fixed costs, and shows both total spend and unit cost per reviewed item.
It can support early planning for collection review, processing, privilege screening, responsiveness review, or a defined discovery workstream. Actual discovery cost can vary dramatically with data sources, hosting volume, deduplication, search methodology, privilege issues, court orders, and vendor pricing. Treat this as a scenario model rather than a prediction of case cost, and keep the inputs aligned to the same project scope and time period.
Calculator inputs
items
hours
$/hour
$
$
%
Result
—
estimated total cost
Estimated labor hours—
Labor cost—
Estimated cost per item—
1. Enter review volume Use the expected number of documents or review units in scope after your chosen processing assumptions.
2. Set handling time Enter average review hours per document or unit.
3. Enter labor rate Use the blended hourly cost for reviewers and supervising staff represented by the assumption.
4. Add platform and outside costs Include allocated review-platform, processing, vendor, or counsel expenses.
5. Add contingency Apply an allowance for scope uncertainty or re-review.
6. Review cost drivers Compare total cost, labor hours, and per-item cost to understand which assumptions drive the budget.
Labor Cost = Items × Hours per Item × Hourly Rate Base Cost = Labor Cost + Technology Cost + Outside Support Total Cost = Base Cost × (1 + Contingency %)
All monetary inputs should use the same currency. The model assumes the average handling time and blended rate represent the scope being budgeted.
What the result means
The result is a planning estimate based entirely on the values entered. Use it to compare scenarios and workload assumptions, not as a legal conclusion.
Confirm applicable law, contracts, policies, court orders, holds, and professional requirements before making compliance or legal decisions.
Result: Total estimated cost = $281,750, or $11.27 per document.
Interpretation: Changing review volume or handling time can materially alter the estimate, so those assumptions should be refreshed as discovery scope becomes clearer.
Should document count be entered before or after deduplication?
Use the volume that corresponds to the work actually being costed. If the review team will see a post-deduplication population, enter that population rather than raw collected files.
Does this include hosting charges?
Only if you place the relevant hosting or platform amount in the software/platform cost field. Usage-based charges should be allocated to the same period and scope.
How do technology-assisted review savings appear in the estimate?
Represent them through a lower review population, shorter average handling time, or different external cost assumption, depending on how the workflow changes.
Is this a litigation budget or legal fee quote?
No. It is a configurable planning model and does not replace case-specific budgeting, vendor estimates, fee arrangements, or legal advice.
Why show cost per item?
Unit cost helps compare scenarios with different volumes. It can also reveal when fixed technology or outside-support costs make small matters relatively expensive on a per-item basis.