Contract redline summary
@dealdesk/contract-redline-summary
Compare two versions of a contract (or one redline with insert and delete markup) clause by clause. Lists every change sorted by risk topic (liability, indemnity, termination, renewal, IP, data, payment) with the numbers that moved, then explains each in plain English with a suggested response. Not legal advice.
- Activity
- New: be the first to try it
- Installs
- 0 installs
- Likes
- 0 likes
- Clones
- 0 clones
- 1---
- 2name: contract-redline-summary
- 3description: Summarize a contract redline. Compares the original and the customer's revised version (or one file with insert and delete markup) clause by clause, sorts every change by risk (liability caps, indemnity, termination, auto-renewal, IP, data protection, governing law, payment terms, SLAs), shows the numbers that moved, and explains each change in plain English with a suggested response. Use when the user says "the customer sent back redlines", "what did legal change", "summarize the markup on the MSA", "compare these two contract versions", or "is anything in this redline scary?". Not legal advice.
- 4license: MIT
- 5---
- 7# Contract redline summary
- 9Turns a redlined contract into a short list a deal team can act on: what changed, how risky it is, and what to say back. The script finds and sorts the changes so nothing is missed; you explain them.
- 11## When to use
- 13- A customer or their counsel returned a marked-up MSA, order form, DPA, or SOW.
- 14- Before a deal review or a call with legal, to know which changes matter.
- 15- Not a replacement for a lawyer. For high-risk changes the answer is often "send to legal", and that is a fine answer.
- 17## Inputs
- 19One of:
- 211. **Two versions** as plain text: `data/original.txt` and `data/revised.txt`. From Word: open the redline, Review, choose "Original" and save as plain text, then choose "No Markup" and save again. From PDF, copy the text.
- 222. **One redline** with markup: `{++added++}` and `{--removed--}` (or `[+added+]` and `[-removed-]`) in `data/redline.md`.
- 24If the user pastes text into chat, save it to `data/` first. Ask which side the user is on (seller or buyer) if it is not clear; it changes the advice.
- 26## Steps
- 281. Save the inputs in `data/`. Check both versions look complete (same opening clause, similar length).
- 292. Run one of:
- 31 ```bash
- 32 node scripts/clause-diff.mjs data/original.txt data/revised.txt --out out --name redline
- 33 node scripts/clause-diff.mjs --markup data/redline.md --out out --name redline
- 34 ```
- 363. Read `out/redline.json`. Every entry has the clause, type (`changed`, `added`, `removed`, `renumbered`), risk (`high`, `medium`, `low`), topics, added and removed text, and numbers before and after.
- 374. **Read each change yourself.** The risk tag is a keyword guide, not a judgment. Decide in one sentence what the change means for the user's side, and raise or lower the risk if the keyword tag is wrong. Say when you did.
- 385. Write `out/redline-summary.md` using the template below and show it.
- 396. If the deal also changed commercially (payment terms, discounts, renewal caps), suggest running `discount-approval-check` with the new terms.
- 41## Output format
- 43```markdown
- 44# Redline summary: <contract>, <customer> (<date>)
- 46**Bottom line:** 4 high-risk changes need legal; 2 are commercial and can be handled by the deal team.
- 48| # | Clause | Change | Risk | What it means for us | Suggested response |
- 49| --- | --- | --- | --- | --- | --- |
- 50| 1 | 5 Limitation of Liability | Cap raised from 1x to 2x fees; data and confidentiality breaches uncapped | High | Unlimited exposure on any data incident | Legal. Offer a separate super-cap (for example 3x) instead of uncapped |
- 51| 2 | 4 Termination | Customer may terminate for convenience on 90 days notice | High | Multi-year value is no longer committed | Accept only after month 12, or with a fee |
- 52| 3 | 2 Fees and Payment | Net 30 to Net 60; late interest removed | Medium | Slower cash | Counter at Net 45; needs finance approval |
- 54**Unchanged but worth a look:** <anything the user asked about that did not change>
- 55```
- 57## Guardrails
- 59- Always say "not legal advice" once, and route high-risk items to the user's legal contact rather than giving a final answer.
- 60- Quote the contract exactly when you describe a change. Never paraphrase a number.
- 61- If the two versions look like different documents (very few clauses matched), stop and ask the user to check the files.
- 62- Do not send anything to the customer. Draft responses only.
