Skip to content

What is a Playbook?

A playbook is your organization’s contract negotiation knowledge, written down in a way that Pactly’s AI can understand and apply. It captures what your most experienced legal counsel would look for in a contract—and makes that expertise available to everyone who reviews contracts.

Consider how contract review typically works without a playbook:

  1. A vendor sends you a contract
  2. You read through 30 pages looking for issues
  3. You’re not sure what’s “standard” for some clauses
  4. You ask a senior colleague—if they’re available
  5. Different reviewers apply different standards
  6. Some risks slip through; others get over-negotiated

A playbook solves this by codifying your organization’s standards. Instead of each reviewer deciding what matters, the playbook tells them: “Here’s what we require for liability caps. Here’s what we accept for governing law. Here’s what we never agree to.”

When you run a playbook review in Pactly, the AI applies these standards automatically—flagging issues and providing guidance, just like having that experienced colleague looking over your shoulder.

A playbook contains positions. Each position covers one contract topic—a specific type of clause or provision you care about.

Here’s what a position looks like in practice:

Position Name: Limitation of Liability

Guidance:

Our liability should be capped at the fees paid in the 12 months preceding a claim. Mutual caps are preferred. If the counterparty proposes unlimited liability or a cap exceeding 24 months of fees, escalate to Legal Director. Never accept unlimited liability for direct damages.

Keywords: “limitation of liability”, “liability cap”, “aggregate liability”, “total liability shall not exceed”

Fallback Clause:

The total aggregate liability of either party under this Agreement shall not exceed the fees paid by Customer in the twelve (12) months preceding the event giving rise to such liability.

When you run a review, Pactly’s AI:

  1. Searches the contract for clauses matching those keywords
  2. Reads the guidance to understand your requirements
  3. Evaluates whether the contract clause meets your standard
  4. Shows the result: Compliant, Non-Compliant, or Uncertain
  5. Provides the fallback clause if you need alternative language

Every position has these parts:

ComponentPurposeExample
NameIdentifies the topic”Limitation of Liability”
GuidanceYour requirements, written in plain language”Cap should be 12 months of fees…”
KeywordsHelp the AI find relevant clauses”liability cap”, “limitation of liability”
FallbacksPre-approved alternative languageYour standard liability clause

The guidance is the heart of each position. Write it as if you’re explaining to a junior colleague what to look for and what to do when they find it.

When you start a playbook review:

  1. Document Analysis: The AI reads the entire contract
  2. Clause Finding: For each position, it identifies relevant clauses using keywords and semantic understanding
  3. Evaluation: It compares each clause against your guidance
  4. Assessment: It determines compliance status:
    • Compliant — Meets your requirements
    • Non-Compliant — Doesn’t meet your requirements
    • Uncertain — Can’t determine; needs human review
    • Not Found — No relevant clause found
  5. Recommendations: For non-compliant items, it explains the issue and offers fallback language

The result is a prioritized list of issues with actionable guidance—not just a generic risk score.

These are complementary but different:

PlaybooksTemplates
For contracts you receiveFor contracts you create
Define what to look forDefine what to generate
Used with third-party paperUsed with your paper
Contain positions and guidanceContain actual contract language

Most organizations use both:

  • Templates when drafting contracts to send out (customer agreements, vendor contracts you initiate)
  • Playbooks when reviewing contracts received from counterparties

Creating playbooks (typically done by):

  • Legal operations
  • Senior counsel
  • Contract managers
  • Pactly administrators

These are the people who know your negotiation standards and can articulate them clearly.

Using playbooks (everyone who reviews contracts):

  • Legal team members
  • Business stakeholders
  • Procurement staff
  • Anyone reviewing third-party contracts

You don’t need to create a playbook to use one. If your organization has playbooks set up, you just select the right one and run a review.

If your organization already has playbooks:

  1. Learn which playbook applies to your contract type (ask your legal team)
  2. Run a review in the Word add-in
  3. Follow the guidance for each flagged issue

If you need to create playbooks:

  1. Start with your most common contract type
  2. Gather existing negotiation guidelines and redline history
  3. Define positions for your key risk areas
  4. Test against recent contracts
  5. Refine based on results

See Creating Your First Playbook for step-by-step instructions.

  • A playbook captures your negotiation standards so the AI can apply them
  • Each position covers one topic: what to look for, what’s acceptable, what to propose instead
  • Playbooks are for reviewing incoming contracts (third-party paper)
  • You don’t need to create playbooks to use them—someone else may have set them up for you