ACORD 125 and 131—What Goes Where

This reference shows what belongs on ACORD 125 vs. 131, who owns 7 handoff tasks, and how to check a restaurant umbrella example before submission. ACORD 125 and 131 are paired commercial insurance applications: ACORD 125 captures account-level business information, while ACORD 131 captures the umbrella or excess liability request.

My recommendation is simple: do not let ACORD 131 leave the agency as if it tells the whole account story. The carrier or wholesaler still needs current account facts, current underlying policy information, and a clear producer-approved coverage request.

Edition note: ACORD forms and carrier supplements can vary by edition, market and agency system. The tables below group related intake facts for agency workflow; they do not reproduce every ACORD field, replace licensed form instructions, or claim to be exact labels for every edition. Before you use this as a desk procedure, verify it against the current licensed ACORD 125 and ACORD 131 forms in your AMS, rater or carrier portal.

TL;DR: ACORD 125 gives the carrier the account context. ACORD 131 gives the carrier the umbrella or excess layer details. Build the package in this order: factual intake, current underlying policies, producer coverage review, CSR form mapping, final signature and submission notes.

Key takeaways:

• Use ACORD 125 for named insured, operations, premises, contacts, prior coverage context and signature information.
• Use ACORD 131 for requested umbrella or excess limits, retained limit, underlying policies, exposure details and loss information requested by the market.
• The CSR can gather facts, but the producer should confirm coverage intent and requested limits.
• Match named insureds across ACORD 125, ACORD 131 and the underlying policies before submission.
• Pull current declarations before typing the ACORD 131 underlying schedule.
• Use current licensed ACORD forms and carrier instructions, not old PDFs or copied screenshots.

What are ACORD 125 and 131 used for?

ACORD 125 and 131 are used together when a commercial account needs an umbrella or excess liability quote. ACORD 125 explains who the insured is and what the business does; ACORD 131 explains the liability layer being requested above scheduled underlying policies.

Think of the forms this way:

Form	Plain-English job	When it appears	Usually paired with
ACORD 125	Account-level commercial application	Commercial package submissions where the market needs business-level facts	Line-specific forms such as GL, property, auto or workers comp
ACORD 131	Umbrella or excess liability section	When the insured wants limits above underlying liability policies	ACORD 125 plus current underlying policy information

For example, a restaurant seeking a 2 million dollar umbrella may need ACORD 125, a GL application, current underlying declarations, liquor liability details if applicable, auto details if hired and non-owned auto is involved, workers comp details if required by the market, and ACORD 131 for the umbrella request. If your team needs the account-level form broken down separately, use our ACORD Commercial Insurance Application 125 field map. For GL packages, the ACORD 125 and 126 field map is the natural companion.

A practical note: ACORD forms are maintained by ACORD and usually accessed through licensed agency management systems, comparative raters or carrier portals. This article is an agency operations reference, not legal advice or coverage advice.

Who fills out ACORD 125 and 131 in an agency?

A CSR can prepare ACORD 125 and 131, but a licensed producer or account manager should confirm coverage intent, limits, exclusions and final submission accuracy. The split I recommend is factual intake to the CSR, coverage intent to the producer, and final packaging to the account manager or producer who owns the submission.

Here is the ownership model I would use when the phones are still ringing at 3:40 p.m. and a producer wants a restaurant umbrella quote out before the end of the day.

Work item	Recommended owner	Why it matters	Rework prevented
Basic named insured, DBA, address, FEIN, contacts	CSR or account assistant	Mostly factual intake	Avoids re-keying the same contact data
Operations description and revenue or payroll context	Producer first, CSR documents	Drives market appetite and classification	Avoids vague descriptions like restaurant or contractor
Requested umbrella or excess limit	Producer	It is a coverage-sensitive decision	Avoids quoting the wrong layer
Underlying policy limits and carriers	CSR gathers, producer reviews	Must match the ACORD 131 schedule and current declarations	Avoids a second request for current declarations
Loss runs and prior claims summary	CSR gathers	Market requirements vary by period and line	Avoids missing claim detail during underwriting review
Signature and date	CSR coordinates, insured signs	Form and carrier rules control	Avoids submitting an unsigned or stale application
Final submission notes to carrier	Producer or account manager	Frames the risk and attachments	Avoids a pile of PDFs with no cover story

