Whether you need to draft amendments to existing agreements or review upcoming renewals, Juro's Operator can scan your repository data and execute key contract actions.
🚨 NOTE: You should always review Operator's responses before relying on them.
For more information, see our guide on working safely with AI in Juro.
Accessing Operator 🔑
Operator, once enabled, shows on your Home page as a chat-style window.
Under the message field where you can type prompts and requests in natural language, you'll see 3 action buttons:
Create a new document: generate a contract from a template, from scratch, or an uploaded file.
Get a document reviewed: send a document for approval without needing to access the contract, run a risk review on a PDF or Word document, or a redline review on a Word document.
Query your documents: a list of suggested prompts to get started with.
Send document for approval: send one or more documents for approval from the chat.
Operator can search your organisation's entire repository or by workspace before replying to your query in natural language. If it's unsure, Operator will clarify the ask instead of guessing. When it needs you to choose between options, it shows a short form so you can answer everything in one place.
💡NOTE: Juro's standard permission tiers govern Operator's actions. It excludes documents you don't have access to from its results.
Understanding how Operator works 👩🔧
After interpreting your query, Operator:
Searches your repository: Operator uses structured filtering and keyword search to define its search. It does this in two ways and performs best with well-structured data in smartfields:
Structured search: SQL-style lookups against smartfields and other structured data (contract title, template, workspace, dates, statuses, etc.) If this data is in a smartfield, Operator should find every correctly named instance.
Semantic search: here, Operator consults contract text/body when it thinks structured search is not sufficient. There is no 'exact match' parameter, and returns are capped at 300.
Reads and analyses your contract data: Operator's ability to filter at scale depends on your contract smartfields; when information is captured in these, Operator can reliably pull results from across your repository. As with all generative AI, specificity and accuracy produce better results (e.g. referencing a smartfield's name exactly in your query).
While the information you're looking for may exist in the contract body text, it's best to input this data into your smartfields so Operator can search for it across multiple contracts at once.
For more layered queries (e.g. "summarise the key terms of this agreement"), Operator retrieves and reads the full contract text.
Presents its findings: formatted as a direct answer, summary, or exportable table with the relevant data columns.
Using Operator ⚙
You can do any of the following actions using Operator:
1. Find contracts 🔎Operator can find contracts by: |
Criteria: status, counterparty, smartfield, renewal dates, and so on.
For example, you may wish to see all contracts awaiting approval in an easy-to-view, exportable dashboard. |
|
Keywords:
If you're looking for a specific counterparty, document name, or language, Operator can run a keyword search across your contracts to locate relevant documents. |
|
When results involve multiple contracts, Operator shows them in a table with custom columns for contract name, template type, contract status, contract owner, last modified date, and relevant smartfield data. When it doesn't find any matching results, Operator will outline what it searched for and suggest ways to amend or broaden your query.
Operator also remembers conversations. You can search for these, rename useful ones for ease of reference, and also delete those you no longer need:
|
You can also ask follow-up questions:
|
2. Analyse and summarise contract data 📈Operator can also search contract content and smartfield data to identify the contracts you're looking for.
This can range from a broad query (such as "Show all supplier contracts signed in the last 5 years") to a more tailored request, like the example below. |
|
Operator can also provide a summary of a small number of contracts or clauses as needed. |
3. Create and send contracts for approval ➡️Start the contract creation flow from the Operator portal: the video below guides users through a selected template's internal flows and into a draft contract in the relevant workspace. |
|
In addition, you can reference your repository's existing contracts and prompt Operator to draft new documents and amendments from a template (whose smartfields will also generate and populate) or from scratch.
You can also upload a file into the Operator chat and store it as a new document or a new version of a document in your workspace.
Once a document is in Juro, you can ask Operator to send it for approval with a message for approvers if you’d like. Operator sends the request to the approvers already set on the document and checks the details with you before anything goes out. |
4. Get a document reviewed 🔬Attach a PDF or Word document, and Operator summarises the key risks it finds, grouped by red, amber and green status. See Running a risk review in Operator for the steps. |
|
You can also ask Operator to redline a Word document against your playbook, either one you’ve attached or one that’s already in Juro. |
Getting the most from Operator 🪶
Below are some answers to questions you may have about using Operator safely and efficiently in your Juro environment:
Is my data safe when using Operator?
Yes, Operator uses the same security and access controls as the rest of Juro. Your contract data isn't used to train AI models.
For more details, see our Working with AI in Juro article.
What if Operator gives me a wrong answer?
AI output is probabilistic and may be inaccurate. Always verify important information directly in the contract. If you notice a recurring issue, let your Customer Success Manager know.
Can Operator update or action my contracts directly (e.g. add a clause and send it for approval)?
Yes, depending on a user's permissions. Operator can create contracts from templates, store uploaded documents, submit third-party paper through contract intake, apply AI edits to a document, and send documents for approval from the chat.
Approvers must be set in your templates first. Re-sending an approval request from Operator isn't supported yet.
How can I pull text data from my contracts in bulk with Operator?
Operator doesn't read the document text of hundreds of contracts simultaneously. For clause-level questions, it's best to query contracts one at a time or in small batches.
💁♀️ As always, our Support Team is happy to help you with anything further if needed. Start a chat with us right here by clicking the Intercom button in the bottom-right-hand corner of this page.
Alternatively, you can email us at support@juro.com 🚀