/
Defensible Quality Control for E-Discovery Defensible Quality Control for E-Discovery

Defensible Quality Control for E-Discovery - PowerPoint Presentation

pasty-toler
pasty-toler . @pasty-toler
Follow
440 views
Uploaded On 2016-10-08

Defensible Quality Control for E-Discovery - PPT Presentation

Geoff Black and Albert Barsocchini How do you defend your collections Question for the Audience A Question for the Audience Page 2 How Much to Collect Page 3 Full Disk Image safe but costly and time consuming ID: 473163

l01s sampling email edocs sampling l01s edocs email sample encase statistical ediscovery data workflow discovery hands review page random enscript test clearwell

Share:

Link:

Embed:

Download Presentation from below link

Download Presentation The PPT/PDF document "Defensible Quality Control for E-Discove..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.


Presentation Transcript

Slide1

Defensible Quality Control for E-Discovery

Geoff Black and Albert BarsocchiniSlide2

How do you defendyour collections?Question for the Audience

A Question for the Audience

Page

2Slide3

How Much to CollectPage 3

Full Disk Image – safe, but costly and time consuming

User-Created Data – probably the most often used in discovery

T

argeted Collections Based on Early Case Assessment

– the current trendSlide4

Let the downstream tools (processing, filtering, review) do the work.Sampling is still beneficial for all of these collection methods.

Full Disk Image | User-Created Data | Targeted

How Much to Collect

Page

4Slide5

Legal Trends in Discovery5

More discovery about discovery

More sanction decisions

Utilizing more than one methodology or technology at different stages of the process 

Transparency in the discovery process

Courts expect attorneys to understand available technology and use itSlide6

Legal Trends in Discovery6

The

increased use of lawyers with practices focused on

eDiscovery

Attorneys must demonstrate that the discovery process used is defensible and reasonable

Increased adoption of predictive coding

Courts expect discovery to be proportional to the case

Still no single "magic bullet" to solve the challenges of discoverySlide7

Legal Trends in Discovery7

Increased

adoption of information governance programs, including defensible disposal of data.

Proliferation of data sources

The days of granting carte blanche discovery are over

More use of early case

assessmentSlide8

Ensure Quality and accuracy of the collection or of the processing results

Defensibility

Sampling – Why Do It?Slide9

Judgmental – subjectively defined data set

Statistical – randomly selected data

Types of SamplingSlide10

Select appropriate filters for the target data setAccomplishing a high

confidence level

and low

margin of error

The ChallengesSlide11

Also known as the “confidence interval”

How closely results will reflect the general population

Lower margin of error is obviously better

Statistics – Margin of ErrorSlide12

We have 100 documents and our margin of error is ± 2%

Testing shows 10% responsiveness

So… the general population should show between 8% and 12% responsiveness, or 8 to 12 documents.

Statistics – Margin of ErrorSlide13

Does the sample accurately represent the results of general population?

Higher confidence level is better

Statistics – Confidence LevelSlide14

What does a 95% Confidence Level mean?

95 out of 100 times, the population will match our sample’s results

Gallup Polls: 98% accuracy in Presidential elections

Statistics – Confidence LevelSlide15

Statistics – Confidence Level

-1.96

1.96

0

95%Slide16

What’s The Catch?Slide17

You must filter out documents that you knowfor sure contain nothing of value:.exe, .

dll

, etc.

What’s The Catch?Slide18

Statistics for eDiscoverySample Sizes for Population of 1,000,000

Margin of ErrorSlide19

[Scaling] Statistics for eDiscovery

Population SizeSlide20

“Every cook knows that it only takes a single sip froma well-stirred soup to determine the taste.”

You can visualize what happens

when the soup is poorly stirred.

If well-stirred, a single sip is sufficient

both for a small pot and a large pot.

[Scaling] Statistics for

eDiscoverySlide21

Finding a good search method is difficultWho chooses search terms?

Requires iterative testing and validation

Sampling WorkflowSlide22

Sampling Workflow

Select Random Sample

Review Sample for Relevance

Search sample with proposed keywords

Compare results

Extrapolate expected relevance and error rates on data set

Can be done in parallelSlide23

Sampling Workflow

Select Random Sample

Review Sample for Relevance

Search sample with proposed keywords

Compare results

Extrapolate expected relevance and error rates on data set

Can be done in parallel

Iterate keywords, and re-test as necessarySlide24

Wait a minute, I always test my keywords!Remember: It’s not whether you test, but what you test on…

Sampling WorkflowSlide25

Small dataset for testingMinimize false positives

More accurate search, reduced data volume

Defensibility of statistically validated testing

Sampling BenefitsSlide26

Saves the cost of loading into review platformAll steps performed in EnCase for collection, processing, and review

