Engineering Blog · Post #32

Cross-System Traceability: How InsightUW Links Policy System Submission Numbers to Corporate Clearance

How a Workers Compensation submission registered in the policy admin system as PAS-SUB-2026-05102 flows through InsightUW's clearance engine — with the policy system number visible in the submission list, detail header, clearance rationale, attestation text, and audit trail — so that every clearance decision is traceable back to the authoritative system of record.

The Problem

Insurance carriers operate multiple systems. The submission intake platform is not the policy administration system. The policy admin system is not the clearance system. And the clearance system is not the audit system. In practice, this means:

Submissions exist in two places without a link. A broker submits an application through InsightUW. The operations team registers the same submission in the policy admin system (or policy admin system, or policy admin system) to obtain a policy system submission number. These two records — one in InsightUW, one in the policy admin system — are not connected. The underwriter toggles between screens, matching records by insured name and date.
Clearance decisions cannot reference the policy system record. When the clearance analyst approves a submission, the clearance record says "SUB-GL-2026-0891 cleared." It does not say "PAS-SUB-2026-05102 cleared." Regulators and auditors care about the policy system number, not the intake platform's internal GUID.
Audit trails are fragmented. The DOI examiner asks: "Show me the clearance record for policy PAS-SUB-2026-05102." The carrier must first map the policy admin system number to the InsightUW GUID, then pull the clearance record, then manually correlate the two. This takes hours and introduces error.
Notifications lack context. When the clearance flag is set, the notification to the underwriter says "submission cleared." It does not include the policy system number that the underwriter needs to proceed in the policy admin system.

The result: a traceability gap between the intake platform and the policy administration system that makes every clearance decision harder to find, harder to verify, and harder to defend.

The InsightUW Approach

InsightUW provides a Policy System Number Registration API that links the policy administration system's submission number to the InsightUW submission record. Once registered, the policy system number appears everywhere the submission appears — in the list view, the detail header, the clearance rationale, the attestation text, and every audit trail entry.

graph TB subgraph Policy Systems["Policy Administration Systems"] A["policy admin system PAS-SUB-*"] B["policy admin system MJS-*"] C["policy admin system GW-SUB-*"] end subgraph Registration["Registration API"] D["Post /policy-system-number/{guid} {system, number, registered by}"] E["Validate Number Format (PAS-SUB-*, MJS-*, GW-SUB-*)"] F["Link to Submission Record"] end subgraph Notification["Auto-Notification"] G["Notify Assigned UW 'Policy system number registered'"] H["Notify Clearance Team 'Number available for clearance'"] end subgraph Visibility["Number Visibility"] I["Submission List View (Policy # column)"] J["Detail Page Header (Badge with system icon)"] K["Clearance Rationale (Referenced in rule results)"] L["Attestation Text (Included in acknowledgment)"] M["Audit Trail (Every entry includes #)"] end subgraph Audit["Cross-System Query"] N["GET /submissions?policy system number=PAS-SUB-2026-05102"] O["Returns: Submission + Clearance + Audit in single response"] end A --> D B --> D C --> D D --> E E --> F F --> G F --> H F --> I F --> J F --> K F --> L F --> M N --> O

The Registration API

The policy system number is registered via a single API call. This can be triggered manually by an operations user, automatically by the policy admin system via webhook, or through a batch integration.

Request Body

Supported Policy System Number Formats

System	Format	Pattern	Example
policy admin system	PAS-SUB-YYYY-NNNNN	`^PAS-SUB-\d{4}-\d{5}$`	PAS-SUB-2026-05102
policy admin system	MJS-NNNNNNN	`^MJS-\d{7}$`	MJS-4821093
policy admin system	GW-SUB-YYYY-NNNNNN	`^GW-SUB-\d{4}-\d{6}$`	GW-SUB-2026-041882

The API validates the number format against the declared system. Invalid formats are rejected with a 422 response and a descriptive error message.

Where the Policy System Number Appears

Once registered, the policy system number is embedded in every surface where the submission is referenced.

Submission List View

The submission list includes a "Policy #" column. Submissions without a registered number show a muted "Pending" badge. Submissions with a number show the formatted number with a system icon (policy admin system shield, policy admin system star, policy admin system arrow).

