How To Draft An Electronic Disclosure Production Protocol

PRODUCTIONPROTOCOLS · AGUIDEFORUKLAWYERS How to Draft an Electronic Disclosure Production Protocol The Agreement That Decides Every Later Argument, Clause by Clause COMPUTERFORENSICSLAB § ABOUTTHEAUTHOR PRE PA REDBYCOMPUTERFORENSICSLABE - DISCOVERYTEAM ESTABLISHED 2007 · LONDON ISO 17025-ALIGNED PROCEDURES FULL CHAIN-OF-CUSTODY DOCUMENTATION § CONTENTS In this guide 01 Executive summary 02 The problem in plain English: the argument you have now or the ten you have later 03 Where the protocol sits: the DRD, PD 57AD and when to agree it 04 The format clauses: natives, images, and the per-type schedule 05 The data clauses: metadata fields, families, threading and load files 06 The protection clauses: redaction, privilege, clawback and confidentiality 07 The operations clauses: exchange, tranches, corrections and disputes 08 Source architecture: where else the evidence lives 09 Worked examples 10 Common mistakes and technical limitations 11 Questions to ask · Suggested wording 12 Checklist and red flags · When to involve a digital forensic expert 13 Frequently asked questions 14 Glossary · References · Disclaimer · How a specialist laboratory can assist § 0 1 · ORIENTATION Executive summary THEHEADLINEPOINT : APRODUCTIONPROTOCOLISTHECHEAP , EARLYAGREEMENT THATPREVENTSTHEEXPENSIVE , LATEDISPUTES : DRAFTITWITHTHEENGINEERSIN THEROOM , TESTITAGAINSTTHEKNOWNDISASTERS , ANDAGREEITBEFORETHEFIRST TRANCHEISBUILT § 0 2 · FIRSTPRINCIPLES The problem in plain English: the argument you have now or the ten you have later § 0 3 · THEFRAME Where the protocol sits: the DRD, PD 57AD and when to agree it § 0 4 · FORMATS The format clauses: natives, images, and the per-type schedule § 0 5 · DATA The data clauses: metadata fields, families, threading and load files § 0 6 · PROTECTIONS The protection clauses: redaction, privilege, clawback and confidentiality § 0 7 · OPERATIONS The operations clauses: exchange, tranches, corrections and disputes § 0 8 · THEWIDERMAP Source architecture: where else the evidence lives QUESTION PROTOCOL CORRECTION DATA PROCESSING PLATFORM MANIFESTS + MAP DESIGN CAPABILITIES RECONCILIATIONS SIGNED DEFECT + + VERSIONS LOG § 0 9 · INTHEWILD Worked examples EXAMPLE1 · THETEMPLATESIGNEDUNREAD EXAMPLE2 · THESAMPLEEXCHANGETHATPAIDFORTHEYEAR EXAMPLE3 · THEDISPUTELADDERTHATKEPTTHEDELIMITEROUTOFCOURT § 1 0 · WHEREITGOESWRONG Common mistakes and technical limitations Common mistakes Technical limitations § 1 1 · INTERROGATORIES & DRAFTINGAIDS Questions to ask · Suggested wording Ask your client Ask your opponent Ask your eDiscovery / forensic provider SUGGESTEDWORDING · CORESKELETONFORTHEPROTOCOL § 1 2 · QUICKCONTROL Checklist and red flags · When to involve a digital forensic expert The protocol drafting checklist Red flags When to involve a digital forensic expert § 1 3 · COMMONQUESTIONS Frequently asked questions Is a production protocol actually required? When should the protocol be agreed? The other side sent their standard protocol. Can we just sign it? What belongs in the protocol versus the DRD's other sections? What if a data type turns up that the protocol never contemplated? How detailed should the load-file specification really be? § 1 4 · REFERENCE Glossary Sources and authoritative references DISCLAIMER § HOWASPECIALISTLABORATORYCANASSIST Working with Computer Forensics Lab Speak to a forensic examiner, not a salesperson. INSTRUCTTHELAB NEWENQUIRIESEMAILE - DISCOVERY