Legal contract review and executive summary generation for in-house counsel

In-house counsel teams face a common bottleneck: reviewing incoming contracts and producing executive summaries takes hours of manual work. A contract arrives via email, someone reads it, flags risks, identifies key dates and obligations, then writes a summary for stakeholders. Repeat this fifty times a month and you've lost entire days to repetitive analysis.

The real cost isn't just time. It's inconsistency. Different reviewers highlight different sections. Some summaries are thorough; others miss critical renewal dates or payment terms. By the time a contract reaches decision-makers, critical information may have been diluted or poorly communicated. And if a contract needs revision, the cycle starts again from scratch.

This workflow solves that problem by combining three focused AI tools into a single automated pipeline. You upload a contract, and within minutes you get a structured executive summary with key commercial terms, risk flags, and action items. No manual handoff. No rework. Just consistent, reliable analysis that your team can actually use.

The Automated Workflow

We'll use Zapier as the orchestration layer here, though n8n and Make offer similar capabilities with more customisation. The workflow has four core steps: trigger on document upload, extract and analyse the contract, generate a summarised version, then store everything in a shared location.

Step 1: Set up the trigger

Start by creating a Zapier zap that monitors your chosen input source. For most in-house teams, this means watching a specific email address, a Google Drive folder, or a SharePoint library. We'll use Google Drive as the example since it's straightforward and works well for document-based workflows.

Create a new Zap in Zapier and select "Google Drive" as the trigger app. Choose the event "New File in Folder". Connect your Google Drive account and select the folder where contract uploads land.

Copy
Trigger: Google Drive
Event: New File in Folder
Folder: /Contracts for Review/
File Type: PDF (add a search filter for .pdf)

Configure a name filter to catch only PDFs. This prevents processing of notes, comments, or other non-contract files that might land in the same folder.

Step 2: Extract contract text using Chat with PDF

Once a PDF arrives, you need to extract its full text and ask it specific questions. Chat with PDF by Copilotus provides an API endpoint that accepts a PDF URL and returns extracted text and answers to your prompts.

In Zapier, add a new action step using a "Webhooks by Zapier" action to call the Chat with PDF API. You'll need your API key from Copilotus.

Copy
POST https://api.chat-with-pdf.copilotus.io/v1/analyze
Headers:
  Authorization: Bearer YOUR_API_KEY
  Content-Type: application/json

Body:
{
  "pdf_url": "{{2. Download File}}",
  "questions": [
    "What is the contract term and renewal date?",
    "What are the payment terms and amounts?",
    "Who are the contracting parties?",
    "What are the key deliverables or services?",
    "What are the termination clauses?",
    "What liabilities or indemnities are mentioned?",
    "Are there any unusual or restrictive clauses?"
  ]
}

The response will be structured JSON containing answers to each question, plus the full extracted text. Store these results in a Zapier storage variable for the next steps.

Copy
Response format:
{
  "answers": {
    "contract_term": "24 months, ending December 31, 2025",
    "payment_terms": "$50,000 annually, quarterly invoicing",
    ...
  },
  "full_text": "[entire contract body]"
}

Step 3: Generate a polished summary with Quillbot

Now you have raw extracted data. Quillbot can take that and generate a professional, concise executive summary. Rather than feeding Quillbot the entire contract, you'll pass it a structured prompt containing the key information Chat with PDF extracted.

Add another action in Zapier. Use "Webhooks by Zapier" again, this time targeting Quillbot's API.

Copy
POST https://api.quillbot.com/api/v1/summarize
Headers:
  Authorization: Bearer YOUR_QUILLBOT_API_KEY
  Content-Type: application/json

Body:
{
  "text": "Contract between {{Company Name}} and {{Counterparty}}.\n\nTerm: {{Contract Term}}\nPayment: {{Payment Terms}}\nDeliverables: {{Key Deliverables}}\nTermination: {{Termination Clauses}}\nRisks/Restrictions: {{Unusual Clauses}}",
  "length": "short",
  "tone": "professional",
  "focus": "key business terms and risks"
}

Quillbot's API accepts free text or pre-structured input. A short summary generated at "professional" tone will be 150-250 words; ideal for busy executives who need the essentials without the contract's full 30 pages.

Store the summary output in another Zapier variable.

Step 4: Transcribe and format with Wispr Flow AI

Before writing the final output, you may want to add voice notes or format the summary for easier reading. Wispr Flow AI specializes in speech-to-text and can also handle basic text formatting and templating.

