COI Automation Checklist: Issue Certificates in 60 Seconds 2026

The average commercial insurance agency spends 22% of its total service team capacity on certificate of insurance processing, according to IVANS Index data from 2025. That figure represents the single largest non-revenue-generating activity in most agencies — larger than policy change processing, larger than claims intake, and larger than renewal preparation combined. The reason is volume: construction, real estate management, and manufacturing accounts generate COI requests at a rate that overwhelms manual workflows, creating backlogs that frustrate clients and drain staff hours.
COI issuance time with automation: under 60 seconds according to ACORD (2024)

This checklist provides the complete, step-by-step framework for automating COI issuance — from initial audit through production launch. Every item is sequenced in implementation order with specific acceptance criteria so you know exactly when each step is done.

Key Takeaways

• Agencies processing 50+ COIs daily lose an estimated 2,080 staff hours annually to manual certificate handling, according to the Council of Insurance Agents & Brokers

• ACORD 25 and ACORD 28 compliance requires validation of 32+ data fields — automation eliminates manual transcription errors

• The checklist covers five phases: audit, preparation, build, testing, and launch — typically 15-25 business days total

• Endorsement library standardization is the most commonly skipped step and the leading cause of post-launch rework

• US Tech Automations provides pre-built AMS connectors that reduce integration time from weeks to days

Phase 1: Current State Audit (Days 1-3)

Before building anything, you need hard data on what your COI operation actually looks like today. According to IVANS, 74% of agencies overestimate their automation readiness because they have not measured their true COI volume, error rate, or processing time distribution.

Checklist Item 1.1: Calculate Total COI Volume

• Pull COI activity records from your AMS for the last 90 days
• Count requests by source: email, phone, fax, portal, walk-in
• Calculate daily average, weekly peak, and monthly trend
• Separate new certificate requests from renewal/revision requests

Acceptance criteria: You have a single number — total annual COI volume — documented and verified against AMS activity logs.

According to the Council of Insurance Agents & Brokers, the average mid-market commercial agency (500-2,000 accounts) processes between 8,000 and 18,000 COI requests annually. Agencies with heavy construction books often exceed 25,000.

Checklist Item 1.2: Measure Processing Time by Complexity Tier

• Time 20 straightforward COIs (single policy, standard holder, no special endorsements)
• Time 15 moderate COIs (multiple policies or 1-2 special endorsements)
• Time 10 complex COIs (multiple policies, special language, non-standard holders)
• Calculate weighted average processing time

Acceptance criteria: You have documented processing times for three complexity tiers and a weighted average.

According to ACORD implementation data, straightforward COIs average 12-18 minutes, moderate COIs average 25-35 minutes, and complex COIs average 40-60 minutes. Your agency's numbers may differ based on AMS efficiency, staff experience, and workflow design.
Automated COI compliance rate: 99.2% vs 85% manual according to myCOI (2024)

Checklist Item 1.3: Document Error Rates and Root Causes

• Review returned or corrected certificates from the last 90 days
• Categorize errors: wrong holder address, wrong policy dates, incorrect limits, missing endorsements, wrong additional insured language
• Calculate error rate per complexity tier
• Estimate rework time per error

Acceptance criteria: Error rate documented with root cause breakdown.

According to the Professional Liability Underwriting Society, COI-related errors account for 18% of all E&O claims filed against commercial insurance agencies. The most expensive errors involve incorrect additional insured endorsement language, which can create coverage gaps that become apparent only at the time of a claim.

Checklist Item 1.4: Map Your Current Workflow

• Document every step from request receipt to certificate delivery
• Identify handoff points between staff members
• Note where data is manually re-entered vs. pulled from the AMS
• Identify bottleneck steps (longest duration, highest error rate)

Acceptance criteria: A visual workflow diagram showing every step, decision point, and handoff.

What does a typical manual COI workflow look like? According to IVANS operational benchmarking, the standard manual workflow involves 7-9 discrete steps with 2-3 handoffs between team members. Each handoff introduces latency (waiting for the next person) and potential information loss.

Phase 2: Preparation (Days 4-8)

This phase transforms your audit data into the configuration inputs your automation platform will need.

