Seattle User Group - Amazon Web Services · What’s your Production horror story?Production ... Steps to Production ... Final Production Volume Quality Control © kCura LLC

© kCura LLC. All rights reserved.

Seattle User Group

Relativity Production Workflows


What’s your Production horror story?Production


1. Identify Documents Eligible for Production

a. Responsive Documents + Family

b. Privileged Documents + Family

c. OK to Producea. Responsive Docs – Privileged Docs

Steps to Production


Steps to Production


Steps to Production


Steps to Production


2. Break Out Documents into Data Sources

a. OK to Produce (Images Only)

b. OK to Produce (Images and Natives)

c. Additional data sources possible

Steps to Production


Steps to Production


Steps to Production


3. Create the Production Set

a. Create a new Production Set

b. Add Data Sources

c. Stage Production

Steps to Production


Steps to Production


4. Create a Recurring Workflow

a. Exclude previously produced documents

a.Production::Begin Bates is not set

b. Create a “Control Valve” field

a.“Ready to Produce” as a Yes/No field

Steps to Production


What to think about before creating your production workflow:

• What are the production set parameters?

– Are there multiple responsiveness or privilege fields?

– Are there multiple markup sets?

• Include relevant fields in the production set search results

• Consider setting up a consistent production set QC system

– Use production set tag

– Update production set QC searches for new tag or use temporary tag

• How are inconsistencies treated?

• Is there a specific production order?

Production Workflow Considerations


In Production Set and:

• Not responsive

• Privileged

• Redacted, not tagged redact (make sure to search on proper markup set)

• Tagged redact, not redacted (make sure to search on proper markup set)

• Previously produced

• Privilege screen terms, not marked privileged

• Imaged and to be produced natively

• To be imaged, not imaged

• Corrupt/unprocessable in production set

• Inconsistent families (related to production, not in production)

• Duplicate/email thread/near duplicate of privilege document

• Not reviewed/question/not sure for responsiveness or privilege

• Outside of relevant date range

Production Set QC Searches


After Production

• Review load files

– Correct number of rows in DAT file

– Correct fields in DAT file

– Native and text paths are correct

– Correct number of documents in

image files (count ,Y, or ,D)

– Number of images in image load files

– Number of natively produced

documents

• Review images

– Proper first bates number

– Proper confidentiality endorsement

– Redactions burned

– Any other special endorsements

– Correct number of images from

image load files

– Image type (B&W, color) are proper

Final Production Volume Quality Control


After Production

• Review text

– Text of first document matches image

of first document

– OCR text for redacted documents

– Empty text files only for documents

with no text in database

• Review native files

– Correct number of native files

– Proper extensions/document types

produced natively

Final Production Volume Quality Control


What to watch out for?

• Production format

– Format conforms with production

specifications/ESI order

– Proper image type (PDF/B&W/color)

produced

• Text

– OCR text produced

– A text file is produced for every

document

– Blank text documents are intentional

• Changes to production set after release

– Additions to production set

– Changes to tagging

– Placeholders

• Treatment of exception files

– Produced natively with a placeholder

– Placeholder only

– Exception log

• Production order

Common Errors in Productions


What are your workflow ideas?
