Chapter 13 — Key Takeaways
The underwriting decision: accept, decline, or modify — and how to make it defensible.
The core claims
- The decision resolves into one of three answers: accept, decline, or modify. The craft is not just reaching the answer but making it defensible — grounded in the file, within authority, consistent with the guidelines, and documented.
- Run three gates, in order: appetite → price → terms. Is the company willing to write this kind of risk? Can it be priced adequately? Can terms close the gap? Each gates the next; document the reasoning at each. The sequence is a discipline for thinking, not a flowchart that decides for you.
- Modify is the most common outcome on any account worth thinking about. Pure accept is for clean risks; pure decline is for threshold failures; the interesting accounts get restructured into something writable.
- A decision is judged on its quality, not the luck of its outcome. A sound, documented decision is defensible even when it produces a loss; a whimsical, undocumented one is indefensible even when it gets lucky.
The three answers
- Accept = bind. The binder puts you on risk now, before the policy issues. Never bind outside your authority. Most binds carry conditions — separate the conditions of the policy (ongoing duties) from the subjectivities (conditions precedent to a clean bind).
- Decline = a real decision in three directions. Business (decline the risk, not the broker — fast, respectful, ideally constructive); legal (a risk-based reason only; adverse-action notice if a consumer report drove it; never a protected-class or redlining reason); file (document it so it can never be mistaken for an offer).
- Modify = counter-offer + subjectivities. A counter-offer is, legally, a rejection of the original ask and a new offer. Two levers: repricing (premium for the risk as-is) and restructuring (changing the risk through terms). Subjectivities condition the bind on the risk actually becoming the version you'll insure — each needs an owner, a deadline, and a tracked status.
The rule of thumb
The decision is not the work; the documented, communicated decision is the work. Reconstruction test: could a stranger reconstruct the decision — and your reasoning — from the file alone? If yes, the file defends itself. The most-neglected element is the rationale (the why) — write it contemporaneously, before you communicate the decision.
More eyes, more authority
- Referral — moves a decision up to the authority that can make it (over-limit, restricted class, mandatory trigger). Refer as a complete recommendation, not a "what do you think?"
- Peer review — a lateral, independent second opinion; its value is that the reviewer isn't anchored by your reasoning.
- Escalation — moves a problem (dispute, stuck referral, ethical concern) up to be resolved.
Defending the decision — three audiences, three languages
- Manager / auditor: defend on the merits and the file — process, not outcome.
- Broker: defend on the value and the relationship — the logic the broker can sell to the client, without giving away the adequate rate or the necessary terms.
- The override: defend with a documented reason a reasonable professional would accept, grounded in something real the model couldn't see. "A good feeling" is not a defense.
Key terms
accept/decline/modify · counter-offer · declination · peer review/referral · subjectivity · file documentation
What you could defend to your manager
"Harbor Steel: I ran the three gates — in appetite subject to the cat-zone aggregate, priceable at the debit-rated indication, and the marginal features (roof, two fire hazards, unverified protection) are fixable with terms. So the decision is modify: a counter-offer at agreed-value property with the 5% named-windstorm deductible and ACV roof, conditioned on five tracked subjectivities (inspection, IR scan, sprinkler cert, hot-work program, roof-replacement contract within 12 months). The \$20M property line and the cat exposure exceed my authority, so I've referred it with a complete recommendation. Every step is documented; the file reconstructs the decision and the reasoning without me in the room."