Checklist Item 2.1: Standardize Your Endorsement Library

• Compile every unique endorsement clause template from the last 12 months of issued certificates
• Remove exact duplicates
• Merge near-duplicates (same intent, minor wording variations) — have legal or compliance review
• Assign each template a unique identifier and descriptive name
• Create a mapping: holder name → required endorsement templates

Acceptance criteria: A canonical endorsement library with unique IDs, reviewed by compliance, and mapped to known holders.

This is the step most agencies skip or rush. According to ACORD's 2025 workflow study, endorsement library inconsistency is the number one cause of post-automation rework — agencies that skip standardization spend an average of 40 additional hours in the first month fixing template issues.

Checklist Item 2.2: Verify AMS API Access

• Confirm your AMS version supports real-time API access
• Obtain API credentials and documentation
• Test read access: pull a sample policy record
• Test write access: create a test activity log entry
• Document any rate limits or access restrictions

Acceptance criteria: Confirmed, tested API access with both read and write capabilities.

According to ACORD connectivity standards, Applied Epic (version 2023+), Vertafore AMS360, HawkSoft (version 5.0+), and EZLynx all support the API access required for COI automation. Agencies on older AMS versions may need middleware, which the US Tech Automations platform can provide through its universal connector framework.

Checklist Item 2.3: Define Exception Handling Rules

• List scenarios that should always route to human review
• Define confidence thresholds for automated processing vs. manual review
• Create escalation paths for different exception types
• Assign staff members to each escalation path

Acceptance criteria: A documented exception handling matrix with clear routing rules.

How do you determine which COI requests need human review? According to IVANS operational data, the most reliable exception triggers are: policies issued within the last 30 days (data may not be fully loaded), requests for coverage types not found on the insured's policy, requests from certificate holders not in the agency's database, and requests with free-text special requirements that don't match any template.

Checklist Item 2.4: Prepare Certificate Templates

• Obtain current ACORD 25 (liability) and ACORD 28 (property) form versions
• Configure your agency branding (logo, contact information, license numbers)
• Set up digital signature or authorized representative stamp
• Create templates for the most common certificate configurations (top 10 by volume)

Acceptance criteria: ACORD-compliant certificate templates ready for automated population.

Agencies that pre-configure their top 10 certificate configurations — covering typically 60-70% of all requests — see significantly faster implementation timelines, according to the Insurance Technology Association's 2025 automation readiness report.

Phase 3: Build and Configure (Days 9-15)

Checklist Item 3.1: Set Up the Automation Platform

• Provision your US Tech Automations environment
• Connect your AMS via API (Applied Epic, Vertafore AMS360, HawkSoft, or universal connector)
• Configure email intake parsing rules
• Set up the client self-service portal (optional but recommended)

Acceptance criteria: Platform is live in staging with AMS connected and email intake functional.

The US Tech Automations platform provides a visual workflow builder specifically designed for insurance operations. The COI automation case study documents a real agency that completed this phase in five business days.

Checklist Item 3.2: Configure Request Parsing Logic

• Define field extraction rules for insured name, policy number, holder info, and endorsement requirements
• Train the NLP parser on 50-100 historical request emails
• Configure cross-reference logic for incomplete requests (pull from historical certificate data)
• Set up holder database auto-population

Acceptance criteria: Parser correctly extracts required fields from 90%+ of test requests.

Checklist Item 3.3: Build Policy Verification Workflow

• Configure real-time policy status checks (active, pending, cancelled, expired)
• Set up coverage limit validation (requested limits vs. actual limits)
• Configure endorsement schedule verification
• Build mismatch detection and exception routing

Acceptance criteria: Verification workflow correctly validates policy data and flags mismatches in test runs.

Checklist Item 3.4: Configure Certificate Generation

• Load ACORD 25 and ACORD 28 templates
• Map AMS data fields to certificate form fields (all 32+ fields)
• Configure endorsement language insertion from the standardized library
• Set up PDF generation with agency branding
• Configure unique certificate tracking numbers

Acceptance criteria: Generated certificates match manually-produced certificates in format, content, and compliance.

Checklist Item 3.5: Set Up Delivery and Logging

