> 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/summarise-changes/why.md). # Why? #### **Why use Summarise Changes?** Summarise Changes helps you quickly understand what has changed in a document—whether those changes are tracked, commented, or simply present in a different version. It focuses on producing a clear, structured overview of all modifications, saving you from manually reviewing each mark-up or comparing versions line by line.\ You can use it to summarise Track Changes and comments, or to generate a differences report between two documents when no markup is available. Because it creates an intelligent summary rather than modifying content, Summarise Changes is most useful when you need insight, clarity, or a review-ready overview—not when you need to edit the document itself. *** #### ✅ **When you should use it:** • **To quickly understand all modifications in a document**\ A consolidated overview of insertions, deletions, rewrites, and comments helps you grasp what changed without scrolling through every mark-up. • **To compare two versions without Track Changes**\ When collaborators didn’t enable markup, you can still generate a clear summary of all differences. • **To prepare for internal or external review**\ A structured summary—grouped by clause, topic, or change type—helps reviewers focus on what matters. • **To reduce back-and-forth in negotiations or collaboration**\ Summaries give counterparts a clean, readable explanation of changes, improving communication. • **To customise how changes are presented**\ Choosing the language, level of detail, grouping, and extra instructions ensures summaries match your workflow or audience. • **To document changes for audit or version control**\ A written overview of modifications supports compliance, internal reporting, or file-tracking processes. *** #### ❌ **When you shouldn’t use it:** • **If you need to apply or accept Track Changes**\ Summarise Changes reports on modifications but does not process or modify them in the document. • **If the document needs formatting or technical cleanup**\ It does not handle structural tasks such as fixing spacing, metadata, or layout issues. • **If you require stylistic or substantive rewriting**\ Summaries describe changes—they do not improve or revise the underlying text. • **If only a single, obvious change needs reviewing**\ Running a full summary may be unnecessary when a quick manual check suffices. --- # 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.clausebuddy.com/summarise-changes/why.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.