Daily operations

From submission to bound policy

The statuses a submission moves through, who can do what at each step, and what the platform generates automatically at binding.

Updated 30 October 2026 · Written and reviewed by the Soldek team

A submission is one risk on one product: the answers, the sum insured or package, the broker or client it came from, and everything the engine and your team did with it.

Statuses

New
Received from a broker, the quote page, the API or your own team. Not yet rated.
Under review
Rated and referred by the rules, or picked up by an underwriter. The referral reasons are shown.
Quoted
A premium is offered; the quote document is generated and the broker or client can accept. Every quote carries a 'valid until' date — your default validity period from Settings → Numbering & invoicing, or a date the underwriter picks.
Bound
Accepted and bound. A policy exists.
Declined / Expired
Declined by a rule or an underwriter, or the quote's validity date passed (the platform marks it expired overnight; it can no longer be accepted, re-quote instead).

Quoting: one figure or several options

When you issue a quote you can offer a single premium, or several priced options on the same quote — three sums insured, a basic and an extended variant, a deductible ladder. Each option has a label, its sum insured, its premium (typed, or suggested by the rating engine for that sum) and a line on what differs; one can be marked recommended. The quote PDF on your letterhead lists the options side by side, the e-mail does the same, and the broker or client picks one when accepting. The chosen option's figures become the policy, the invoice and the bordereau line — the database refuses any figure that was not quoted.

Your own team can enter a submission for a client directly (no broker): choose or create the client, answer the product's questions and quote. The client receives the quote by e-mail with an accept link if an e-mail address is on file; otherwise download the PDF or send it from the submission once the client has agreed, and bind it there.

Yearly or in instalments

A product says how its premium can be paid — yearly, every six months, quarterly or monthly — and what paying in instalments costs extra (Products → Pricing → Payment frequency; new products are yearly only). When a product offers more than one, the applicant picks on the application (quote page, broker portal, your own intake), the underwriter sees that choice and confirms or changes it on the quote, and whoever accepts the quote confirms it once more. The premium stays the premium for the term — rating, commission and the bordereau never change; the choice only decides how the invoice run splits it, and the surcharge appears as its own invoice line. The quote PDF and the e-mail state the schedule.

What happens at binding

  • A policy is created with the next number in your own series (prefix, year, sequence — Settings → Numbering & invoicing), its period and status Active.
  • The policy schedule PDF is generated with your letterhead and the wording attached.
  • An invoice is created from the policy: premium plus insurance premium tax, your policy fee and your payment term as set in Settings → Numbering & invoicing (a product can carry its own tax rate), with the broker commission recorded. Paying in instalments gives one invoice per instalment, spread over the term, with the surcharge as a separate line. Sending it is one click, or automatic on bind if you switch that on.
  • The broker (or client) receives the documents by e-mail; everything is in their portal too.
  • The policy is counted against the binder it was written under and appears in the next bordereau.
  • If the product carries conditions at bind (a medical declaration, a survey, a document), the policy starts provisionally: each condition gets its own deadline and the provisional terms are printed on the schedule. See 'Bound subject to' below.

Bound subject to: conditions with a deadline

Some lines cannot wait for every document before cover starts — a health declaration still to be assessed, a survey still to be done, a signed statement still to arrive. A product can declare such conditions once (Products → Rules → Conditions at bind): what has to come in, how many days after binding it is due, the terms that apply in the meantime (for medical underwriting typically: pre-existing conditions excluded until assessed), what happens when the deadline passes, and when the reminder goes out. A condition can be per policy or per insured person on the schedule.

At binding
The policy is active from day one, marked provisional. The conditions and their deadlines are created automatically, the provisional terms are on the policy schedule, in the bind e-mail and in the broker and policyholder portals under 'Still needed'.
Reminder
The platform mails the broker (or the policyholder) a set number of days before the deadline; the policy shows a counter for what is open, due soon or overdue. When the condition is collected online, the reminder to the policyholder carries the questionnaire link again.
Collected online
Instead of a paper form, a condition can carry a questionnaire you define on the product (the questions, an introduction, whether it goes out at bind). The client receives a personal link - no account needed, forwardable to their physician - and the answers land on the condition as 'received', readable by your underwriting team only: never by brokers, never in the client portal, never by e-mail. The link works once and stops at the deadline; sending it again from the policy (to the client, or to the physician's address if the client asks) invalidates the earlier one. The medical preset comes with a generic health questionnaire you edit word for word.
Received
When the form or report arrives, mark the condition received and attach the file in the same step — it is filed under the client's Documents and linked to the condition. A broker can send it from the portal; it then waits for your team to confirm receipt. The deadline can be moved when more time is agreed.
Decision
The underwriter decides: accepted (provisional terms lifted), accepted with terms (a specific exclusion or loading), not accepted (keep the provisional terms permanently, or cancel the policy with pro-rata return premium) or waived. Every decision is applied as an endorsement — the policy document is reissued, a loading becomes a pro-rata invoice, and the broker or policyholder receives the outcome by e-mail.
Deadline passed
What the product set: back on your to-do as overdue, the provisional terms made permanent, or the policy cancelled — always as an endorsement or a cancellation in the trail, never silently.

See it running.

Book a demo and we show you the complete platform live. Still stuck? Write to hello@soldek.io.