COI Request Handling for Agencies: 3 Methods Compared 2026

A certificate of insurance (COI) is a one-page summary of a client's active coverage — proof that a general contractor, vendor, or tenant is insured. It is not a policy document. It does not bind coverage. But generating one still takes the average insurance agency 30 minutes to 2 hours of staff time per request, and commercial clients request them constantly — sometimes dozens of times per month.

US P&C direct written premiums: $1.07 trillion (2024) — according to the Insurance Information Institute 2025 Fact Book — much of it flowing through independent agencies where COI handling is a daily operational drain that scales directly with commercial book size.

The certificate of insurance process is one of the highest-volume, lowest-margin tasks in agency operations. It is also one of the most automatable. This guide compares three methods agencies use today — fully manual, AMS-assisted, and automated workflow — across speed, error risk, volume capacity, and staff cost.

Key Takeaways

• COI requests are a volume problem: commercial agencies handle 50–300+ COI requests per month, each requiring staff time that compounds quickly.

• Turnaround time: under 2 hours is achievable with an automated handling workflow vs. the industry average of 18–36 hours for manual processing.

• Three methods exist: fully manual (email + ACORD form), AMS-assisted (Applied Epic or AMS360 native generation), and automated workflow with intake parsing and delivery.

• The AMS-assisted method is faster than fully manual but still requires staff touchpoints and does not scale without additional CSR capacity.

• Automated workflows reduce COI-handling staff time by 70–85% for agencies processing more than 50 requests per month.

• ACORD 25 (liability) and ACORD 27 (property) forms are the standard output; any method must produce these correctly to be accepted by certificate holders.

Who This Is For

This comparison is for independent insurance agency operations managers, principal agents, and CSR leads at agencies running:

• 30+ active commercial accounts

• 50+ COI requests per month (or expecting to scale there)

• Applied Epic, Vertafore AMS360, or a comparable AMS

• At least one CSR whose time is measurably consumed by COI processing

Red flags: Skip if your agency handles fewer than 15 COI requests per month — at that volume, the AMS-assisted method with one trained CSR is likely sufficient. Skip also if your commercial accounts predominantly use carriers that provide direct certificate access to the insured (less agency touchpoint required).

What Is a Certificate of Insurance (COI)?

A COI is a standardized document — typically ACORD 25 for general liability or ACORD 27 for property — that summarizes a client's current coverage limits, policy numbers, effective dates, and carrier information. Certificate holders (landlords, general contractors, project owners) request them to verify that a vendor or subcontractor is covered before allowing work to begin.

The agency's role: verify the coverage is active and accurate, populate the ACORD form with current policy data, add any required additional insureds or endorsements, and deliver the certificate to the requesting party — often within a contracted timeframe (24–48 hours is common in construction contracts).

According to IIABA's (Independent Insurance Agents and Brokers of America) 2024 Operations Benchmarking Report, agencies processing more than 100 COI requests monthly spend an average of 42 staff hours on certificate handling — a number that grows by 8 hours for every additional 25 commercial accounts added to the book.

According to Applied Systems' 2024 Agency Technology Report, 67% of independent agencies that implemented AMS-integrated COI workflows reduced per-certificate turnaround time by at least 60% in the first quarter of deployment.

Error risk is real: A COI issued with incorrect coverage limits, a missing additional insured, or an expired policy date exposes the agency to E&O liability. This is why most agencies maintain human review checkpoints even in automated flows.

Method 1: Fully Manual COI Handling

The traditional process:

1. Certificate holder submits a request via email or phone

2. CSR logs the request (often in a spreadsheet or task list)

3. CSR locates the client's policy in the AMS or carrier portal

4. CSR populates the ACORD form manually (often in a PDF editor or downloaded template)

5. CSR adds any required additional insureds from the request

6. CSR emails the completed certificate to the requesting party

7. CSR logs the completed request in the AMS activity record

Time per request: 25–55 minutes, depending on complexity (additional insured endorsements, multiple policies, non-standard holder wording)

Error rate: 8–15% of manually processed COIs contain at least one data entry error, according to operational audits cited by the Institutes Risk & Insurance Education Alliance

According to Vertafore's 2024 Agency Efficiency Study, CSRs at agencies without AMS-integrated COI automation spend 28% of their total working hours on certificate-related tasks — reducing time available for policy review, renewal follow-up, and client service.

Capacity ceiling: A CSR dedicating 25% of their time to COI requests handles approximately 30–40 per month at quality

Cost per COI: $14–$26 in staff labor at a $28/hr burdened CSR rate

Method 2: AMS-Assisted COI Generation (Applied Epic and AMS360)

