January 14, 2026: Everlaw Archive, deduplicate against processed data in native uploads, coding filters in category columns, and more!

Avatar
[System] Everlaw Support

Expected AU release: January 14, 2026 ACT

Expected release for all others: January 14, 2026 PT

Knowledge Base updates:  January 14, 2026 PT

With this release, we’ve added Everlaw Archive and more — read on for more information about the features coming out this month! If you would like to learn more about the features in this release, join us for a live training session.

User-facing features in this release:

Introducing Everlaw Archive

Everlaw now supports database cold storage via Everlaw Archive. Everlaw Archive lets you archive inactive databases in a lower‑cost, non‑reviewable, non‑exportable state while preserving all documents, work product, and configurations exactly as they were. You can later restore access with your prior work intact. 

Everlaw Archive is designed for medium- to long‑term retention (e.g. closed matters you must keep for 5–10 years) or for pausing work on matters for extended periods (> 6 months) without exporting and re-importing the database.

Note

Everlaw Archive is not available on Everlaw GovCloud at this time.

Note

Everlaw Archive is an add-on contract feature and will not be available in your organization until it is enabled. For more information, contact your Everlaw Customer Success representative.

It can help you in the following ways:

  • Reduce hosting costs for inactive databases: Move complete databases into an archival state priced below active hosting, intended for long‑term retention periods.
  • Data preservation: All documents, work product, settings and configurations, user and document histories are retained, so you can restore and resume where you left off after reactivation without manual reimport and reconfiguration
  • Clear operational expectations: Databases living in Everlaw Archive are non‑reviewable and non‑exportable until reactivated
  • Visibility: Data usage notifications can include Everlaw Archive usage, supporting proactive monitoring

The table below outlines some differences and similarities between Everlaw Archive and database suspension:

  Everlaw Archive Suspension
Review Documents cannot be reviewed Documents cannot be reviewed
Data export Data cannot be exported Data can be exported
Reactivation time Typically hours Immediate
Optimization Optimized for long‑term retention and lower cost (6+ month) storage  Optimized for short‑term pauses and administrative workflows (< 6 months)

For longer term storage of databases (e.g. you don’t plan on revisiting the case), you may prefer to export your database before deleting the database entirely.

Learn more in our Everlaw Archive article.

Deduplicate native data against processed data during native upload

You can now deduplicate the documents in a native upload against processed documents already in the database. This new functionality gives you more control over your data and is useful in the following scenarios:

  • You have migrated native data from a different platform to Everlaw, and uploaded the migrated data as processed data or via our migration process. You want to deduplicate future native uploads against this data
  • You have reopened an Everlaw database by uploading the previously exported documents as processed data, and want to deduplicate new native uploads against this data
  • You have already uploaded received productions as processed data, and think that some data in your native upload might be duplicative of this data

This helps you:

  • Speed up review: Only review a single copy of a document
  • Reduce billable size: Avoid hosting multiple copies of the same document

Learn more in our Upload Native Data article.

Pinned Primary Date on Search and Data Visualizer

We have made the Primary Date metadata field more prominent in two locations: the Search page and in Data Visualizer. Primary Date is an Everlaw smart term that populates the most relevant date field for a document based on the document's type. This makes it useful for searches across document types and becomes particularly useful for visualizing the distribution of dates for your data across all document types.

Primary Date is now one of the top four suggested metadata fields on the Search page:

Before After

And the Primary Date visualization has replaced the Date visualization as the default pinned date visualization in Data Visualizer.

Before After

Improved filtering for Coding Suggestions 

We have improved the filtering options for Coding Suggestions in the results table and search page. Now, you can multi-select the options in the Suggestion section, which lets you filter down to any combination of suggestions you are interested in. Previously, you could only select Any or filter by one suggestion at a time.

Before After
Results table
Search page

Filter by code in coding category columns 

You can now filter by individual code(s) from within the results table column for a coding category added as a column to the view. For example, if you have added a column for the coding category "Responsiveness" to your results table view, you can now filter to view only documents with the "Responsive" code. As with other coding filters, you can filter by multiple codes using:

  • Any of: Documents must have at least one of the selected codes
  • All of: Documents must have all of the selected codes
  • Exclude: Documents cannot have any of the selected codes

  You could not previously filter using coding category columns.

