Single-Document Playbooks

Last updated: June 3, 2026

Background

Single-document playbooks give your project team a structured, topic-by-topic compliance guide for a specific contract or agreement. Once a document is executed, run a playbook on it to surface the obligations, requirements, and key provisions your team needs to understand — organized by topic and cited back to the source language. Use single-document playbooks for standalone contracts, subcontracts, or any agreement where you need a focused compliance reference for one PDF. For teams managing multiple project documents at once, see Project-Level Playbooks.

Things to Consider

  • Run playbooks on fully executed documents only. Unsigned drafts or mid-negotiation versions will produce results that don't reflect your final obligations.

  • Playbook templates are configured by your CS team. Contact your Document Crunch representative to add or adjust topics.

  • Supported file types: .pdf, .doc, .docx (up to 500MB, 3,000 pages).

  • Single-document playbooks are accessed from the document view and are separate from project-level playbooks, which are accessed from the Playbooks tab on the project page.

Steps

Running a Single-Document Playbook

  1. From your Dashboard, open the document you want to run a playbook on.

Note: You will see an In Progress icon next to your upload on your Dashboard while the system processes your document. Once completed, the icon will disappear and you will receive an email letting you know your crunch is ready.

  1. Select Playbook as the solution type.

  2. Choose the playbook template to apply from the available list and confirm.

  3. The playbook run begins. You will receive a notification when it's complete.

Reading Your Playbook

  1. Open the playbook from your document view. Topics are organized into sections in the left panel

  2. Click any section to jump to it. Multiple topic accordions can be open at the same time.

  3. Each topic shows a synthesized summary with inline citations back to the source language in your document.

  4. Use the playbook as a daily reference — for time-sensitive decisions, scope clarifications, compliance guidelines, and site-specific requirements.

Best Practices

  • Run your playbook immediately after contract signing, before project kickoff.

  • Reference it during project meetings to validate decisions against contract requirements.

  • If your contract is amended or updated, re-run the playbook on the updated document to capture any changes.

Note: All markups will be visible to anyone who views this document.