Checks

Each playbook rule includes: 

• Issue definition — What the rule checks for. Example: “Limitation of liability caps direct damages at less than 12 months of fees.”
• Redline guidance — How to mark up the clause when the issue is found. This can include preferred language and fallback positions.
• Comment guidance — What comment to insert explaining the change or flagging the issue for review.
• Internal notes — Escalation steps, reviewer guidance, or context that stays internal and isn’t shown to counterparties.

​

Anatomy of a check

A complete rule is composed of three mandatory core elements and several optional parameters:

​

Mandatory elements

• Title: The name displayed in the Word Add-in during an active review.
• Rule: The explicit pass/fail criteria defining what the AI should inspect. If an agreement violates this rule, a “Fail” status triggers your redlining instructions.
• Redline Instructions: Specific instructions guiding the AI on how to rewrite, delete, or add language when a contract fails the rule criteria.

​

Additional features

• Comment Guidance & Audience: Generates automated contextual remarks explaining why a change was made. You can dictate whether these comments are Internal (for your team only) or External (directed at the counterparty).
• Fallback Instructions: Configure up to three alternative concession levels (e.g., “If counterparty rejects a 10-day review period…”). Each fallback includes description of when to use, distinct redline instructions, and comment guidance.
• Scope: Limits execution to First-party only, Third-party only, or Both parties based on whose contract paper is being reviewed.
• Risk Score: Sets a severity label (Low, Medium, High, or AI-generated) surfaced when the rule fails.
• Internal Documentation: Reference notes for your contract reviewers that do not impact AI decision-making.

​

Build a check

​

Four ways to build a check

1. Approve AI Suggestions: Add checks instantly by reviewing and approving the automated items generated under the AI-suggested checks window.
2. Generate with AI: Under the New Check menu, select Generate with AI, type your requirement (e.g., “Cap liability at 12 months of fees”), and let the platform map out a complete check.
3. Pull From Your Library: Reuse work by searching your organization’s existing library. You can save an exact linked check or use the Copy feature to create an independent, unlinked duplicate. You can also use pre-configured Pincites Managed industry benchmarks natively provided by Filevine.
4. Build Directly From Word: While reviewing a document in Microsoft Word, highlight a text snippet where you applied manual track changes, click the (+) button, and add context. The AI utilizes your real-world redline to construct a playbook check.

​

Rule writing tips

• Be specific about the trigger. “Indemnification is missing” is vague. “Agreement lacks mutual indemnification for IP infringement claims” is actionable.
• Include fallback positions. Your first ask might get rejected. Give LOIS for Word a second and third option to suggest.
• Match your team’s voice. If your comments are typically collaborative, write comment guidance that sounds collaborative. If you’re more formal, reflect that.
• Add escalation criteria. Use internal notes to specify when an issue needs senior review or client approval.

​

Test your rules

Before deploying a new check across your organization, utilize live testing to verify its accuracy:

1. Ensure you have sample agreements uploaded under the Test Contracts section of your playbook’s Knowledge Base.
2. Inside any check editing window, select the Test panel.
3. Choose a document, run the evaluation, and view a live simulation of the pass/fail results, the analytical explanation, and the exact redlines the AI will execute in production.