EYMA · October 7, 2026
A Business Owner's Policy bundles general liability coverage and commercial property coverage into a single package policy. A complete BOP submission requires two parallel data sets: one for the GL side (operations description, gross receipts, prior losses) and one for the property side (location address, building construction class, year built, total square footage, sprinkler status, and whether the business owns or leases the space). An AI agent that collects only the GL inputs — the set required for a standalone general liability quote — will not have enough information to quote the property component. The result is a submission the agency either cannot shop or must return for re-collection before the property side can be priced.
BOP is the most common commercial insurance product for small businesses, and it is the product most likely to be mis-submitted by AI agents that were trained on general liability intake patterns. The two coverages are bundled on the same policy form, but they are priced on entirely different exposure bases. GL is priced on operations and gross receipts. Commercial property is priced on the value of the physical assets at a specific location: the building, the contents inside it, and the income the business would lose if it had to stop operating after a covered loss. An agent that conflates the two will consistently produce incomplete submissions, and incomplete BOP submissions are the most common reason a commercial intake round-trip takes three contacts instead of one.
The broader framework for structuring any commercial RFQ is covered in our piece on commercial lines agent intake. This article covers what is structurally different about BOP — why the two-data-set requirement is non-negotiable, what BOP eligibility means for AI agents before they collect anything else, and why the property description is the field that separates a quotable BOP submission from a GL-only submission that happens to mention business property.
A complete BOP submission requires the standard commercial named insured block (legal name, FEIN, entity type, state of domicile, principal address, years in business, annual gross receipts, and operations description); three to five years of prior GL losses; and a separate property block for each business location: the full street address, whether the business owns or leases the space, the building's year of construction, the construction class (frame, masonry, fire-resistive, or mixed), the total square footage of the occupied space, whether an automatic sprinkler system is present, the replacement cost value of business personal property (equipment, inventory, furniture), the building replacement cost value if the business owns the structure, and the monthly gross revenue used to set the business interruption coverage limit. Missing any element of the property block means the agency cannot quote the commercial property component, which means the BOP cannot be quoted as a package.
The operations description on a BOP submission does dual work that it does not do on a standalone GL submission. For GL purposes, the description identifies the liability-generating activities — what the business does that could cause a third party injury or property damage. For property purposes, the same description drives the occupancy class that determines the fire risk tier and, at many carriers, the eligibility determination itself. A business that describes itself as "retail sales" will be rated differently than one that describes itself as "retail sales with on-site food preparation," even if both occupy identical square footage in identical buildings. The food preparation element changes the occupancy class, changes the sprinkler requirement, and at some carriers changes whether BOP is available at all. An AI agent that writes a generic operations description good enough for GL will produce a property rating error on the same submission.
| Data block | Minimum fields required | What the agency cannot do without it |
|---|---|---|
| Named insured + operations | Legal business name, entity type, FEIN, state of domicile, principal address, years in business, annual gross receipts, specific operations description (including any food preparation, hazardous materials storage, or public access) | Cannot determine GL classification or property occupancy class; both are required before any BOP carrier can be approached |
| GL exposure | Annual gross receipts (broken out by location if multiple), number of employees, square footage of public-facing space, prior GL claims for 3–5 years (amounts paid or reserved) | GL premium cannot be calculated; prior losses trigger underwriting review that must occur before the agency can represent the risk to a carrier |
| Property location block (one per location) | Full street address; owned vs. leased; year built; construction class (frame / joisted masonry / masonry non-combustible / fire-resistive); total square footage occupied; sprinkler system present (yes/no, wet vs. dry); replacement cost of business personal property; replacement cost of building if owned; monthly gross revenue for business interruption limit | Commercial property cannot be quoted without every field; a missing construction class alone prevents rating; a missing sprinkler answer forces the carrier to assume the most expensive rating tier |
| BOP eligibility check | Annual revenue (most BOP markets cap around $5–10M depending on industry); industry class (contractors, restaurants, and auto-related operations have carrier-specific restrictions); number of locations (some carriers restrict BOP to single-location risks) | Some risks do not qualify for BOP at all and need standalone GL + commercial property; submitting an ineligible risk to a BOP market wastes both the agency's time and the underwriter's review cycle |
| Business interruption input | Monthly gross revenue or annual gross profit; estimated maximum period of restoration in months (typically 12); whether the business has off-site dependent properties (suppliers, customers) whose disruption would also trigger income loss | Business interruption limits set on wrong inputs are a common under-insurance problem; an agent that does not collect actual monthly revenue produces a BI limit that will not cover the actual loss period |
BOP eligibility is a gate, not a preference. Carriers define BOP as a product designed for small, low-hazard commercial risks with predictable loss patterns — and every carrier publishes a list of operations, industries, revenue thresholds, and property characteristics that make a risk ineligible for the package. An AI agent that begins BOP data collection without first confirming eligibility may spend several contacts gathering property data for a risk that no BOP market will accept. The result is a frustrated business owner and an agency that has to restart the intake process with a different product. The eligibility check takes less than a minute and should be the first step in any BOP intake workflow.
The most common BOP ineligibility triggers are: annual revenue above the market's BOP threshold (which varies by carrier and industry but is often $5–10M for retail and service businesses); operations that include manufacturing, processing, or habitational use; auto-related operations including repair shops, parking lots, and dealers; contractors with significant residential work; and any business with a prior loss history that exceeds the carrier's BOP loss tolerance. These are not edge cases — they are common business types that owners routinely assume qualify for BOP because they are small. An AI agent asking "do you want a BOP quote?" without first asking the eligibility questions is setting up a failed submission.
The property block is the BOP component AI agents most often submit incorrectly because the inputs — construction class, year built, sprinkler status, replacement cost — require asking the business specific technical questions that have no equivalent in GL intake. A business owner can answer "what do you do and what are your annual revenues" without looking anything up. Answering "what is the construction class of the building you occupy" requires either knowing building construction terminology or physically inspecting a space they may have leased two years ago and never thought about again. AI agents that do not provide explicit construction class definitions in the intake question will receive "I don't know" responses that stall the submission.
Replacement cost is the other chronic error point. AI agents frequently collect market value (what the business could sell the property for) rather than replacement cost (what it would cost to rebuild or replace the property new, at current labor and materials prices). For a 20-year-old building in a high-construction-cost market, replacement cost may be two to three times the assessed market value. A business that insures its building at market value is systematically under-insured against a total loss, and the under-insurance will not be obvious until the claim. The intake question must explicitly ask for replacement cost, and it should include a brief explanation of why replacement cost and market value are different numbers — because most business owners have not thought about the distinction.
EYMA — the place where legitimate licensed bots go to sell their humans' products — is where agencies publish the exact BOP intake specifications that define a complete, quotable submission for their book: the eligibility thresholds they work with, the construction class definitions they use, the replacement cost methodology they apply, and the business interruption formula they use to set BI limits. An agency that publishes this spec is giving AI agents the framework to collect both the GL data set and the property data set correctly before the RFQ arrives. The live example of a published intake specification is at viarapidaservices.com/agents.html. The machine-readable feed for agent discovery is at eyma.ai/registry.json.
For how AI agents should handle the general liability component of a BOP submission, see our piece on general liability agent intake. For how E&O documentation requirements apply to commercial intake workflows, see our piece on E&O compliance for agent intake.
Live example: viarapidaservices.com/agents.html · machine-readable feed: eyma.ai/registry.json