Engineering Blog · Post #35

Managing Corporate Clearance Rules from the Platform UI: No Code Changes Required

How an underwriting manager at Atlantic Mutual disables the LOB-001 moratorium rule for Property LOB after market conditions change — from the Platform Features > Clearance Rules tab, with a single toggle click — and the change takes effect immediately on the next clearance run, without a code deployment, a Jira ticket, or a conversation with IT.

The Problem

Corporate clearance rules change. Markets shift. Moratoriums are lifted. Regulatory requirements evolve. New LOBs are added. Thresholds need adjustment. And in most organizations, every one of these changes requires:

A change request to IT. The underwriting manager emails the development team: "We need to turn off the Florida Property moratorium." The request enters a backlog.
A code change. A developer modifies a configuration file or a database record. The change is tested in a staging environment. A pull request is reviewed.
A deployment. The change is deployed to production during the next release window — which might be next week, or next month.
No visibility into current state. The underwriting manager cannot see which rules are active, what their thresholds are, or which LOBs they apply to. They know what they asked for. They do not know what is actually configured.

The result: a 4-week lag between a business decision and its implementation in the clearance system. During that lag, submissions are being incorrectly blocked by outdated rules, or worse, passing through rules that should be active but are not.

The InsightUW Approach

InsightUW provides a Clearance Rules Administration UI under Platform Features > Clearance Rules. This interface displays all 11 clearance rules in a table with their code, name, type (color-coded badges), severity, failure action, required role for override, configurable threshold, and active status. Underwriting managers can toggle rules on and off, adjust parameters, and scope rules to specific LOBs — all from the browser, with changes taking effect on the next clearance run.

graph TB subgraph AdminUI["Platform Features > Clearance Rules"] A["Rules Table 11 Rules Displayed"] B["Type Badges (Sanctions, Duplicate, LOB, Premium, etc.)"] C["Active/Inactive Toggle Per Rule"] end subgraph Config["Rule Configuration"] D["Severity Setting (Block / Warning / Info)"] E["Failure Action (Block Clearance / Flag for Review / Log Only)"] F["Threshold Parameters (Json Configuration)"] G["LOB Scope (All LOBs or Specific)"] H["Required Role for Override"] end subgraph Actions["Admin Actions"] I["Toggle Rule Active/Inactive"] J["Edit Parameters (Threshold, Scope)"] K["Seed Default Rules (Initial Setup)"] end subgraph Effect["Immediate Effect"] L["Next Clearance Run Uses Updated Rules"] M["Audit Entry Created: rule configuration changed"] N["No Code Deployment Required"] end subgraph LOBScope["LOB-Scoped Rules"] O["LOB-001 for Property: Inactive"] P["LOB-001 for Casualty: Active"] Q["Same Rule, Different Behavior per LOB"] end A --> B A --> C C --> I A --> D A --> E A --> F A --> G A --> H D --> J E --> J F --> J G --> J H --> J I --> L I --> M J --> L J --> M K --> A L --> N G --> O G --> P O --> Q P --> Q

The Rules Table

The Clearance Rules tab displays a table with the following columns:

Code	Name	Type	Severity	Failure Action	Required Role	Threshold	Active
SAN-001	OFAC Sanctions Screening	`SANCTIONS`	BLOCK	Block Clearance	COMPLIANCE_OFFICER	Match score >= 90%	Active
DUP-001	Duplicate Insured Detection	`DUPLICATE`	WARNING	Flag for Review	CLEARANCE_MANAGER	Similarity >= 85%	Active
BRK-001	Broker Conflict Detection	`BROKER`	BLOCK	Block Clearance	CLEARANCE_MANAGER	Triggered by DUP-001 match	Active
LOB-001	LOB Moratorium Check	`LOB`	BLOCK	Block Clearance	VP_UNDERWRITING	Per-LOB moratorium list	Active
LIC-001	State Licensing Verification	`LICENSING`	BLOCK	Block Clearance	COMPLIANCE_OFFICER	Licensed in submission state	Active
PRM-001	Minimum Premium Threshold	`PREMIUM`	WARNING	Flag for Review	SENIOR_UNDERWRITER	Premium >= $10,000	Active
TER-001	Coverage Territory Check	`TERRITORY`	WARNING	Flag for Review	SENIOR_UNDERWRITER	Within approved territories	Active
IND-001	Insured Industry Appetite	`INDUSTRY`	WARNING	Flag for Review	SENIOR_UNDERWRITER	SIC code in appetite list	Active
LOS-001	Prior Loss History	`LOSS`	INFO	Log Only	UNDERWRITER	No claims in prior period	Active
REI-001	Reinsurance Treaty Compliance	`REINSURANCE`	BLOCK	Block Clearance	VP_UNDERWRITING	Within treaty capacity	Active
AGG-001	Aggregate Exposure Limit	`AGGREGATE`	WARNING	Flag for Review	VP_UNDERWRITING	Within LOB aggregate	Active

