
A quote in the app — its details and coverages, with actions to jump back to the submission or to the bound policy.
Working in the app? See the Quotes feature reference for the list view, detail tabs, statuses, and actions.
How its data works
A quote is a set of fields configured per company. The platform requires a handful — a system-assigned quote number, a status, and the primary insured’s name — and your configuration defines the rest, including the coverage structure and any custom fields. A quote’s status starts in progress and moves through your configured workflow. Pricing produces a rating result that’s stored on the quote. The quote also holds the proposed policy term (start and end dates), which carry over if the quote binds.What it connects to
The quote sits in the middle of the chain: Submission → Quote → Policy.
A quote and its submission are created together. In the app, the Create
Submission button opens a new quote, and saving it creates the parent submission
and this quote in one step — so a quote created this way always has a submission.
(Use New Quote to add further quotes to an existing submission.) That pairing
is the norm, but it isn’t strictly enforced: at the data-model / API level the
submission link is optional, and can even be changed later. See
Submission for the other side of this flow.
Files, Notes & Contacts
In the app, a quote has a Notes tab only (no Files or Contacts tabs). Note that the API is broader than the in-app tabs — see the overview.Technical reference
Technical reference
API. Managed through the unified entity CRUD surface as
quote. See the
Entities API overview.Framework-required fields.Additional fields are configured per company; discover them via the
/entities/quote/configuration endpoint.