Contract Guides

How to Redline a Contract: Steps and Worked Example

By Anirudh Menon, Viaclause editor

Use Track Changes or Suggesting, check related clauses and exchange revisions until the final wording is agreed.

Updated October 11, 2026Contract redliningContract negotiation

To redline a contract, preserve the received draft, enable Track Changes or Suggesting, edit the wording and explain substantive proposals in comments. Review connected clauses, return the marked version and compare each response. Before treating a clean copy as the agreed text, confirm both sides approved it and follow the contract's amendment terms.

Comments	Comments do not edit clause text
Private notes	An @mention does not restrict the thread’s audience

Choose the right first action for your file

Redlining means proposing visible changes during contract review. Identify the version you received, the purpose of the review and who will consolidate the next turn. Agree on the format so neither side assumes the other sees the same markup.

Choose the workflow before editing
Received file	First action
Editable Word draft	Preserve it, create a working copy and enable tracking
Google Docs link	Confirm access and switch to Suggesting
Two versions with uncertain edits	Compare the correct original and revised files
PDF only	Request the editable source; check any conversion
Signed agreement	Check the amendment process before revising

How to redline a contract in Word

Microsoft’s Track Changes instructions document the Review tab controls. Enable tracking before editing and display relevant reviewers and revision types. All Markup is a view; check the filters too. Turning tracking off does not remove earlier revisions.

A comment requesting “45 days” leaves “30 days” in the contract until somebody edits the wording. Make the replacement in the clause, then explain it. Preserve useful numbering and formatting, and avoid burying commercial changes in stylistic rewrites.

Save the received file unchanged and create a named working copy.
On Review, select Tracking and Track Changes; show the relevant markup and reviewers.
Read the draft and schedules before changing related obligations.
Edit precise wording rather than putting the entire proposal in a comment.
Explain substantial changes with an external-facing business reason.
Check affected definitions, notices, schedules and cross-references.
Save and reopen the draft to confirm intended revisions and comments remain.

How to redline a contract in Google Docs

Switch Editing to Suggesting before changing the text. Google’s Suggest edits instructions explain that suggestions preserve the original until approved. If Suggesting is unavailable, request access or ask the owner to give you Commenter or Editor permission.

Edit the clause and explain the proposal in a comment. Review with Accept or Reject. For group review, Google documents Tools, Review suggested edits, followed by preview and Accept all or Reject all. Use bulk actions only after the decisions are settled.

Google documents conversion between Office tracked changes and Docs suggestions. Agree on the exchange format and check the returned file rather than assuming conversion preserves every aspect of a complex agreement. Keep the prior version available when changing tools.

Align internally and make the negotiation readable

List what the business needs before marking the draft. Separate requirements, possible fallbacks and questions needing another person’s decision. Assign payment to finance, delivery to operations and unusual legal risk to counsel licensed in the governing state. Keep private fallbacks out of the external draft.

Prioritize scope, payment, acceptance, liability, intellectual property, confidentiality, renewal and ending the relationship according to this transaction. A crucial delivery date can matter more than a stylistic preference. Read each risk in context rather than giving every sentence equal weight.

Make focused edits with concise reasons. If two changes can be decided independently, make that clear. Leave workable language alone. Ask rather than accuse when a returned draft is unclear. If tracking was off, disclose the problem and supply a comparison; do not present unmarked changes as untouched wording.

Use an issue list as a call agenda when email rounds stop resolving the same points. After the call, record the decided text and remaining questions. Allow time for people using different tools or needing clearer language. A deadline alone does not remove a misunderstanding.

Sample issue-list entry

Issue: Payment period. Proposed outcome: 45 calendar days after receipt of an undisputed invoice. Owner: Finance. Connected clause: Suspension trigger. Status: Open, pending payment timing and advance-notice confirmation.

A payment edit can require a second suspension edit

This synthetic example is not recommended legal wording. Assume calendar days, invoice receipt on day 0, an undisputed amount and no other provisions. The received clause requires payment within 30 days. Another clause permits suspension if the invoice remains unpaid 40 days after receipt.

Changing only payment to 45 days leaves suspension at day 40. The stated suspension trigger then falls five days before the new due date. Tracking makes the number edit visible; reading both clauses reveals the consequence.

