Location: Discovery->Production Validation
The production validation process is intended to alert users that the production contains documents that are inconsistently coded for responsiveness and privilege following review. All production jobs must pass validation before being run in the Lexbe eDiscovery Platform (LEP).
Specifically, the production validation process detects files that:
Contain email family documents that have been deleted from LEP;
Are not coded Responsive or Non-Responsive;
Are Non-Responsive within a Responsive email family;
Contain inconsistent coding for Privilege or Work Product;
Contain a page count number that may cause errors in production.
For video instruction for validating a production, follow this link.
Select a Production Job for validation by the title. The drop down menu will display all the productions that have not yet run in LEP.
Showing Stage Validation-Quality Control Of Productions
The first six tabs isolate from the production set all the files coded as follows:
1. Partial Email Families. Identifies any document in the production where the parent email has been deleted.
2. Redaction. Ensures that any redacted versions of documents are pulled into the production.
3. Responsive. Confirms that all documents in the production are appropriately marked as Responsive.
4. Privilege. Ensures that email family members are coded consistently for privilege.
5. Work Product. Ensures that email family members are coded consistently for work product privilege.
6. Page Count. Identifies documents more than 500 pages in length, which may lead to extended processing times.
7. Validated. Confirms that all validation steps are complete, which will allow users to run and download the production.
Validating Before Switching Tabs
To remedy coding inconsistencies:
Partial Email Families
Identifies documents where the Parent Email has been deleted from the case;
The Parent Email must be restored in order to continue with inclusion of the document in the Production (see Partially Privileged Emails);
Users may choose to completely remove the email family from the production, in which case a new Production Job should be created with only the documents for production.
Displays documents that have not been coded as Responsive, and identifies Non-Responsive documents in the Production;
Users may code all displayed documents as Responsive by clicking Fix to expand the responsiveness coding to the inconsistent documents;
User may also choose to “Accept” Non-Responsive coding for documents within an email family where one or more documents is Responsive;
Documents that are coded Non-Responsive within the email family will receive a Placeholder;
Native or “lone” Non-Responsive documents will not pass validation. The documents will need to be coded Responsive or be removed from the Production.
Every email family member must be consistently marked for Privilege;
If one email family member is marked Privilege and the rest of the email family is not, the document should be reviewed in the Doc Viewer to redact the privileged content and the privilege coding removed or no members of the email family will pass validation (see Redaction and Redaction Log);
Users may code all displayed documents as Privileged by clicking Expand. If privilege is expanded to the entire email family, all members will be withheld from the production and added to the privilege log (see Privilege Log).
Every email family member must be consistently marked for Work Product;
If just one member is marked Work Product and the rest of the email family is not, the document should be reviewed in the Doc Viewer to redact the protected content and the Work Product coding removed or no members of the email family will pass validation.
Users may code all displayed documents as Work Product by clicking Expand. If Work Product is expanded to the entire email family, all members will be withheld from the production and added to the privilege log.
Lists all documents in the Production with page counts over 500 pages;
Productions with 20,000+ page documents have occurred in past and may take over 24 hours to complete a single document;
This step acts as a warning for processing time prior to running the Production, and allows users to address large documents before processing occurs, if necessary (see PDF Split/Remove and Splitting, Merging and Unitization).
Confirms that the documents have passed validation for the previous five steps;
User is free to Run Production after Validation is complete (see Production Job).
If edits need to be made to a production, leave the page before moving forward to the next tab. Once a production is validated, the production set will be locked and no additional documents can be added. If a production is validated and documents need to be added or removed, then a new production job must be created.
Professional Services is available to perform this service at the standard hourly rate.