May 3, 2024 Release: Difference Viewer, collaborative searching, project templating improvements, and more!

AU release: April 30, 2024 PT (May 1, 2024 ACT)

Release for all other: May 3, 2024 PT

Knowledge Base updates: May 3, 2024 PT

With this release, we’ve added Difference Viewer, collaborative searching, project templating improvements, 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:

Difference Viewer

You can now efficiently view, compare, and code documents across entire near duplicate groups from a single view displaying only unique text. To access Difference Viewer, open the duplicates context on the left-side context panel of the Review Window and select “View differences” on the bottom left. Or, press “d” on the keyboard. 

diff viewer 1.gif

Difference Viewer will display a combined view of the text from an entire near duplicate group. 

  • Shared text is unmarked and is consistent across the entire group. 
  • Differences are highlighted boxes marking where the text is not the same across the entire group. 
  • On the right-side panel, you can see Variants representing the unique text, and associated documents, that could appear within each difference. 
  • On the top-left, you can change the Reference Document to view the group in relation to a particular document.

    diff viewer 2.gif

Navigating Difference Viewer

Differences represent places where text diverges within the near duplicate group. Click on a difference to select it. A selected difference will be highlighted. You can also navigate differences with the up and down arrows, entering the number of the difference they’d like to jump to, or using the up/down arrows on their keyboard. 

diff viewer 3.gif
Learn more about the Difference Viewer here


Collaborative Searching

You can now collaborate on searches and see changes to shared searches in real time! 

Sharing a Search and Managing Permissions

Similar to other collaborative objects, like binders, all users can now share searches with individual users or groups, granting varying levels of access:

  • View: Recipients can view the search but cannot make edits. They can create a personal copy of the search if they would like to make changes; these changes will not update the search for other users. 
  • Edit: Recipients can edit the search and its versions, including renaming. All edits are shared with collaborators on the search.
  • Full Access: Recipients can view, edit, rename, share, and delete the shared search.

You can share searches directly from the results table, with the current results table view becoming the default for collaborators.

You can also share searches from the homepage by selecting the three-dot menu on the search card and choosing "Share."

All search parameters (e.g. name, applied filters, grouping, etc), except Sort, are shared along with the search.  

Receiving Shared Searches 

Recipients of a shared search will receive a message in the Message Center with the search card attached. Clicking on the search card allows you to open up the search and begin collaborating. 

Editing Searches and Managing Search Versions

To edit any search, you can click the “Edit” button in the search toolbar and make modifications to the search in the query builder. 

All edits to a search are saved and logged in the search’s version history, accessible from the search card menu or the dropdown menu next to the timestamp in the results table. 

Each entry in the version history includes the timestamp of the edit, the type of edit, and the name of who made the edit.

Collaborating on a Shared Search

On shared searches, you will receive toast notifications whenever the search is updated when you are on the Results Table. 

To apply the latest changes, you need to select the “Refresh” button from the toolbar. When there are updates to the search, or documents have been added or removed from the result set, a green star will appear under the Refresh icon. 

If edits to the search occur when you are not on the results table, changes to the search will update automatically and you will see a yellow dot by the search timestamp when you next open the search. 

Learn more about collaborating on searches


EverlawAI Beta Update

Writing Assistant 2.0

This release brings major updates to Writing Assistant. We’ve overhauled the entire feature with an eye toward making it more intuitive to use and easier to incorporate into various writing and research workflows. 

Accessing the Writing Assistant

You can access the Writing Assistant by clicking the “Assistant” button in the toolbar of any Draft or Deposition. This will open a side panel where you can create new Writing Assistant tasks and view past tasks.

Everlaw will preserve and display a history of all Writing Assistant tasks for each Draft or Deposition, including (1) the user prompt and configuration settings used to create the task and (2) the full result from that task. 

Unlike before, all AI generations will be added to the side panel instead of directly into the body of the draft. This makes it easier to distinguish AI-generated content from human written content and gives you more control over whether and how you incorporate AI content into your drafts. 

Create new tasks

You can create new tasks by clicking the “Compose” button in the side panel. This will open a flow with two steps:

  • Evidence selection: you can select which documents they want to use as part of the task. Everlaw supports up to 500 documents per task. 
  • Task configuration: in this step, you can configure options that determine both the form and substance of the task. 

Rewriting existing content

