> ## Documentation Index
> Fetch the complete documentation index at: https://vaquill.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Contract Playbook Review

> Score contracts against your firm's own playbook and get counter-proposal language plus a draft negotiation email

**Best for:** in-house counsel who want playbook-grounded redlines without a Word add-in. Upload contract plus playbook, get a per-issue scorecard, counter-proposal language tied to firm-preferred positions, and a draft negotiation email.

Every contract is scored against every item in your playbook and returned as a redline package with counter-proposal language, ordered by priority. The playbook is reusable: upload it once and run repeated reviews against it.

|                |                                                              |
| -------------- | ------------------------------------------------------------ |
| Category       | In-House                                                     |
| Jurisdiction   | US                                                           |
| Practice areas | In-house, commercial, SaaS, vendor management, transactional |
| Runtime        | 6-25 minutes                                                 |

<Frame caption="The Contract Playbook Review launcher: document slots, inputs, and what you get">
  <img src="https://mintcdn.com/vaquill/IQprJWBbOye-Rc1f/images/wf-contract-playbook-review.webp?fit=max&auto=format&n=IQprJWBbOye-Rc1f&q=85&s=905e8c7c01b9e4b2b698b31fa98b045a" alt="Screenshot of the Contract Playbook Review launcher showing its document slots and input form" style={{ borderRadius: '0.5rem' }} width="1712" height="1367" data-path="images/wf-contract-playbook-review.webp" />
</Frame>

## What you need

| Slot                       | Required | Count | What goes in it                                                                     |
| -------------------------- | -------- | ----- | ----------------------------------------------------------------------------------- |
| **Contracts under review** | Yes      | 1-500 | The contracts you are reviewing against the playbook. PDF or DOCX, text-searchable. |
| **Firm playbook**          | **Yes**  | 1-20  | Preferred positions, fallbacks, deal-breakers per issue.                            |

<Note>
  The playbook slot takes **multiple documents**. Upload a main playbook plus addendums, per-contract-type splits (NDA, MSA, DPA), and a fallback-language library. All uploads are merged and deduped, and more-specific sources win on overlapping items.
</Note>

## Inputs

| Field                 | Type | Required | What it changes                                                |
| --------------------- | ---- | -------- | -------------------------------------------------------------- |
| Matter / counterparty | Text | No       | Labels the artifacts. Example: "Q2 MSA negotiations vs BigCo". |

That is the whole form. The playbook carries the configuration that other review workflows put in select fields, which is the point: your positions live in a document you control rather than in a picker.

## How it runs

A matrix-review pipeline with a playbook-parsing stage in front.

<Steps>
  <Step title="Parse firm playbook">
    Reads every uploaded playbook document, extracts the issue list with preferred positions, fallbacks, and deal-breakers, then merges and dedupes across sources.
  </Step>

  <Step title="Prepare">
    Turns the parsed playbook items into extraction-matrix columns, so the matrix asks exactly the questions your playbook cares about.
  </Step>

  <Step title="Extract and wait">
    Each contract is answered against every playbook item, with the supporting quote captured.
  </Step>

  <Step title="Normalize and score">
    Assigns each item one of five postures: matches, fallback, deviates, deal-breaker, or missing.
  </Step>

  <Step title="Synthesize">
    Portfolio synthesis across contracts: outliers, rejection patterns, and ranked playbook revisions. Verified before persistence.
  </Step>

  <Step title="Render">
    Writes the three DOCX artifacts.
  </Step>
</Steps>

## What you get

| Artifact                           | Format | Contents                                                                                                                                                     |
| ---------------------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Playbook Review Executive Memo** | DOCX   | Per-contract posture table (matches, fallback, deviates, deal-breaker, missing) plus portfolio synthesis, outliers, and ranked playbook revisions.           |
| **Per-Contract Detail**            | DOCX   | One section per contract: per-item scorecard, counter-proposal language tied to your preferred positions, and a draft negotiation email ordered by priority. |
| **Citations and Authorities Used** | DOCX   | Deduplicated authority appendix.                                                                                                                             |

## What this will not do

* Negotiate with the counterparty. The workflow drafts the asks; you send them.
* Update the playbook based on negotiation outcomes. The synthesis flags rejection patterns, but you decide whether to soften the firm's stance.
* Replace partner review on items marked deal-breaker. Some deal-breakers are deal-savers in context.
* Apply non-contractual context: relationship history with the vendor, regulatory pressure, business-team preferences.
* Verify that the playbook itself is current. The workflow trusts what you upload.

## Related

<CardGroup cols={2}>
  <Card title="Playbooks" icon="book" href="/docs/guides/playbooks">
    Building and maintaining the playbook this workflow consumes.
  </Card>

  <Card title="Contract review" icon="file-contract" href="/docs/guides/contract-review">
    The interactive, single-contract version.
  </Card>
</CardGroup>