> For the complete documentation index, see [llms.txt](https://help.clausebuddy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clausebuddy.com/checklists/why.md). # Why? ### **Why use Checklists?** Checklists offer a structured yet flexible way to review legal documents, sitting comfortably between manual review and full AI automation. They help legal teams ensure consistency, support junior staff, and build institutional review knowledge. **✅ When you *****should***** use it:** * **To obtain structured, consistent reviews**\ Use checklists to ensure nothing is forgotten, especially in recurring document types or when multiple reviewers are involved. * **To review non-standard or complex contracts**\ Unlike automated review tools, checklists are flexible and can handle documents that don’t follow a fixed structure. * **To support junior team members**\ Checklists act as guidance or a reminder system, particularly helpful for less experienced lawyers during reviews. * **To stay in control**\ For lawyers who are hesitant to fully rely on GenAI, checklists offer a middle ground: human review, enhanced with light AI assistance. *** **❌ When you *****shouldn’t***** use it:** * **You want fast, fully automated results**\ If your goal is to review documents in seconds with minimal effort, the [Playbooks](https://help.clausebuddy.com/playbooks/) feature is more appropriate. * **You have no internal rules or review structure**\ Checklists require some upfront effort. If no checklist logic exists yet, you may need to first build that foundation. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.clausebuddy.com/checklists/why.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.