Industry insights

What to send a wholesaler for a bar or restaurant liquor liability quote

A retail agent's checklist for a useful bar or restaurant GL/liquor inquiry, followed by the documents a fuller underwriting submission may need.

Tobias Lendl Co-Founder & CTO September 4, 2026

An agency has a restaurant renewal to compare, but the loss runs have not arrived and the application needs updating. The first email can still be useful if it explains the account and what the producer needs.

The distinction is between asking whether a risk may fit and supplying enough information for underwriting to offer terms. Label the first email accordingly.

Start with an account summary

For an initial liquor liability and GL discussion, send Nomos:

  • Agency and contact: who owns the submission and how to reach them.
  • Operation and location: bar, tavern or restaurant; legal entity and risk state.
  • Timing: renewal or requested effective date, including any deadline.
  • Sales: total annual receipts, the alcohol-sales proportion and whether figures are historical or projected.
  • Hours and activities: closing times, food service, entertainment and any security arrangements.
  • Current terms: premium, GL/liquor limits and whether you want both lines reviewed.
  • Loss summary: known claims and open matters; say when updated loss runs have been requested.

Attach existing applications and current terms if available. State the commercial question in a sentence: “Please review this tavern renewal for a competitive GL/liquor alternative.” Avoid presenting an estimate as a confirmed fact.

Then assemble the underwriting file

The market’s requirements determine the complete submission. Ask which application, supporting documents and loss-history period it needs. Prepare to reconcile the named insured, liquor-license holder and locations across those documents.

License information, sales mix, hours, entertainment and training appear in this published Great American Ocean Marine liquor questionnaire. The dated form illustrates the questions an insurer may ask; it is not a Nomos application or evidence of current market eligibility.

For each material claim, provide the available status and a factual explanation. If the insured changed a procedure after an incident, identify the change and when it occurred. Do not substitute a favorable narrative for the loss record.

Resolve contradictions before forwarding the file

Consider a hypothetical tavern described as closing at 11 p.m. in the application while its website advertises Friday service until 1 a.m. Ask the operator which schedule is current. Update the application or explain the exception so the underwriter receives one coherent description.

The same check applies when receipts differ between the application and renewal worksheet. Identify the period behind each number, and explain a new location or material change in trading hours. This is preparation for an accurate review, not a promise of a particular rate.

Use the bars and taverns page for bar accounts and the restaurant page for food-service operations. Once offers arrive, the GL/liquor comparison checklist helps your agency show the insured what changed in both price and protection.

Short answers.

Do I need a complete application before asking about appetite?

You can start an account discussion with the risk state, operations, effective date and current terms. A quote may require completed applications, loss runs and further underwriting information.

Should I send GL information with a liquor liability inquiry?

Yes. Include the existing GL arrangement and say whether the agency wants to retain it or compare both lines. That helps frame the coverage and pricing review.

Tobias Lendl

Co-Founder & CTO

Tobias started building software at 13. A two-time global hackathon winner, he wrote software for the Austrian government and built systems handling terabytes of satellite data, doing all of this before graduating from Austria's top CS school, HTL Spengergasse. He has since left TU Vienna to build Nomos.

LinkedIn →