Playbooks
A playbook is a set of rules that define your standards for a specific contract type. For example, an "IT Software MSA Buyer" playbook contains rules about liability caps, IP ownership, termination rights, and more. When you analyze a contract, Vallor compares it against your selected playbook.
Rules
Each playbook contains rules. A rule defines what a specific clause should look like. For example: "Limitation of Liability should include uncapped carve-outs for data breach and IP infringement." The AI checks each rule against the contract and flags gaps.
Redlines
A redline is a proposed change to the contract. Vallor generates redlines from three sources, each with different action buttons:
Opposing Party Changes
Tracked changes made by the counterparty (detected via Compare mode). Actions: Reject, Counter, Accept.
Internal Changes
Tracked changes made by your own team. Action: Discard only (since these are your own edits).
AI Suggested Modifications
Changes the AI recommends to align existing clauses with your playbook. Actions: Edit, Discard, Include.
AI Suggested New Clauses
Entirely new sections the AI recommends to fill playbook gaps. Actions: Discard, Insert with AI, Insert. These show a "Locate" button instead of "Highlight" since the clause doesn't exist yet.
Risk Levels
High Risk: Critical issues that could expose significant liability
Medium Risk: Important issues that should be addressed
Low Risk: Minor issues or nice-to-haves
Compliance Status
Compliant: Clause meets the playbook rule
Non-Compliant: Clause exists but doesn't meet the standard
Missing: Required clause is not in the contract at all
Review Status
Needs Review: Not yet acted on
Confirmed: Accepted or included
Discarded: Rejected or removed
Countered: Counter-proposal submitted
Two Review Views
The Playbook tab groups changes by rule (best for compliance-focused review). The Redlines tab shows changes in document order (best for sequential review). Both share the same data.