A coordinated proposal could instead place suspension 10 days after the payment due date. The proposed 45-day period then produces day 55 under the example’s assumptions. Notice, disputed amounts and lawful suspension still need separate review.

Sample proposed clauses to check against the agreement and governing law

4. Customer shall pay undisputed invoices within 45 days after receipt.
8. Supplier may suspend services if an undisputed invoice remains unpaid 10 days after its payment due date.
External comment: We propose 45 days for payment and a corresponding suspension edit. Please confirm the grace period and any required advance notice.

Read the two triggers together
Version	Payment due	Suspension trigger	Relationship
Received wording	Day 30	Day 40	10 days after payment is due
Payment changed alone	Day 45	Day 40	5 days before payment is due
Coordinated proposal	Day 45	Day 55	10 days after revised due date

Check private notes before sharing

Microsoft’s feedback instructions distinguish comments from text edits. They explain that an @mention draws attention to a thread without excluding other authors. Tagging finance is not a privacy control.

Resolving a Word thread leaves it in the document until deleted. It can be reopened, and resolved threads remain in the Comments pane. Inspect that pane, not just the visible margin, before sharing an external copy.

Run Document Inspector on a copy and review the categories before removing anything. Microsoft warns that removed data may not be restorable. Stripping revisions from the draft intended to show proposals can destroy the markup the recipient needs. Preserve the internal history and clean the appropriate external copy.

Keep an internal review copy and a separate external draft.
Check the full Comments pane, including resolved threads.
Remove private notes without destroying intended proposal markup.
Inspect the chosen copy and read the resulting file before sending.

Return the next-turn packet and verify the execution copy

During negotiation, return the editable marked draft. If you include a clean reading copy, label it “proposed text” with the same version identifier. Name the baseline, major changes and open decisions. Our blackline versus redline guide explains comparison file selection.

Compare the returned draft with the version you sent. Word’s legal blackline instructions normally create a third document, but other output choices can modify a source. Preserve the inputs and read prompts about existing tracked revisions.

When decisions are settled, accept or reject the tracked edits in the intended final copy. Then read the full clean wording, check schedules and obtain required approvals. A software click is not every legal requirement for a contract change. For goods, model UCC section 2-209 retains relevant writing and waiver rules; check the governing state enactment and actual agreement.

For AI proposals, retain human responsibility. OpenAI’s Terms of Use require evaluating output accuracy and appropriateness before use or sharing, with human review as appropriate. Do not turn generated wording into a verified legal conclusion or replace the clause comparison with an automated summary.

Copyable first-round cover note

Attached: ServiceAgreement_Customer_2026-10-11_R1.docx
Baseline: Supplier draft received October 11.
Purpose: Proposed wording for discussion, not an execution copy.
Changes: Clause 4 proposes 45-day payment. Clause 8 makes suspension follow the due date.
Open: Please confirm the grace period and advance-notice requirement.
Please respond in this version or identify the baseline you use.

Frequently asked questions

Can ChatGPT redline a contract?

Treat wording it proposes as a draft requiring review. OpenAI’s terms warn against using output as a sole factual source or a substitute for professional advice. Verify the wording, connected clauses and document comparison before sharing proposals.

What are the best practices for redlining contracts?

Preserve the baseline, track changes, edit the text, explain substantial proposals, align internally, check connected clauses and compare responses. Keep private comments separate and verify the final clean copy.

Can you provide an example of a redline contract?

The example changes 30-day payment to 45 days and a receipt-based day-40 suspension trigger to 10 days after the due date. Under the stated assumptions, the coordinated trigger becomes day 55. It is illustrative, not a legal recommendation.

Can I redline a PDF in Word?

Word creates an editable copy, but Microsoft warns that conversion can change layout and mishandle tables, footnotes and tracked changes. Request the editable source where possible and compare converted text with the original PDF.

Should I accept every change before sending?

Not if the recipient needs to review your proposals. Preserve the marked draft. A separately labeled clean reading copy can help, but keep open decisions explicit. Prepare the execution copy after the relevant approvals.

Does resolving a comment remove private notes?

No. Microsoft says resolved threads remain until deleted and can be reopened. Check the Comments pane and external copy before sharing.

What if the agreement is already signed?

Preserve the executed version and check its amendment procedure, authority and governing law. A redline can help discuss a proposal, but should not silently replace the signed record.