An enterprise eDiscovery budget is easier to explain when it follows the work: finding relevant sources, collecting information, processing it, hosting it, and reviewing it. A single total hides the assumptions behind each phase and makes changes difficult to track.
For IT, compliance, and legal operations teams, the useful starting point is not a universal price per matter. It is a shared scope and a model that shows how volume, source complexity, review effort, and duration affect spending.
Start with sources and custodians
Build an initial inventory with the legal team. Identify relevant systems, likely custodians, date ranges, and any existing collections that may be reusable. Distinguish estimated volumes from measured exports so the budget does not present both with equal certainty.
Email is only part of the picture. Depending on the matter, the source list could include collaboration tools, cloud file storage, endpoints, mobile devices, and historical archives. Each source needs an owner who can explain access and export options.
Custodian count is another planning variable, but it does not translate neatly into a fixed charge per person. Two custodians may share much of the same correspondence, while another may hold unique data across several systems. Note those differences instead of multiplying one assumed mailbox size by headcount.
Legal stakeholders own preservation and scope decisions. The budget should record their working assumptions and show what would change if additional sources or custodians are included.
Separate the billing units
Ask providers to break out the phases rather than comparing headline totals alone. Collection may involve hourly work, source-based charges, or a defined project fee. Processing may be priced by data volume, while hosting may combine recurring storage and access charges. Review arrangements can use different pricing models as well.
For each quoted item, record:
- The billing unit and what it measures.
- The quantity assumed in the estimate.
- The services included in that charge.
- Any minimum commitment or separate setup fee.
- What event starts and ends recurring billing.
This makes proposals easier to compare. A lower processing rate may not produce a lower total if the proposals assume different volumes or include different tasks.
Also confirm whether a volume-based charge uses the original collection size, expanded data, or the set remaining after processing. The same label can conceal different measurement points, so the model needs the provider’s actual definition.
Account for difficult sources
Source complexity affects the preparation needed before review. A well-organized export differs from a collection spread across local drives, old PST files, and a retired archive with limited access.
Ask IT to identify likely extra work: obtaining permissions, arranging exports, restoring accessible copies, converting formats, or investigating failed items. Give that work its own estimate rather than burying it in a general contingency.
Longer-term data management belongs in a separate planning conversation. For an enterprise discussing archive organization or migration support with Bluesource, recurring collection difficulties can help define the operational requirements. Any improvement project should have its own scope and budget, rather than being treated as an automatic saving on the current matter.
That separation keeps immediate discovery spending distinct from investments intended to make future retrieval more manageable.
Model review effort and hosting duration separately
Collected volume is not the same as the material requiring human review. Processing choices, duplicate handling, search decisions, and review workflows can affect the size and organization of the review set.
Ask counsel and the review provider to estimate the work using the expected document population and the tasks involved. Reading for relevance, assessing privilege, preparing redactions, and checking quality may require different effort. Avoid applying one unsupported reading speed across every document type.
Hosting needs a timeline of its own. A review may finish while the data remains available for later questions or related work. Model recurring charges across the expected period, then ask how costs change if that period extends.
The end of active review should trigger a budget update, not an assumption that all spending has stopped.
Build low, base, and high scenarios
Use the base case for the currently agreed scope and expected duration. Create a lower scenario with clearly stated assumptions, such as fewer sources requiring collection. Build the higher scenario around identifiable changes, such as additional custodians, a wider date range, or longer hosting.
Keep those scenarios connected to billing units. An extra month should change the relevant recurring costs; an additional collection should change the appropriate source and processing lines. This is more informative than adding the same percentage to every category.
Assign ownership to the assumptions. IT can update export estimates, providers can clarify billing quantities, and counsel can revise review scope. Record changes with their dates so stakeholders can see why the forecast moved.
Keep the forecast useful as work progresses
Compare actual invoices and quantities against the model at agreed milestones. Investigate differences early, especially where volume definitions or recurring charges were misunderstood.
A useful eDiscovery budget does not pretend that the scope will never change. It shows the current assumptions, separates the work into understandable costs, and gives the enterprise a consistent way to update the forecast when new information arrives.
