Skip to main content
Review is the depth tool. Where Discovery pulls the same handful of values out of many documents at once, Review goes deep on the contract in front of you — typically a draft you’ve received from the counterparty, when you want to know whether it actually fits your standards. The check runs against a Playbook: your firm’s framework for a particular contract type, like an employment contract, an NDA, or a service agreement. Libra reads the contract, evaluates it against every Rule in the Playbook, gives each Topic a risk level, and cites the passage it based that on.

​
What’s in a Playbook

A Playbook is built in three nested layers — Topics at the top, Positions inside each Topic, Rules inside each Position. A quick example. For the Topic Working hours in an employment contract, your Starting position might consist of two Rules:
  • Weekly working time does not exceed 40 hours.
  • The agreed gross monthly salary compensates for no more than 10 overtime hours per month.
Together, those two Rules describe what an acceptable working-hours clause looks like for you. Libra checks the contract against the whole framework and tells you, Topic by Topic, where it holds up and where it falls short. You’ll learn how to build one in Create a Playbook. Once a Playbook exists, you can run it against any contract of that type, as often as you like.

​
Where a Review starts

There are two paths, and they end in the same result. From the Review page. Open Review in your project. Your Playbooks sit across the top under three tabs — My Playbooks, Shared and Libra — for the ones you built, the ones your team shared with you, and the ones Libra ships. New Playbook starts an empty one and Browse templates opens the full library. Pick a Playbook and choose Run; the Select Documents to review dialog opens, and once you’ve picked the files, Start Review kicks it off. You can select more than one file — the Review returns a single set of Topic verdicts across everything you attached. From Chat. Drop the contract into a chat and ask Libra to “review this against our standard NDA terms”, or pick Tools → Create new → Review explicitly. Libra offers you the matching Playbooks to choose from, runs the Review, and shows the result inline. See Reviews from chat. Either way the finished Review is saved into the project’s Reviews folder in Project files, and the run joins the list below the Playbooks on the Review page with its status, document count and Topic count.

​
What you get back

A Review result is structured, not narrative. Topics are numbered 01, 02, 03 and laid out one after another, each with a risk badge and a Reasoning paragraph. The Positions underneath start collapsed; open one to see its Rules. Once the Review has finished, Export in the result header writes the whole thing out as a Word document. See Understanding Review results for how to interpret each part.

​
When to use Review

A new draft of a contract you've negotiated before

The fastest way to spot where a redline has drifted from your standard positions.

A document you receive from the other side

Run a Review to see at a glance which Topics need a redline, and where the deviations actually sit.

A first pass on a high-volume queue

Every contract is measured against the same Topics and Rules, so you can triage a stack the same way and see which ones need a partner’s attention.

A research-grounded check

Auto mode swaps a Topic’s rules for a question — “is this clause enforceable under prevailing case law?” — and answers it from your research sources.

​
Review vs. Discovery

Both extract structured information from documents, but they answer different questions. When in doubt: if the question is “is this one contract OK?”, run a Review. If the question is “how do these many contracts compare?”, run a Discovery.

​
Tips for getting good Reviews

A Playbook with a couple of well-defined Topics gives you cleaner output than a sprawling one that tries to cover everything. Add Topics once you trust the basics.
“Weekly working time does not exceed 40 hours” is a rule. “Working time should be reasonable” is not. Specific, testable, unambiguous.
On a Starting or Fallback position, Add ideal language attaches the wording you would actually accept, and the Word add-in uses it when it redrafts a flagged clause. Not acceptable positions don’t take one — there is no ideal version of a clause you never want to see.
Red is the signal, whatever word it carries: Not met on a Starting or Fallback position, Detected on a Not acceptable one. Click through to the cited passage and confirm Libra read the contract the way you would before you act on it.

​
Next steps

Build a Playbook

Topics → Positions → Rules → ideal language.

Auto mode

Skip the rule-building and ask a research-backed question instead.

Understanding results

What the risk badges, Met counts, and citations actually mean.

Reviews from chat

Run one without leaving the conversation, and keep the result as context.