Accept or reject tracked changes

To accept or reject a tracked change in GitLaw, click the change in the document and choose Accept or Reject in the popover that appears. To resolve several changes at once, use the bulk controls on the card that proposed them in chat, such as Accept all. Every decision is saved as a new version, so nothing is lost.

Before you start: a document open in the GitLaw Editor, and edit access to it.

How do I accept or reject a tracked change in GitLaw?

GitLaw shows every proposed edit as a tracked change, the same revision marks you would see in Microsoft Word. Insertions appear as coloured text and deletions as strikethrough, each labelled with the author's name and the date. To resolve a single change:

1. Click the tracked change in the document. An action popover appears.
2. Choose Accept to apply the change: insertions stay and deletions are removed.
3. Or choose Reject to discard it: insertions are removed and deleted text is restored.

Each accept or reject creates a new version in the document's history, so you can view version history at any time. This works identically for changes made by you, a collaborator, the AI Agent or an imported Word file.

How do I accept or reject all tracked changes at once?

To resolve several changes at once, use the bulk controls on the card that proposed them. An Agent proposal in chat offers Accept all and Discard all. An incoming change request arrives as a Changes proposed card in chat, with Accept all and Decline all. Opening its review panel in the editor gives you the same Accept all button - it relabels to Merge & Close once nothing is left to decide - plus Cancel, which closes the review without deciding either way. In the document itself, changes are accepted or rejected one at a time. A bulk decision creates a single new version capturing the result, and all pending changes are shown inline first, so you can scroll the document and see exactly what has been proposed, who proposed it and when.

Turning Track changes on and off

When Track changes is on, every edit you make in the GitLaw Editor is recorded as a tracked change rather than applied directly to the document.

1. Open the document in the GitLaw Editor.
2. Toggle Track changes on using the control in the editor toolbar. When enabled, the control is highlighted and your edits appear as coloured insertions or strikethrough deletions attributed to your name.
3. Toggle it off to return to direct editing. Changes you already made with Track changes on remain as revision marks until accepted or rejected.

The AI Agent follows the same toggle. When Track changes is on, Agent edits also appear as tracked changes attributed to you, so your counterparty sees your name, not the AI's.

Tracked changes from imported Word documents

When you import a DOCX file that already contains tracked changes, GitLaw preserves those revision marks with their original author names. Imported authors are shown with an External badge, so you can tell them apart from GitLaw collaborators at a glance. Accepting or rejecting these marks works exactly like native GitLaw changes: click a change and choose Accept or Reject. When you export the document back to DOCX, tracked changes round-trip correctly and open with redlines in Word, so a counterparty working outside GitLaw sees a normal redlined Word document.

Frequently asked questions

Can I undo an accepted or rejected tracked change in GitLaw?

Yes, in effect. Every accept or reject creates a new version in the document's history. Open version history to view and compare the version from before the decision, then re-apply the wording you want. Restoring a previous version in one click is not yet supported.

Why do the AI Agent's edits show my name on them?

When Track changes is on, edits made by the AI Agent are recorded as tracked changes attributed to you. Your counterparty sees your name on the change, not the AI's.

What does the External badge on a tracked change mean?

The change came from an imported Word document. GitLaw preserves the original author's name from the DOCX file and marks them with an External badge to distinguish them from GitLaw collaborators.

Related articles

• Negotiate and redline a contract
• Review a document using Agent
• View version history
• Add comments to a document

Reviewed by the GitLaw team. Last updated 29 July 2026.