Skip to content

Running a Playbook Review

When a counterparty sends you their paper, you have to check every clause against your organization’s standards before you can negotiate or sign. A playbook review does that pass for you: the Word plugin reads the document, compares it to a playbook, and returns a list of positions (one per topic) each marked Compliant, Not compliant, or Not applicable, with guidance and approved language for the ones that need work.

This guide covers the full loop: starting the review, reading the results, and acting on each position.

Open the contract in Microsoft Word, then open the Pactly pane from the ribbon. From the home screen, choose Review Contract, fill in the New Counterparty Contract dialog, and click Review.

Step 1 of 4
1
Open the document and the Pactly pane

Open the contract in Word, then click Pactly in the ribbon to open the task pane. If you are not signed in, sign in first.

2
Choose Review Contract

On the home screen, click the Review Contract card ("Analyze your document against your playbook").

3
Fill in the contract details

In the New Counterparty Contract dialog, enter a Name (at least 4 characters), pick the Contract type, and select a playbook under Choose a playbook. The default playbook is marked with a Default badge.

4
Click Review

Click Review to start the analysis. The plugin uploads the document and begins comparing it to the playbook you chose.

Step 1 of 4

You see AI analysis in progress while the plugin compares the relevant clauses in your document against the playbook. This typically takes 3 to 5 minutes depending on document length. You can tick Play sound when complete to be notified, then carry on with other work.

When the analysis finishes, the pane lists your positions. Each position is one check from the playbook (a stance on a clause or topic, like “Limitation of Liability” or “Governing Law”) with a compliance status. A counter at the top tracks your progress, for example 3/22 positions completed.

Every position carries one of three statuses. Work through them by what each one means:

Click a concept to learn more 3 concepts

The plugin found a relevant clause and it meets the playbook position. These usually need no action. Skim them, confirm, and move on.

A relevant clause exists but it deviates from your position. This is where the work is: negotiate a change, insert approved language, or accept the deviation with a written justification.

The position does not apply to this contract, so there is nothing to assess. Mark it accordingly so it drops out of your remaining work.

Open a position to see the detail behind its status, organized into tabs:

  • Evidence: the clauses in the document that matched this position. This is what was assessed. If nothing matched, you see “There were no matches for this position’s keywords and/or model(s).”
  • Preferred clauses: your organization’s approved language for this topic, ready to insert.
  • Notes: context recorded against the position.
  • Examples: sample wording for reference.

A Why Compliant? / Why Not compliant? block (the heading reflects the position’s status) explains the AI’s reasoning for the status it assigned, with thumbs up / thumbs down so you can give feedback on the assessment.

For every position, record a decision. On a flagged position you have a few moves: insert your approved fallback language, have the AI draft a fix, or override the assessment with a justification. The actions available depend on the status.

Acting on a flagged position
A flagged position
Not compliant Limitation of Liability A clause was found, but it deviates from your position.
Your moves
Insert fallback Adapt & Insert Rewrites your approved clause to match this contract’s own terms, then inserts it.
Insert fallback Insert as-is Drops the approved clause in unchanged, for when the wording already fits.
AI redline Generate Fix Drafts a redline toward your position when there is no neat fallback. Add guidance first.
Accept Override + justify Set the status, write a justification (up to 550 characters), and Confirm.

The flagged position Inserting approved language · the other moves are always available

On the Preferred clauses tab, you have two ways to bring approved language into the document:

  • Adapt & Insert rewrites the clause to match the contract’s own terminology (for example, swapping “Supplier” for “Provider”) before inserting it. Use this so the inserted language reads as part of the document, not a paste from elsewhere. See Using the Clause Library for how adaptation works.
  • Insert as-is drops the approved clause in unchanged.

Tick Include comment to attach the clause’s default comment alongside the insertion. Inserted language lands with track changes on, so the counterparty sees exactly what you proposed.

Each position has an AI action that changes with the status:

  • On a Not compliant position, Generate Fix drafts a redline that brings the clause toward your position. You can add guidance first (for example, “Make the liability cap lower”) in the optional guidance box.
  • On a Compliant position, Start Chat opens a conversation about the clause if you want to dig in.

Review anything the AI drafts before you insert it. See Using AI Chat for working with the plugin’s chat.

When you accept a deviation, disagree with the assessment, or confirm a position, set the status and add a justification, then click Confirm. The justification box takes up to 550 characters.

A justification is your audit trail. For a non-compliant clause you are accepting, explain why (“Client is strategic; business approved a higher cap”). For one you confirmed compliant despite different wording, say so (“Different wording, same protection”). Future reviewers and auditors rely on this record.

Work down the list until the position counter reaches the total. Aim to leave every position with a recorded status, and every accepted deviation with a justification. Your inserted clauses and edits are already in the document as tracked changes, ready to send back to the counterparty.

When the counterparty returns a revised draft, you record it as a new round and review again. The plugin compares rounds so you focus on what changed rather than re-reading the whole document.

Chat with us

We typically reply within a few minutes