If you have highlighted content in the draft body, the “Rewrite” option will be available in the Writing Assistant. Clicking “Rewrite” will open a configuration page where you can provide instructions on how to rewrite – or write against – the highlighted text and select additional pieces of evidence you want included as part of the task (evidence found in the highlighted text will be included automatically). 

Task history

Each task generated within a draft or deposition is represented as an entry on the task table. Clicking a task entry will open the full output and configuration view for that task. 

You can sort the task history by date and filter by user. To learn more about Writing Assistant, see this article

Review Assistant updates

A number of changes are being made to the Review Assistant as part of this release:

  • We are updating the existing topics task to improve topic coverage within a document and the depth to which a given topic is summarized
  • Entity extraction and sentiment analysis will be integrated into the topics task.
  • Dates and numbers extraction will be deprecated.

Document overview tab and topics task

The existing “Summary” tab in the Review Assistant context panel has been renamed “Overview” and will contain the description/summary task and the revamped topics task. Topics generated for a document will now appear as expandable cards in this tab. 

A topic card has up to 5 components:

  • Topic name: The high-level topic 
  • Topic summary: A bullet-point summary for the topic based on the document text. 
  • Relevant area: Navigation between document snippets relevant to the topic.  
  • Sentiment: The sentiment rating for the topic and an analysis of the rating. The rating will be “positive”, “negative”, “harmful and offensive”, or “neutral”. Everlaw will not display any sentiment information if the rating is neutral. 
  • Entities: Any entities associated with the topic, categorized into organizations and natural persons. Clicking on an entity will open up additional information about it and the option to add the entity as a hit highlight.  

Learn more about the topic task here

Coding suggestions search, filter, and export improvements 

With coding suggestions, you can quickly evaluate your documents against user-provided coding criteria in the review window or in batch from the results table. With this release, we are improving the search functionality and introducing a filter and an export option from the results table.

With the “Suggested code” search term on the search page, you can now specify “Yes”, “No”, or “Any” for the “Suggested” value. You can also select the “Actionable” checkbox to include only documents with at least one actionable suggestion. By default, this checkbox is selected, meaning that the search will return only documents for which an Apply or Remove action is recommended for the selected code.

You can also filter on the same parameters and export suggestions to CSV directly from the results table. Including coding suggestions in the CSV export will include a column for the “Yes” suggestions and a column for the “No” suggestions.

Learn more about coding suggestions here, and our overall set of beta features here.   


Project Templating improvements

With project templating, you can now copy over assignments groups and homepage folders, including the searches and assignment groups within them. Users with appropriate permissions can copy over homepage folders, searches, and assignment groups as part of a template when creating a new project. 

This means that searches relevant to multiple projects can now be copied into new projects from the beginning, even before documents have been uploaded into the new database.

  • Homepage folders must be shared with at least Edit permissions to a user group that will copy over to the new project. This allows users in the new project to manage the homepage folders. 
  • The only searches that will be templated into a new project are those that are included in homepage folders that are being copied from a template project.  Searches that are not in a homepage folder, or that depend on unselected settings, will not be copied over. 
  • Assignment inclusion criteria, review criteria, sort order, default review window layout, grouping, and configuration settings will all be copied over. User assignments and assignment groups that depend on unselected settings will not be copied over. 

To copy these objects to a new project, users with database and project administrator permissions on the existing project, or Organization Administrators, can navigate to Database Settings, add a new project, and select the settings they’d like to copy over. Organization Administrators can do this from the Organization Administrator dashboard when they create a new database.

Learn more about project templating here


Addition of GIS file type

Geographic Information Systems (GIS) files will now be identifiable and searchable as a new file type, GIS, on the platform. 

These GIS files will include KMZ, KML, GPX, SHP/SHX, and GEOJSON files. 

For GIS file types, Everlaw will:

  • Not extract children
  • Allow for native production, which means that you can produce GIS files in their native form and open them on the corresponding application (e.g. KMZ files are opened in Google Earth) for proper viewing. Please note that GIS data, unless it is a text-based GIS file type, is still not a fully supported file type and is not viewable on the platform.

Learn more about supported data types for upload on Everlaw here


Platform time/review activity export improvements

You can now see any in-platform changes to their project’s “Platform Time” and “Review Activity” tables reflected in your export. These will include: 

  • Applied filters, such as date range, User Group, and User
  • Any applied sorting behaviors on any column
  • Removal/addition of any columns

Learn more about Project Analytics here.

Have more questions? Submit a request


Article is closed for comments.