Skip to main content

Reviewing contracts with Operator

Assess the risk of incoming contracts against playbooks from Operator

Written by Kaveesha Thayalan

Attach a PDF or Word document and ask Operator for a clear read on a document's risks against your defined playbooks, all within Operator.

When to use a risk review ✋


A risk review helps you to determine whether a document complies with your internal playbook or contains issues of concern. Operator's risk review can be used to:

  • Conduct a first-pass review of incoming contracts: For standard terms, e.g. vendor contracts, AI review in Operator gives you an initial compliance check against one of your playbooks.

  • Enable business teams to conduct initial reviews autonomously: End users can sense-check documents against your playbooks, with your Legal Team overseeing the broader contract lifecycle.

Redlining of documents is currently only supported in our Word plugin. To learn more, you can read our dedicated article on AI Review in Word.

What to use a risk review against 🖊️


You can run a risk review with Operator using:

  • Your organization's playbook(s). Operator uses the same playbooks as AI Review in Word, so any playbook your organisation has published is available. It checks the document against every rule in the playbook. To learn more about building your own playbooks, see our Setting up AI Review playbooks article.

  • A default playbook. If your organisation hasn't published playbooks, you can choose one of Juro's default playbooks for NDAs, DPAs and MSAs (SaaS).

  • No playbook. Operator reviews the document using its own judgement alone. It doesn't know your organisation's preferred positions, so the result is an AI view of the issues and not your organization's defined positions.

Running a risk review 📋


Anyone in your workspace can run a risk review, except users with the Viewer role.

You can start in one of two ways.

Begin with the suggested prompt

On the Operator page, select Get a document reviewed, and then Review document.

Operator fills in the relevant prompt in the input box and opens the file picker. You can add your playbook there if conducting a review against a playbook.

When prompted, choose your PDF or Word document from your desktop and upload it for review.

Start from your own prompt


In Operator, click the paperclip icon and attach your PDF or Word document.

Type your request, such as "Run a risk review against my NDA playbook", and click Send ↑.

Reading the results 📊


Operator groups compliance with your playbook using RAG statuses (red, amber or green).

🚨 NB: Ratings are a judgement made by the AI rather than a fixed formula, so treat them as a starting point for your own review.

Status

What it means

🔴 High priority

The clause shouldn't be accepted as it stands because it is a high priority issue as specified in a playbook or, if no playbook is specified, it is deemed to be high risk in general.

🟠 Medium priority

The clause shows a medium priority issue as specified in a playbook or, if no playbook is specified, it is deemed to be medium risk in general.

🟡 Low priority

The clause shows a low priority issue as specified in a playbook or, if no playbook is specified, it is deemed to be low risk in general.

Operator takes several factors into account when determining what status to apply to a clause:

  • Your playbook's parameters: On a playbook review, Operator checks every rule of the designated playbook and compares each clause against your acceptable and unacceptable positions.

  • What's typical: If a clause breaches your playbook but Operator considers it a commonly accepted term, it says so in the description rather than quietly lowering the rating.

  • Seriousness and likelihood: Operator weighs how costly or disruptive the issue could be, whether it could bring reputational or regulatory attention, and how likely any of this is to arise. It doesn't show a score for these, and they only inform the status.

  • Your side: The same clause can be a very different problem depending on which party you are.

Frequently asked questions❓


Can I narrow a playbook review to certain clauses?

Not at the moment. Ask for a review without a playbook and name the clauses you want covered instead.

What if my organisation doesn't have a playbook?

You can choose one of Juro's default playbooks (NDA, DPA or MSA (SaaS)), or run the review without a playbook.

Is my document saved to Juro after a risk review?

Not automatically. The document isn't added to your repository.

Do I need contract intake set up to run a risk review?

No. Risk review works on its own.

I can't see 'Review document' in the Submit menu.

Users with the Viewer role can't run a risk review. If you have another role, the feature may not be available for your workspace yet, so please reach out to our Support Team.

💁‍♀️ 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 🚀

Did this answer your question?