Coverage rules

Who this is for

Owners and administrators who want to define validation rules that protect against E&O exposure. Rules control which COI requests get auto-approved, flagged for human review, or blocked outright.

Before you start

You must be an Owner or Manager to create and edit coverage rules. Team members with the Member or Agent role can view the rules list but cannot make changes.

How it works

Anatomy of a rule

Each rule has:

• Name — a plain-language label visible in the rules list (e.g., “Min $1M GL limit”).
• Conditions — one or more predicates comparing a request field to a value (e.g., “Coverage amount is less than 1,000,000”).
• Logic — how multiple conditions are combined: AND (all conditions must be true) or OR (any condition is enough).
• Action — what happens when the conditions match: auto-approve, block, or require agent review.
• Active toggle — whether the rule participates in evaluation. Inactive rules appear in the list but are skipped.

Create a rule

1. Go to Library in the left sidebar and select Coverage rules.
2. Click New rule.
3. Enter a Name.
4. Add one or more Conditions. For each condition, select the field to check, the operator (e.g., less than, equal to, is in), and the comparison value.
5. If you have multiple conditions, set the logic to AND or OR.
6. Choose an Action from the dropdown. If you choose Require agent review, the preset panel shows common review-trigger patterns you can apply in one click.
7. Click Save.

The rule appears in the list in the position you added it.

Edit a rule

Click any rule in the list to open the editor. All fields are editable. Save when done.

Reorder rules (priority)

Rules are evaluated top-to-bottom. The first rule whose conditions match wins; later rules are not checked. Drag a rule up or down in the list to change its priority.

Put more specific rules above broader ones so narrow cases are caught first.

Test a rule

From the rule editor, use the Test panel to enter sample request values and see how the rule responds. The test runs against the live rule definition on the server, so the result matches what would happen on a real request.

Enable or disable a rule

From the rules list, use the active toggle next to any rule to enable or disable it without deleting it. Disabled rules appear in the list with a muted style and are skipped during evaluation.

How rules are enforced

When a COI request is submitted, the rule engine evaluates all active rules in priority order automatically. The outcome — auto-approve, agent review required, or blocked — is stored with the request and surfaces in the agent dashboard as a coverage-gap badge.

The block list is checked first: a requester matched on the block list is rejected before any rule runs.

Block list

The block list lets you prevent specific requesters from ever receiving a COI, regardless of coverage rules.

Entries can match by:

• Email address — exact match on the requester’s email.
• Domain — any requester whose email belongs to the domain (e.g., badactor.com).
• FEIN — the requester’s federal employer identification number (9-digit or XX-XXXXXXX format).
• Contractor name — a substring match on the insured or contractor name.

To add an entry, scroll to the Block List section on the Coverage rules page, click Add entry, fill in the kind and value, and optionally add a reason for your records.

What happens next

• A request that matches a block rule stays blocked and the requesting party cannot resubmit without the rule being changed.
• A request that triggers agent review lands in the agent’s queue for manual inspection. The agent can approve or decline.
• A request that passes all rules (or matches an auto-approve rule) continues automatically.
• Rule edits are written to the audit trail so every change is traceable (Settings → Audit trail).

Troubleshooting

• The Test panel shows a different result than I expected. Double-check the logic setting (AND vs. OR) and the operator on each condition. AND requires every condition to be true; OR requires only one. Also confirm the rule is Active — inactive rules are skipped even in the test panel’s live-endpoint path.
• A rule I created is not being applied at submission. Confirm the rule is toggled Active in the list. Rules are evaluated in priority order — if a higher-priority rule already matched, this one is skipped.
• I cannot see the rules page. Library access for managing rules requires Owner or Manager role. Contact your agency owner to request elevated permissions.

Related

• Your library — overview of all Library sections.

Last verified: 2026-05-22