Requires an external

EnScript

for sampling

Extra step to import random sample results back into ECC

Review capabilities less than ideal

Using ECC for Random Sampling

Page

26

Pros

ConsSlide27

EnCase

eDiscovery

Workflow Hands-On

Collect Data in ECC

eDocs

L01s

(Entries)

Fork to

eDocs

and Email L01s

Email L01s

(Records)

Random Sampler

EnScript

Sample

eDocs

L01s

Sample Email L01s

Review & TestSlide28

EnCase

eDiscovery

Workflow Hands-On

Collect Data in ECC

eDocs

L01s

(Entries)

Fork to

eDocs

and Email L01s

Email L01s

(Records)

Random Sampler

EnScript

Sample

eDocs

L01s

Sample Email L01s

Review & TestSlide29

EnCase

eDiscovery

Workflow Hands-On

Collect Data in ECC

eDocs

L01s

(Entries)

Fork to

eDocs

and Email L01s

Email L01s

(Records)

Random Sampler

EnScript

Sample

eDocs

L01s

Sample Email L01s

Review & TestSlide30

EnCase

eDiscovery

Workflow Hands-On

Collect Data in ECC

eDocs

L01s

(Entries)

Fork to

eDocs

and Email L01s

Email L01s

(Records)

Random Sampler

EnScript

Sample

eDocs

L01s

Sample Email L01s

Review & TestSlide31

EnCase eDiscovery Workflow Hands-OnPage 31

What

is

a “Workflow” in

EnCase

eDiscovery

?Slide32

EnCase

eDiscovery

Workflow Hands-On

Collect Data in ECC

Random Sampler

EnScript

Sample

eDocs

L01s

Sample Email L01s

Review & Test

eDocs

L01s

(Entries)

Fork to

eDocs

and Email L01s

Email L01s

(Records)Slide33

EnCase eDiscovery Workflow Hands-OnPage

33

Look good?

WF Processed

eDocs

WF Collected

eDocs

WF Forked Email

WF Forked

eDocs

WF Processed Email

Fork email from

eDocs

Process Email

Process

eDocsSlide34

EnCase eDiscovery Workflow Hands-OnPage

34

Survey says…

WF Processed

eDocs

WF Collected

eDocs

WF Forked Email

WF Forked

eDocs

WF Processed Email

Fork email from

eDocs

Process Email

Process

eDocsSlide35

EnCase eDiscovery Workflow Hands-OnPage 35Slide36

EnCase eDiscovery Workflow Hands-OnPage 36

MagicSlide37

EnCase eDiscovery Workflow Hands-OnPage 37Slide38

EnCase eDiscovery Workflow Hands-OnPage 38Slide39

External EnScript, not a part of EnCase eDiscovery

Uses known formulas to determine sample size

Preferred input is L01's created by

EnCase

eDiscovery

Auto-detects the L01 type - Entries

vs

Records/Email

Creates a random sample across all of the L01's and outputs items to new sample L01's (“*.SAMPLES.L01”)

Random Sampler

EnScript

Hands-OnSlide40

Random Sampler

EnScript

Hands-OnSlide41

Sampling can be performed directly in the review platformRobust reviewer and oversight capabilitiesOnce the data is in the review platform, you don’t need to go back to

EnCase

Extra costs associated

Split workflow requires moving data outside of

EnCase

and into review platform

Using Review Platforms for Sampling

Page

41

Pros

ConsSlide42

Statistical Sampling With RelativitySlide43

Statistical Sampling With RelativitySlide44

Statistical Sampling With RelativitySlide45

Statistical Sampling With RelativitySlide46

Statistical Sampling With RelativitySlide47

Statistical Sampling With RelativitySlide48

Statistical Sampling With RelativitySlide49

Statistical Sampling With RelativitySlide50

Statistical Sampling With RelativitySlide51

Statistical Sampling With

ClearwellSlide52

Statistical Sampling With

ClearwellSlide53

Statistical Sampling With

ClearwellSlide54

Statistical Sampling With

ClearwellSlide55

Statistical Sampling With

ClearwellSlide56

Statistical Sampling With

ClearwellSlide57

Statistical Sampling With

ClearwellSlide58

Statistical Sampling With

ClearwellSlide59

Statistical Sampling With

ClearwellSlide60

Contact Info & DownloadPage 60

Geoff Black

gblack@strozfriedberg.com

Product Manager, Digital Forensics

Stroz

Friedberg LLC

https://github.com/geoffblack/EnScript/tree/master/RandomSampleSelector

Albert

Barsocchini

abarsocchini@nightowldiscovery.com

Discovery Counsel & Director of Strategic Consulting

NightOwl

DiscoverySlide61

Thank YouGeoff Black and Albert Barsocchini