CloudSketch AI Logo
FeaturesTemplatesPricingEnterpriseAboutContactLog in
πŸŒ™β˜€οΈ
Log inStart free
Home/Templates/Legal

βš–οΈ Legal Β· Data Flow

E-Discovery Data Pipeline

How electronic evidence is collected and reviewed in litigation: legal hold, collection, processing, review and production to the other side.

More Legal templates

Opening a template is free and never counts toward your daily diagrams. Asking the AI to change it counts as one.

Drawing diagram…

What this diagram shows

  • Legal hold stops relevant data being deleted
  • Processing removes duplicates and system files before review
  • Privileged documents are withheld and logged

Prompt used

Data flow for e-discovery (EDRM): legal hold notices go to custodians, data is collected forensically from email, file shares, chat and laptops, processing extracts text and metadata, removes duplicates and system files, and applies date and keyword filters. Analytics (threading, technology-assisted review) prioritise documents for reviewers, who code them as relevant, not relevant or privileged. Relevant non-privileged documents are produced to opposing counsel; privileged ones go on a privilege log.

Mermaid code
flowchart LR
subgraph EXT ["External entities"]
legal["Legal Team"]
cus["Custodians"]
rev["Reviewers"]
opp["Opposing Counsel"]
end
subgraph PROC ["Processes"]
p1("1.0 Issue legal holds")
p2("2.0 Collect data forensically")
p3("3.0 Process, de-duplicate and filter")
p4("4.0 Prioritise with analytics (TAR)")
p5("5.0 Code documents")
p6("6.0 Produce and log privilege")
end
subgraph STORE ["Data stores"]
d1[("D1 Collected Evidence")]
d2[("D2 Review Database")]
d3[("D3 Privilege Log")]
end
legal -->|"Matter and custodian list"| p1
p1 -->|"Legal hold notices"| cus
cus -->|"Email, files, chat, laptops"| p2
p2 -->|"Forensic images"| d1
d1 -->|"Collected data"| p3
p3 -->|"Text, metadata, filtered documents"| d2
d2 -->|"Documents"| p4
p4 -->|"Prioritised batches"| rev
rev -->|"Relevant, not relevant, privileged"| p5
p5 -->|"Coding decisions"| d2
d2 -->|"Relevant non-privileged documents"| p6
p6 -->|"Production set"| opp
p6 -->|"Privileged entries"| d3

Inside this diagram

A data flow diagram with 10 processes and outside parties, 3 data stores and 13 data flows.

Processes and outside parties

  • Legal Team
  • Custodians
  • Reviewers
  • Opposing Counsel
  • 1.0 Issue legal holds
  • 2.0 Collect data forensically
  • 3.0 Process, de-duplicate and filter
  • 4.0 Prioritise with analytics (TAR)
  • 5.0 Code documents
  • 6.0 Produce and log privilege

Data stores

  • D1 Collected Evidence
  • D2 Review Database
  • D3 Privilege Log

Data flows

  • Legal Team β†’ 1.0 Issue legal holds: Matter and custodian list
  • 1.0 Issue legal holds β†’ Custodians: Legal hold notices
  • Custodians β†’ 2.0 Collect data forensically: Email, files, chat, laptops
  • 2.0 Collect data forensically β†’ D1 Collected Evidence: Forensic images
  • D1 Collected Evidence β†’ 3.0 Process, de-duplicate and filter: Collected data
  • 3.0 Process, de-duplicate and filter β†’ D2 Review Database: Text, metadata, filtered documents
  • D2 Review Database β†’ 4.0 Prioritise with analytics (TAR): Documents
  • 4.0 Prioritise with analytics (TAR) β†’ Reviewers: Prioritised batches
  • Reviewers β†’ 5.0 Code documents: Relevant, not relevant, privileged
  • 5.0 Code documents β†’ D2 Review Database: Coding decisions
  • D2 Review Database β†’ 6.0 Produce and log privilege: Relevant non-privileged documents
  • 6.0 Produce and log privilege β†’ Opposing Counsel: Production set
  • 6.0 Produce and log privilege β†’ D3 Privilege Log: Privileged entries

Boundaries

  • External entities: Legal Team, Custodians, Reviewers and Opposing Counsel
  • Processes: 1.0 Issue legal holds, 2.0 Collect data forensically, 3.0 Process, de-duplicate and filter, 4.0 Prioritise with analytics (TAR), 5.0 Code documents and 6.0 Produce and log privilege
  • Data stores: D1 Collected Evidence, D2 Review Database and D3 Privilege Log

Make your own diagram like this

Describe your own system in plain English and CloudSketch AI draws it in seconds. See all AI diagram generators.

Related templates

State MachineLegal

Contract Lifecycle (CLM)

The states of a commercial contract in a contract lifecycle management system, from request and drafting to renewal or expiry.

SequenceLegal

E-Signature Flow

How a document gets signed electronically by several parties in order, with identity checks and a tamper-evident audit trail.

C4 ArchitectureProLegal

Legal Case Management Architecture

A law firm's case management platform: matters, documents, court dates, time tracking and billing, with a client portal.

FlowchartLegal

Legal Document Review and Approval

How a contract or legal document is reviewed inside a company: intake, playbook check, risk rating, approvals and signature.

Database ERDLegal

Legal Matter and Billing Schema

A schema for law firm matters and billing: clients, matters, timekeepers, time entries, expenses, invoices and trust accounts.

State MachineLegal

Litigation Case Lifecycle

The stages of a civil court case from filing to judgment and appeal, including settlement at any point.