October 7, 2026: A New Everlaw Add-in for Microsoft Word, Conversations in Deep Dive , Export Documents with Burned-in Redactions, and More!

Avatar
[System] Everlaw Support

With this release, we’ve added an Everlaw add-in for Microsoft Word, the general release of Conversations in Deep Dive, the ability to export documents with redactions burned in, 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:

Everlaw for Word

Everlaw for Word is a Microsoft Word add-in that brings your Story's evidence into the document you are drafting. Type or paste a Bates number and the add-in links it to the underlying evidence in Everlaw, and a task pane alongside your draft lists everything you have cited, shows evidence details, and opens any cited document in Quick Review. Until now, citing evidence in Word meant switching back and forth to find cited evidence, often as loose PDFs. Now, just open any Word document with Bates citations in the Word add-in, and the citations link back to the right version securely stored in Everlaw with all your team’s work product for that evidence.

Everlaw’s Word add-in is available for all organizations using Storybuilder, at no additional cost.

Note

The Everlaw add-in will be available in the Microsoft Word store along with the release on October 7, 2026 (Pacific Time).

Note

Everlaw for Word is not yet available in Gov Cloud.

Conversations in Deep Dive

With this release you can hold a conversation with Deep Dive and ask follow-up questions that build on the evidence that Deep Dive has already found, rather than starting over with each question.

Under the hood, Deep Dive has a more sophisticated approach to generating responses, and shares its thinking as it responds. You can watch that work as it happens and review the quotes it relied on.

Note

Deep Dive is not available in GovCloud.

Deep Dive ingestion tracking

The Deep Dive page will now track the status and estimated timeline of document ingestion. This will help teams understand the timeline for when they can start using Deep Dive.

Export documents with redactions burned in

You can now export documents to PDF with their redactions burned in, so redacted areas are fully opaque and the content underneath is removed rather than covered. PDF exports previously offered only gray, transparent redactions that left the text beneath them visible and selectable, which meant running a production whenever you needed to share a properly redacted copy outside of Everlaw.

Understand your project and build better searches with new MCP server tools

Everlaw's MCP server now includes tools that provide key information about a project, which lets you ask more sophisticated and detailed questions. The Everlaw details and associated tools are:

  • Search Term Reports
    • GetProjectSearchTermReports: Lists the search term reports that have been created on a project
  • Categories and codes in the project
    • GetProjectCodes: Lists the coding categories and codes available on a project
  • Freeform codes in the project
    • GetProjectFreeformCodes: Lists the freeform codes available on a project
  • Productions, and their details:
    • GetProjectProductions: Lists the productions on a project.
  • Extraction fields
    • GetProjectExtractionFields: Lists the extraction fields configured on a project
  • Bates prefixes
    • GetProjectBatesPrefixes: Lists the Bates prefixes in use on a project
  • Users
    • GetProjectUsers: Lists the users added to a project

Using these tools, an AI agent can get information about your project and leverage it to perform searches.

Visualize Coding suggestions in Data Visualizer

Data Visualizer now displays Coding suggestions. The Coding suggestions visualizations display how many documents were suggested for each code and each code category. This upgrade lets you visualize and filter for Coding suggestions as you do other review work and document metadata, which helps teams who use data visualizer for tasks like building document sets for review or QC.

Overlay metadata for all matching documents using a non-Bates identifier

When using a non-Bates custom identifier to overlay metadata, you can now overlay multiple documents from one load file value. There is no longer a one-to-one requirement for uniquely identifying every document to overlay. For example, if you want to add a value for an "Employee ID" field based on email address, you can now use an email address field as the document identifier and overlay all documents with value "good.employee@company.com" with the Employee ID field value of "12345". 

Select the AI model to use for extractions

You can now choose between two different AI models when generating extractions:

  • Standard: Best for straightforward extraction fields where the relevant information is clearly identifiable, such as names or dates
  • Advanced: Best for nuanced extraction fields with detailed descriptions, especially when relevant information may be expressed in different ways or appear in multiple locations

Custodian portal for legal holds

Custodians can now open a Legal Holds custodian portal that lists every hold notice they have received from your organization, shows what still needs their attention, and launches the acknowledgment workflow for each notice. Previously, a custodian could only reach the acknowledgment portal for one notice at a time, through the link in that specific email, which meant relying on saved emails or on admins to confirm which holds were still active.

Custodians reach the portal from a link included in their legal hold communications and sign in with a one-time code sent to their email address. No Everlaw account is required.

Granular permission settings for user groups in ECA projects

Project Admins in ECA projects can now customize user group project permissions. ECA projects previously offered only two fixed permission levels, Admin and Default, with no way to adjust the permissions.

Beta: Initial support for Magnet Axiom Artifacts

Everlaw now provides limited support for Magnet Axiom Artifacts. Magnet Axiom Artifacts are forensic collections from custodial devices, such as computers and cell phones. With this release, you can review uploaded XML exports on Everlaw.

Beta: This is a beta release, with ongoing development to improve handling for the file types (Artifacts) supported in this initial release and to add support for more file types and export formats over time. Please email support@everlaw.com with feedback.

The following classes of files are expected to render and be reviewable on Everlaw:

  • Emails 
  • Videos
  • Voice recordings and voice mails
  • Images (JPEGs, PNGs, etc)
  • XLS files
  • Chat data exported as HTML, with the following details to consider:
    • The chat files will be reviewable as an HTML image of the entire thread
    • Chat upload configuration selections, such as segment size, do not apply to these files
    • Standard Everlaw metadata fields are extracted
    • Axiom metadata from the XML file will not be associated with the chat file, but is included in the XML file(s) for the Artifact from which it’s derived

