Everlaw AI Case Description

Before you use Deep Dive or Coding Suggestions for the first time, add a case description. The description adds context for the AI to better understand your questions and prompts. See the best practices section below for some tips.

Requirements

To write a case description, you must be a Project Admin.

Write a case description

To write a case description:

1. Go to Project Management > Project Settings > Everlaw AI > Case Description.

2. Enter your case description in the Case overview field. It must be a minimum of 40 characters and a maximum of 16,384 characters.
   

   Your changes are saved automatically.

Refine a case description

The case description must contain at least 300 characters before you can refine it.

1. Go to Project settings > Everlaw AI > Case Description.
2. Select Enhance.
   
   A suggested version appears in a popup.
3. Review the suggested version.
4. [Optional] To guide the refinement, enter instructions (e.g. “make this more concise”), then select Regenerate.
   
5. Select Replace to use the suggested version instead of the existing description, or select Append to add it to the end of the existing description.
   Generated versions are temporary until you replace or insert one into the case description. Closing the refinement dialog discards the generated versions.
   

View tips

To view custom tips to improve your case description, select the case description’s Show tips button. The displayed tips are suggestions specific to your current case description.

Best practices for writing a case description

The purpose of the case description is to provide  high-level background on your matter to help the AI  contextualize your questions/coding suggestions configurations and improve its responses. Similar to how you would describe the case to a reviewer unfamiliar with the matter, provide a concise summary describing the nature of the dispute. Include context and information that is generally relevant across your matter. This can include the legal claims at issue, jargon or technical terms, and key events and entities involved (including alternative ways an entity may be referred to in the text. In less than a page—ideally in no more than a few short paragraphs:

• What side of the dispute you are on
• Summarize the overall claims and issues
• Summarize the factual background
• Define key entities, acronyms, or terms of art that are essential to understanding the overall case. This is especially important when the context in which a term is used differs from its ordinary meaning.