Bind condition completeness validation

A ready-to-bind flag is valid only when every required condition on the quote is listed with the evidence that satisfied it. If a condition has no evidence, that row stays empty. The flag does not bind the policy. Bind ops still binds.

Pricing is already on the quote. What remains are signatures, deductibles, warranties, subjectivities, and approvals the quote made prerequisites to bind. An agent can assemble and cite that list. It cannot close a gap by inferring what the broker must have meant.

Keep the flag as a reading of the file. Bound is a transaction recorded in Guidewire, Duck Creek, Salesforce, or Applied Epic. Do not treat a complete checklist as an in-force policy, and do not write bind state from this step. Once every row is actually cited, field population is a separate path: bind instruction extraction and system population.

If the quote may have aged past the priced terms, stop. Run stale-quote repricing lock before you treat any condition as still current.

Start from the quoted terms that will bind. Pull the condition set as written: named insured and additional-insured signatures, deductible restatements by coverage part, warranty wording, outstanding subjectivities, and any underwriter, referral, or compliance approval required before bind.

The same items may already sit in the policy administration system as outstanding requirements. Load from the quote, then confirm the system list is the same version, not a leftover from a prior quotation. If the lists disagree, stop so a human can reconcile them.

Build one working row per condition and copy the source wording. Do not merge two subjectivities because they arrived in one email. Do not add conditions that are not on this quote. Do not drop a condition because it looks minor.

Only then gather candidate evidence: the signed quotation or proposal, broker attachments, warranty acknowledgement pages, deductible schedules, underwriting-file approval notes, and any document the quote named as clearing a subjectivity. Evidence-first review creates false completeness. A signed packet can still miss a required warranty initial. If the inbox disagrees with the quote, the quote wins.

Each passed row needs two cites: the condition as written on the quote, and the artifact that satisfies it. A green check without a document, page, signatory, or date is a fail. Empty stays empty. A blank required row means the flag stays down.

Signatures. Cite the document, the signatory role, and the date on the page. A broker email that the insured has agreed is not a signature. A signature from a prior quotation version is not a signature on this quote. If both insured and additional-insured signatures are required, each needs its own cite.

Deductibles. Cite the deductible that will bind. A prior-year declaration, a marketing one-pager that omits it, or a specimen that does not match this quote does not pass. If the quote split deductibles by coverage part, each part needs its own cite.

Warranties. Cite the warranty text and the acknowledgement page. A cover email that warranties are agreed is not acknowledgement. Three warranties on the quote means three cites or three blanks, not one bundled pass.

Subjectivities. Clearance requires the artifact the quote asked for. A broker note that loss runs, a survey, or an engineering report are coming, or should be fine, leaves the row empty. Open items go to outstanding subjectivity tracking and chasing. Do not write cleared because the rest of the file looks clean.

Approvals. Point at a named approver and a dated note or system status in the underwriting file. A chat fragment that an underwriter said it is fine is not an approval unless your bind playbook already treats that channel as the system of record.

License, surplus-lines, and admitted versus non-admitted checks sit beside this commercial list. Keep them on regulatory compliance check at bind.

A mid-market property quote is priced and the broker has sent a bind request. The file has a signed quote letter, a deductible schedule that matches the quote, a warranty acknowledgement initialed on the last page, and a dated underwriter approval to bind subject to the quoted conditions. The quote also required a completed sprinkler-impairment form before bind. That form is not in the file.

The agent loads five rows from the quote: insured signature, deductible restatement, warranty acknowledgement, sprinkler-impairment subjectivity, and underwriter bind approval. It cites the signed letter, the matching schedule, the initialed warranty page, and the dated approval note. The sprinkler row has no artifact, so it stays empty. Ready-to-bind is not raised. Bind ops sees four cites and one blank and does not bind.

Raising ready because four of five rows were green would put coverage out with an open subjectivity. Filling the blank with a broker confirmation that sprinklers are satisfactory would invent a clearance. Both are refusals. The blank is the correct output.

The agent's job ends when every required row is cited or the incomplete rows are visible. Bind ops still binds: they select the transaction, confirm effective date and named insured, and take the bind action in the policy administration system.

Do not auto-bind when the last empty row later fills. A complete, cited checklist is a signal that bind ops may proceed. It is not a trigger that creates a policy number, a binder number, or an in-force status.

Until bind ops acts, bind fields stay as they were. Empty stays empty. Do not stamp bound, do not mint a binder reference, and do not push a ready flag into a status that downstream jobs treat as coverage on risk. That holds in Guidewire, Duck Creek, Salesforce, and Applied Epic: this validation does not own bind state.

Keep this step read-only with respect to bind.

A ready flag with no evidence cite. The worksheet is green, but there are no document IDs, page numbers, signatory names, or dates. Bind ops cannot reconstruct the pass. Treat an uncited pass as a fail, wipe the flag, and rebuild from the quote.

Treating ready as bound. Someone tells the broker coverage is on risk because the flag flipped. Premium booking starts. A later claim or audit finds no policy. Ready is a file opinion. Bound is a system transaction owned by bind ops.

Inventing a cleared subjectivity. The quote required an engineering report. The file has a broker email that the report should be acceptable. The agent writes cleared and cites the email. That is a new underwriting decision dressed up as validation. Leave the row empty and send the open item to chasing.

When any of those appear, strip the flag, restore blanks, and return the file to bind ops with the incomplete rows visible. The useful output is a cited checklist or an honest set of empty rows, never a bind.