The main rule: a CSR should not be forced to decide whether the insured needs umbrella, excess or both. That is producer work.

Which fields go on ACORD 125 versus ACORD 131?

ACORD 125 gets the account facts; ACORD 131 gets the umbrella or excess request and the underlying coverage schedule. If your CSR understands that split, the package becomes much easier to review.

ACORD 125 intake groupings for an umbrella package

Use this as a pre-check before anyone starts typing into the form. Verify the exact location and required fields against your licensed edition.

ACORD 125 intake grouping	What to collect	Staff note
Applicant identity	Legal name, DBA, mailing address, physical address, website, phone, email	Match the legal name to every underlying policy
Agency and contact details	Agency name, producer, CSR contact, agency code if used	Make the submission owner obvious
Business description	Operations, years in business, entity type, NAICS or SIC when used	Avoid one-word descriptions
Premises and locations	Locations, occupancy, lease or ownership, square footage if relevant	Match location schedules on other forms
Prior carrier and coverage context	Current carriers, policy numbers, effective dates, limits	Reconcile against ACORD 131 before sending
Loss information	Date of loss, type, amount paid or reserved, status, market-required period	Attach loss runs when available and required
Remarks and attachments	Clarifications, unusual operations, contract-driven needs	Add underwriting context, not coverage advice

This is where small inconsistencies start. The website says Bayview Bistro, the GL policy says Bayview Bistro LLC, and the umbrella application uses Bayview Restaurant Group. Fix that before ACORD 131 is touched.

ACORD 131 intake groupings for umbrella and excess liability

ACORD 131 should make the requested layer clear and show the current underlying policies that support it. Treat the table below as a review checklist, not as a substitute for the form instructions.

ACORD 131 intake grouping	What to collect	What to verify before sending
Applicant and proposed term	Same named insured, proposed effective date, expiration date, requested quote timing	Dates align with the intended policy term
Coverage requested	Umbrella, excess, or both if the market asks that way	Producer confirms intent in writing
Requested limit	Each occurrence, aggregate or other limit basis requested by the market	Requested limits match the client and producer conversation
Retained limit or self-insured retention	Amount and when it applies if the market requires it	Do not guess or leave ambiguous when required
Underlying policies	GL, auto, employers liability, liquor liability or other scheduled lines	Carrier names, policy numbers, limits and dates are current
Exposure information	Sales, payroll, vehicles, employees, premises, subcontractor use or other market-requested facts	Numbers match the underlying applications
Loss information	Open claims, closed claims, large losses or prior umbrella losses for the required period	Attach current loss runs or explain availability
Remarks	Special contracts, unusual operations, additional insured needs	Clarify facts without promising coverage

A concrete reconciliation procedure helps: pull the current declarations first, enter the underlying policy rows second, then compare named insured, policy term, carrier, policy number and limits against the account file before the producer signs off.

Filled example: ACORD 125 and 131 for a restaurant umbrella

A filled example should show the source document, reviewer and exception for each fact, not just which form gets the data. The example below is fictional and should be checked against your licensed ACORD edition and the carrier portal before use.

Scenario: Bayview Bistro LLC is a neighborhood restaurant with dine-in service, takeout, limited catering, beer and wine sales, 22 employees, and hired and non-owned auto exposure. The owner asks for a 2 million dollar umbrella quote over general liability, liquor liability, hired and non-owned auto, and employers liability.