• Configure email delivery with customizable cover messages
• Set up portal delivery for holder portal users
• Configure AMS activity logging (certificate issued, delivered to [holder], tracking number)
• Set up notification to insured (optional — some agencies notify the account of every certificate issued)

Acceptance criteria: Certificates deliver through all configured channels with full AMS logging.

Phase 4: Testing (Days 16-20)

Checklist Item 4.1: Run Historical Replay Test

• Select 200+ historical COI requests representing all complexity tiers
• Process through the automated workflow
• Compare automated output to the original manually-issued certificates
• Document discrepancies and root causes

Acceptance criteria: 95%+ match rate between automated and historical certificates. All discrepancies explained and addressed.

According to the Insurance Technology Association, historical replay testing catches 85% of configuration issues before they reach production. The remaining 15% typically surface during the parallel run phase.
COI automation annual labor savings: $40,000-$80,000 per agency according to myCOI (2024)

What accuracy rate should you expect from COI automation? Industry benchmarks from IVANS suggest targeting 98%+ accuracy for straightforward requests and 95%+ for complex requests during initial testing. After calibration, production accuracy should exceed 99%.

Checklist Item 4.2: Run Parallel Production Test (5-7 Business Days)

• Process all incoming COI requests through both automated and manual workflows simultaneously
• Compare outputs daily
• Track automated processing time vs. manual processing time
• Document all exceptions and how they were routed
• Measure false positive rate (requests unnecessarily flagged for human review)
• Measure false negative rate (errors that automation missed)

Acceptance criteria: Automated output matches or exceeds manual quality for 5+ consecutive business days.

Checklist Item 4.3: Conduct Staff Training

• Train all CSRs on the exception review process
• Train account managers on the self-service portal (for client-facing demos)
• Document the escalation procedures for edge cases
• Run a tabletop exercise with 5 simulated exception scenarios

Acceptance criteria: All relevant staff have completed training and successfully resolved simulated exceptions.

According to the Council of Insurance Agents & Brokers, agencies that invest at least 8 hours in staff training before launch experience 60% fewer support escalations in the first month compared to agencies that rely on informal on-the-job training.

Phase 5: Launch and Optimize (Days 21-25+)

Checklist Item 5.1: Go Live

• Switch automated workflow to primary processing mode
• Disable manual processing for standard requests (keep manual path for exceptions only)
• Monitor first 50 certificates in real-time for quality
• Confirm AMS logging is capturing all activity

Acceptance criteria: First day of production processes 100% of standard requests automatically with no critical errors.

Checklist Item 5.2: Calibrate Exception Thresholds (Weeks 2-4)

• Review all human-routed exceptions from week 1
• Identify false positives and adjust confidence thresholds
• Add new endorsement templates for any uncovered scenarios
• Update holder database with new certificate holders encountered

Acceptance criteria: Human review rate below 8% with zero false negatives.

Checklist Item 5.3: Establish Ongoing Monitoring

• Set up daily accuracy reports (automated)
• Set up weekly volume and processing time dashboards
• Schedule monthly exception review meetings
• Configure alerts for anomalies (sudden spike in exceptions, new error patterns)

Acceptance criteria: Monitoring dashboards live and alerting functional.

The US Tech Automations platform includes built-in analytics dashboards that track all key COI metrics in real time — no separate reporting setup required. For agencies exploring adjacent automation opportunities, the multi-carrier quoting automation guide and the client onboarding workflow cover the most common next steps.

Checklist Item 5.4: Measure and Report ROI

• Calculate monthly labor hours saved
• Calculate monthly error rate reduction
• Track client satisfaction metrics (response time, CSAT scores)
• Document E&O risk reduction for your underwriter
• Present quarterly ROI report to agency leadership

Acceptance criteria: First ROI report delivered within 60 days of launch.

Common Mistakes to Avoid

Mistake 1: Skipping the endorsement library audit. This creates a cascade of post-launch errors as non-standard endorsement requests hit the automation and fail to match any template. Budget 8-12 hours for this step.

Mistake 2: Setting exception thresholds too tight. Overly aggressive exception routing defeats the purpose of automation. Start with moderate thresholds and tighten gradually based on actual production data.