Add a final action step using Wispr Flow AI's API. You'll format the summary into a standard template that your legal team uses.

Copy
POST https://api.wispr-flow.ai/v1/format
Headers:
  Authorization: Bearer YOUR_WISPR_API_KEY
  Content-Type: application/json

Body:
{
  "content": "{{Quillbot Summary}}",
  "template": "legal_executive_summary",
  "metadata": {
    "contract_parties": "{{Company Name}} and {{Counterparty}}",
    "date_received": "{{Today's Date}}",
    "reviewer_assigned": "{{Assigned Counsel}}"
  }
}

Wispr will return a formatted document ready for sharing. The template ensures consistency across all summaries your team produces.

Step 5: Store the output and notify your team

In the final Zapier action, save both the original contract and the generated summary to Google Drive or your document management system, then send a notification.

Copy
Action: Google Drive - Create Spreadsheet Row
Spreadsheet: Contract Review Log
Columns:
  Contract Name: {{File Name}}
  Date Received: {{Today}}
  Counterparty: {{Company Name}}
  Term End Date: {{Contract Term}}
  Executive Summary: {{Summary Output}}
  PDF Link: {{Download File URL}}
  Status: Pending Review

Action: Send Email Notification
To: {{assigned_counsel@yourcompany.com}}
Subject: Contract Review Ready - {{File Name}}
Body: 
A new contract is ready for review. Summary attached.
Summary: {{Summary Output}}
View full contract: [Link to Drive]

The entire workflow now runs automatically. From the moment a PDF lands in your Google Drive folder to the moment your counsel receives a notification with a ready-made summary takes roughly 2-3 minutes.

The Manual Alternative

Some teams prefer more control over the analysis process, particularly for complex or unusual contracts. Instead of full automation, you could use these tools interactively within your regular workflow.

Open Chat with PDF directly in your browser, upload a contract, and ask specific questions about indemnification clauses, termination rights, or renewal terms. Have the conversation right there with the document, asking follow-up questions as needed. Then use Quillbot on the extracted answers to polish your notes into a formal summary. This approach works well if your contracts vary significantly in structure or if you want legal review at each step before automation takes over.......

For smaller teams or occasional contract reviews, this semi-automated approach may actually be faster than setting up Zapier workflows. The real value of full automation kicks in when you're reviewing ten or more contracts per month.

Pro Tips

1. Set up error handling for failed uploads

PDFs occasionally fail to process: they might be image-based scans with no searchable text, corrupted, or password-protected. Add a Zapier filter that checks the Chat with PDF API response for errors. If extraction fails, send the contract to a designated folder for manual review rather than letting it vanish.

Copy
Zapier Filter:
Condition: API Response contains error
Action: Move file to /Manual Review Needed/
Action: Email team lead with original file

2. Control costs by filtering on file size

Large contracts with 50+ pages will consume more API tokens. Add a simple check in Zapier that only processes PDFs under 10 MB. For larger files, send a notification asking whether to proceed or handle manually.

Copy
Zapier Filter:
Condition: File size < 10 MB
If true: Continue to Chat with PDF
If false: Create task for manual review

3. Batch process during off-hours

Configure Zapier to collect incoming contracts throughout the business day, then process them all together at 7 PM when API rates may be lower. Use Zapier's "Schedule" feature to trigger batch processing rather than real-time processing on each upload. This can reduce costs by 20-30% depending on your API plan.

4. Create contract templates for responses

Not all contracts are the same. Add a Zapier filter that routes summaries to different templates based on contract type. Legal agreements use one template; vendor contracts use another; employment agreements use a third. This ensures your summaries match your team's actual needs.

Copy
Zapier Filter Logic:
If filename contains "NDA": Use NDA summary template
If filename contains "Service Agreement": Use services template
If filename contains "Employment": Use employment template
Else: Use default template

5. Track version history

Every time a contract is revised and re-uploaded, Zapier will generate a new summary. Store both the old and new versions with timestamps. This helps your team spot what changed between negotiations and whether new risks were introduced.

Cost Breakdown

For teams processing more than 100 contracts monthly, consider the Enterprise tier on Chat with PDF (£199/month) and Zapier's Team plan (£38/month), bringing total cost to around £275-300. At that volume, the per-contract cost drops to roughly £2.75-3.00, which is far less expensive than paying a lawyer or paralegal to spend an hour on each one.