ACORD 126 · Form guideCommercial lines · US

ACORD 126: commercial general liability section, explained, then automated.

The ACORD 126 is the general liability section of a commercial application. It travels with the ACORD 125 and carries everything a carrier needs to rate GL: coverage limits, classifications and class codes, deductibles, products exposure, and additional interests. It is also the form whose class codes your CSRs retype into every carrier portal, one dropdown at a time.

Free tool · No signup

Paste a USDOT and get the GL section pre-filled from the FMCSA stack: insured identity, class description, description of operations, and a carrier snapshot in the remarks. Free, no signup.

Autofill an ACORD 126 from a USDOT number →
What’s on the 126

The sections that actually drive the quote.

Coverage & limits

  • Occurrence vs. claims-made coverage selection
  • Each-occurrence and general aggregate limits
  • Products / completed operations aggregate
  • Personal & advertising injury, damage to rented premises, medical expense
  • Deductibles and how they apply (per claim vs. per occurrence)

Classifications & exposure

  • Premises/operations classifications with GL class codes
  • Exposure bases: gross sales, payroll, area, units
  • Per-location classification splits
  • Products and completed-operations details

Underwriting questions

  • Contractor and subcontractor questions (certificates collected? written contracts?)
  • Hazardous operations, prior products recalls, discontinued products
  • Athletic teams, special events, exposures the schedule doesn’t show

Parties & interests

  • Additional insureds and their relationships
  • Loss payees and certificate holders downstream
  • Cross-references to the ACORD 125 applicant record
Where it goes wrong by hand

The 126 is filled once, then retyped everywhere

  • GL class codes get re-looked-up and retyped per carrier, and each carrier maps to its own code system, so the same operation can carry different codes in different portals.
  • Limits and deductibles live on different screens in every portal; transposing an aggregate is the kind of error that surfaces at claim time, not at quoting.
  • Additional insureds are typed one at a time, per portal, for every market quoted.
  • A 126 plus its 125 takes 15+ minutes per carrier to rekey, so quoting five markets burns more than an hour on data entry alone.
The automated version

Our pipeline reads every field off the ACORD 126, digital or scanned, with per-field confidence scores, maps it to each carrier’s vocabulary, and fills carrier portals or APIs from the same record. One form in, every appointed market quoted. See the full picture in ACORD to portal, the engineering behind it in ACORD integration services, or feel it free: autofill an ACORD 126 from a USDOT number. Want this running inside your own stack? Hire insurtech developers who ship it.

Reading the 126 is one component. The submission system around it, the intake queue, the class-code review screen, the fan-out to every appointed GL market, the status back to the producer, is a build. That is custom insurance software development, and the ACORD pipeline described above is one of the parts we bring to it.

FAQ

ACORD 126 questions, answered.

What is an ACORD 126 used for?

It is the Commercial General Liability section of the ACORD application set. Agencies submit it with the ACORD 125 (the commercial application core) so carriers can rate GL coverage: limits, classifications, exposures, deductibles, and the underwriting questions specific to liability.

Does ACORD 126 automation require a carrier API?

No. Extraction reads the form itself, and delivery uses whatever the carrier offers: an API where one exists, deterministic portal automation where it doesn’t. No carrier approval is needed to stop retyping your own application data.

How does automated GL class code mapping work across carriers?

The pipeline reads the class codes and operation descriptions from your 126, then maps them per carrier, because carriers genuinely differ in their code systems. Mapping rules are explicit and reviewable, so a wrong-code surprise becomes a mapping fix, not a recurring mystery.

Can it handle multi-location GL schedules?

Yes. Per-location classifications, varying limits by location, and location-specific exposures are extracted as structured schedule data and placed into each portal’s location screens, the exact part humans hate most.

What about scanned or faxed 126s?

Scans are the normal case, not the exception. OCR runs with per-field confidence scores; anything below threshold routes to quick human review instead of flowing into a carrier submission wrong.

Related form guides: ACORD 130 (Workers’ Comp) · ACORD 140 (Property) · ACORD to portal

The next 20 minutes

Never retype an ACORD 126
into a portal again.

Bring a real 126 from last week. We’ll run it through extraction live and show you the fields landing in a carrier portal, then you decide if it’s worth a conversation.

Book a 20-min demo →