Workflow FoundationsChapter 3622 min read

ACORD Forms, the standardized application stack and what gets passed in narrative emails the apps never reach.

ACORD forms are the standardized application templates that every commercial submission uses. The 125, 126, 130, 137, and 140 are the headline forms, with dozens of supplementals layering specialty information on top. Knowing what each form captures (and what it doesn't) is foundational for anyone working with submissions, and the variations across carriers' interpretations are where IDP work actually happens.

§ 01

The mental model

ACORD forms are the standard envelope for commercial insurance submissions in the United States. The forms exist so that brokers can collect the same information from insureds in a consistent format, and so that carriers can compare submissions across the market without each carrier developing its own application templates. The standardization is genuine but partial. The forms capture the structured exposure data; the qualitative narrative still lives in cover emails and supplemental documents.

ACORD (the Association for Cooperative Operations Research and Development) is the U.S. insurance industry's standards body. ACORD develops and maintains hundreds of forms covering nearly every line of commercial insurance. The forms are voluntary in the sense that no regulator mandates their use, but the network effect is decisive: brokers default to ACORDs because every carrier reads them, and carriers accept ACORDs because every broker produces them. The result is a common application layer that has stayed remarkably stable across decades. The forms are also the foundation for ACORD's data standards, which underpin most carrier-broker electronic data interchange. Understanding which ACORD captures which information, and where the structural gaps are, is the foundation for any submission-focused IDP project.

Anchor concept

ACORD forms are the structured shell. The substance lives in supplementals, narrative emails, and prior policy documents. A submission package may include 6-15 documents; the ACORD applications are the smallest portion by page count but the most consistent in format and meaning.

§ 02

ACORD as standards body

ACORD is a not-for-profit consortium funded by member carriers and brokers. Its primary deliverables are forms, data standards, and electronic data interchange protocols.

What ACORD produces

  • Forms. The visible standardized templates used by brokers and carriers.
  • XML data standards. The structured data formats that underpin electronic submission, policy issuance, claims, and accounting transactions between carriers and brokers.
  • Lifecycle governance. Versioning, deprecation, and updates to forms and data standards on a defined cadence.
  • Implementation guides. Technical documentation for trading partners adopting ACORD standards.

The form numbering convention

ACORD form numbers follow a rough categorical convention:

  • 1-99: General and personal lines.
  • 100-199: Commercial property and casualty applications and supplementals.
  • 200-299: Life insurance.
  • 300-399: Health insurance.
  • 400-499: Personal lines.
  • 800-899: Inland marine and specialty.
  • 900-999: Reinsurance.

Within a category, related forms cluster by line of business. The numbering is not perfectly systematic but is consistent enough to navigate.

Form versioning

Each ACORD form has a version date (e.g., ACORD 125 (2016/03)). Carriers may accept multiple versions, but newer versions are preferred. Some carriers reject older versions when key fields have changed.

§ 03

The headline ACORD forms

For commercial property and casualty, a small set of forms cover the bulk of submissions.

ACORD 125 · Commercial Insurance Application (Applicant Section)
The cover application. Captures named insured information, FEIN, business description, locations, ownership, premium history, prior insurance, and producer details. This is the "common section" that every commercial submission uses regardless of line of business.
ACORD 126 · Commercial General Liability Section
The CGL-specific application. Captures premium basis (sales, payroll, area), location-specific exposure data, products and completed operations description, additional insureds, and coverage limit selection.
ACORD 130 · Workers Compensation Application
WC-specific application. Captures payroll by class code, job description detail, ownership and officer payroll, OSHA recordables, prior carrier history, and experience modification information.
ACORD 137 · Commercial Auto Section
Auto-specific application. Captures vehicle schedule, driver schedule, garaging locations, radius of operations, hired and non-owned exposure.
ACORD 140 · Property Section
Property-specific application. Captures location-specific COPE data (construction, occupancy, protection, exposure), values by location and category, deductible selection, and coverage extensions.
ACORD 25 · Certificate of Insurance
Not an application but ubiquitous. Captures evidence of coverage for third parties (lenders, contractual counterparties, certificate holders).

What a typical commercial submission includes

A baseline mid-market submission package: ACORD 125 (cover), one or more line-specific forms (126 for GL, 130 for WC, 137 for auto, 140 for property), supplementals tied to specific exposure types, loss runs, prior carrier dec page, and broker cover narrative. Larger or more complex placements add supplementals, schedules, financial statements, and engineering reports.

§ 04

Property and casualty supplementals

Beyond the headline forms, dozens of supplemental ACORD forms address specific exposures.

Property supplementals

  • ACORD 141. Property statement of values supplement.
  • ACORD 175. Equipment breakdown.
  • ACORD 181. Outdoor signs and miscellaneous.
  • ACORD 109. Additional information for premium computation.

Liability supplementals

  • ACORD 127. Business auto coverage form (where 137 is insufficient).
  • ACORD 128. Garage liability and dealers.
  • ACORD 131. Liquor liability.
  • ACORD 132. Hired auto and non-owned auto liability.
  • ACORD 133. Drive other car coverage.
  • ACORD 145. Excess liability.

Class-specific supplementals

  • ACORD 169. Restaurant supplemental.
  • ACORD 174. Apartment building supplemental.
  • ACORD 176. Hotel and motel supplemental.
  • ACORD 168. Day care supplemental.
  • ACORD 167. Habitational supplemental.
  • ACORD 161. Convenience store supplemental.
  • ACORD 191. Amusement and recreational supplemental.

Why supplementals matter

The headline forms collect general exposure data. Supplementals collect class-specific risk factors that drive pricing and acceptance decisions. A restaurant submission without an ACORD 169 is missing the supplemental questions about deep frying, alcohol service, after-hours operations, and other restaurant-specific exposures that the underwriter needs.

§ 05

ACORD 25 and certificates of insurance

ACORD 25 is the certificate of insurance form. It deserves specific treatment because of its operational volume and its frequent misuse.

What the certificate is

Evidence of insurance. The certificate confirms that specific coverages, with specific limits, are in force on the date of issuance. It is a snapshot, not a contract; the certificate itself does not extend, alter, or otherwise modify the underlying policies.

What the certificate is not

  • It does not create coverage for the certificate holder. The certificate holder may or may not be an additional insured under the underlying policy; that determination depends on the policy and any endorsements.
  • It does not promise notification of cancellation. The cancellation notification language on the certificate is informational only; the actual cancellation notice obligations are governed by the policy and applicable state law.
  • It does not waive subrogation. Waiver of subrogation requires a specific endorsement on the underlying policy.

Volume

Brokers issue millions of certificates per year. Construction projects, commercial leases, vendor contracts, sponsorship agreements all generate certificate requirements. The COI request, issuance, and tracking workflow is one of the most volumetric operational processes in the broker's office.

Validation

For certificate holders (project owners, lessors, contractors), validating that the certificate accurately reflects coverage is its own workflow. Common validation points: limit accuracy, named insured exact match, additional insured status, waiver of subrogation, primary and noncontributory language, completed operations coverage for construction projects.

§ 06

Specialty supplementals

Specialty lines have their own application forms, often outside the ACORD numbering system.

Cyber

Cyber applications are typically carrier-specific rather than ACORD-standardized. The applications are detailed, technical, and capture security control data: MFA, EDR, backup posture, incident history, security awareness training, encryption, network segmentation. Each carrier has its own application format, and the variations across carriers are substantial.

D&O, EPLI, fiduciary

Management liability lines use carrier-specific applications. Common content: governance structure, securities-related events, ownership and capital structure, prior litigation, and line-specific exposures (employment policies for EPLI, plan inventory for fiduciary).

Professional liability

By occupation. Lawyers, architects, engineers, accountants, healthcare professionals all have specialized application templates. The application captures professional credentials, practice areas, prior claims, and contractual risk transfer practices.

Environmental

Environmental applications focus on operations, sites, materials, and historical use. Phase I assessments are typically attached as supporting documents rather than captured in the application itself.

Energy and aviation

Highly specialized application formats reflecting the specific exposure structures of each line. London market applications often use different forms than U.S. domestic applications for the same exposure.

§ 07

What ACORDs do not capture

The structured forms have known gaps. Knowing what isn't on the form is as important as knowing what is.

Narrative context

Why the prior carrier non-renewed. Why the broker is moving the account. Strategic plans for the insured. Key personnel changes. Acquisitions or divestitures pending. None of this is on the ACORD; it lives in the broker's cover email.

Loss detail

The ACORD has space for a summary of significant claims but not for the substantive detail. Material loss runs are required as separate attachments, and even those are summary tables rather than narrative descriptions of the underlying events.

Operations description

Operations are described in summary text on the application. The full description (process flow, materials handling, customer interactions, third-party relationships) typically requires supplemental documentation, narrative provided by the broker, or a site visit.

Policy term and condition negotiations

Coverage selection on the ACORD is binary or quantitative. The actual terms of negotiated endorsements, manuscript wording, and bespoke conditions are documented elsewhere, in the prior policy or in negotiated drafts during the placement.

Pricing context

The expiring premium and the renewal target are not always on the ACORD; they are routinely communicated separately by the broker. Underwriters frequently work without explicit pricing context until they ask for it.

§ 08

Reading and validating an ACORD

For an underwriter or operations team, several validation checks are routine.

Common errors and inconsistencies

  • FEIN mismatches. The FEIN on the ACORD does not match the prior policy or the legal entity records.
  • Address inconsistencies. The mailing address, location address, and prior policy address do not align. Could indicate a missing location or an entity restructuring.
  • Class code drift. WC class codes on the application do not match prior policy class codes. Could be intentional reclassification or could be an error.
  • Exposure base discrepancies. Payroll on the WC application does not match payroll on the GL application.
  • Date inconsistencies. The proposed effective date is later than the prior policy expiration, indicating a coverage gap that needs to be addressed.
  • Missing data. Specific fields are blank that should not be blank for the line of business.

Cross-form validation

Information that should be consistent across the 125, 126, 130, 140, and supplementals (named insured, FEIN, locations, payroll, sales) needs to match. Inconsistencies are flags, not necessarily errors, but they need attention.

The data quality math

For high-volume programs, automated ACORD validation reduces underwriter time spent on data quality. Even modest detection rates (5-15% of submissions with at least one validation flag) translate to meaningful time savings at scale.

§ 09

Where IDP earns its keep

ACORD forms are the most consistent input format in commercial insurance. They are also the most processed: every submission generates an ACORD or two, every renewal generates a refresh. The structural consistency of the forms makes them an early target for automation. The variations within forms (handwriting, scanning, version differences, partial completion) are where actual extraction work happens.

1
Intake
ACORDs arrive as PDFs (often scans) attached to broker submissions.
2
Classify
Identify form type and version. Tag the line of business and category.
3
Extract
All fields per form: insured details, FEIN, locations, exposure data, prior insurance, ownership.
4
Validate
Cross-form consistency checks; FEIN verification; address normalization; class-code lookups.
5
Triage
Generate clean structured submission record. Flag missing supplementals or unusual data points.
6
Underwriter
Underwriter receives a normalized submission profile, with ACORD data already in policy admin.
Indico use cases for ACORD processing

The single highest-leverage extraction in commercial insurance. ACORDs are the most volumetric structured-form input in submissions; they are also the most consistent across the market. An extraction agent that handles ACORD 125, 126, 130, 137, 140, 25, and the major class-specific supplementals covers a large fraction of the structured submission data flow. Beyond extraction: form-version detection, completeness checking against a per-line required-form matrix, ACORD-to-policy-admin mapping for direct system population, certificate of insurance verification against issued policies.

Chapter 36 · Workflow Foundations · 22 min read

ACORD Forms — Cheat Sheet

ACORD forms are the standardized application templates that every commercial submission uses. The 125, 126, 130, 137, and 140 are the headline forms, with dozens of supplementals layering specialty information on top. Knowing what each form captures (and what it doesn't) is foundational for anyone working with submissions, and the variations across carriers' interpretations are where IDP work actually happens.

The mental model: ACORD forms are the structured shell. The substance lives in supplementals, narrative emails, and prior policy documents. A submission package may include 6-15 documents; the ACORD applications are the smallest portion by page count but the most consistent in format and meaning.

Key terms

ACORD · Standards body for insurance forms and data
ACORD 125 · Commercial application cover section
ACORD 126 · CGL section
ACORD 130 · Workers compensation application
ACORD 140 · Commercial property section
ACORD 25 · Certificate of insurance
Supplemental · Class- or line-specific add-on application

If you remember three things

ACORD forms are the standardized envelope for commercial submissions, with the 125, 126, 130, 137, and 140 covering the bulk of the volume. The forms capture structured exposure data; the qualitative substance lives in supplementals, broker narrative, and prior policies. ACORD-driven extraction is the single most leveraged document automation entry point in commercial insurance because the format is consistent, the volume is high, and the downstream uses are well understood.