No Right to a “Hit Report” For Facially Overbroad Search Terms?

Why It Matters

The ruling reshapes e‑discovery strategy by limiting automatic hit‑report demands, forcing parties to negotiate narrower terms and assess data volume, which can reduce costly, burdensome searches.

Key Takeaways

• E.D. Cal. denies a blanket right to hit reports for overbroad terms
• Court may still order limited hit reports on narrow custodian sets
• Proportionality analysis now hinges on custodian context, not just term breadth
• System‑size caps (e.g., 5‑TB) influence court’s burden assessment
• Early hit reports can help parties refine disputed search terms

Pulse Analysis

Hit reports—documents that list the number of records matching a search term—have become a staple of modern e‑discovery negotiations. They allow parties to gauge the relevance and volume of data before committing to costly collection and production. Historically, many courts have treated the provision of such reports as an "expected and customary" practice, especially when parties are cooperating on discovery protocols. However, the utility of a hit report is directly tied to the precision of the underlying search terms; overly broad queries can generate millions of hits, inflating costs and overwhelming review teams.

The United Farm Workers v. Noem decision marks a pivotal shift. By refusing to grant an automatic right to hit reports for facially overbroad terms, the court emphasized the Rule 26(b) proportionality test, which requires a contextual assessment of the custodian, repository size, and the relevance of the data sought. The judge’s order to produce hit reports only for 22 custodians—while rejecting a broader request that could have triggered a 5‑terabyte system limit—illustrates how courts will now weigh technical constraints alongside legal standards. This nuanced approach signals that parties must substantiate the necessity of each term rather than rely on blanket reporting privileges.

Practitioners should adapt by embedding hit‑report provisions within ESI protocols that tie reporting to narrowly defined custodial scopes. Early, limited hit reports can still serve as a diagnostic tool, enabling parties to refine terms before full‑scale searches. Moreover, documenting system limitations and cost estimates can strengthen arguments against overbroad requests. In an era where data volumes are exploding, aligning hit‑report practices with proportionality and technical feasibility will be essential to avoid unnecessary litigation and preserve discovery efficiency.