
AI Contract Redline: Compare Signed Documents Against Originals
Saves ~45 min
Details
Automatically redline any signed contract or agreement against its original and produce an exhaustive change report before counter-signing. Upload the returned signed document (PDF, DOCX, or scanned image), name the original stored in Google Drive (DOCX or native Google Doc), and the workflow OCRs the signed copy, locates and downloads the original from Drive, converts both to clean text, and surfaces every difference categorized by type: substantive wording and clause changes with section numbers and side-by-side quotes, filled-in fields such as parties, effective dates, dollar amounts, addresses, and signer names and titles, signature block label differences, DocuSign and other e-signature artifacts, OCR rendering artifacts to ignore, and shared typos worth fixing in the original. Built for legal contract review, NDA comparison, MSA and SOW intake, vendor agreement onboarding, employment offer letter audits, partnership and referral agreement review, sales contract redlining, real estate purchase agreement comparison, insurance policy diff, lease and rental agreement review, and any returned-document intake workflow where you need to know exactly what changed before filing or counter-signing. Eliminates manual side-by-side reading, accelerates legal and operations review cycles, and prevents accidental acceptance of unfavorable revisions hidden inside a returned signed document.
Tools In This Workflow
Workflow Steps
- 1Collect Inputs
- 2OCR Signed Document
- 3Find Original in Drive
- 4Download Original
- 5Extract Original Text
- 6Compare and Diff
- 7Deliver Report
Step 1 of 7
Prompt1
Collect Inputs
Goal: Confirm the two documents the user wants to compare: the signed/returned document and the original. | Inputs: User chat message and any uploaded files. The signed document may be referenced by File Management file_id (if uploaded earlier) or attached as a chat upload. The original is identified by a Google Drive name (preferred) or document ID. | Outputs: Two values: (1) signed_file_id - File Management file_id for the signed document; (2) original_query - the exact Drive search string for the original (file name including extension if known). | Constraints: If the user has not uploaded a signed document, ask them to upload it before continuing. If the user has not named the original, ask explicitly. Do not proceed until both values are known. Never invent file_ids or original names. | Success criteria: Both signed_file_id and original_query are captured and confirmed back to the user before continuing.




