For more information on productions in Everlaw, please see the help articles in our Productions section.
Table of Contents
- Getting started
- Creating a protocol
- Reviewing documents for production
- Performing pre-production QA
- Contact Everlaw for help with productions
This workflow guide illustrates how to best leverage Everlaw’s review platform and services to streamline your production process. We recommend reading through this document before beginning your production preparation efforts. When you're ready to create your productions on Everlaw, you can read this article.
Turning on Production Tools
When setting out to review documents for production purposes, the first thing to do is to make sure Production Tools are turned on, which will enable your reviewers to redact documents.
This setting is on the General tab of the Project Settings page (only accessible to project admins).
Configuring Production Codes
In addition, enabling Production tools also makes it easy to create production-oriented codes for your project. The code wizard will walk you through the process of setting up the codes you want the reviewers to use throughout the lifecycle of review.
Below are some sample codes you can use:
Responsive and Not Responsive - You can use these codes to mark which documents are responsive to the production, or not.
Confidential and Highly Confidential - These codes designate which documents should be stamped for confidentiality.
Privileged and Not Privileged - You can use these codes to identify whether documents are privileged. You can also set up Attorney Client and Work Product codes to designate privilege types.
Redaction Needed and Redaction Completed - These codes are particularly helpful if you have different teams handle review and redaction. One team can identify documents needing redaction, which will then be assigned to the team performing redaction.
Creating a protocol
We highly recommend creating a protocol on Everlaw as soon as the production protocol is negotiated. During protocol set-up, you can set the criteria for documents that you want to produce based on relevant production codes. For example, if you are using the production code “Responsive” to designate the documents that you want to produce, you can input that as your production criteria for your protocol.
Creating protocols early will keep you informed of possible QA issues as they come up. The pre-production QA tool will list issues and suggest resolutions, and so being informed earlier on will give you time to resolve any problems during the lifecycle of review. You’ll also be able to easily produce periodically in rolling productions, instead of all documents at once.
Creating protocols early also gives you the chance to see whether or not you need Everlaw to set up custom settings or fields. For example, a production protocol might require you to produce a field that is not in your project. In that event, Everlaw can add custom metadata fields to your project.
To learn more about creating a protocol on Everlaw, you can read Productions 1 of 3: Creating a Production Protocol.
Reviewing documents for production
Applying the appropriate production codes to your documents during review enables you to easily gather documents for production, withhold privileged information, and flag documents for customized stamping or redactions. You can use the assignments tool to send batches of documents out to your reviewers.
Here are some types of production codes you can apply to your documents:
When reviewing documents for production, apply the production set code to all documents you would like to produce. Please make sure to review and code all family members if you are required to produce the entire family. Auto-coding may be a useful feature for this purpose.
A privilege code can be applied to identify privileged documents and what you intend to do with them. For example, you can use “Privilege: Privileged” to flag privileged documents you would like to withhold, and “Privilege: Partially Privilege” to flag partially privileged documents needing redaction.
In addition, you need to decide whether to produce a placeholder for each privileged document. If placeholders are required, include all privileged documents in the production criteria search and specify how you want to handle them in the production protocol.
Confidentiality stamping needs
You can use “Confidentiality: Confidential” or “Confidentiality: Highly Confidential” to flag documents needing confidentiality stamping. When creating a production protocol, you can customize the text we will stamp on the documents based on their code.
A redaction code such as “Redaction Status: Redaction Needed” can be used to flag documents for redaction. Once redaction is complete, you can switch the redaction status to “Redaction: Redaction Completed”.
Performing pre-production QA
Throughout the lifecycle of review, we highly recommend periodically checking back to your production protocol to be informed of any potential review or protocol set-up issues. Everlaw automatically runs common quality assurance (QA) checks on the documents specified in your production criteria. You can resolve issues in the weeks leading up to your production date.
You can check for any pre-production issues by navigating to Productions, then choosing the relevant protocol in the Protocols tab. From there, you can resolve them, or choose to produce the documents with or without issues with your production set.
To learn more about the pre-production QA tool, you can read this article.
Contact Everlaw for help with productions
If you ever have questions about producing documents, please contact your account lead or the Everlaw Support team (firstname.lastname@example.org). Additional educational material can also be found in our Knowledge Base and Training Center.