Before After

Learn more about filtering a results table in our Filters in the Results Table article.

Update to filters on non-search homepage objects

When you add a filter to a results table for a homepage object, e.g. a binder or document set, the filter is no longer added to that object's card on the homepage. Instead, the filter is applied to a card in the Search column, which represents a search for that object with the filter(s) applied. 

This is the case both for objects accessed by selecting the relevant card from the homepage and for those accessed by building a search for the object.

Users who want to access the object with the applied filter should use the search card. This update should speed up the homepage performance for users with lots of objects. 

The images in the table show a binder card on the homepage after a filter has been applied. Before this release, the filter was applied directly to the object card. With this release, the filter is not applied to the object card and is instead displayed on a search card. 

Before the release After the release

Increased amount of text that document Q&A can consider

We have upped the limit for the amount of document text that the Document Q&A tool can analyze to generate its response. This tool can now analyze up to 1.2MB of text, which is typically 300-600 pages (depending on the density of the text on the page). Previously, the limit was 200-300 pages. 

If your document exceeds this limit, answers will only be generated on the first ~1.2MB of text. In the context panel, you are told how many pages are being analyzed.

Learn more in our Document Summaries, Topic Analysis, Custom Extractions, and Q&A article.

Include project-level user activity history in project ZIP exports

When exporting a project from Everlaw, either from the Organization home or Database Settings page, users now have the option to include User activity with the export. Including this information in the export provides a log of the historic project-level actions of all users, which is important in the case of any future audit of a closed Everlaw project. 


Learn more in our Delete, Suspend, Export, and Archive Databases and Projects article.

Customize the delimiter for export and production of multi-value address fields 

In the Project metadata settings, there is a new setting to select the delimiter (separator) used for multi-value address list fields (To, Cc, Bcc) in exports and productions. 

Here you can choose to keep the delimiter as the original value(s), or specify that they are separated with either a comma or a semicolon. This is helpful if the recipient of the export/production needs to load it into a system with specific requirements for how these values are separated because it optimizes your exports and productions to be loaded into their destination software.

Learn more in our Project Settings Metadata article.

Parent-level user reporting for sub-organizations

Parent-level Organization Admins can now download a single CSV report of all users across a parent organization and its sub-organizations. This is helpful for accelerating and standardizing access reviews and compliance reporting for large account hierarchies.

This setting is enabled by default for all sub-organizations but can be disabled by a sub-organization’s Organization Admin if they do not want to share this information with the parent organization. 

The report includes the following columns:

  • First Name
  • Last Name
  • User Identification Labels (formatted as a comma separated list)
  • Email
  • User type
  • Primary org
  • Date added to org (e.g. Nov 05, 2024 9:28 am PST)
  • Date account created
  • Date last project login
  • Org admin permission
  • Organization Name
  • Number of Active Projects
  • Number of Suspended Projects

To export this report, go to Organization home > Sub-organizations, and select Export all user data. This downloads the report to your computer.

Redaction stamps are editable 

Project redaction stamps and custom redaction stamps can now be edited. This is helpful when Project Admins need to update redaction stamps that are already in use and avoid time-consuming manual effort of replacing them.


Learn more in our Production Tools and Redaction Stamps article.

Everlaw AI Custom Extractions available via Everlaw’s API

Organizations using Everlaw AI Custom Extractions and Everlaw’s API to power internal reporting and deliverables can now pull AI custom extraction values directly from Everlaw, alongside standard document metadata, Bates/Control numbers, document IDs, and URLs. This eliminates the need to export CSVs of extraction fields and then ingest them separately into downstream tools.

Two existing endpoints now support returning AI extracted values:

  • GetProjectDocument
  • GetProjectSearchResult

A new endpoint, GetProjectExtractionFields, is also now available to help integrations understand which Custom Extraction fields exist in a given project before requesting their values.

To learn more about these endpoints, visit the API documentation for your region. For more information, visit Organization Admin: Everlaw API.

Improvements to Storybuilder work product included in project exports

You can now include Storybuilder content when you export a project. This improvement means that your project export can now automatically include narrative-building work product. Previously, all Storybuilder content had to be exported separately.

