> For the complete documentation index, see [llms.txt](https://help.jurisphere.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.jurisphere.ai/redline-analysis/overview-of-the-redline-analysis-tool.md).

# Overview of the Redline Analysis tool

The Redline Analysis feature accelerates your contract review process by automatically detecting and interpreting changes in your documents. It intelligently analyzes files with existing redlines or "track changes" and generates a clear, structured summary table of all revisions, saving you from the manual effort of reviewing each edit individually. 

***

## What it does

* **Summarizes Tracked Changes**: Parses `.docx` files with tracked changes and presents all edits in a clear, structured format.
* **Highlights Key Edits**: Automatically categorizes changes into substantive, typographical etc. so that you can address important changes instantly.
* **Simplified Review**: No need to manually scroll through long markups — get a bird’s-eye view of what changed and where.
* **Easy Export**: Download the reviewed redline summary as a Word file, ready for further edits and circulation.

***

## Ideal Use Cases

* Reviewing contract markups from counterparties
* Examining client-side edits in policy drafts or legal notices
* Quickly validating whether suggested changes were incorporated
* Preparing clean summaries of changes for internal review

{% hint style="info" %}
Jurisphere <mark style="color:red;">**cannot create a marked-up document**</mark> comparing two versions of the same document. The Redline Analysis tool only <mark style="color:green;">**reviews a word document with existing changes**</mark> made in track.
{% endhint %}


---

# 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.jurisphere.ai/redline-analysis/overview-of-the-redline-analysis-tool.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.