October 1, 2025: Directly Upload from iManage, Bates Gap Report, and More!

Expected AU release: September 30, 2025 ACT

Expected release for all other: October 1, 2025 PT

Knowledge Base updates: October 1, 2025 PT

With this release, we've added the ability to upload directly from iManage, a Bates gap report, 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:

• Directly upload from iManage
• New PDF export file naming options
• Bates gap report
• Update the objects within homepage folders from more places
• Copy a Search Term Report from an Early Case Assessment (ECA) project to a Review project
• Customize metadata during upload to Early Case Assessment projects
• Updated ECA project permissions
• Updates to Deep Dive permissions
• Organization Admin login redirect [Reverted 10/6/2025]
• Rename suspended databases
• New legal hold notice merge field: #CustodianList
• 200 searches available within the Prior Search term
• Bates numbering parsing and OPT file processing improvements for processed uploads
• Updated format for Purview exports uploaded locally
• New fields for the Document endpoint through the Everlaw API
• Visual Improvements

Directly upload from iManage

Teams using iManage Work 10 on iManage Cloud can now directly upload native data files from iManage using Everlaw's iManage Connector. This integration not only dramatically accelerates your workflow but also automatically copies key iManage metadata as raw metadata in Everlaw, making your data more accessible and useful within Everlaw.

Learn more in our iManage Connector article.

New PDF export file naming options

Users can now select from three file naming options when exporting or downloading documents as PDFs from the results table or review window. Previously, all PDF files were automatically named based on their assigned Bates or control number.

The file naming options are:

• Bates number (e.g. ABC001.pdf)
• Filename (e.g. report.pdf)
• Bates number and filename (e.g. ABC001-report.pdf)

Learn more about exporting documents from the results table.

Learn more about downloading documents from the review window.

Bates gap report

With this release, a Bates gap report is available to export from any results table. Gaps in Bates numbers can indicate incomplete productions and/or missing data. Since this new report automatically identifies any such gaps, including in natively uploaded documents (# prefix), users are now enabled to act quickly to resolve issues with any unexplained missing data.

Learn more in our Bates Gap Report article.

Update the objects within homepage folders from more places

The option to add an object (such as a search or Storybuilder Draft) to, or remove it from, a homepage folder is now available when you are accessing that object. Previously, this option was only available when you were on the homepage. This applies to:

• Searches
• Binders
• Assignment Groups
• Uploads
• Storybuilder Story, Drafts, and Depositions
• Search Term Reports

This new option reduces a step for teams that collaborate and stay organized using folders.

Learn more in our Homepage Views and Folders article.

Copy a Search Term Report from an Early Case Assessment (ECA) project to a Review project

You can now copy Search Term Reports (STRs) that you create in an Early Case Assessment (ECA) project to Review projects within the same database.

Early in the discovery process, STRs in an ECA project are a crucial tool to understand your data and identify documents that should be promoted for full review. Once you've promoted documents into the Review project, those STRs can be equally valuable in helping your team get a handle on your review process. With this update, you can now get your STRs into a Review project without manually recreating them.

Learn more in our Search Term Reports article.

Customize metadata during upload to Early Case Assessment projects

Uploads initiated in ECA projects now have the option to create and apply custom metadata to the documents on the Additional options step, just as can be done for uploads into all other projects.

Learn more in our Applying Custom Metadata Values and Work Product During Upload article.

Updated ECA project permissions

We have updated the default permissions for user-created groups in ECA projects. Users added to a user-created group now have Receive permission for Search Term Reports (STRs) and View permission for Clustering. Previously, users exclusively in user-created groups were not able to access these tools.

Learn more in our Early Case Assessment Databases article.

Updates to Deep Dive permissions

We have updated the names and permissions for each of the permission levels of Deep Dive. The new permissions are:

• None: No access to Deep Dive (no change from previous)
• Ask: Ask, view and delete your own questions
• View and ask: Ask and delete your questions, and view all questions

Learn more in our Deep Dive Admin Guide.

Rename suspended databases

Organization Admins can now rename suspended databases, just as they would an active database.

The Rename database action is available from each database's three-dot menu on the Organization Admin > Project & Users page.

Learn how to rename databases.

New legal hold notice merge field: #CustodianList

A new merge field - #CustodianList - is now available for legal hold notice emails. This merge field inserts a bulleted list of all custodians (regardless of acknowledgement or release status) in the hold notice, in alphabetical order.

Learn more in our Legal Holds: Hold Notices article.

200 searches available within the Prior Search term

With this release, 200 previously run searches are available when you use the Prior Search term.

The searches included in the list are the 200 most recent searches that the user has accessed or favorited.

Previously, the limit was 50.

Bates numbering parsing and OPT file processing improvements for processed uploads

We've implemented several changes to enhance our processed uploader's Bates number processing and OPT file handling, allowing Everlaw to support a wider range of page numbering schemes for incoming processed uploads.

Updated format for Purview exports uploaded locally

When uploading a Purview export locally, you are no longer required to zip (compress) the files you have downloaded from Purview.

Instead, prior to initiating the upload, you should add the exported files into their own folder. You do not need to zip it. When you start the upload, select that folder to add to the uploader.

Learn more in our Uploading Microsoft Teams Files from Your Local Machinearticle.

New fields for the Document endpoint through the Everlaw API

Num pages and End Bates are both now available as fields for the Document endpoint for organizations using Everlaw's API.

Learn more in our API article.

Visual Improvements

We have made improvements to the dialog for creating an auto-code rule:

• We have updated the label for selecting the coding category to which you want an auto-code rule to apply, from Select designation to Select coding category
• The input field for this label has been updated from Enter portion of designation to Search coding category
• We have moved the information about what review work can be selected for an auto-code rule. It is now above the review work selection.

_____

October 6, 2025 update

Following feedback, we have reverted the recent change to the Organization Admin login flow.

Upon logging in to app.everlaw.com, Organization Admins are once again directed to their most recently accessed project, rather than to the Organization Admin > Projects & Users page.

_____

Do you have feedback about:

• this release document? Submit your feedback
• the features in this release? Email [email protected]