Performing QC of Productions

Creating and exporting a production successfully can be complicated. It's important to perform a QC of your productions to ensure accuracy.

Recipe overview

This recipe points out all possible areas of conflict and errors to consider when creating and exporting a production.


  • Workspace Access
    • Saved Searches
    • Production sets
  • Relativity Desktop Client
  • This recipe is applicable to all versions of Relativity.


When you're preparing to create a production, it's beneficial to verify some standard checklist items to prevent incorrect items mistakenly included in a production. Many of these items are intended to check for conflicts between items in a group and to show where unwanted items are brought in while segmenting desired items and including a group.

This recipe assist you in preparing a plan on how to move forward when locating unwanted data. This recipe also assist you in identifying who reviews this data and when a review of the data should occur.

See Using saved searches to complete conflict checks for conflict searching when considering the following in the production set:

Conversation before Production

Consider the following questions before you create a production:

  • What field are reviewers using to code responsiveness of documents?
  • What field are reviewers using to denote privilege?
  • What markup set does the production use?
  • Which fields do you want to produce?
  • Which fields do you want to produce if you're producing redactions?
  • Is there a production set tag?
  • What order are you producing items in?
  • What is the bates prefix?
  • How many digits are in the bates number?
  • What language do you want to use on the placeholders? (if applicable)
  • What type of production is it? (images, natives, both)
  • Do you want to export tiffs or PDFs?

Items to check in a production set

Review the production set for the following document codings:

  • 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
  • Password protected documents in production set
  • Duplicate/email thread/near duplicate of privilege document
  • Not reviewed/question/not sure for responsiveness or privilege
  • Outside of relevant date range

QC of production data

Review load files for:

  • Ensure the number of rows in DAT file is correct.
  • Ensure the fields in the DAT file are correct.
  • Ensure the native and text paths are correct.
  • Verify the number of images in image load files.
  • Verify the number of natively produced documents.
  • Ensure the bates and sort order are correct.
  • Ensure the header/field names in DAT file are correct.

Sample and Check Review images for:

  • The correct first bates number.
  • The correct confidentiality endorsement.
  • Redactions are in the appropriate location.
  • Any other special endorsements.
  • The correct number of images from image load files.
  • The image type (black and white, color).
  • No thumbs.db file is present.

Review text files for:

  • Ensure the text of the first document matches image of the first document.
  • The OCR text for redacted documents.
  • Ensure empty text files only exist for documents with no text in database.
  • Ensure no thumbs.db file is present.
  • Ensure file names contain the bates number.

Sample and Review native files for:

  • The correct number of native files.
  • The proper extensions/document types produced natively.
  • No thumbs.db file is present.
  • Ensure file names contain the bates number.