Once you have a Playbook, using it is straightforward. You open a contract, select the Playbook, and run it. The AI works through every rule and returns its findings directly in the document. This chapter explains what that output looks like and how to work through it efficiently.

Running a Playbook

1. Open a contract in Word and launch the SimpleAI sidebar
2. Select Playbooks from the navigation
3. Choose the Playbook you want to run
4. Hit run

The AI reads the contract, checks it against each rule in your Playbook, and returns its output. For a standard NDA this takes seconds. For a longer, more complex agreement it may take a little longer.

What the output looks like

Every rule in your Playbook is set to produce one of two types of output.

Redlines. Where the AI has identified a clause that doesn't meet your defined position, it proposes a tracked change directly in the document. You see the suggested language alongside the original, exactly as you would with a manually marked-up contract. Nothing is applied to the document until you approve it.

Red flags. Where the AI has identified an issue that requires your judgment rather than a straightforward fix, it surfaces a flag for your attention. Red flags don't propose specific language. They tell you something needs reviewing and, if your Playbook includes guidance notes for that rule, they will tell you what to consider and what to do next.

Working through the output

For each redline the AI proposes, you have four options.

Apply. Accepts the proposed change and inserts it into the document as a tracked change.

Dismiss. Discards the suggestion without making any change.

Edit directly. Opens the proposed language so you can modify it before applying. Use this when the AI has the right idea but the wording needs adjusting for this specific contract.

Regenerate. Asks the AI to try again. You can retry with no changes for a fresh attempt, or retry with additional instructions to steer the output.

     "Softer tone." "Use the defined term 'Services' instead of 'Deliverables'." "Shorter."

For red flags, review the issue and the guidance note attached to it. The guidance note will tell you what the rule is checking for, what your organisation's position is, and what to do if the issue is flagged — including whether to escalate.

Guidance notes and comments

If the lawyer who built the Playbook added guidance notes to a rule, you will see them alongside the output for that rule. Guidance notes are internal: they are instructions to you and your team, not visible to the counterparty.

They might explain the rationale for a position, tell you which fallback to choose if the counterparty pushes back, or direct you to escalate a particular issue to a senior lawyer or compliance. They turn the Playbook from a review tool into a workflow: the institutional knowledge of the people who built it, available at the point where it's needed.

If the rule is set to include comments, a margin comment will also appear in the document when a redline is applied or a red flag is raised. Unlike guidance notes, comments are visible to the counterparty. They explain why a change has been made or why an issue has been flagged, which reduces back-and-forth and makes your positions easier to understand.

Fallback positions

Some rules in your Playbook may include fallback positions: secondary positions the rule accepts if your preferred position can't be achieved. When a rule with a fallback is triggered, you will see both options and can choose which to apply based on the context of the deal.

For example, a rule on governing law might have English law as the preferred position and New York law as a fallback. If the counterparty's paper uses New York law, the Playbook surfaces both options and you decide which to apply rather than the AI making that judgment for you.

What to do after the Playbook run

A Playbook handles your standard positions. It won't cover everything. Once you've worked through the output, use the AI Assistant to handle what the Playbook didn't catch.

Ask: "Are there any issues in this agreement that the review may not have covered?"

Ask: "Are there any clauses that are unusual or more aggressive than market standard for this type of agreement?"

From there, use Redline and Draft as you normally would for any clause-level work that falls outside your Playbook rules.

Next chapter → Tesing Your Playbook

‍