The following will be rendered their own XML files per Artifact: 

  • Contacts
  • Phone call logs
  • Internet history

Improved processing error visibility

This release includes some behind the scenes processing improvements for handling partially corrupt files, as well as user interface updates to build long-term support for identifying processing errors and warnings. The processing improvements allow Everlaw to partially process documents that would previously have been blocked from processing at all. These user-facing updates are available to all users who have permissions to access the relevant documents. The updates are:

  • New flags in the Uploaded search term
    • Error Message: Identifies documents  that have error messages indicating the reason for their processing failure
    • Warning Message Identifies documents with processing warning messages. A processing warning  typically indicates that a document was not fully processed or may not render as expected.
  • New flags in the native upload report

    Error Messages and Warning messages link to searches for documents in the upload with the given message type
  • New results table columns
    • Processing Error Messages: To view messages about processing errors
    • Processing Warning Messages: To view messages about processing warnings

  • New review window tool: View processing messages to view messages about the processing of your document.

    Note

    You must add this tool to your toolbar by customizing your review window.
     

This release includes these infrastructure improvements, but not all known errors are incorporated into the tools. With this release the following error and warning will be flagged and displayed using these new tools:

  • Error message: “Bad offset for central directory. Files cannot be extracted from the zip file which is likely corrupt”

  • Warning message: “Page <page number> is too large to OCR and has been skipped”

    Note

    This warning is specifically for documents reprocessed using the OCR optimized for English handwriting option.

    Note: this warning is specifically for documents reprocessed using the OCR optimized for English handwriting option.

We will continue to build support for more warning and error messages, and document them as they are released.

Create databases through the Everlaw API

You can now create a Review or ECA database in your organization through the Everlaw API, and optionally use an existing project or database as a template so the new database inherits its settings. Database creation previously required an Organization Admin to complete the workflow manually in the Organization home. The new endpoint, available to org-level API keys that have it enabled,  is PostOrganizationDatabase.

View KMZ and KML locations on a map in the review window

Documents whose native file is a KMZ or KML now open with a Map tab in the review window, plotting the locations in the file on an interactive map. Reviewing those locations previously meant downloading the native file and opening it in a separate desktop mapping application each time.

 

Grant Staging Drive upload permissions for Non-Organization Admin

Organization Admins can now give organization members a Staging Drive Upload Only permission, which lets them upload data to Staging Drive without receiving full Organization Admin access. Staging Drive was previously available only to Organization Admins, with no finer-grained control, so delegating uploads meant granting broad organization-level powers or routing data through a separate intake system. This permission bridges that gap.

Improved character counting in the Case overview field

The Case overview (Project Management > Project Settings > Everlaw AI > Case description) now counts only the characters you can see. Previously, the character count included hidden characters from rich text formatting. This improvement means that you can add more context and detail to your description, without formatting using up valuable characters.

Historical Staging Drive size in the billing API

The billing API now returns Staging Drive size for prior months, not just the current month. Staging Drive size became available in the API in the previous release, but only as a live current-month value, because end-of-month sizes were not being recorded.

Filter Project Analytics metrics by assignment group

The Platform Time and Review Activity tables in Project Analytics can now be filtered to the users in one or more assignment groups. Narrowing these tables to a single phase of review previously meant filtering by user group, which often does not match how review phases are staffed, or selecting reviewers one at a time.

Designation and highlight activity recorded in User Activity

Work on deposition transcripts in Storybuilder is now captured in User Activity. Adding and editing designations and highlights, along with designation imports and exports, are recorded as user activity events, so Project Admins can see who marked what testimony and when. These actions were not previously tracked, leaving no record of designation work alongside the rest of a project's activity.

Visual Improvements

  • When you assign a default time zone upon native upload to documents without time zone metadata: The metadata will display in the project time zone (converted from the raw timestamp with the default time zone applied). The metadata will have (time zone assumed at upload) appended.
  • On Project Settings > Groups: When creating a new user permission group from a template, the dialog now displays the permissions available to that group. This applies to new user groups created from either an Everlaw template or from an existing group. 
  • The Project Management > User Activity > Project Analytics > Platform Time and Review Activity tables have been updated. Filtering, adding and removing columns, setting the date range, and exporting all remain available, but their controls look different and filtering is now done from the table's Filter control rather than from separate dropdowns.
Before
After
  • On side menus tabs with subpages, the carets are now selectable to collapse or expand display of the subpages. Previously, selecting the main tab would automatically expand to display the subpages, with no way to collapse them again..
Before After
  • Annotations slipsheets created during PDF export have updated headings: The title for the annotations slipsheet has changed from Notes to Annotations, and the Notes section header has changed from Attorney Notes to Notes. We have also added clearer headers for the highlight and redaction notes sections.
Before After
  • As is mentioned in Export documents with redactions burned in, the PDF export dialogs have also been reorganized around a new Highlights and redactions step, which sits between Options and Slipsheets. Highlights and redactions are now separate options on the new step. The dialog’s step navigation has also moved from the top of the dialog to its left side.
Before After
  • The Native data uploads page is now separated into In progress  and Complete tabs. Previously, all native upload cards were displayed in one view.

Do you have feedback about:

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

Do you have feedback about this article? Let us know