Track Changes, Redlines, and Clean Copies for Legal Documents

The safest general workflow is to identify one authoritative working draft, preserve a recoverable pre-review milestone, use tracked edits for proposed text changes, use comments for focused questions, obtain decisions from the authorized reviewer, and generate the redline and clean copy from the same approved decision set.

Track Changes is evidence of proposed edits, not proof that an edit is correct or approved. A redline shows differences between identified versions; a clean copy shows the chosen text without intended review markup. Neither label proves substantive approval, signature, filing, service, or entry.

Microsoft distinguishes tracking changes from displaying them. Turning Track Changes off stops marking new edits; it does not remove existing revisions. No Markup hides unresolved revisions instead of accepting or rejecting them. Review with All Markup, the required change types, and all reviewers visible before making final decisions.

Confirm whether the workflow requires changes from everyone or only the current editor to be tracked. Verify the approved reviewer identity, because attribution becomes part of the review record and should not be silently rewritten later.

Anchor a comment to the relevant text, state the question or requested action, and identify who can decide it. Keep the discussion focused enough that the resulting edit and approval can be followed later.

Resolving a comment changes its display state; it does not necessarily prove that the underlying issue was decided or that the document was changed correctly. Follow the firm’s rule for preserving, resolving, deleting, or exporting comment history.

When reviewers edited separate copies, preserve each source and identify its role before using a comparison tool. Microsoft’s desktop Word guidance for Windows explains that legal blackline assigns an Original and Revised document and normally shows differences in a third document; Combine is intended for consolidating revisions from multiple reviewers. Availability, labels, and behavior vary by Word version and platform, so follow the current supported workflow for the firm’s approved installation.

The direction matters. A comparison can accurately report differences and still answer the wrong question if the source versions were reversed, incomplete, or not the intended baseline. Software finds differences; the authorized reviewer decides their meaning and disposition.

A system-generated legal blackline is a comparison output, not automatically the negotiated or lawyer-approved redline intended for an outside recipient.

After the authorized reviewer decides every required change, preserve the approved milestone and create separately labeled redline and clean outputs from it. Identify the compared versions and direction on the redline, and make the clean copy’s status and intended audience clear.

Reopen both exact outputs. Confirm that the redline reconciles to the clean copy, no required decision was omitted, and no late edit exists in only one output. A clean appearance is not enough when hidden revisions, comments, properties, or prior content remain.

The Florida Bar’s Ethics Opinion 06-2 supports confidentiality caution when lawyers send electronic documents, but it is advisory and expressly does not address metadata in discovery documents. Follow the responsible lawyer’s direction and the governing discovery, production, and firm process for those materials.

Use the firm’s approved inspection and sanitation process, understand what the tool can and cannot detect or remove, and work on a copy when an action may be irreversible or delete information the firm must preserve.

Record the approver, approval evidence, source versions, redline basis, clean-copy status, storage location, intended recipients, and any open issue. The next person should not have to guess which document now controls.