Mistake 3: Failing to train staff on exception handling. The automation does not eliminate human involvement — it concentrates it on the 5-8% of requests that genuinely need judgment. Staff need to be prepared for this shifted role.

Mistake 4: Not measuring baseline metrics before implementation. Without pre-automation data, you cannot calculate ROI or demonstrate the value of the investment to stakeholders. According to McKinsey's Insurance Operations Benchmark, agencies that skip baseline measurement are 3x more likely to have their automation budget questioned at renewal.

Mistake 5: Treating COI automation as an isolated project. The data infrastructure, AMS integration, and workflow patterns you build for COI automation directly accelerate the implementation of other automation use cases — policy change processing, renewal preparation, and claims intake. Plan for expansion from day one.

Frequently Asked Questions

What ACORD forms does COI automation need to support?
At minimum, ACORD 25 (Certificate of Liability Insurance) and ACORD 28 (Evidence of Commercial Property Insurance). According to ACORD, these two forms cover 92% of all COI requests. Some agencies also need ACORD 24 (Evidence of Auto Liability), ACORD 27 (Evidence of Property Insurance for personal lines), and ACORD 855 (for international certificates).

How long does the full COI automation implementation take?
According to IVANS operational data, most mid-market agencies complete implementation in 15-25 business days. The timeline depends primarily on endorsement library complexity and AMS integration requirements. Agencies using Applied Epic or Vertafore AMS360 with the US Tech Automations platform typically finish in 15-18 business days.

Can COI automation handle certificates for multiple carriers simultaneously?
Yes. Modern automation platforms pull policy data regardless of the underlying carrier, as long as the policies are in the agency's AMS. According to ACORD connectivity standards, the certificate of insurance is an agency document — not a carrier document — so multi-carrier certificate issuance is a standard capability.
Certificate request volume reduction: 70% fewer phone/email requests according to ACORD (2024)

What happens during an AMS outage or API downtime?
Well-designed COI automation includes a queuing mechanism that holds requests during AMS outages and processes them automatically when connectivity resumes. According to the Insurance Technology Association, planned queue-and-retry logic prevents the backlog cascades that make AMS outages so disruptive to manual workflows.
Insurance quoting automation speed: 90 seconds vs 45 minutes manual according to IVANS (2025)

How does automated COI tracking compare to spreadsheet tracking?
Spreadsheet-based COI tracking fails at scale because it requires manual updates, offers no real-time visibility, and provides no automated expiration alerts. According to IVANS, agencies that switch from spreadsheet tracking to automated tracking reduce certificate lapses by 73% and spend 85% less time on renewal certificate processing.

Does COI automation require changes to existing client workflows?
Clients can continue submitting COI requests via email exactly as they do today — the automation handles parsing without requiring any changes on the client's side. The optional self-service portal provides a faster path for frequent requesters, but adoption is voluntary. According to industry data, portal adoption typically reaches 50-65% within three months without any mandate.

What security and compliance requirements apply to automated COI issuance?
Automated COI systems must maintain the same audit trails, access controls, and data protection standards as manual processes. According to ACORD, the key compliance requirements are: certificate authenticity verification, authorized signatory controls, activity logging for E&O documentation, and data encryption in transit and at rest.

How do you handle COI requests that reference policies not yet in the AMS?
The automation flags these as exceptions and routes them to human review with a notation that the referenced policy was not found. According to IVANS, this scenario accounts for 3-5% of all COI requests and is most common during policy inception periods. The exception handling process ensures no certificate is issued against unverified coverage.

Conclusion: Start With the Audit, Then Move Fast

The checklist above contains 18 discrete items across five phases. Agencies that follow it in sequence — without skipping the audit or preparation phases — consistently achieve production-ready COI automation in 15-25 business days, with accuracy rates above 99% and processing times under 60 seconds.

The operational math is straightforward: every day you spend on manual COI processing is a day your staff is not cross-selling, not deepening client relationships, and not growing premium volume.

Get a free COI workflow audit →

For additional context, the COI automation case study documents real-world results from a 42-person agency, and the multi-carrier quoting guide covers the next natural automation target after COI.