Skip to main content
A submission is the record that holds one request for insurance. Under it sit the quotes you work up for that request and the exposures those quotes cover. The submission also keeps details that apply to the whole request, such as loss history. What the applicant asked for, such as the coverage and the term, is recorded on the quote. Every new business or renewal quote belongs to a submission; an endorsement, cancellation or reinstatement belongs to the policy it changes. This page is the reference for the Submissions area; for the step-by-step guide to getting submissions into the system (manual entry, AI import, email), see Creating submissions.

The Submissions list

Open Submissions in the sidebar. Each row is a submission; selecting a row opens its detail page.
The Submissions list page showing columns Submission Number, Submission Name, Status, Type, Last Updated, and Created, an Add Filters button above the table, and toolbar buttons Import, Edit Columns, Export Submissions, and Create Submission.

The Submissions list with its toolbar: Import, Edit Columns, Export Submissions, and Create Submission.

Toolbar

Columns

Column headers follow your company’s configured field labels. By default the list shows Submission Number (always pinned as the first column), Submission Name, Status, Type, Last Updated, and Created. Edit Columns can add any other configured submission field, plus the system columns Created, Last Updated, Created By, and Updated By.
  • Sorting — click a column header to sort (the default sort is Last Updated, newest first); see Sorting for how each kind of column orders.
  • Filters — Add Filters shows the filters configured for the Submissions list, with inputs chosen by each definition (text, dates, numbers, option choices, or users). Active filters show as pills you can edit or remove.
  • Pagination — the footer pages through results at 25, 50, 100, or 200 rows per page.

Submission statuses

Every submission carries a status. The status keys are fixed by the platform; the labels shown in the app are configurable per company. The defaults: The status is system-managed, so no page lets you pick it. The platform seeds In Progress when the submission is created and recomputes the status whenever a quote on the submission changes. Close Submission and Reopen Submission in the Actions menu are the only direct controls, in the app and through the API.

The submission detail page

The detail page is headed by the submission’s name (falling back to its number), with the Actions menu at the top right and the tab bar beneath.
A submission detail page with the submission name as the heading, an Actions button at the top right, tabs labeled Summary, Files, Loss History, Notes, and Contacts, and the Summary tab showing a details card and a Quotes card.

A submission's detail page: name, Actions menu, and the Summary, Files, Loss History, Notes, and Contacts tabs.

Tabs

The Quotes card

The Summary tab’s Quotes card lists every quote on the submission. Each quote shows its number, a status tag, its Total Amount Due, and its Quote Description, with a View button that opens the quote. New Quote (shown when your role can create quotes) starts another quote on this submission in the quote wizard:
  • If the submission already has a quote that isn’t cancelled, the new quote starts as a copy of the newest one, with the same quote type and the same values filled in. A bound quote can be the one that is copied.
  • Otherwise it starts a fresh new-business quote seeded from the submission’s details.
See Quoting new business for the wizard itself.

Clearance warnings

When a submission’s primary insured name matches another submission in your company (a case-insensitive match, ignoring extra whitespace), a Clearance Warning banner appears at the top of the detail page and links to the potential duplicates so you can compare before proceeding. The status of the other submission does not matter. A closed or bound submission can still count as a match. Renewal submissions and existing endorsement, cancellation, or reinstatement submissions never show clearance warnings or appear as matches. These transactions share an insured with an existing policy. New-business submissions and older submissions without a recognized type still take part.
A yellow warning banner at the top of a submission reading Clearance Warning: This has an existing submission associated with it, with the matching submission's number as a link.

A clearance warning banner linking to the matching submission.

Actions

The Actions menu at the top right of the detail page collects the submission-level actions. Options your role isn’t allowed to perform don’t appear — if none are allowed, the menu itself is hidden.

The menu at a glance

Close a submission

Close Submission opens a two-step dialog. First pick a Close Reason (required) from your company’s Close Reason list and, if you want, add an Explanation. Then confirm. The confirmation states how many open quotes the close will cancel. On confirm, the platform cancels every open quote on the submission (In Progress or Quote Complete), stores the reason and explanation on the submission, and sets the status to Closed. The option is disabled while the submission has a bound quote (the menu shows “A submission with a bound quote cannot be closed.”). A bound quote makes the submission Bound to Policy, and that status outranks Closed.
Closing is reversible. Reopen Submission, or a new quote saved on the submission, reopens it. The quotes cancelled by the close stay cancelled.

