Early Case Assessment: A Complete Guide for Legal Teams

ECA looks different across organizations, practice areas, and matter types. But underneath all of that variation, the same six activities define every effective early case assessment.We call it the DECIDE Framework: a practical, repeatable process for any matter, from a routine employment dispute to complex multi-jurisdictional litigation.
1. Document the trigger event and the date
2. Issue a litigation hold to all potentially relevant custodians, immediately
3. Tell IT to suspend auto-deletion on affected data sources
4. Assemble the ECA team: lead attorney, legal ops, eDiscovery/IT liaisonSet a 72-hour checkpoint to confirm hold compliance
Gate 1 output: the hold is in place, the right people are involved, and data destruction has stopped.

Before you collect anything, know what universe you're dealing with.Gate 2 is reconnaissance. You need to understand what data exists, where it lives, and who controls it, before you collect a single document.This is the gate most teams rush. It's where most downstream problems start.Start with custodians. Who was involved in the events at issue? Who communicated with the other party? Who had decision-making authority? Each of these people is a potential custodian, someone who holds or held relevant ESI.
1. Email: corporate and personal, where applicable
2. Collaboration tools: Slack, Teams, Google Chat, Zoom
3. Cloud storage: OneDrive, SharePoint, Google Drive, Dropbox
4. Local devices: laptops, phones, tablets, USB drives
5. Enterprise systems: CRM, ERP, HR platforms, project tools
6. Physical documents and paper files
‍What is an ECA database? As you enumerate your data, you'll stage collected ESI in what practitioners call an ECA database - a secured, indexed repository within your ECA platform. It enables keyword search, analytics, and AI prioritization before data enters a full review environment, at a fraction of the cost.

‍Gate 2 output: a custodian list with mapped data sources - your explicit collection scope.

Targeted, defensible collection, not a comprehensive collection.
Gate 3 is where ECA meets eDiscovery digital forensics. The goal isn't a broad collection; it's a targeted, defensible collection proportionate to the matter.Set boundaries before you collect:

‍Custodian scope: Start with your confirmed list; expand only if analysis reveals gaps
‍Date range: Anchor to the period directly relevant to the claims, with a reasonable buffer
‍File types: Exclude installers, system files, and unrelated media upfront
‍Preliminary keywords: A keyword pass during collection, not just review, cuts volume early
Document everything. Every collection decision needs a record: who collected what, from where, when, and how. If your methodology is challenged, this documentation is your defense. Proper forensic collection preserves metadata, maintains the chain of custody, and keeps data admissible.
‍De-NIST and deduplicate. Removing NIST-listed system files and collapsing duplicates across custodians routinely cuts raw data volumes by 30-50% before analysis begins. Do this before data enters your ECA workspace.

‍Gate 3 output: a deduplicated, processed, indexed dataset ready for analysis.

Where ECA earns its ROI, without reading every document.Gate 4 is where the investment pays off. You have the data. Now you need to understand it without having to read every document.Targeted, defensible collection, not a comprehensive collection.