Reading Playbook Results in the Web App

Once a playbook review has run, its findings live on the contract, not just in the tool that produced them. A colleague picking up the negotiation, or an approver signing off later, needs to see where the document stands against your standards without re-running anything.

A review takes the playbook’s positions, compares each one against the contract, and returns a single verdict per position:

The Playbook results view on the contract record is that record. It shows every position the review checked, the verdict each one got, and the reasoning behind it. This article is a reference for reading those results in the web app: where they appear, how to drill into one position, and how to re-run a review. Acting on the findings, inserting approved language or redlining a clause, happens in the Pactly Word plugin, not here.

Open the contract from the repository and go to its timeline. Each review pass shows up as a round entry, titled by the exchange it belongs to:

• Finalization for the finalized version.
• Sent to [party] for a round you sent out.
• Received from [party] for a round the counterparty returned.

Next to the round title, two counters summarize the pass: a green tick with the number of Compliant positions, and a red mark with the number of Not compliant positions. That ratio tells you how far the document is from your standards before you open anything.

Below the header, the entry expands into the Playbook results section. If the playbook the contract was reviewed against has since been deleted, this reads Playbook not found instead, with a note that the playbook could not be located.

The results list every position the review assessed, grouped under the playbook’s own group headings (for example Risk Allocation or Commercial Terms). Each row shows the position’s verdict icon and its name. Where positions carry written reasoning, Expand all and Collapse all open or close it for every position at once, so you can scan the whole pass or focus on one.

Every position resolves to one of five verdicts. There is no severity scale and no high / medium / low ranking, just where each clause stands against its position.

A position that carries reasoning shows a short preview inline when you expand its row, with an Explain button that opens the full position detail. The detail shows everything behind one verdict:

• The verdict at the top, labelled Compliant, Not compliant, or Uncertain, alongside the position name and its group.
• Playbook position: the requirement the document was checked against, taken from the position’s description in the playbook.
• AI Reasoning or Justification: why this verdict was assigned. AI Reasoning is the model’s own explanation, which you can rate with a thumbs-up or thumbs-down. Justification is a note a reviewer recorded when they confirmed or overrode the verdict, the human decision on top of the model’s read. A position shows one or the other.
• Relevant clauses: the passages from the document the review matched to this position. This is the evidence the verdict rests on.

Arrow controls (or the left and right arrow keys) step between positions without closing the detail, so you can work through the findings one after another.

If the document was reviewed against an older version of the playbook, or the playbook has since changed, the results can be regenerated. Re-run playbook review re-analyzes the current document against the playbook and replaces the verdicts. It is restricted: available only to master admins, only on the latest round, and never on a Finalization round. For everyone else the results are read-only, which is what you want, the record should not shift under an approver relying on it.

• Reviewing a Third-Party Contract: getting the document reviewed in the first place.
• Running a Playbook Review (Word plugin): acting on the findings clause by clause.
• What Is a Playbook?
• Workflows Overview: triggering reviews automatically by category.
• Recording Negotiation Rounds