> 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-operations/what.md).
# What?
### What are Bulk Operations?
The Bulk Operations feature allows you to simultaneously apply one or more actions across multiple Word or PDF files. Instead of opening each file manually and making the same changes over and over, ClauseBuddy can perform these tasks in just a few clicks, often saving hours of tedious editing work.
Despite its simple interface, this module is remarkably versatile. Some typical examples include:
* Replacing placeholders (e.g. `[Client name]`, `[Date]`, `[Location]`) across ten different files in under 20 seconds.
* Bundling a set of DOCX files into one single document, or into a polished PDF package with a graphical cover page.
* Running a proofreading check on a batch of contracts to identify missing definitions, placeholders, or broken cross-references.
* Cleaning up formatting issues, such as removing consecutive spaces, empty paragraphs or manually inserted numbers.
* Ensuring all documents in a bundle use the same footer, author or track changes formatting.
* Generating an Excel table with all clauses across dozens of annexes that contain a specific keyword.
* Extracting legal definitions, digital fingerprints or clause fragments across a set of documents.
Bulk Operations are applied in three steps: (1) select the relevant documents, (2) select one or more operations, and (3) execute and export the results, either as modified files, a bundled DOCX/PDF file or a structured table.
Whether you're handling a set of templates, reviewing a batch of contracts or preparing annexes for signing, Bulk Operations allows legal professionals to automate complex tasks with confidence and precision.
---
# 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-operations/what.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.
