> For the complete documentation index, see [llms.txt](https://help.jurisphere.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.jurisphere.ai/word-add-in/review-playbooks.md). # Review Playbooks Review Playbooks let your team define how contracts should be reviewed, clause by clause, and apply those standards instantly during review. Whenever you review a standard agreement, you’re working with a structured set of: * Ideal positions * Acceptable fallbacks * Pre-approved language Instead of reviewing each agreement from scratch, you work with a predefined set of clause-level positions, including what is acceptable, what requires negotiation, and what should be flagged. This creates a consistent review standard across matters, teams, and levels of seniority. {% hint style="info" %} A Review Playbook captures how your team actually reviews and negotiates contracts, not just how templates are drafted. {% endhint %} *** ### When you would use a Review Playbook Review Playbooks are most useful when your team is handling: * Repetitive contract types such as MSAs, NDAs, leases, or financing documents * High-volume reviews where consistency matters * Multi-level review structures involving juniors and seniors * Client-specific positions that need to be applied uniformly They are particularly effective in situations where the same clauses are negotiated repeatedly and institutional knowledge needs to be applied consistently. *** ### How it is used in practice A Review Playbook is created once on the Jurisphere app, and then reused across documents when reviewing on the [Word Add-In](/word-add-in/overview-of-the-word-add-in.md). During review, the playbook acts as a reference layer: * Clauses in the document are evaluated against your defined positions * Deviations from your standards are identified * Reviewers are guided on what is acceptable and what requires changes This allows reviewers to move faster while staying aligned with your team’s expectations. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.jurisphere.ai/word-add-in/review-playbooks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.