This worked case belongs to the underwriting referral triage guide, which covers what to inventory before a workbench rollout. Its job here is different: walk one hard case in order, show which record each decision left, and end with how an insurance transformation advisor can spot the same pattern at a client.
The case: a warehouse above the line underwriter's limit
Illustrative and invented for this page. A 340-person specialty commercial insurer receives a broker submission for a distribution warehouse. The total insured value is $38M. The line underwriter's authority limit for this class is $25M. The building is partly sprinklered, with the remaining sprinkler work scheduled but not complete.
Two things went wrong at once: the value sat above authority, and the protection was incomplete. Either alone might have been routine. Together they needed a decision nobody on the line desk could make.
Step by step: who decided, and which record it left
| Day | What happened | Who acted | Record it left | Where it usually sits |
|---|---|---|---|---|
| 1 | Workbench rules compare the $38M value with the $25M limit and raise a referral flag | Rules engine | Flag with reason code and timestamp | Underwriting workbench |
| 2 | Line underwriter writes the referral question: accept with partial sprinklers, or decline? | Line underwriter | Referral note with a recommendation | Workbench note, sometimes email |
| 3 | Broker asked for the sprinkler contractor's completion schedule | Line underwriter | Broker email with attachment | Underwriter's mailbox |
| 5 | Senior underwriter approves, subject to sprinkler completion within 90 days of binding and a $40,000 deductible | Senior underwriter | Approval with conditions and approver ID | Workbench approval record |
| 6 | Policy bound with the sprinkler subjectivity listed | Underwriting assistant | Binder and policy schedule | Policy administration, document store |
| 96 | Loss control inspection confirms completion; condition cleared | Loss control | Inspection report and clearing note | Loss control system |
Workbench software formalizes parts of this. In Guidewire PolicyCenter, an underwriting issue is a flag on a job or policy that may need review, and a user who cannot clear it can request approval from someone with greater authority. Approvals can be ordinary or special, and can carry a value limit, an editability setting and a duration. If the sprinkler problem had surfaced mid-term instead, with no job open, it would have been held as a referral reason until it was closed or special closed. Other platforms use different names, and many insurers still run step 3 entirely in email.
Why this sequence is useful evidence
The value is in days 2 to 5 read together with day 96.
- The question (day 2) shows what a capable underwriter was unsure about. That is the judgment a later reviewer, or a model trained on such cases, most needs to see.
- The evidence (day 3) shows what was asked for to resolve the doubt. Without it, the approval appears to rest on nothing.
- The conditions (day 5) show what the senior underwriter traded for accepting the risk: a time-limited protection requirement and a higher deductible.
- The outcome (day 96) shows whether the trade held.
Remove day 96 and the file shows a condition with no known result. Remove day 3 and nobody can say why the senior underwriter felt comfortable. Remove day 2 and the approval looks like a rubber stamp. The general case for this kind of record is made on why AI agents need work data, and the wider family of file notes on the underwriting notes page.
Three variations that change the record
The condition is missed. If the day 96 inspection had found sprinklers incomplete, the next records would be a reminder, an extension or a mid-term action. Those are some of the most informative records an insurer holds, because they show what happens when a condition fails.
The approval is special. A special approval, or one with a short duration, means the insurer treated the case as a one-off. That distinction only survives if the approval type was kept.
The referral happens in email. Many referrals never touch the workbench. Then days 2 and 5 live in mailboxes, and their survival depends on the insurer's retention policy. The system map covers which keys join email to the policy.
How to recognize similar cases at a client
An advisor can tell from conversation, without opening a file, whether a client holds cases like this. Listen for:
- An authority grid. Named limits by underwriter grade and class, changed over the years.
- Conditional approvals. Subjectivities, warranties or deductible changes attached to approvals, with due dates.
- Condition tracking. Someone, often loss control or an underwriting assistant, who records when conditions clear.
- A chief underwriting officer review. A share of referrals that went all the way up.
- Years of history. Six or more years of referrals still linked from flag to outcome.
A managing general agent may not own its referral files outright; MGA data ownership explains why the delegated authority agreement matters. A similar decision trail in lending appears in the credit memo underwriting example. The who can say yes decision tree covers whom to introduce.
Qualification and what stays unknown
The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the data is in English.
Partners sign the Channel Partner Agreement before submitting introductions; the first valid introduction within the 90-day window is credited when the company submits a verified application. Discovery stays at metadata level: record classes, years, volumes, systems and owners. Buyer interest, what rights review concludes about policyholder, broker and carrier data, what must be de-identified, and any offer stay unknown until SourceX reviews the opportunity.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If a client insurer can show referrals that still run from flag to cleared condition, register as a partner, check the insurer against who qualifies, and read the program terms before introducing its leadership.