> 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/multi-document-table/why.md).

# Why?

### **Why use Multi-document Table?**

Multi-document Table enables you to efficiently query multiple documents with multiple questions simultaneously, delivering all answers in a clear, structured table. This helps streamline contract review, compliance checks and comparison tasks by providing clear insights in one place.

**✅ When you *****should***** use it:**

* **To compare documents on large-scale**\
  Quickly analyse multiple documents simultaneously without manual effort.
* **To review grouped document sets**\
  Examine related documents (e.g., main agreements plus annexes) together for consolidated answers.
* **To extract data and facilitate reporting**\
  Export results to Excel or Word for easy sharing, reporting, and further analysis.
* **To reuse question sets**\
  Save and share predefined questions to maintain consistency and speed up repetitive tasks.

***

**❌ When you *****shouldn’t***** use it:**

* **If your review only pertains to a few documents or simple queries**\
  For small-scale reviews, manual checks or single questions might be faster.
* **If you're drafting or negotiating documents**\
  This tool focuses on analysis and comparison, not document creation or editing.


---

# 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/multi-document-table/why.md?ask=<question>&goal=<user_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.