Regulatory compliance check at bind

A bind-time regulatory compliance check returns pass, hold, or empty. A pass cites the jurisdiction rule, the rate filing, or the form checklist the risk satisfies. A hold cites the same sources and states the mismatch. Empty means the rule file for that jurisdiction, product, or surplus-lines path was not loaded. Empty is not a pass. Do not invent a filing identifier. Do not invent a surplus-lines stamp. Compliance still signs off. This check does not bind the policy.

Write the quality outcome as status plus citation fields. If the file is missing, leave those fields blank and route the pack for file retrieval.

This check does not replace bind condition completeness validation. Completeness asks whether subjectivities, inspections, and premium conditions are present. This page asks whether the jurisdiction will accept the placement on admitted or surplus-lines terms, with the filings and forms the rule file names.

Do not score until the rule file is in memory. The file is the source of truth for admitted states and territories, lines that require surplus-lines placement, rate filings and form editions tied to product and effective date, and checklists such as diligent search, surplus-lines tax, cancellation notices, and state-specific endorsements.

Take identifiers from the quote and the policy-admin record: location of risk, the current admitted versus surplus-lines flag, product code, effective date, and class or occupancy. Match those to a versioned rule file. If the match fails, stop. Do not fall back to a neighboring state's file, last year's filing, or a model that usually applies this form.

Policy administration platforms such as Guidewire or Duck Creek, forms and statistical libraries such as Verisk, and account records in Salesforce often store fragments of the bind pack. Treat them as systems of record for the quote, the account, and published form or filing identifiers. None of them is the compliance decision. If two systems disagree on admitted status, record a hold. Do not let the model break the tie.

Load in this order so a reviewer can replay the check:

1. Resolve jurisdiction from the location of risk, not from the producer's license state, unless the rule file says otherwise.
2. Confirm whether the program is filed as admitted in that jurisdiction for this product and effective date.
3. If it is not admitted, load the surplus-lines path: eligibility, tax, stamping if the jurisdiction uses a stamping office, and the affidavit or diligent-search checklist the file lists.
4. Load the rate-filing identifiers and the form checklist attached to that path, including editions and mandatory endorsements.
5. If any load returns no file, write empty on the citation fields and send the pack to compliance. Do not classify against a missing file.

Machine learning can help classify occupancy, match a class to a filing footnote, or flag a form name that looks like a required edition. It cannot stand in for the file.

Once the file is loaded, run checks a reviewer can audit without opening a chat log.

Jurisdiction. Confirm the location of risk maps to a rule the file contains. A pass cites the jurisdiction identifier and the rule version. A hold cites the same and states the mismatch: wrong state, extra-territorial exposure the file does not cover, or a location the program excludes.

Admitted versus surplus lines. Compare the quote's placement to the file. If the file lists the carrier as admitted for this line, a surplus-lines placement is a hold unless the file also describes a lawful surplus path. If the file lists the line as non-admitted only, an admitted bind is a hold. Cite the admitted-status table or bulletin in the rule file, not a model score.

Rate filings. Match product, class, and effective date to a filing identifier the file contains. A pass cites that identifier. A hold cites the closest filing the file does list and states why this risk sits outside it: class not on the filing, effective date outside the approved period, or a rating plan the file does not authorize. A pass with no filing cite is a defect in the check, not a quality outcome.

Required forms. Walk the checklist: policy jacket, mandatory state endorsements, notices, surplus-lines legend if that path applies, and any jurisdiction-specific cancellation or fraud language the file names. A pass lists form IDs and editions. A hold lists missing or wrong-edition items. Do not assemble or issue documents here. Later work on automated policy document assembly and issuance accuracy verification still has to match these IDs.

Illustrative example. A general liability quote for a contractor with operations in a state where the carrier is not admitted for that class. The surplus-lines rule file lists a diligent-search affidavit, a surplus-lines tax worksheet, and a specific legend on the declarations. The admitted filing on the same product does not include that class. If the quote is marked admitted, output hold, citing the admitted-status table and the filing's class list. If the producer has already marked surplus lines and every listed item is present with matching editions, output pass with those cites. If the surplus rule file for that state is not loaded, citation fields stay empty and the pack goes to compliance with no stamp.

A missing rule file, missing filing row, or missing form checklist means blank citation fields. Do not copy a filing from a sibling product. Do not reuse last term's surplus-lines stamp. Do not let the model generate a likely filing number so the policy-admin system can store a value.

Empty means the check could not ground its answer. Route empty packs like holds, except the reviewer starts by fetching or versioning the file rather than by amending the risk. After the file is loaded, re-run the check. Do not convert empty to pass on a producer note that this is how the class is always placed.

If premium or terms may have moved while the file was being fetched, run stale-quote repricing lock before anyone treats the pack as ready to bind. A compliance pass on yesterday's terms is not a pass on today's.

Three failures show up as ready in a queue and are not.

A pass with no filing cite. A workflow required a boolean. The boolean is green and the filing field is blank. Treat that result as empty or hold. A pass that cannot point to a filing, a jurisdiction rule, or a form checklist is not a quality outcome.

Treating pass as bound. The check returned a cited pass. An operations user, or an automation watching the same flag, issued the binder, booked premium, or notified the insured. The quality outcome is permission to continue the path. Compliance still signs. Until that sign-off, the policy is not bound. If the policy-admin system can bind on a workflow flag, keep this check's pass off that flag.

Inventing a surplus-lines stamp. The model or a user filled a stamping-office number, an eligibility legend, or a non-admitted-OK flag because the admitted path failed. If the surplus rule file did not supply that stamp or legend, the field stays empty and the result is hold or empty. A fabricated stamp is worse than a slow hold: it can travel into customer documents and look like a real placement at issuance.

Also reject producer-license state in place of location of risk, admitted editions on a surplus-lines declarations page, and a forms-library match that disagrees with the rule file's edition for the effective date.

Send compliance the pass or hold, every citation (rule version, filing ID, form checklist IDs), a clear empty marker if the file was missing, and the quote identifiers from the policy-admin and CRM records. Compliance signs or returns the pack with the fields that must be fixed. Bind-ops do not auto-bind on pass.

After sign-off, completeness, document assembly, and issuance checks still apply.