Form location to verify in licensed edition	Example entry	Source document or source call	Reviewer	Common exception
ACORD 125 applicant identity area	Bayview Bistro LLC, DBA Bayview Bistro	Secretary of State lookup, current GL dec, insured intake	CSR verifies, producer reviews	Website shows DBA only
ACORD 125 proposed policy term area	04/01 to 04/01, aligned with package renewal	Renewal list, current declarations	Account manager	Umbrella requested mid-term
ACORD 125 premises or location area	418 Cedar Street, Portland, OR	Lease, current GL dec, insured intake	CSR	Mailing address differs from premises
ACORD 125 business description or remarks area	Full-service restaurant with dine-in, takeout and catering under 10 percent of receipts	Producer call notes	Producer	One-word description does not explain catering
ACORD 131 requested limit area	2 million dollars umbrella limit requested	Producer email, client request	Producer	Contract asks for higher limit than client mentioned
ACORD 131 retained limit or SIR area	To be completed per market requirement after producer review	Carrier instructions, producer review	Producer	CSR is tempted to leave blank without checking instructions
ACORD 131 underlying GL row	Current GL carrier, policy number, 1 million per occurrence, 2 million aggregate, 04/01 to 04/01	Current GL declarations	CSR enters, producer reviews	Last year’s limits copied from old file
ACORD 131 underlying liquor liability row	Current liquor liability carrier, policy number, applicable limits, 04/01 to 04/01	Liquor liability declarations	Producer	Liquor is endorsed on GL rather than standalone
ACORD 131 underlying auto row	Hired and non-owned auto only, scheduled according to market instructions	Auto endorsement or business auto dec	Producer	No owned autos, but contract asks about auto liability
ACORD 131 employers liability row	Employers liability limit from workers comp policy	Current workers comp declarations	CSR enters, producer reviews	Work comp placed with different carrier or renewal date
ACORD 131 loss information area	One slip-and-fall claim closed at 18,500 dollars paid	Loss run, claim notes	Account manager	Loss run period does not match market request
ACORD 125 or ACORD 131 remarks area, depending on form and market instruction	Catering is under 10 percent of receipts; no delivery drivers; hired and non-owned auto exposure only	Producer notes, insured confirmation	Producer	Operations changed since last renewal

A clean producer note to the underwriter might read:

"Bayview Bistro LLC is a 7-year restaurant account with dine-in, takeout and limited catering. The insured is requesting a 2 million dollar umbrella over GL, liquor liability, hired and non-owned auto, and employers liability. One GL claim is closed with 18,500 dollars paid. Current loss runs and underlying declarations are attached."

That paragraph does not sell coverage. It frames the risk so the underwriter does not have to reconstruct the story from five PDFs.

What mistakes should you check before sending ACORD 125 and 131?

The mistakes I recommend checking first are mismatched names, incomplete underlying policy details, unclear coverage intent and vague operations descriptions. These are plain workflow errors, but they create avoidable back-and-forth.

Check	Why it breaks	Fix
ACORD 125 shows DBA only, but ACORD 131 shows legal entity	The market may not be able to confirm the insured	Use legal name plus DBA consistently
Underlying limits are copied from last year	The umbrella quote may be based on stale attachment information	Pull current declarations before typing ACORD 131
Producer says umbrella, CSR marks excess	The market may quote on the wrong basis	Require producer confirmation in the submission file
Loss information period is assumed	Carrier and market requirements vary	Ask what loss-history period this market requires and collect open and closed claims for that period
Operations say contractor, restaurant or consultant only	Appetite review lacks context	Add specific operations, revenue mix and unusual exposures
Contract-driven needs are buried in email	The submission may miss why the limit is being requested	Summarize the contract driver in remarks or submission notes
Signature date is missing or stale	The market may require a current signed application	Check signature rules before sending

This is also where companion forms matter. If the umbrella sits over GL, use the GL package workflow. If workers comp is part of the account, our ACORD 130 fillable field map covers that companion form.

What documents should accompany ACORD 125 and 131?

The supporting documents should prove the account facts, the underlying schedule and the loss story. Carrier instructions control, but I would not send an umbrella submission without first checking this packet.