Reopen a submission

On a Closed submission, Reopen Submission takes the place of Close Submission in the menu. It asks for confirmation, then recomputes the status from the submission’s quotes. Because a bound quote blocks closing, a reopened submission normally returns to In Progress. The Close Reason and Explanation stay on the submission as the record of the earlier close. A new quote saved on a Closed submission, from New Quote on the Quotes card or through the API, also reopens it, with no confirmation step.

Delete a submission

Delete Submission asks for confirmation, permanently deletes the submission, and returns you to the Submissions list. The option is disabled while the submission still has quotes (the menu shows “Delete every quote on this submission before it can be deleted.”) — delete the quotes first from each quote’s own Actions menu.
Deleting a submission is permanent — there is no undo.

Imports and parse-run history

The Import button on the Submissions list opens the Import page, where dropped documents are parsed by AI into submissions (or policies). The page — available to roles that can upload files — has two parts: a dropzone on top and the Imports table below it.
The Import page with a dashed drag-and-drop area reading Drag files or a folder here, or click to browse, and below it an Imports table with columns Files, Type, Source, Uploaded, Status, and Parsed Result, plus a Show hidden toggle.

The Import page: the dropzone on top, and the Imports table listing every import with its type, source, status, and parsed result.

Uploading files

Drag files (or a whole folder) onto the dropzone, or click it to browse. As soon as you drop, a dialog asks what you’re importing — Submission or Policy — listing every dropped file so you can see exactly what the choice covers. Cancel abandons the drop; choosing a type uploads the files and adds one row to the Imports table (one row per drop, however many files it contained). Accepted file types are the ones the parser can read: PDF, PNG, JPEG, WebP, plain text, CSV, and Excel (.xls/.xlsx), up to 2 GB per file. Unsupported or oversized files are rejected up front — before anything uploads — with a message naming the file. During import, a legacy .xls workbook over 10 MB fails parsing with a message naming the workbook; split or reduce it and try again.
Uploading and parsing are separate steps. The upload only stores the files (they land in a dated import folder you can also reach in your company files); nothing is parsed until you run the import.

The Imports table

One row per import, newest first — including imports from previous sessions and imports that arrived by email: Trailing actions on each row:

Run statuses

Each parse run moves through these statuses: The table refreshes automatically every few seconds while any run is live.

Run history

The history icon on any row opens Run history — every parse run of that import, newest first:
The Run history dialog for an import, showing a table of parse runs with columns Status, Type, Started, Finished, Extract, and Parsed Result, a View extract link on a run, and a replay icon that opens Re-run from Extract and Re-run from Start options.

The run history dialog: one row per parse run, with status, timings, the extract, the parsed result, and the re-run menu.

A failed run’s error message appears in full directly under its row.

Re-running an import

The replay icon on a finished (succeeded or failed) run opens two choices:
  • Re-run from Extract — re-parses using that run’s already-extracted data, skipping re-reading the documents. Available once the run’s extract succeeded.
  • Re-run from Start — re-extracts the documents and re-parses from scratch. Always available.
A re-run never replaces or cleans up what earlier runs of the import saved. The confirmation before it starts says whether to expect duplicates:
  • Re-run from Start creates a new submission and quote, so if an earlier run’s records still exist, you’ll have duplicates you may need to delete.
  • Re-run from Extract usually gets back the records already saved from that extract instead of creating new ones. It creates new ones only if the parser or your company’s configuration has changed since.
  • A failed submission or policy import saves nothing, so it leaves nothing of its own to duplicate.

Email imports

Depending on how your company is configured, brokers can email applications straight to a company inbox — each such email becomes an import row with an Email source chip, and its first parse run starts automatically (the row shows Starting… with no action needed). See Creating submissions for the email workflow. An email from a sender your company hasn’t recognized is stored but not processed: the row shows a warning chip and a Needs sender review status. Users who can manage company settings get two actions on the row:
  • Recognize sender — adds the sender to your company’s allowed senders; their stored imports become runnable and future emails from them are processed automatically.
  • Block sender — future emails from the address are dropped entirely (not stored, not shown, nobody notified). The stored import stays visible — hide it separately if you want it gone. Blocked senders can be unblocked later from your company’s inbox settings — see Company settings & inboxes.
Both choices ask for confirmation, since they set company-wide policy.