A Playbook is only as good as its rules. Once you've generated a Playbook, the real value comes from fine-tuning those rules so the AI redlines the way your team actually negotiates — catching what matters, leaving titles and structure intact, and avoiding unnecessary changes.
This guide covers how to write, test, and maintain strong Playbook rules. If you haven't built a Playbook yet, start with Building AI Playbooks.
Overview
In this article you'll:
Learn what separates a good rule from a vague one
Edit AI-generated rules before relying on them
Merge duplicate and overlapping rules that produce conflicting redlines
Protect section titles and document structure
Add conditional logic and fallback positions
Enforce exact wording with the verbatim keyword
Test against saved agreements and maintain the Playbook over time
Anatomy of a Good Rule
Each rule tells the AI a position to enforce and how to act on it. The clearest rules:
State a single, specific position — one concept per rule
Say what the acceptable language is, and what the fallback is if the counterparty won't agree
Use precise wording — the AI follows your phrasing closely
Step 1: Generate, Then Edit
Let Aline generate a first set of rules from a template, a rulebook, or a set of previously redlined agreements — then review and edit every rule before you rely on it. The generated rules are a strong starting point, not a finished Playbook.
💡 Best Practice: On the first run, read each rule carefully and test it. It's much faster to correct wording now than to unwind bad redlines later.
Step 2: Merge Duplicate and Overlapping Rules
When rules are generated from multiple documents, you'll often get several that cover the same ground — for example, three variations on limitation of liability. Overlapping rules can produce conflicting redlines.
Combine them into a single, clear rule so the AI has one unambiguous instruction per concept.
Step 3: Preserve Section Titles and Structure
A common problem: the AI rewrites a clause so aggressively that it removes the section heading.
Add a rule that explicitly preserves section titles — for example, an instruction that "Limitation of Liability" and similar headings must never be deleted when the clause is edited. Fold this into the relevant liability or structure rules rather than adding it as a loose one-off.
Step 4: Use Conditional Logic and Fallbacks
Real negotiation positions are conditional. Write rules that say if a condition is present, then apply a specific position — for example:
Requiring a waiver of subrogation only when workers' compensation coverage is in play
Limiting additional-insured language to the counterparty and no third parties
Add fallback provisions so the AI has an acceptable second position when the first is rejected.
💡 Conditional rules also cut down on noise — they stop the AI from redlining clauses that don't apply to the agreement in front of it.
Step 5: Enforce Exact Language With "Verbatim"
When a clause must match specific wording exactly, include the keyword "verbatim" in the rule. This tells the AI to insert the language word-for-word rather than paraphrasing — essential for indemnification, governing law, or any clause your legal team has settled on.
Step 6: Test Against Saved Agreements
Before rolling a Playbook out, run it against real, previously redlined contracts you already know the answers to. Compare the AI's redlines to how your team actually marked them up, and adjust any rule that over-reaches or misses.
📌 Use Suggesting Mode so changes come through as tracked suggestions you can accept or reject, rather than direct edits.
Step 7: Maintain and Extend
Playbooks are living documents. When a master agreement gains a new exhibit or a materially new term, add a new rule or category for it rather than stretching an existing rule.
💡 You can ask the AI chat to draft a new rule for a specific clause to speed this up, then edit it to fit.
💡 Best Practices
One concept per rule. Two positions in one rule is how conflicting redlines start.
Never ship generated rules unedited — treat them as a first draft.
Always pair a position with a fallback so the AI has somewhere to go when the first ask is refused.
Use "verbatim" for any clause where the exact words matter.
Test on contracts you already know before running a Playbook across live deals.
Add rules, don't stretch them, as your agreements evolve.
📚 Related Articles
Refining AI Prompts for Reports, Playbooks & Chat
❓ Need Help?
Tuning a Playbook that isn't redlining the way your team does? Click the Support button in Aline — send us a contract you've already marked up and we'll help you close the gap rule by rule.