Certified E-Discovery Specialist (CEDS) common mistakes
CEDS · Understand the traps and how to avoid them.
Treating the EDRM as a strict linear waterfall, so a candidate answers that collection must be fully finished before any processing or review planning begins, even when the scenario involves early case assessment or iterative targeting.
The EDRM diagram is presented as a sequence, and candidates memorize the left-to-right order without internalizing that the model is iterative and that later stages inform earlier ones.
What to do instead
Practice identifying which stage a scenario is really testing (e.g., proportionality judgments at identification, sampling during processing) and answer with the iterative, feedback-driven version of the model rather than the linear one.
When asked to choose a preservation scope, the candidate defaults to 'preserve everything for every custodian' rather than applying the proportionality factors to identify a defensible, targeted scope.
Over-preservation feels like the 'safe' answer and candidates confuse defensibility with maximalism, forgetting that courts can and do fault unreasonable over-preservation as disproportionate.
What to do instead
For each scope question, explicitly weigh relevance, accessibility, cost, and the needs of the case; if the scenario gives cost or burden data, use it, and select the option that is reasonable and documented rather than the broadest one.
Confusing the litigation hold's trigger and audience: candidates issue holds only to the legal department or only after a complaint is filed, missing that the duty can attach at reasonable anticipation and must reach all custodians and relevant data sources.
Candidates conflate the duty to preserve with the formal filing of litigation and overlook that the trigger is reasonable anticipation, not service of process.
What to do instead
Anchor on 'reasonable anticipation' as the trigger and remember the hold must reach every custodian and system holding potentially relevant data, including third parties under control; rehearse scenarios where the trigger predates the complaint.
Failing to build or evaluate a defensible project plan: the candidate answers a planning question without addressing scope definition, budget, timeline, roles, or quality-control checkpoints, and instead jumps straight to a tool or vendor choice.
Technical tooling questions are more concrete and memorable, so candidates skip the planning discipline of scoping, resourcing, and QC that the planning domain is actually testing.
What to do instead
Before selecting any option, check whether it names scope, budget, timeline, staffing, and QC; prefer answers that establish a documented, repeatable process over ones that name a specific technology.
Assuming the same discovery rules apply worldwide: the candidate answers an international scenario using FRCP-style concepts (broad relevance, US-style preservation duties, US privilege) without accounting for blocking statutes, data protection law, or local procedural limits.
Candidates study the US framework most heavily and reflexively apply it, without recognizing that foreign jurisdictions may restrict transfer, limit relevance, or impose different privacy regimes.
What to do instead
For every international scenario, first identify the jurisdictions involved and ask whether a blocking statute, data protection law, or Hague Convention mechanism changes the analysis; select answers that address cross-border legal constraints explicitly.
Ignoring the Hague Convention and other formal cross-border mechanisms when the scenario involves obtaining evidence from a foreign party or a foreign-based custodian, and instead assuming direct US subpoena power reaches the data.
Candidates assume US court authority is globally effective and are unfamiliar with the Convention's procedures, central authorities, and the limits on direct requests.
What to do instead
When data or a custodian sits abroad, evaluate whether a Hague Convention request, letters rogatory, or a local proceeding is required; prefer answers that route through the proper mechanism rather than asserting direct US compulsion.
Overlooking data protection and privacy transfer restrictions (e.g., GDPR-style rules, adequacy, and transfer mechanisms) when planning collection from or review of EU or other foreign data, and answering as if data can simply be shipped to a US review platform.
Candidates treat data transfer as a purely technical step and underestimate that privacy law can prohibit or condition the transfer and review of personal data.
What to do instead
In any cross-border collection or review question, check whether personal data is involved and whether a lawful transfer basis or local processing arrangement is needed; choose answers that address privacy compliance alongside discovery needs.
Treating foreign blocking statutes and local privilege rules as irrelevant because the US case controls, and answering that US privilege and relevance standards automatically govern foreign documents.
Candidates assume the forum's law uniformly governs all evidence, missing that foreign law can restrict production and that privilege may be defined differently abroad.
What to do instead
Separate the forum's procedural rules from the foreign jurisdiction's substantive limits; select answers that acknowledge both and that propose reconciling them (e.g., local counsel review, redaction, or negotiated protections).
Relying on a single custodian's or vendor's assurance that ESI is complete and defensible without independent verification, sampling, or quality-control review, and certifying completeness on that basis.
Candidates want a clean, efficient answer and accept representations at face value, forgetting that counsel has an independent duty of reasonable inquiry and competence.
What to do instead
Prefer answers that build in sampling, validation, and documented QC steps before any completeness or accuracy representation; treat unverified vendor or custodian assurances as insufficient.
Failing to recognize and manage conflicts, including the candidate's own or counsel's, and answering a scenario as if a conflicted party can continue without disclosure, screening, or withdrawal.
Candidates focus on the substantive discovery issue and overlook the ethical overlay, especially when the conflict is subtle (e.g., prior representation of a custodian or vendor relationship).
What to do instead
For every ethics scenario, run a conflict check first: identify the parties, prior relationships, and whether disclosure, informed consent, screening, or withdrawal is required before proceeding.