With this release, select the Storybuilder work product option to export the following along with your project export:

  • Deposition transcripts: The original native transcript file
    Note: Video files and sync files (MDB) are not included
  • Deposition transcript annotations: A CSV, DOCX, and PDF of the transcript annotations
  • People profiles: Exported as an importable CSV file

Storybuilder content is a key component of an Everlaw project. The new option to include it as part of a project export reduces the burden to exporting all your work product from a project.

Exporting this content might be required to meet data retention policies when a project is closed on Everlaw. Having the data accessible and importable can also be useful for later audits, or for hopping back into a project that re-opens.

Learn more in our Delete, Suspend, Export, and Archive Databases and Projects article.

Apply Storybuilder filters to results tables opened from the Storybuilder Evidence page

When you use the Review button to open a results table from your Storybuilder Evidence page, any filters or selections (checkboxes) you have applied to your view now carry over to the documents listed in the results table.

Prior to this release, a results table opened from the Evidence page always included all the documents, including document highlights, regardless of any selections or applied filters.

The results table itself does not have any filters applied to it; it is built as a search for the document ID of each document included.

You can rename the search to a more descriptive name.

Deposition transcript sync file downloads

You can now download the original native sync files and videos that were used to connect deposition transcripts to deposition videos within Storybuilder. This means that data uploaded to Everlaw is readily accessible for download, eliminating the need to search through personal file systems for the original video and sync files if they’re needed.

To download transcript files from a Storybuilder Deposition, select the More download/export options button. Then select Native transcript + sync file.

To learn more visit Work with a Deposition Transcript.

Export Deposition transcripts with only highlights

You can now export Storybuilder deposition transcripts with highlights, without the need for an accompanying annotations report. Previously, you could only export either the transcript with highlights and an annotations report or just the annotations report. Both options are available through the Export Annotations dialog.

To learn more visit Work with a Deposition Transcript.

Legal hold management centralized to organization level

With this release, legal hold matters become the primary home for configuring and managing legal holds in Everlaw. Database-specific legal holds are being migrated to matters. This centralizes legal holds at the organization and matter level. 

We’ve also introduced a new organization-level read-only role for visibility without edit access.

These changes are beneficial for:

  • Centralized management: All legal holds are configured and managed from the organization legal holds pages, rather than from two different interfaces
  • Clear separation between matters and databases: matters are now the only container for legal holds; databases can be linked to a matter but no longer serve as containers for legal holds
  • Safer, more flexible permissions: A new organization-level Legal Hold Viewer permission supports read-only visibility of holds without granting edit rights, replacing database-based workarounds for “view only” access

Edit hold notice acknowledgement status and questionnaire on behalf custodians

Organization Admins and Legal Holds Organization Admins can now edit the hold notice acknowledgement status and questionnaire responses for custodians. This adds flexibility for admins seeking to keep legal holds information on Everlaw up to date and helps keep legal hold notice statuses and questionnaire responses accurate, as custodians do not always respond to email notifications about legal holds, and may instead respond in-person or in other formats.

To learn more visit Track and Modify a Legal Hold.

Visual improvements

  • Exported Storybuilder deposition transcripts with highlights have reduced whitespace in their margins, making the visible text area wider.
Before After
  • The Storybuilder deposition transcript Download transcript menu now contains two sections: one for downloads (i.e. Native transcript) and one for exports (i.e. Transcript with annotations).
Before After

  • The button to create a new search card from an edited search has been updated. Previously, it read Save as new search. With this release, it reads Create new search. This should make it clearer that this option creates a new search card on the homepage.

    Before After
  • There are updates to the order of settings in the General tab on the Project Settings page, without any changes to functionality. For example, the Default binder sharing setting is now above the Default search grouping setting. Previously it was toward the bottom of the page. The table below shows the order of settings prior to this release and after this release.
Before After
  • We have updated the pop-up notifications for exports created from the results table. In particular, the notification for a completed export now includes a more obvious link to download the export directly from the notification.
Before After


 
  • We have improved the banner for the PDF view of container files and PDF portfolios. The banner now directs you to the file path explorer to view the extracted files
Before
After

_____

Do you have feedback about:

Was this article helpful?
1 out of 1 found this helpful

Do you have feedback about this article? Let us know