About contract review

Contract review checks a contract against your team's playbook and gives you back a first draft of the review. You point it at a contract and a playbook; it reads one against the other and produces the outputs a reviewer works from.

Like all workflows, contract reviews run in the background, so you can start one and carry on with other work while it completes. The dashboard shows the review as queued and then as processing, and you can watch its progress there.

A playbook holds your standard positions

A playbook is your team's library of standard positions, held one issue at a time. Each issue sets out where your team stands on a single point. You build and maintain them in the Playbooks view.

A review checks the contract against every issue in scope. The standard it applies is the one your team wrote down, so two reviewers running the same playbook are working to the same positions.

What a review produces

A review returns reviewer-ready outputs:

• A deviation table — the findings, each with the drafting proposed to deal with it.
• An issue analysis — what the contract says on each issue in scope.
• A marked-up Word document — the proposed amendments carried into the contract itself.

The findings and the proposed drafting for the Word document are there for you to edit and approve - the judgement remains yours.

You can review the same contract again

You can run a review of the same contract and playbook as many times as you need — after the other side sends a new draft, for instance, or after you have changed the playbook.

Analysis only skips the drafting

Drafting the proposed amendments is the longer part of a run. When you want the findings alone, select Analysis only to return the analysis without drafting proposals.

A review you ran as analysis-only cannot be opened for editing, because there is no proposed drafting to edit. If you decide you want the drafting after all, start a new review of the same contract and playbook without the option set.