Type Badges

Each rule type is displayed with a color-coded badge for quick visual identification:

Type	Badge Color	Rules
SANCTIONS	Red	SAN-001
DUPLICATE	Orange	DUP-001
BROKER	Pink	BRK-001
LOB	Blue	LOB-001
LICENSING	Purple	LIC-001
PREMIUM	Green	PRM-001
TERRITORY	Teal	TER-001
INDUSTRY	Amber	IND-001
LOSS	Gray	LOS-001
REINSURANCE	Indigo	REI-001
AGGREGATE	Cyan	AGG-001

Toggle: Activate and Deactivate Rules

Each rule has a toggle button in the "Active" column. Clicking the toggle immediately changes the rule's status:

Active → Inactive: The rule is skipped during the next clearance run. Submissions that would have been evaluated against this rule will not be. The rule result will show "SKIPPED — Rule inactive" in the audit trail.
Inactive → Active: The rule is included in the next clearance run. Submissions created while the rule was inactive are not retroactively evaluated (unless a re-run is triggered).

Toggle Confirmation

Toggling a BLOCK-severity rule requires a confirmation dialog:

"You are about to deactivate LOB-001 (LOB Moratorium Check). This rule has BLOCK severity. Submissions that would have been blocked by this rule will no longer be blocked. Are you sure?"

The manager must click "Confirm Deactivate" to proceed. The confirmation is logged as an audit entry.

Configurable Parameters (JSON)

Each rule has configurable parameters stored as JSON. The admin UI provides a structured editor for these parameters — not a raw JSON text box.

Example: PRM-001 Parameters

LOB-Scoped Rules

Rules can be scoped to apply only to specific LOBs. This is configured in the rule's parameters and displayed in the admin UI as a "Scope" column showing either "All LOBs" or a list of specific LOBs.

How LOB Scoping Works

When a submission enters clearance, each rule checks whether it applies to the submission's LOB:

If the rule's scope is "All LOBs" — the rule is evaluated.
If the rule's scope is a specific LOB list — the rule is evaluated only if the submission's LOB matches.
If the rule is inactive for the submission's LOB — the rule result shows "SKIPPED — Not applicable to [LOB]."

This allows carriers to have different clearance behavior per LOB. For example:
- LOB-001 moratorium active for Property but inactive for Casualty
- PRM-001 minimum premium set to $25,000 for Property but $5,000 for Workers Comp
- AGG-001 aggregate limit applies to all LOBs but with different thresholds per LOB

Seed Default Rules

When a new InsightUW instance is deployed, the Clearance Rules tab includes a "Seed Default Rules" button. This button populates the rules table with the standard 11 rules, each configured with sensible defaults:

SAN-001 through AGG-001, all active
Default thresholds (85% for DUP-001, $10,000 for PRM-001, etc.)
Default severity levels (BLOCK for sanctions and licensing, WARNING for duplicates and territory, etc.)
Scope set to "All LOBs"

After seeding, the underwriting manager customizes the rules for their specific carrier requirements. The seed operation is logged as an audit entry and can only be performed once (subsequent clicks show "Rules already seeded").

Audit Trail for Configuration Changes

Every change to a clearance rule is logged as a Audit Entry with action type rule configuration changed:

