The ACORD 126, formally the Commercial General Liability Section, is the supplemental ACORD form that documents a commercial account's general liability exposure. It attaches to the ACORD 125 common application and gives a GL underwriter the specific inputs they price from: the coverage form, the limits requested, and the classification-and-exposure schedule that drives the premium. If the 125 tells you who the applicant is, the 126 tells you what they do that could hurt someone, and how much of it they do.

General liability is the most widely purchased commercial coverage, which makes the 126 one of the most frequently read documents in the whole ACORD forms family. It is also one of the easiest to misread, because a single misclassified operation or a wrong premium basis quietly distorts the rate.

TL;DR

• The ACORD 126 is the Commercial General Liability Section, the supplement that documents GL exposure on a submission.
• It captures the coverage trigger (occurrence vs claims-made), limits (each occurrence, general aggregate, products/completed operations, personal and advertising injury, medical payments), and the classification/exposure schedule.
• The classification schedule (class code plus premium basis: gross sales, payroll, area, or units) is the field that drives the rate, and the field most often keyed wrong.
• Underwriters read the 126 alongside loss runs. The two together are the core of GL risk selection.
• Template-agnostic extraction pulls the 126's classifications and limits into structured fields with source links, so the schedule an underwriter rates from is verified, not re-typed.

What the ACORD 126 captures

Coverage and trigger. Whether the policy is written on an occurrence or claims-made basis, and, for claims-made, the retroactive date. This one distinction changes how losses are counted and reserved, so it sits near the top of the form for a reason.

Limits of insurance. Each-occurrence limit, general aggregate, products and completed-operations aggregate, personal and advertising injury, damage to premises rented to the insured, and medical expense. Underwriters check these against the applicant's contracts and the risk, not just against what was requested.

Classification and exposure schedule. The heart of the form. Each operation is listed by classification code, with a premium basis (gross sales, payroll, area, total cost, or units) and the exposure amount. The classification codes follow ISO/Verisk's commercial general liability system. A restaurant, a general contractor, and a manufacturer carry very different codes, bases, and hazard grades, and the schedule is where those get pinned down.

Additional detail. Subcontractor use and controls, contractual liability, additional insured arrangements, and coverage-specific supplemental questions that surface hazards the class code alone would miss.

Why the ACORD 126 matters at intake

The 126 is where GL underwriting either starts clean or starts wrong. The classification schedule feeds directly into the rate, so an error there is not cosmetic. It is a mispriced policy. Yet the schedule is exactly the part of the form most likely to arrive incomplete, handwritten, or spread across a supplemental the broker attached separately.

That is why generic optical character recognition struggles here. It reads characters; it does not understand that a class code and its premium basis belong together, or that a blank exposure field on an otherwise-populated row is a question an underwriter must chase. Reading the 126 correctly means understanding the form's meaning, not just its pixels, a point we made in why AI alone won't fix submission intake. And because GL losses are what ultimately validate the rate, the 126 is read alongside the account's loss run history, never in isolation.

How Pibit.ai reads the ACORD 126

Pibit.ai's CURE™ (Centralized Underwriting Risk Environment) platform reads the 126 as a structured object, not a picture. DocumentCURE™ extracts the coverage basis, the full limit set, and every row of the classification-and-exposure schedule with template-agnostic extraction, so a clean form and a marked-up one both resolve into the same structured fields without per-template training. Each field carries a link back to its source location on the form, which is what lets an underwriter accept the schedule and rate from it rather than re-verifying every code by hand.

Fed into submission intake, that turns the 126 from a document someone has to transcribe into rater-ready data that arrives with the rest of the submission, at 100% data accuracy. The GL underwriter opens the file and finds the classification schedule already reconciled against the ACORD 125 and the loss runs, and spends their time on risk selection instead of data entry. More on the intelligence hiding in these forms in what ACORD forms reveal to underwriters.

Sources

• ACORD (Association for Cooperative Operations Research and Development), insurance data standards and standardized forms, 2026. (ACORD maintains the standardized commercial lines forms, including the ACORD 126 Commercial General Liability Section.)
• ISO / Verisk, Commercial General Liability classification system, 2026. (Named, not linked: the class-code framework referenced on the ACORD 126 exposure schedule.)
• Pibit.ai product documentation, 2026. (Internal, not linked: DocumentCURE™ template-agnostic extraction; 100% field-level data accuracy with source-linked provenance.)