Supporting item	Why it helps	Owner
Current underlying declarations	Confirms carrier, policy number, term and limits	CSR gathers, producer reviews
Applicable underlying applications	Supports GL, auto, workers comp, liquor or other scheduled exposures	CSR packages
Loss runs or loss details for the required period	Gives the market claim context	CSR requests, account manager reviews
Contract or lease driving the umbrella request	Explains requested limits or additional insured needs	Producer reviews
Prior umbrella or excess policy, if any	Shows expiring structure and limits	Account manager reviews
Submission note	Connects the PDFs into a coherent story	Producer or account manager writes

A short intake script helps the CSR collect facts in underwriting order, not caller order:

1. "What is the exact legal name of the business and any DBA you use?"
2. "What does the business do, in plain English, and what has changed since last year?"
3. "How many locations do you operate from, and are any new locations opening during the policy term?"
4. "What umbrella or excess limit are you asking us to quote?"
5. "Which policies should the umbrella or excess layer sit over, such as general liability, auto, liquor or employers liability?"
6. "Do you have current declarations pages for those policies?"
7. "What loss-history period does this market require, and were there any open or closed claims during that period?"
8. "Are contracts, landlords or customers requiring specific limits or additional insured wording?"
9. "Who at the business is authorized to sign applications?"
10. "What deadline are you working against?"

Put those questions into your intake template and require producer review before anyone sends ACORD 131. The CSR can prepare the package. The producer should confirm the requested layer and any coverage-sensitive wording.

Where Sera fits, and where she does not

Sera fits at the front of the ACORD workflow by capturing intake facts, routing the request and making sure a commercial caller does not disappear into voicemail. Sera is an AI receptionist: she answers every call, text and web chat 24/7, qualifies the caller, and books them with your team.

For an independent insurance agency, Sera can sit at the front of this workflow by answering and qualifying inbound inquiries. For ACORD 125 and 131 work, that means she can help before licensed review.

Intake task	Sera can help?	Human still needed?
Capture caller name, business name, phone and email	Yes	CSR verifies before submission
Ask whether the request is new business, renewal or contract-driven	Yes	Producer decides next step
Collect deadline and preferred appointment time	Yes	Team confirms availability
Route an umbrella or excess request to a commercial CSR or producer	Yes, based on your escalation rules	Agency owns routing design
Log the conversation transcript	Yes	Staff reviews and enters data into the agency system
Explain whether umbrella or excess is better	No	Licensed producer handles it
Quote premium, bind coverage or file a claim	No	Licensed agency staff and carriers handle it

Important limits: Sera has no direct integration with EZLynx, HawkSoft, Applied Epic, AMS360 or QQCatalyst. Intake notes can go to email or tools such as Gmail, HubSpot, Salesforce, or Slack. Sera does not bind coverage, quote premiums, give coverage advice or file claims with carriers. Twig is SOC 2 Type II certified, but Sera is not HIPAA compliant and Twig does not sign BAAs.

If your problem is missed calls, after-hours web quote leads or CSR interruption, Sera can be live quickly by forwarding the phone line or adding website chat. If your problem is completing ACORD fields inside your agency management system, Sera will not replace that workflow. You can review plans on Sera pricing.

Next step: add one required ACORD 125 checkbox

The next step is to turn ACORD 125 and 131 into a checklist your team uses before every umbrella or excess submission. Keep it short enough that a CSR will actually use it.

Start with these 8 checks:

1. Legal name and DBA match across all forms and underlying policies.
2. Operations description is specific enough for underwriting review.
3. Requested umbrella or excess limit is producer-approved.
4. Current underlying declarations are attached.
5. Underlying carriers, policy numbers, dates and limits match ACORD 131.
6. Loss runs or loss details match the period required by the market.
7. Contract-driven requirements are summarized in the submission note.
8. Signature and date meet the carrier’s instructions.

If you do only one thing this week, add a required checkbox to your submission checklist: current ACORD 125 attached, or carrier confirmation that one is already on file.