Redlining generates a comparison showing changes between two document versions. It may be produced by tracked changes during editing or by comparison software applied to separate files.

Comparison tools identify changes tracked changes would have missed.

Alternative Names:

Track Changes, Comparison Redline

Why it Matters?

Comparison software is more reliable than tracked changes for verifying what changed, since a counterparty can accept changes before returning a draft and eliminate the visible history. Running a comparison against the version sent rather than relying on the redline received is basic transaction discipline. Residual tracked changes and comments in produced documents are also a recurring metadata disclosure problem.

Frequently Confused with

Related terms

Frequently asked questions

Why run a comparison rather than trust a received redline?

Why run a comparison rather than trust a received redline?

Because a counterparty can accept changes before returning the draft, eliminating the visible history of what was altered.

What metadata risk does redlining create?

What metadata risk does redlining create?

Residual tracked changes and comments in documents that are shared or produced, which reveal editing history unintentionally.