For Business Development Managers ·
What you'll accomplish
A partner sends back a redlined agreement and legal wants to know what changed before the review call. Reading both versions side by side and noting every deviation used to take 45-60 minutes. With a Claude Project set up for contract comparison, you get a plain-language summary of every changed clause in about 15 minutes, so the legal call starts with answers instead of a first read-through.
What you'll need
This is worth stating plainly: contract text is confidential, and it belongs in an account your company has approved for that purpose, not a personal ChatGPT or Claude login. Check with IT or legal if you're unsure which account qualifies.
In claude.ai, click New Project in the left sidebar and name it "Contract Redline Review." Add instructions describing the task: comparing a standard template against a partner's redline and summarizing every deviation in plain language, without giving legal advice or opinions on whether a change is acceptable.
Example instructions:
I'll upload two versions of a partnership agreement: our standard template and a partner's redlined version. Compare them clause by clause and list every difference in plain language. Don't offer an opinion on whether a change is acceptable. That's legal's call. Just describe what changed.
Under the Project's Knowledge section, or directly in a chat, upload your standard template and the partner's redline for this specific deal. If your Claude plan supports PDF uploads, use the original files rather than retyping content, since retyping risks introducing errors of your own.
What you should see: Both files listed as available for the chat to reference.
Troubleshooting: If the redline is a tracked-changes Word document, export it to PDF first so formatting stays intact.
Ask Claude to list every clause that differs between the two documents, with a plain-language explanation of what changed and why it might matter.
Example prompt:
Compare our standard template to the partner's redlined version. List every clause that differs, with the original language, the new language, and a one-sentence plain-language explanation of what changed. Group by section (term, liability, termination, revenue share, confidentiality, etc.).
What you should see: A structured list, typically organized by section, with the original clause, the redlined version, and a short explanation for each deviation.
Before you send this to legal, spot-check at least the two or three deviations that seem most significant against the actual contract text. Confirm the summary reflects what's really in the documents rather than a plausible-sounding paraphrase.
Flag which changes are likely to matter most:
Of the deviations you found, which two or three would typically be the highest priority for legal to review first, and why? Don't give legal advice, just flag which categories (liability, indemnification, term length) tend to carry the most risk.
Draft talking points for the legal call:
Based on the deviation summary, draft three questions I should ask legal on our review call to make sure we cover the changes that matter most.
Second-pass check for missed changes:
Re-read both documents one more time and confirm you haven't missed any clause-level difference, including small wording changes that might still carry legal weight (like "shall" versus "may").