> 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/bulk-compare/why.md).

# Why?

### Why use Bulk Compare?

Bulk Compare is designed for situations where you need to track changes across a large number of documents, without wasting hours manually opening and comparing each one. It gives you a bird’s-eye view of all deviations from your original, while still allowing you to drill down into the details.

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

* **To make high-volume comparisons**\
  Quickly compare your template against dozens of signed or negotiated versions.
* **To detect drafting hotspots**\
  Identify which clauses are most frequently altered by counterparties or colleagues.
* **To ensure cross-team alignment**\
  Check whether multiple teams or departments are using the same template — or how far they've drifted from the original.

***

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

* **If you only need one-on-one comparisons**\
  Use the regular [Text Compare](https://help.clausebuddy.com/text-compare/) module for individual document comparisons.
* **If you expect deep semantic analysis**\
  Bulk Compare doesn’t use AI to interpret or summarize — it compares wording literally.


---

# 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/bulk-compare/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.