ACORD Forms and Your Tech Stack: What Belongs in CRM vs AMS
Every commercial submission produces ACORD form data somewhere. This reference maps the forms agencies handle most often to where the resulting data should actually live.
Common ACORD forms and where their data belongs
| Form | What it captures | Primary system of record | What a CRM may reasonably reference |
|---|---|---|---|
| ACORD 25 — Certificate of Liability Insurance | Proof of coverage issued to a third party | AMS (certificate issuance and tracking) | Whether a certificate is outstanding or needs renewal follow-up |
| ACORD 125 — Commercial Insurance Application | Applicant identity, operations, prior carriers, loss history, coverages requested | AMS / agency rating or submission platform | Line of business, submission status, next action |
| ACORD 126 — Commercial General Liability Section | GL exposure, classification, limits, additional insureds | AMS | Coverage line flag only; no exposure detail |
| ACORD 127 — Business Auto Section | Vehicle and driver exposure detail for commercial auto | AMS | Coverage line flag only |
| ACORD 130 — Workers' Compensation Application | Payroll class codes, experience modifiers, prior carrier history | AMS | Renewal date, coverage line flag |
| ACORD 131 — Umbrella/Excess Liability Section | Underlying limits and excess layer detail | AMS | Cross-sell flag (client has underlying but no umbrella) |
| ACORD 140 — Property Section | Building values, construction, protection, occupancy | AMS | Renewal date, property count for account context |
Form names and numbers are drawn from ACORD's public forms library. Confirm current editions and state-specific variants directly with ACORD's Forms Portal before relying on this table for compliance purposes.
Why this split holds up under scrutiny
The detail inside a 126, 130 or 140 is exposure and underwriting data tied to a specific submission and carrier. It changes with every endorsement, audit and renewal. An AMS connected to carrier downloads stays current almost automatically; a CRM field that mirrors the same data has to be updated by hand, and usually is not. The gap between the two is where E&O exposure and client-facing mistakes come from—see CRM vs AMS for insurance agencies for the broader system-of-record framework this table fits into.
Where the CRM still adds real value
- Flagging that a client has GL but no umbrella—an ACORD 131 opportunity—without storing the umbrella application itself
- Tracking renewal dates pulled from the AMS as a trigger for producer outreach
- Recording the sales conversation and next action that led to an ACORD 125 being started
- Surfacing certificate (ACORD 25) status as a service reminder, not as the certificate record itself
The mistake this reference is meant to prevent
Some CRMs make it easy to build a custom field for every ACORD data point because the platform allows unlimited fields. That flexibility is not the same as suitability. If a field's value depends on carrier underwriting data that changes outside the CRM, treat it as a read-only reference synced from the AMS, not a field producers update manually. Pair this with the field-level guidance in Insurance CRM Fields: What Agents Should Track.
FAQ
Should a CRM store ACORD form data directly?
Usually not as the system of record. Most agencies keep submission and policy-section data in the AMS, and let the CRM reference a small summary (line of business, effective date, renewal date) for sales and service context.
Is it an E&O risk to keep ACORD-derived data only in a CRM?
It can be, if the CRM copy goes stale after a policy change and a producer or CSR relies on it in a client conversation. The AMS record tied to the actual carrier download is generally the more defensible reference.
Can a CRM help producers before an ACORD form is even filled out?
Yes. Lead qualification, coverage interest and next-action tracking ahead of a formal application are exactly the kind of activity a CRM is built for. The handoff point is when that interest becomes a submission that needs an ACORD form.
Keep reading
Primary sources & verification
Form names, numbers and purposes are checked against ACORD's public forms library. Confirm current form editions before compliance use.