Collect certificates of insurance from every vendor, have an agent read each one against your contract requirements, and chase gaps and expirations automatically, with a human deciding any exception.
Anyone who lets a contractor onto a property or into a building is supposed to hold current proof that the contractor is insured to the limits the contract requires — and almost nobody does it consistently. Property managers need certificates from every plumber, roofer, landscaper, and cleaner; general contractors and home services companies need them from every subcontractor; restaurants and logistics operators need them from every vendor that works on site; enterprise procurement needs them from thousands of suppliers. The standard evidence is the ACORD 25 Certificate of Liability Insurance, and the form itself explains why reading it carefully matters. It says, in capitals, that it is "issued as a matter of information only and confers no rights upon the certificate holder." It says that if the holder is meant to be an additional insured, "the policy(ies) must have ADDITIONAL INSURED provisions or be endorsed," and that "a statement on this certificate does not confer rights to the certificate holder in lieu of such endorsement(s)." And its cancellation box says only that notice "will be delivered in accordance with the policy provisions" — so the certificate holder should not assume anyone will tell them when coverage lapses. In practice that means three recurring jobs: compare each certificate to the contract's required coverages and limits, get the endorsement when additional-insured status is required, and re-collect before every expiration date. Those jobs are mostly reading and reminding, which is exactly what a document-reading model and a scheduler do well. The decision to let a vendor work with a gap stays with a person.
Most organizations have three or four tiers: low-risk (cleaning, landscaping), trades (plumbing, electrical, HVAC), high-risk (roofing, structural, anything at height), and professional services. For each tier write the required coverages and minimum limits — general liability each occurrence and aggregate, auto, umbrella, workers' compensation, professional liability where relevant — plus whether you must be named additional insured and whether waiver of subrogation is required. Get your broker or counsel to confirm the table once. This table, not the model, is the standard every certificate is measured against.
Build an Airtable form linked to the vendor table with attachment fields for the certificate and, where your tier requires it, the additional-insured and waiver-of-subrogation endorsements. Send each vendor its own pre-filled link. Endorsements are separate policy documents; a certificate that merely ticks the ADDL INSD box is not one, and the form should say so.
An n8n flow sends each upload to the Claude API with the extraction schema in the assets. PDF input is processed page by page as text and image, so scanned certificates work. The agent extracts the insured name, producer, insurers with NAIC numbers, each policy type with policy number, effective and expiration dates, and every limit, plus the ADDL INSD and SUBR WVD markers and the certificate holder block. Every field is copied as printed; anything unreadable is UNREADABLE, never estimated.
The comparison of extracted limits to required limits is plain arithmetic: do it in an n8n code step or an Airtable formula so it is deterministic and auditable. The model's job ends at extraction. Flag: missing coverage, limit below requirement, expired or expiring within 30 days, insured name not matching the vendor's legal name, certificate holder not your entity, additional insured required but no endorsement uploaded, any UNREADABLE field.
For each flag, the agent drafts a specific request using the templates in the assets — naming exactly which coverage or limit is short and what the contract requires — and sends it to the vendor contact and, where the certificate lists one, the producer. Specific requests get fixed on the first reply; "please send an updated COI" gets the same certificate back.
Each vendor carries a status: compliant, expiring, deficient, or expired. Post deficient and expired vendors to a Slack channel that the people who schedule work and run payments both watch, and make checking status a step before any work order is approved or payment released. Only a named person can grant an exception, with a reason and an end date recorded on the vendor record. The agent never grants one.
Because the certificate does not promise you notice of cancellation, the expiration date is the only signal you control. Start requests 45 days before each expiration, follow up at 30 and 14 days, and move the vendor to expired the day after the date passes. Once a quarter, compare active vendors in your payables against the COI table; a vendor you paid who is not in the table is the gap that matters most.
Use these templates as-is or customize for your business.
You are extracting data from a certificate of insurance (usually ACORD 25). Copy values exactly as printed. Never calculate, infer, or fill gaps. If a value is illegible or absent, use "UNREADABLE" or "ABSENT" respectively.
Return JSON only:
{
"form": "ACORD 25 | other | UNREADABLE",
"form_edition": "e.g. 2025/12 | UNREADABLE",
"certificate_date": "MM/DD/YYYY",
"insured_name": "...",
"producer_name": "...",
"producer_email": "... | ABSENT",
"insurers": [{"letter": "A", "name": "...", "naic": "..."}],
"policies": [
{
"type": "general_liability | auto | umbrella | excess | workers_comp | professional | other",
"insurer_letter": "A",
"policy_number": "...",
"effective": "MM/DD/YYYY",
"expiration": "MM/DD/YYYY",
"addl_insd_marked": "Y | N | ABSENT",
"subr_wvd_marked": "Y | N | ABSENT",
"limits": {"each_occurrence": "...", "general_aggregate": "...", "products_completed_ops": "...", "combined_single_limit": "...", "el_each_accident": "...", "other": "..."}
}
],
"description_of_operations": "verbatim text",
"certificate_holder": "verbatim text",
"notes": "anything unusual, e.g. handwritten changes, missing signature"
}
Remember: a Y in the ADDL INSD column is not an endorsement. Do not state or imply that additional insured status exists.tier | GL each occ | GL aggregate | Auto CSL | Umbrella | Workers comp | Prof. liab | Addl insured endorsement | Waiver of subrogation --------------|-------------|--------------|-----------|----------|--------------|------------|--------------------------|---------------------- low_risk | $[ ] | $[ ] | $[ ] | none | statutory | none | [Y/N] | [Y/N] trades | $[ ] | $[ ] | $[ ] | $[ ] | statutory | none | Y | [Y/N] high_risk | $[ ] | $[ ] | $[ ] | $[ ] | statutory | none | Y | Y professional | $[ ] | $[ ] | $[ ] | none | statutory | $[ ] | [Y/N] | N Certificate holder must read exactly: [Legal entity name, address] Insured name must match: vendor legal name on W-9 Expiring-soon threshold: 30 days Exception authority: [name/role]; every exception has a reason and an end date COMPARISON RULES (implement in code): - missing required policy type -> DEFICIENT - any extracted limit < required limit -> DEFICIENT - expiration < today -> EXPIRED; < today + 30 -> EXPIRING - addl insured required AND no endorsement file uploaded -> DEFICIENT (a marked box is not enough) - insured_name != vendor legal name, or certificate_holder != required text -> DEFICIENT - any UNREADABLE in a required field -> NEEDS_HUMAN
SUBJECT: Insurance update needed for [Vendor] — [Company] vendor file DEFICIENT (specific): "Hi [Name], we reviewed the certificate of insurance dated [date] for [Vendor]. Our agreement requires the following, which the certificate doesn't show yet: - [General liability each occurrence: certificate shows $X; required $Y] - [Additional insured: our agreement requires [Company] as additional insured — please send the endorsement page from the policy, not only the certificate] - [Certificate holder should read: [exact text]] Please send the updated documents to [upload link] by [date]. We can't schedule new work until the file is complete. Your insurance agent, [Producer], is copied." EXPIRING (45 / 30 / 14 days): "Hi [Name], our records show [Vendor]'s [policy type] policy expires on [date]. Please upload the renewed certificate (and endorsements, if required) at [upload link] before then so there's no gap in your vendor status." EXPIRED: "Hi [Name], [Vendor]'s [policy type] coverage on file expired on [date]. Your vendor status is paused until we receive current documents at [upload link]. If coverage was renewed, a current certificate resolves this immediately."
Get a new AI workflow every week. Prompts, tool stacks, and ROI math included.
AI does the categorization or first-draft work, a human approves before action is taken. The pattern of choice for anything irreversible, externally visible, or financially sensitive.
Learn the agentic glossary →Where this workflow tends to break in production — and what to put in place before you ship it.
Model reads a marked ADDL INSD box as proof of additional-insured status
Mitigation: Prompt forbids implying endorsement status; comparison rule requires an uploaded endorsement file wherever the tier requires additional insured.
Extraction error on a limit or date lets a deficient certificate pass
Mitigation: Comparison runs in code on extracted values; UNREADABLE routes to a human; monthly spot-check of 10 certificates against the PDFs.
Coverage cancelled mid-term without notice to the holder
Mitigation: Treat the certificate as point-in-time; re-request before every expiration; for high-risk vendors, request a current certificate at each new job start.
Vendor paid or scheduled while non-compliant
Mitigation: Status check is a step before work-order approval and payment release; quarterly reconciliation of paid vendors against the COI table.
Exceptions granted informally and never expire
Mitigation: Only a named role can grant one; reason and end date required; expired exceptions revert status automatically.
Do not use the agent's output to decide that a vendor is adequately insured for a specific loss — a certificate is information only, it does not amend the policy, and coverage questions after an incident go to your broker and counsel with the actual policy. Skip the automation if you work with a dozen vendors; a spreadsheet with expiration dates and a calendar reminder does the job. If you are an enterprise with thousands of suppliers and contractual requirements that vary by contract rather than by tier, the extraction and reminder pieces here still apply, but put the requirements in your procurement system of record rather than a hand-maintained table, and expect the exception process, not the reading, to be the hard part.
A phased approach to get this workflow running and delivering ROI.
Days 1–30
Foundation
Days 31–60
Optimization
Days 61–90
Scale
Both sell an AI receptionist, reviews and texting to the same office manager. Only one publishes a starting price, neither publishes an overage, and the number that decides your bill is the bulk-text allotment.
None of the three big legal AI platforms publishes a per-seat price. Here is what each one does publish (research content, security commitments, plan terms) and how a 25-lawyer firm should structure the quote.
The managed tool layers for AI agents price the same action four different ways. Here is what Composio, Arcade.dev and Pipedream Connect publish, what running your own MCP servers costs you instead, and a worked monthly bill.
One practical AI workflow per week. No fluff.
Get the full guide with step-by-step setup, workflow templates, and copy-paste assets.