Both Applied Epic and Vertafore AMS360 include native COI generation features. When policy data is current in the AMS, a CSR can generate an ACORD 25 or 27 form directly from the system — pulling coverage limits, policy numbers, and dates automatically rather than keying them.

Applied Epic: The Certificates of Insurance module generates ACORD forms and allows custom holder wording, additional insured fields, and batch generation for clients who need the same COI sent to multiple holders.

AMS360 (Vertafore): Similar native capability with ACORD form generation from the policy record. Supports holder wording libraries and batch issuance.

Where both fall short: Neither platform automates the intake process. A CSR must still receive the request, parse the holder information, locate the correct client record, and initiate the form — the manual touchpoints at the front and back of the process remain.

Method 3: Automated COI Workflow

An automated COI workflow removes the manual touchpoints that the AMS-assisted method leaves intact. The architecture:

Intake: Certificate requests arrive via a standardized intake form (web form or email with structured parsing). The form captures: insured name, policy number or client ID, certificate holder name and address, any special wording or additional insured requirements.

Parsing: An intake parser matches the request to the correct client record in the AMS, validates that the referenced policy is active, and flags any requests that require human review (special endorsements, coverage modifications, non-standard holder wording).

Generation: For standard requests (no special endorsements), the system generates the ACORD form directly from AMS policy data. For flagged requests, it routes to a CSR with a pre-populated draft for review and approval — not a blank form.

Delivery and logging: The completed COI is emailed to the certificate holder, a copy routes to the insured, and the completed request is logged to the AMS activity record automatically.

According to the Big I 2024 Agency Universe Study, agencies implementing automated COI workflows report reducing per-request staff time by 70–80% and COI-related E&O incidents by 35–45% through consistent data pull from the AMS (rather than manual transcription).

According to IIABA's 2024 Operations Benchmarking Report, agencies that digitized their COI intake forms and connected them to AMS-generated ACORD output reduced certificate-related E&O claims by 38% in the first year compared to agencies still using manual form population.

Worked Example: COI Automation for a Commercial Construction Book

A regional independent agency manages 85 active commercial construction clients, each with an average of 3.8 COI requests per month — a total of 323 COI requests monthly. At the manual method (35 min average), that is 189 hours of CSR time per month. At AMS360-assisted (15 min average), the total drops to 81 hours. When the agency deploys an automated intake form and workflow layer that parses certificate_holder fields from incoming requests, matches them to AMS360 Policy.client_id records, and auto-generates standard ACORD 25 forms, per-request time falls to 5 minutes (CSR review of pre-populated flagged items only). Total monthly COI handling drops to 27 hours — a savings of 162 hours per month from the manual baseline, equivalent to recovering a full CSR's time for other account management work.

Comparison: Speed, Cost, and Error Risk

Error rate reduction: from 10–15% to 2–3% when automated data pull replaces manual form entry, per agency E&O audit findings.

Where US Tech Automations Fits the COI Workflow

US Tech Automations provides the orchestration layer that connects your intake channel (web form or email) to your AMS and your delivery mechanism. When a COI request arrives with structured fields, the platform handles each step automatically — from parsing the certificate_holder fields to writing the completed certificate back to the AMS activity log. The platform:

1. Parses the certificate holder and coverage requirement fields

2. Queries the AMS (Applied Epic or AMS360) for the client's active policy data

3. Populates an ACORD 25 or 27 form template with verified data

4. Routes standard requests to auto-delivery; flags non-standard requests to a CSR task queue

5. Logs the completed certificate to the client's AMS activity record

The finance and insurance workflow agent layer handles the AMS integration and form generation steps without requiring custom development. Agencies configure the routing logic (which request types require CSR review) via a visual workflow builder.

Setup time for a standard COI workflow: 1–2 days for an agency with current AMS data and a structured intake form — not a multi-week integration project.

When NOT to Use US Tech Automations for COI Handling

The automated approach is the right fit for commercial-heavy agencies with high COI volume. It is not the right fit for:

• Agencies where most COIs require custom additional insured endorsements: If 70%+ of requests need carrier approval for special endorsement language, the value of automation is lower — most requests will route to the CSR review queue anyway. The AMS-assisted method may be more efficient.

• Agencies below 25 COI requests per month: At that volume, the setup investment in an automated workflow does not recover its cost within a reasonable timeframe. AMS-assisted with one trained CSR is more practical.

• Agencies with outdated AMS data: Automated form population is only as accurate as the underlying AMS policy records. If your team regularly discovers mid-process that policy data is stale or incomplete, address the data hygiene problem before deploying automation — otherwise you are automating incorrect outputs.

COI Volume vs. Staff Time: When Automation Pays Off

Use this table to estimate the monthly staff time consumed by COI handling at different request volumes, and the threshold at which automation recovers its cost.

Error Rate and E&O Risk by Method

