When a counterparty sends back a redlined agreement, Gerri analyzes each change, applies your playbook rules, and presents the results in a single review for your team to work through. This article explains how Gerri evaluates redlines, how to make decisions on each one, and what to do when the review is complete.

When Gerri processes a redlined .DOCX file, it identifies each tracked change and evaluates it against your playbook. For each redline, one of the following happens:

The more complete your playbook, the more Gerri can handle automatically. Changes that fall outside your playbook's coverage will always be routed to a reviewer.

Once Gerri finishes processing a file, you'll see a summary on the Review Details page showing how many redlines were detected and how each was handled. The About this review panel on the right shows when the review was initiated, who uploaded the file, which playbook was used, and who last updated it.

From this page you can:

Click Details on any redline to open its detail view. Here you'll see the exact change the counterparty made — deleted text appears as a strikethrough, and proposed new language is shown in blue underline.

Below the change, two sections provide additional context:

When a redline has been counterproposed, a Counterproposal block also appears on the detail page showing the proposed replacement text. Click Edit this proposal to modify the suggested language directly.

How you interact with a redline depends on whether Gerri was able to make an initial determination.

When Gerri's playbook covers a change, it will make one of four initial decisions - Accepted, Rejected with comment, Counterproposed, or Needs review and displays that result in the History panel. If you agree with Gerri's call, no action is needed. If you want to change it, click Edit decision to override.

The History panel also maintains a full audit trail of every action taken on a redline including Gerri's initial determination, any subsequent human decisions, and timestamps for each. This gives your team a complete record of how a decision evolved from first review to final outcome.

When no playbook rule covers a change (or a rule specifically escalates it), the redline will be marked Needs review and the decision panel will be presented to you directly. You have four options:

Accept this redline
Gerri will accept the counterparty's change and incorporate it into the updated .DOCX.

Counterpropose
Gerri will suggest replacement language based on your playbook. When a counterproposal is generated, a Counterproposal block appears on the detail page showing the proposed text. Click Edit this proposal to modify it, or describe what you're looking for and ask Gerri to generate a different version. The counterproposal will be written into the document as a tracked change.

Reject without counterproposing
The counterparty's proposed change will remain in the document, but Gerri will attach a comment explaining the rejection. You can edit the comment text before submitting.

Handle this manually
Gerri will add a comment in the Word document flagging the redline for manual attention. Use this when the change needs a conversation or offline review before a decision can be made.

Click Submit decision when you're ready.

Redlines are automatically assigned to reviewers based on your playbook. Each rule in your playbook can have a designated team member - when a redline touches that rule, it's assigned to that person by default. For redlines that don't match any rule, a default reviewer can be set at the organization level.

Assignments can be changed at any time. On the detail view for an individual redline, click Reassign next to the assigned reviewer's name to route it to a different team member.

At any point during your review, you can open the Ask about this review chat to ask Gerri questions about the agreement or any of the redline decisions. Click the chat icon from the review page to open the panel, then type your question in plain language — for example, asking how significant a particular change is or what the business impact might be.

Gerri has full context of both the agreement and the redline evaluations, so it can provide detailed, specific answers rather than generic guidance.

The Download menu on the Review Details page gives you four options depending on what you need:

Original doc (.DOCX) - The file exactly as it was uploaded, with no changes applied. Use this if you need to reference the counterparty's original markup.

Updated doc (.DOCX) - The version intended to be sent back to the counterparty. Each redline is handled as follows:

Audit doc (.DOCX) - No changes are made to the document itself. Instead, Gerri adds a comment to each redline containing the decision and the audit logic behind it. Use this for internal review or to give stakeholders a plain-language summary of every decision without altering the agreement.

Package of all - Downloads all three documents together as a single package.

If you'd like help writing a follow-up email to your counterparty, click Draft a response - Gerri will generate suggested email text you can use when sending the updated file outside of Gerri.