Early Case Assessment Databases

Table of Contents

Introduction to Early Case Assessment

Early in the litigation review process, you likely have a large number of documents you have collected and uploaded as native data. At this stage, you might have a sense of search terms to apply to your data (such as keywords, dates, or custodians) but you probably don’t have enough information to assign documents out for review. To help determine which documents to prioritize in review, Everlaw offers dedicated Early Case Assessment (ECA) projects with Search Term Reports and Data Visualizer, among many other ECA tools. These can help you identify documents that are likely to be relevant to your matter.

ECA Database Workflow Overview

To help with the costs associated with hosting large amounts of data, only a portion of which will need to be reviewed, Everlaw offers ECA databases. These databases contain both a limited-functionality ECA project and at least one full-functionality review project. ECA projects have a limited feature set, described below, that is targeted specifically toward the ECA stage of a matter. In an ECA database, the ECA project is the complete project, and all review projects are partial projects.

Once you have used the ECA project to identify at a high level the documents that should be reviewed, you can promote batches of documents to one or more review projects in the ECA database. Documents housed in the ECA project but not in a review project are billed at a lower rate than documents housed in both.

Feature availability in ECA 

All Everlaw features are available within review projects in an ECA database. ECA projects have limited functionality. 

The following features are available in ECA projects, though they may have modified functionality. 

The following features are not available in ECA projects.

Creating an ECA Database

To create an ECA database, you must be an Organization Administrator. Create a database on the Organization Administrator page and select ECA as the database type. 

create_new_db.gif

When creating the ECA database, you can also copy project settings from an existing project. All selected settings will be copied to the default review project. Permissions settings, project defaults, search term reports, and deduplication settings will be copied to the default ECA project.

To migrate an existing database to an ECA database, you must be an Organization Administrator and your organization must have migration permissions. Please contact Everlaw Support if you are interested in migrating databases to ECA.

To migrate, navigate to the Organization Administrator page. Click the three-dot menu next to the database you wish to convert and select "Migrate to ECA".

migrate_db.png

Using the ECA Project

When you are on an ECA project, you will notice several differences. There will be an ECA label near the case name. The menu bar will show fewer icons and the Data Transfer icon will be replaced with a dedicated upload icon. 

2_eca_toolbar.png

To upload documents, click on the upload icon to the right of the home icon. From there, you can upload processed or native documents.

Once you have documents in your ECA project, you can run searches based on metadata (such as Custodian or Date) and keywords. From there, you can promote documents to review projects in the ECA database to access full Everlaw functionality. 

Please note that in ECA projects, you cannot perform any operations at the document level. All actions must affect the entire results table. This means that you cannot add a binder or promote documents from the review window. You also cannot select a subset of documents in the results table.

Promoting documents

The action of adding a document to a review project from the ECA project is called “promotion.” You can promote documents to a review project from the results table. Click the Batch icon on the toolbar and then select Promote. You will have to apply a promotion code to documents that you upload. This will help you keep a record of why certain documents were promoted. 

eca_promotion_from_binder.gif

Documents can be promoted to any number of review projects with different promotion codes for each project, but all promotion codes applied to a document will appear together on the ECA project. This means that if you are promoting documents to Project A with the Custodian promotion code and promoting documents to Project B with the Date Range promotion code, the documents in the ECA project will have both promotion codes. There will be no indication of which code was used to promote the documents to which project. 

3_eca_results_table.png

Once documents have been promoted, you can search by promotion code or by project membership to see which documents have been promoted. 

Adding documents to binders

To add documents to binders, create a binder on the homepage of your ECA project. Then, click the Batch button from the results table and select “Add to or remove from binder”. You can also add a new binder at this step. 

From there, you can apply a binder to or remove a binder from your documents by clicking the binder name twice. Binders will function the same as they do on a review project. You will have to affirmatively share your binder or add it to a shared homepage folder for it to be accessible to other users.

eca_binders.gif

Auditing promoted documents 

You can see a record of each promotion that has taken place on the Promotion Activity page under User Activity. Every promotion is displayed alongside information about who promoted the documents and when, the description of the search used, the promotion codes applied, and which projects the documents were promoted two. There are also two additional columns that allow you to view the count of documents that match the search. The first column shows the documents that were actually promoted at the date in the row. The second column represents the documents that currently match the search. These numbers could differ, for example if you uploaded new documents after the first promotion that match the search. 

Documents uploaded directly to a review project will not appear in the Promotion Activity table.

By clicking the export button in the upper right, you can download a CSV with all the promotion information represented in the table. 

promotion_activity.png

ECA billing

Any document that is in a review project will have its size added to the review size bucket. If a document is not in any review project, its size will contribute to the ECA size bucket. You can view size totals on the Organization Administrator Database Sizes page.

databases.png

On the Project Size tab of the Analytics page, you can see the project sizes of the individual projects as in any Everlaw database.

Using the Review Project

Review projects in an ECA database are identical to any standard partial project on Everlaw, with the following exceptions:

  • Documents added to the review project via promotion from an ECA project will display the promotion code in the Document History tab. Note that you must have permissions on the ECA project to see the promotion code in the review project. 

keyword.png

  • Documents uploaded directly to the review project (without being promoted from the ECA project) will also be uploaded to the ECA project with the Uploaded Directly promotion code.

uploaded_directly.png

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.