This audit entry ensures that configuration changes are traceable. If a DOI examiner asks "why was LOB-001 inactive when this Property submission was cleared?" the carrier can produce the configuration change record showing who deactivated it, when, and why.

The Scenario

Jennifer Blake, VP of Underwriting at Atlantic Mutual, manages the Property LOB. In January 2026, she activated a moratorium on new Property submissions in Florida, Texas, and Louisiana during the 2026 CAT season (June through November). It is now April 21, and updated CAT models show improved conditions. She decides to lift the moratorium early.

The Action

Jennifer opens Platform Features > Clearance Rules. She locates LOB-001 (LOB Moratorium Check) in the table. She clicks the row to open the configuration panel and sees the moratorium parameters:

LOB	States	Reason	Effective From	Effective Until	Status
Property	FL, TX, LA	CAT season moratorium	2026-06-01	2026-11-30	Active

She clicks the toggle to deactivate the Property moratorium. The confirmation dialog appears:

"You are about to deactivate the Property LOB moratorium (LOB-001). This rule has BLOCK severity. Property submissions in FL, TX, and LA will no longer be blocked. Are you sure?"

Jennifer clicks "Confirm Deactivate" and enters the reason: "Property moratorium lifted — market conditions improved, CAT models updated for Q2 2026."

The Immediate Effect

The LOB-001 rule for Property LOB is now INACTIVE.
LOB-001 for all other LOBs remains ACTIVE (if any other moratoriums are configured).
The next Property submission from Florida that enters clearance will not be blocked by LOB-001. The rule result will show: "SKIPPED — LOB-001 moratorium inactive for Property LOB (deactivated by Jennifer Blake on 2026-04-21)."
An audit entry is created capturing the change, the actor, and the reason.
No code deployment occurred. No IT ticket was filed. The change took effect in seconds.

The Next Clearance Run

A new Property submission arrives 10 minutes later — a $2.4M commercial property in Miami submitted by Aon. The clearance engine evaluates all 11 rules:

Rule	Result	Note
SAN-001	PASS	No OFAC matches
DUP-001	PASS	No duplicates
BRK-001	PASS	No broker conflict
LOB-001	SKIPPED	Moratorium inactive for Property (deactivated 2026-04-21)
LIC-001	PASS	Licensed in FL
PRM-001	PASS	$2.4M exceeds minimum
TER-001	PASS	FL is approved territory
IND-001	PASS	Commercial real estate in appetite
LOS-001	PASS	No prior property claims
REI-001	PASS	Within treaty capacity
AGG-001	WARNING	FL Property aggregate at 87% of limit — flagged for review

The submission clears (with one warning on AGG-001) and proceeds to underwriting review. Without Jennifer's configuration change, it would have been blocked.

What This Means for Underwriters

Business decisions take effect immediately. When the underwriting manager decides to lift a moratorium, the change is live in seconds. There is no deployment queue, no IT dependency, and no gap between decision and implementation.
The rules table is the source of truth. The manager can see every rule, its status, its threshold, and its LOB scope at a glance. There is no need to ask IT "what's configured in production?"
LOB-scoped rules enable granular control. A moratorium can be active for Property but inactive for Casualty. A minimum premium can be $25,000 for Property and $5,000 for Workers Comp. Each LOB can have the clearance behavior it needs.
Every configuration change is audited. The toggle click, the parameter edit, the LOB scope change — all logged with actor, timestamp, and reason. Configuration changes are as traceable as clearance decisions.
Seed defaults accelerate onboarding. New carrier deployments start with sensible defaults. The underwriting team customizes from there, rather than building from scratch.

What's Next

This post completes the Corporate Clearance series. The five posts in this series have covered duplicate detection and broker conflicts (Blog 31), policy system number integration (Blog 32), the clearance flag and notification workflow (Blog 33), the complete audit trail (Blog 34), and rules administration (Blog 35). Together, they describe a clearance system that is automated, auditable, configurable, and ready for regulatory examination from day one.

Ready to put clearance rule management in the hands of your underwriting team? InsightUW's Clearance Rules admin UI lets managers toggle rules, adjust thresholds, and scope by LOB — no code changes, no IT tickets, no delays.

Schedule a Rules Administration Demo →