Proofing controls in the Rules Studio

A practice leader’s standards — “never deliver with an unresolved high-severity difference”, “tell the client in writing when cover narrows” — usually live in a procedures manual. In InsightProofing they are proofing controls in the Rules Studio: readable sentences, run on every check, with their hits counted.

The eight starter controls

Control	Effect	What it says
High-severity failure unresolved	block	Have the carrier correct it, or have a practice leader waive it, before the policy goes to the client.
High-severity failure waived	refer	A practice leader signs off before delivery.
Exclusion never agreed	refer	An exclusion on the policy not on the binder or quote: a practice leader reviews.
Total cost above $250,000	refer	A large account: a practice leader reviews the proofing.
Cover narrowed at renewal	warn	The client delivery summary must say so in plain words.
Premium up more than 25%	warn	Confirm the client approved it in writing.
Not delivered 30 days after inception	warn	Chase the carrier or deliver what is checked.
Correction request overdue	warn	Follow it up.

The thresholds above are the starter values. Each brokerage sets its own.

From a draft to live

flowchart LR D["Draft a change"] --> T["Test against a
real policy check"] T --> I["See what it affects"] I --> P{"Publish?"} P -- yes --> L["Live: runs on every check,
hits counted"] P -- no --> D

The Rules Studio with eight proofing controls — Rules Studio: eight proofing controls, all published, with their hits over 30 days on the illustrative book.

Key facts and the proofing controls that fired on an illustrative check — The side panel: key facts, a control that blocks delivery, a heads-up, and the four documents in the file.

Where a control shows

On the check, the controls panel lists what fired with its effect; a block also shows as a banner under the hero. The supervisor agent prepares the practice leader’s sign-off when a referral fires, and every hit is written to the decision record.