Write margin comments explaining my redlines to the other side
Turns your contract markup into short, persuasive comments that explain each change and keep the negotiation moving.
The prompt
Help me write the explanatory comments that go with my redlines to the counterparty.
Contract type and deal context: [e.g. "supplier MSA, $400k/year, long-term relationship"]
My changes: [LIST each change: section, original text, my revised text, my real reason]
Relationship tone: [collaborative / firm / formal]
What I can concede if pushed: [OPTIONAL - for my eyes only]
For each change, write a margin comment that:
- Is 1-3 sentences and addressed to the other side's lawyer or contract manager
- Explains the business or risk reason in neutral terms ("to align the cap with the fees paid") rather than accusing ("your clause is one-sided")
- Points to market practice only in general terms, never invented statistics or cases
- Offers a path forward where useful ("happy to discuss a mutual version")
- Never reveals my fallback position or internal reasons I marked as private
Also flag:
- Any change where my stated reason is weak and I should rethink or drop it
- Places where accepting their language would be fine and I may be over-lawyering
Return:
1. A table: Section | My change (short) | Margin comment.
2. A short cover email (under 120 words) sending the markup and naming the 2-3 points that matter most.
A qualified lawyer must confirm the substance of the redlines before they are sent; this only helps with how they are explained.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Legal & Compliance prompts
What to fill in
- e.g. "supplier MSA, $400k/year, long-term relationship"
- collaborative / firm / formal
- OPTIONAL - for my eyes only
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Explain to customers how my product's AI features use their dataA clear, accurate AI data-use FAQ and trust page section that answers what procurement and security teams actually ask.
- Explain the reasons for a credit denial in an adverse action noticeClear, specific, compliant principal-reason statements for a declined or counter-offered credit application.
- Flag defamation and privacy risks in an article before publishingA pre-publication read that highlights risky statements about people or companies, why they are risky, and safer edits to discuss with a lawyer.
- Track lien deadlines and preliminary notices to protect paymentA job-by-job tracker of notice and lien dates, plus a plain-English checklist so I do not lose my right to get paid.