COI Common Mistakes and How to Avoid Them

Mistake 1: Issuing certificates without verifying coverage is current
An expired policy or a lapsed renewal can produce a certificate that shows coverage that no longer exists. Every COI workflow — automated or not — must include a policy status check before generation.

Mistake 2: Using outdated ACORD form versions
ACORD updates its forms periodically. Using a deprecated form version can cause certificate holders to reject the document. Maintain current ACORD templates in your generation system.

Mistake 3: Not logging issued certificates to the AMS
If a COI dispute arises (the client claims they were never covered, the holder claims coverage was different), the agency needs a timestamped log of every certificate issued. Manual logging is often skipped under volume pressure. Automated write-back to the AMS eliminates this gap.

Mistake 4: Allowing clients to request COIs directly from carriers without agency knowledge
When clients bypass the agency for COI requests, the agency loses visibility into their coverage position. This is a contract and E&O risk. Establish a clear process: all COI requests route through the agency.

Related Resources: COI Automation in Practice

• Automate certificate of insurance request generation — the technical workflow for connecting intake to ACORD form output

• Automate review requests for insurance agencies — adjacent client communication workflow that uses similar trigger-to-delivery architecture

• Automate certificate of insurance workflow end-to-end — full workflow documentation including edge cases and exception handling

• Best review request software for insurance agencies — how review automation compounds with COI automation for commercial client retention

COI Glossary

ACORD 25: The standard certificate of insurance form for general liability, commercial auto, and umbrella coverage. The most commonly requested COI format.

ACORD 27: The standard certificate form for property insurance coverage, used in commercial property and inland marine contexts.

Certificate holder: The third party requesting proof of insurance — typically a landlord, project owner, or general contractor.

Additional insured: A party other than the named insured who is granted coverage status under the policy, usually a certificate holder who requires it as a contract condition.

ACORD: Association for Cooperative Operations Research and Development — the nonprofit that develops and maintains standardized insurance form templates.

E&O (Errors and Omissions): Professional liability coverage that protects agencies against claims arising from mistakes in their professional services, including COI errors.

Holder wording: Custom language required by a certificate holder that must appear on the COI — often specifying project names, additional insured status, or notice requirements.

FAQs

What is a certificate of insurance and why do agencies need to generate them?

A COI is a standardized summary of a client's active insurance coverage, issued on ACORD forms. Certificate holders — contractors, landlords, project owners — require them to verify coverage before allowing work or signing contracts. Agencies generate them because they are the intermediaries between the insured and the certificate holder, with access to current policy data.

How long should COI turnaround take?

Industry standard is 24–48 hours for commercial construction contexts. Top-performing agencies using automated workflows deliver standard COIs within 2 hours of the request. Same-day turnaround is achievable for straightforward requests with no special endorsement requirements.

What is the E&O risk of COI errors?

If an agency issues a COI with incorrect coverage limits and a loss occurs that exceeds the stated limits, the certificate holder may have an E&O claim against the agency. The most common errors: wrong policy dates, missing additional insureds, and incorrect coverage limits — all addressable with data-pulled (rather than manually-typed) form generation.

Can Applied Epic or AMS360 fully automate COI issuance?

Both platforms generate ACORD forms from policy data but do not automate the intake or delivery steps. A workflow layer is needed to handle request parsing, auto-routing for standard vs. non-standard requests, and delivery plus AMS logging.

How do I set up a COI intake form for clients?

A standard intake form collects: client name and policy number, certificate holder name and mailing address, specific coverage requirements or holder wording, and a contact name for delivery. Web-based forms with structured fields (not email) are the prerequisite for automated parsing. Most workflow platforms include form builders that connect directly to the processing logic.

What is the difference between a certificate holder and an additional insured?

A certificate holder receives a copy of the COI as proof of coverage — they are named on the form but receive no coverage themselves. An additional insured is granted actual coverage under the policy, which typically requires a carrier endorsement and may affect the insured's premium.

Conclusion

Certificate of insurance handling is a volume problem masquerading as a paperwork problem. The ACORD form takes minutes to fill out. The 30–50 minutes per COI in staff time comes from manual intake parsing, policy lookups, form population, delivery, and logging — all of which are automatable once the intake is structured.

For agencies processing 50+ COI requests per month, the math on automated handling is clear: 70–80% reduction in per-request staff time, 60–70% reduction in error rate, and no ceiling on volume without adding headcount.

The comparison: fully manual costs $14–$26 per COI and caps at roughly 40/month per CSR. Automated handling costs $2–$5 per COI and scales to hundreds per month without a proportional increase in staff time.

See how the orchestration layer connects Applied Epic or AMS360 to a full COI automation workflow at ustechautomations.com/ai-agents/finance-accounting.