Submission	Insured	LOB	Broker	Policy #	Status
SUB-WC-2026-1204	Ironclad Manufacturing	Workers Comp	Willis	PAS-SUB-2026-05102	Clearance Pending
SUB-GL-2026-0891	Bluefin Dining	GL	Marsh	PAS-SUB-2026-04471	Cleared
SUB-PL-2026-0933	TechVault Solutions	Prof Liability	Aon	Pending	Clearance Pending

Detail Page Header

The submission detail page displays the policy system number as a prominent badge in the header, directly below the insured name. The badge includes the system name, the number, and the registration timestamp.

Clearance Rationale

Every clearance rule result includes the policy system number in its rationale text:

"OFAC screening completed for submission SUB-WC-2026-1204 (policy admin system: PAS-SUB-2026-05102). Insured 'Ironclad Manufacturing' checked against SDN list — no matches found. Clearance rule SAN-001 PASSED."

Attestation Text

When the underwriter acknowledges clearance, the attestation includes the policy system number:

"I, Sarah Martinez, acknowledge that I have reviewed the corporate clearance results for submission SUB-WC-2026-1204 (policy admin system: PAS-SUB-2026-05102), insured Ironclad Manufacturing. I confirm that all clearance rules have passed or that flagged issues have been reviewed and resolved."

Audit Trail

Every Audit Entry created after the policy system number is registered includes the number in its metadata:

Auto-Notification on Registration

When a policy system number is registered, InsightUW sends automatic notifications to two audiences:

The assigned underwriter receives a notification: "Policy system number PAS-SUB-2026-05102 has been registered for your submission SUB-WC-2026-1204 (Ironclad Manufacturing, Workers Comp). The number is now visible in clearance and throughout the submission record."
The clearance team receives a notification: "Policy system number registered for SUB-WC-2026-1204. Clearance rationale and attestation text will now reference PAS-SUB-2026-05102."

These notifications are logged as Audit Entry records with action type policy system number notification sent.

The Scenario

Sarah Martinez, a Workers Comp underwriter at Atlantic Mutual, has a new submission for Ironclad Manufacturing — a steel fabrication company with 340 employees seeking $1M/$1M WC coverage. The submission was created in InsightUW three days ago. Today, the operations team registers it in the policy admin system.

The Registration Event

The operations coordinator opens the submission in InsightUW and clicks "Register Policy System Number." They select "Policy System A" from the system dropdown and enter PAS-SUB-2026-05102. The API validates the format, links the number, and fires notifications.

What Sarah Sees

Sarah receives a notification on her dashboard: "Policy system number registered — PAS-SUB-2026-05102." She opens the submission and sees:

Header badge: "policy admin system: PAS-SUB-2026-05102" displayed next to the submission GUID
Clearance panel: The clearance rationale for each of the 11 rules now references the policy admin system number
Attestation preview: The acknowledgment text she will sign after clearance includes the policy admin system number

What the DOI Examiner Sees (18 Months Later)

The DOI examiner queries: "Show me the clearance record for policy admin system submission PAS-SUB-2026-05102."

The carrier runs:
The response returns the complete submission record, all 11 clearance rule results, the attestation, and the full audit trail — all cross-referenced to PAS-SUB-2026-05102. The examiner has everything they need in a single API call.

What This Means for Underwriters

One number, everywhere. The policy system number is not buried in a notes field. It is displayed in the list view, the detail header, every clearance rationale, the attestation text, and every audit entry. The underwriter never has to search for it.
Cross-system queries work instantly. When someone asks "what happened with PAS-SUB-2026-05102?" the answer is one API call away. No manual mapping between systems.
Notifications include context. The registration notification includes the policy system number, so the underwriter can immediately proceed in the policy admin system without looking it up.
Clearance is defensible. The attestation text explicitly references the policy system number. When a regulator asks "did the underwriter acknowledge clearance for this policy admin system submission?" the answer is in the signed attestation.
Multi-system support is built in. policy admin systems formats are all supported. Carriers running multiple policy admin systems across LOBs can register numbers from any system.

What's Next

In the next post, we will explore how the clearance flag works — the moment when InsightUW signals that a submission has passed all clearance rules and is authorized to proceed to underwriting review, triggering notifications to the underwriter and the Underwriting Assistant team.

Ready to close the traceability gap between your intake platform and your policy admin system? InsightUW's policy system number registration ensures every clearance decision references the authoritative record — policy admin systems.

Schedule a Cross-System Traceability Demo →