Chat Mode - Gavel

Documentation Index

Fetch the complete documentation index at: /llms.txt

Use this file to discover all available pages before exploring further.

Gavel Exec Chat works best when it has context beyond the contract you have open in Word. Uploading a reference file — a letter of intent, a term sheet, a prior redline, or a comparable executed agreement — gives the AI a second document to work with. It can compare the two, check for consistency, flag deviations, or use the uploaded file’s language and structure as a model when drafting or redlining your agreement. File uploads in Chat are session-scoped: they apply to the current conversation and are not automatically available in future chats. If you need a document to be present in every session for a given matter, use Projects to attach it permanently.

What you can upload

Use Chat file uploads for reference material that is specific to a particular task or question:

The uploaded file becomes part of the conversation context. Gavel Exec treats its contents as reference material when responding to your prompts for the duration of that chat session.

How to upload a file

  1. Open a Chat session
    • With your contract open in Word, activate the Gavel Exec panel and start or open a Chat session.
  2. Attach the reference file
    • Use the file upload control in the Chat panel to select the document you want to add as reference material. Gavel Exec processes the file and confirms it is available for the session.
  3. Ask your question or give your instruction
    • Reference the uploaded document in your prompt. For example: “Redline this agreement based on the uploaded LOI” or “Flag any inconsistencies between this contract and the attached term sheet.”
  4. Review and apply the output
    • Gavel Exec incorporates the uploaded file into its analysis and response. If it proposes redlines, review them in the Chat panel and click Apply All to push them into your Word document as tracked changes.

Uploaded files apply to the current Chat session only. If you close the session and start a new one, you will need to upload the file again if you want to reference it. For permanent, session-persistent reference documents, add them as Project Files instead.

Example prompts using uploaded files

Ad-hoc uploads vs. Project files

Both approaches let Gavel Exec reference external documents, but they serve different purposes.

Chat file upload Project files
Scope Current chat session only All chats within the Project
Best for One-off references specific to a single task Ongoing matter context available across all sessions
Persistence Expires when the session ends Permanently attached to the Project
Setup required None — upload directly in Chat Requires creating a Project and adding files

Start with ad-hoc uploads when you are still exploring what reference material is useful for a matter. Once you identify the documents you consistently refer to, move them into a Project so they are always available without re-uploading.