A submission is the broker’s argument to the market. It is also, in most broking teams, a Word document assembled by hand from five sources the night before it goes out. The gaps nobody noticed are the questions underwriters send back a week later — or the reason they decline.
InsightPlacement’s submission builder assembles the package from the record, flags every gap inside the package itself, keeps every version, and only proposes approval when the high-severity gaps are closed. This post follows two illustrative placements: a food manufacturer whose version 3 has nine open items, and a software company whose version 3 is one item from market-ready.
| Actors | Placement broker (approves), account manager (closes the gaps), account executive |
|---|---|
| Trigger | The placement enters data collection; the data behind the submission changes; Analyze |
| Agents involved | Submission builder (with the readiness agent and the data-gap chaser upstream) |
| Decisions | Approve a version as market-ready; redraft; download for review |
| Systems touched | Client record, the data room (SOV, loss runs, expiring policies, application), InsightPulse company profile |
| Outcome | A versioned, market-ready package whose open items are stated, not hidden |
| What is measured | Open items at approval, versions before approval, underwriter questions per submission |
What goes into the package
The submission is an HTML document generated from the engines’ output, in a fixed order:
- Cover note — the one place a model may write prose, and it is checked against the facts before it is used.
- The applicant — industry and NAICS, headquarters, revenue, employees, client since; the company profile is dated and attributed to InsightPulse.
- Program requested — each line with the limit and retention asked.
- Exposures — this year against last, with the changes that need explaining.
- Property schedule — locations, TIV by state and construction, the sprinklered share.
- Loss history — five years per line: claims, incurred, the largest loss, the loss ratio, and the valuation date.
- Expiring program — carrier, limit, retention and premium per line.
- Open items — every gap, by area and severity.
builder"] B["Exposures"] --> S C["SOV check"] --> S D["Loss runs
5 years per line"] --> S E["Expiring program"] --> S F["InsightPulse
company profile"] --> S S --> V["Version N:
HTML package,
open items flagged"] V --> Q{"High-severity
items open?"} Q -- yes --> R["Drafted only:
close the gaps first"] Q -- no --> P["Prepared: approve
as market-ready"] P --> H{"Placement broker"} style R fill:#fff4e2,stroke:#f4a03a style H fill:#e8f8f4,stroke:#10b981,stroke-width:2px
A version is a state, not a file name
Each build is a new version. A newer draft supersedes an older draft; an approved or sent version is never rewritten. When a submission is already ready or sent, the submission builder says so and stops — it will not redraft what a person has approved.
Case one: version 3 with nine open items
The food manufacturer from the 120-day post is in data collection. Version 3 is drafted with nine open items: drivers not collected; construction missing at location 5; sprinklers unknown and an old roof at location 8; the SOV last updated in September 2025; three loss runs not received; and the umbrella’s expiring policy not on file. Because high-severity items are open at the data-collection stage, the agent drafts the version and stops — it does not ask anyone to approve a package with known holes.
Case two: version 3 with one open item
An illustrative software company renewing property, general liability, cyber and management liability is at the submission stage, 88 days out, readiness 100%. Its version 3 has one open item. Here the submission builder prepares the decision: Approve submission version 3 as market-ready (1 open item), listing the item so the broker approves knowingly. It sits on the placement broker’s Home under “What needs me” beside the market selector’s plan.
Step by step
Food manufacturer: nine open items, five of them high severity. The agent’s step says so in one line and lists the drivers; nothing waits on a person yet.
The client’s answers come back through the data-gap chaser’s request; the SOV is re-imported.
Fewer open items; any that remain are stated in the package’s Open items section.
Software company: “Approve submission version 3 as market-ready (1 open item)”, with the item listed and the facts behind it.
Accept marks the version ready and writes the approval, with the broker’s name, to the decision record. Reject keeps it a draft; Ask sends a question back.
The approved version is what the outreach drafter attaches to each market’s e-mail.
What the agents prepared, and what each rests on
| Agent | What it prepared | What it cites | Who decides |
|---|---|---|---|
| Submission builder | Draft version N; approve it as market-ready only when no high-severity item is open | Client record, exposures, SOV, loss runs, expiring program, Pulse profile | Placement broker |
| Data-gap chaser | The client request that closes the open items | SOV rows and exposure data | Account manager |
| Renewal readiness | Loss-run orders for the lines not in | Loss-run status per line | Account manager |
Edge cases
| What happens | What InsightPlacement does |
|---|---|
| The placement is still at intake | The submission is not built: “the submission is built once data collection starts.” |
| A version is approved, then a loss run arrives | The approved version stays as approved. A redraft makes a new version for a person to approve. |
| No model configured | The cover note falls back to a plain sentence built from the facts; every other section is the engines’ anyway. |
| InsightPulse not connected | An illustrative stand-in answers in the demo; the profile is always dated and attributed. |
The decision record for this step
| Section | Hit | Outcome |
|---|---|---|
| Agent | Submission builder: version 3 drafted, 9 open items (food manufacturer) | warn |
| Agent | Submission builder: approve version 3 as market-ready, 1 open item (software company) | refer |
| Person | Placement broker approved version 3 (when accepted) | proceed |
For the account team
You approve a package, not a pile of attachments, and you see its open items before the market does.
For broker IT
The package is generated HTML with every figure from the engines; versions are rows with a status, so “what did we send to whom” is a query, not an inbox search.
For practice leaders
Open items at approval is a quality number for each team. It is the leading indicator for underwriter questions and declinations.
Questions we get asked
Can the model rewrite the loss history to read better?
No. Loss history, exposures, the schedule and the program are rendered from the engines. The model may write the cover note only, and that note is checked against the facts.
Can we use our own submission template?
The package layout is the product’s; a branded template is a configuration project, not a model prompt.
Keep reading
Choosing the markets for a coastal property renewal
Eighty-three million of TIV in Florida, and capacity that runs out at fifty.
Read article
Claims advocacy, company intelligence and policy checking in the renewal
The loss story from InsightAdvocate, the company from InsightPulse, the bound policy for InsightProofing.
Read article