Skip to main content
Playbooks turn review policies, clause checklists, rule tables, fallback positions, and negotiation guidance into reusable document reviews. TextMine Playbooks screen showing reusable review rules for Vault documents Use Playbooks when a team wants consistent review logic across documents. Use Workbench when the review is still exploratory, and use Workflows when the review should run automatically or require approvals, reports, records, or integrations.

​
What a playbook contains

A playbook can include:
  • Review rules.
  • Expected positions.
  • Fallback positions.
  • Red flags.
  • Clause examples.
  • Risk severity.
  • Recommended actions.
  • Reviewer guidance.
  • Comparison criteria.
TextMine can parse playbook content from source text, policies, checklists, tables, uploaded documents, or Knowledge Base artifacts and convert it into structured review rules.

​
Playbook types

​
Where playbooks run

Playbooks can be run manually, from Workbench, from Vault, after Vault processing, or as a Workflow step. Runs are tracked as playbook applications with status, reviewed documents, results, and comparison details. Typical run sources:
  • A user runs a playbook against selected Vault documents.
  • Workbench applies a playbook during supervised analysis.
  • A workflow applies a playbook after document import or processing.
  • A document type or Vault configuration auto-applies a playbook where enabled.

​
Playbook outputs

A playbook run can produce:
  • Clause-by-clause findings.
  • Risk issue lists.
  • Pass/fail or accepted/deviation status.
  • Comparison against preferred and fallback positions.
  • Review memos or Word artifacts.
  • Evidence references to the underlying document.
  • Escalation or approval inputs for a workflow.

​
Analytics and improvement

Use Playbook analytics after a playbook has completed runs. Analytics shows compliant rules, non-compliant rules, rules needing review, unobserved rules, potential conflicts, and recommendations for improving rule wording or correction guidance. Analytics helps playbook owners decide whether repeated exceptions are genuine document issues, missing evidence, or playbook rules that should be clarified.

​
Example use cases

​
Agent guidance

Agents should inspect existing playbooks before creating a new one. If the user wants a repeatable policy review, propose a playbook. If the user wants routing, scheduling, approvals, emails, or integration steps, propose a workflow that applies a playbook. Before running a playbook across many documents, confirm the scope, Vault, document type, and expected output. Before changing a mature playbook, inspect analytics and ask before applying recommendations.
Last modified on June 25, 2026