GUIDE DE LA SOCIÉTÉ

Predictive Coding and Court Approval: Da Silva Moore and After

The 2012 Da Silva Moore decision approved a negotiated predictive-coding protocol for one large electronic discovery matter.

  • 3 minutes de lecture
  • Dernière mise à jour
Sur cette page3 minutes de lecture
  1. Aperçu
  2. Plongée profonde
  3. Impact stratégique
  4. The Future of Predictive Coding and Court Approval: Da Silva Moore and After
  5. Mise en œuvre dans le monde réel
  6. Risques et garde-fous
  7. Feuille de route de mise en œuvre
  8. Continuez à explorer
  9. Questions fréquemment posées

Aperçu

It did not endorse a vendor, require predictive coding in every case, or guarantee accuracy; it emphasized transparency, quality control, and context-specific review.

Plongée profonde

Predictive coding, also called technology-assisted review or computer-assisted review, uses human judgments about sample documents to train or guide software in prioritizing potentially relevant electronically stored information (ESI). In Da Silva Moore v. Publicis Groupe, the U.S. District Court for the Southern District of New York considered a parties’ negotiated ESI protocol in a large discovery matter. The February 2012 order allowed computer-assisted review under that protocol, with iterative review and transparency provisions. The decision was an early judicial approval in its factual setting, not a rule that predictive coding must be used or that a particular vendor or tool is endorsed. The court emphasized circumstances including the parties’ agreement, large document volume, available alternatives, cost and proportionality, and the proposed process’s transparency. A later district-judge order affirmed the magistrate judge’s discovery ruling under the applicable deferential review standard. Neither order declared the software infallible; the record recognized that no review method guarantees perfection. For modern discovery, counsel should agree on scope, responsiveness criteria, training and validation samples, privilege handling, production format, and quality control where appropriate. Monitor recall and precision as useful measures, but explain sampling limits and the consequences of errors. The case does not decide every future protocol or replace the Federal Rules, local rules, or case-specific judicial discretion. Treat it as an example of a court evaluating a transparent, negotiated protocol, not as blanket approval of any automated review process. In practice, the parties should clarify what counts as responsive before training, and specify how privileged material will be screened. Quality control can include a second-level review of selected nonresponsive documents and additional review when sampling reveals uncertainty. A negotiated protocol should explain who receives information about the process and how disputes are brought to the court.

Impact stratégique

Risques et sécurité

Les dommages catastrophiques et quotidiens causés par l’IA dépendent tous deux de la personne qui comprend les risques et qui peut agir.

Décisions plus claires

Les connaissances du public et des professionnels déterminent si une politique de sécurité forte est politiquement possible.

Passer à travers le battage médiatique

Des explications claires réduisent la capture par le battage médiatique, les relations publiques en laboratoire et le théâtre d'éthique vague.

The Future of Predictive Coding and Court Approval: Da Silva Moore and After

Courts continue to encounter different data volumes, tools, and party agreements. Predictive coding remains one option within technology-assisted review, with defensibility depending on the protocol and case record. Teams should document methods and adapt validation to the matter rather than relying on a single historical decision as a guarantee. Later cases may take different approaches because the data, parties, rules, and protocols differ. Counsel should use current rules and local precedent, consult on proportionality, and avoid presenting one district court order as a nationwide mandate. The enduring lesson is to make the method and quality controls explainable in the specific matter.

Mise en œuvre dans le monde réel

Counsel proposes an ESI protocol and documents training and quality-control steps.

A discovery team discusses sampling and transparent reporting with opposing counsel.

A lawyer avoids citing Da Silva Moore as a universal mandate for predictive coding.

A court evaluates proportionality and the record in the case before it.

Risques et garde-fous

  • Traiter le risque existentiel comme de la science-fiction alors que les capacités s’accroissent.

  • Confondre sécurité des produits de surface et alignement sous haute autonomie.

  • Laisser le public non anglophone et non expert avec uniquement des sources de mauvaise qualité.

Feuille de route de mise en œuvre

  1. Séparez les dommages causés aux produits, leur mauvaise utilisation et les risques de perte de contrôle/désalignement.

  2. Demandez quelles preuves pourraient changer votre point de vue sur les délais et la gravité.

  3. Préférez les sources primaires et les évaluations concrètes aux allégations marketing.

  4. Identifiez une voie d’action : carrière, politique, financement ou compétences – et pas seulement la sensibilisation.

Continuez à explorer

Free newsletter

Get the daily AI briefing

Three verified AI stories every weekday morning, written in plain English. Free forever, no ads.

One email each weekday. Unsubscribe in one click. We never sell or share your address.

Test yourself

Take the Predictive Coding and Court Approval: Da Silva Moore and After quiz

Instant feedback on every answer, and a shareable certificate with a verifiable ID once you pass a course.

Démarrer le quiz

Support free AI education. AI Understanding is a 501(c)(3) nonprofit — no ads, no paywall, ever. Make a donation

Questions fréquemment posées

What is Predictive Coding and Court Approval: Da Silva Moore and After?

The 2012 Da Silva Moore decision approved a negotiated predictive-coding protocol for one large electronic discovery matter. It did not endorse a vendor, require predictive coding in every case, or guarantee accuracy; it emphasized transparency, quality control, and context-specific review.

What did the Da Silva Moore court approve?

The opinion approved the case-specific protocol and explicitly did not mandate use in every case.

Which factor supported approval in the case?

The court considered agreement, volume, alternatives, proportionality, and transparency.

What does the case imply about future matters?

The opinion cautions that this protocol is not automatically right for future cases.

Why are transparency and quality control important in a review protocol?

The court considered transparent process and quality review, while recognizing no tool is perfect.

In e-discovery, which workflow is called predictive coding in the guide?

Predictive coding supports review of electronic documents; legal relevance criteria remain contextual.