How to Build a Carrier Cheat Sheet Your Team Uses

Photo via Unsplash
Every agency has one. A spreadsheet, a shared doc, a folder of PDFs, built with real effort by someone who cared. And within about six weeks it has drifted far enough from reality that the experienced producers stop opening it and start asking each other instead.
The problem is almost never the format. It is that the document was built as a snapshot of something that moves.
Why Carrier References Rot
Carrier rules change without announcement, on their own schedule, across products. A build chart gets revised. An appetite tightens. A product is repriced or withdrawn. None of that arrives as a notification to your spreadsheet.
Worse, the rot is invisible. A stale cheat sheet does not display an error. It displays last quarter’s rule in the same confident formatting as the current one, which makes it more dangerous than having no document at all. A producer who knows they do not know will go check. A producer holding a wrong answer will not.
This is the same structural problem underneath AI tools built on stale data. Confident, unsourced, unmaintained information is the failure mode, whichever technology is presenting it.
Regulators are moving the same way on documentation. NAIC guidance on accelerated underwriting stresses that models must rely on “sound actuarial principles, transparent data inputs”, and Departments of Insurance have broad authority to examine how life insurers actually run their processes. An internal reference nobody can source is the agency-side version of the same weakness.
Build It Around Sources, Not Answers
The single change that makes these documents survive: every entry points at where it came from and when it was last checked.
An entry that reads “Carrier A: accepts controlled diabetics at Standard” is a liability. An entry that reads “Carrier A: controlled Type 2 may qualify for Standard per the 2026 field guide, page 14, verified Sep 3” is usable. A producer can see the age of the claim and decide whether to trust it or verify. That single design choice is the difference between a reference and a rumor.
It also makes maintenance tractable. You can sort by verification date and work the oldest entries, instead of facing an undifferentiated wall of text where everything might be wrong.
What Belongs In It
Keep it to the questions producers actually ask under time pressure. Everything else belongs in the carrier’s own guide, linked rather than copied.
-
Appetite by condition. The handful of conditions your book actually sees, and which carriers treat them favorably.
-
Hard stops. The declines and exclusions that disqualify a carrier outright. This is the highest-value section because it prevents wasted submissions.
-
Product boundaries. Face amount ranges, issue ages, and where a product stops being available. Cheap to record, constantly misremembered.
-
Process quirks. Which carrier requires what, how they handle records requests, where their portal hides the build chart. This is the knowledge that otherwise lives only in one person’s head.
-
Turnaround reality. Their stated timeline and what your agency actually observes, which are not always the same number.
Resist the urge to reproduce the underwriting guide. A document that tries to be complete becomes impossible to maintain, and an unmaintained document is the thing you were trying to avoid. Point to the source guidelines instead.
Make Maintenance Someone’s Job
Unowned documents die. That is the whole of it.
Name one person accountable for the reference, give them a recurring block to work the oldest entries, and give every producer a frictionless way to flag a discrepancy the moment they hit one. The flag matters more than the schedule: your producers are running live tests against carrier rules every day, and most agencies capture none of what they learn.
A note when a case comes back differently than the sheet predicted is the cheapest possible source of truth, and it only happens if reporting it takes seconds and the report visibly changes something.
Expert Insight: The Sheet Is a Byproduct, Not the Goal
The real asset is not the document. It is the habit of writing down what your agency learns about carriers, so that knowledge stops evaporating when someone leaves or gets busy.
Agencies that do this well end up with something more valuable than a reference. They end up able to see their own patterns: which carriers actually place for their book, where submissions get wasted, which appetite assumptions were never true. That is the data behind real carrier matching, and it does not come from a vendor. It comes from your own case history, written down.
The sheet is just the place it accumulates. Which is why the formatting matters far less than whether anyone is adding to it.
Frequently Asked Questions
Spreadsheet, wiki, or CRM field?
Whichever your team already opens daily. A worse tool that gets used beats a better one that does not. What matters is that entries carry a source and a date.
How often should entries be re-verified?
Tie it to how often that carrier publishes changes rather than a fixed interval. Sorting by oldest-verified and working the top is more practical than a calendar rule.
Should producers be able to edit it directly?
Let them flag freely and let a named owner commit changes. Open editing produces drift, and no editing produces abandonment.
Peach Pilot supports licensed agents’ workflow. Carriers make final underwriting and issue decisions.
Keep Reading
Recommended for you

How to Prep Clients for the Life Insurance Phone Interview
What the carrier teleinterview covers, why a mismatch with the application costs you cases, and the five-minute prep call that keeps the file clean.

Term vs Final Expense: Matching Product to Client
Term and final expense solve different problems for different clients. A practical comparison of coverage length, underwriting, face amounts, and the wrong-product trap.

What Is Accelerated Underwriting in Life Insurance?
Accelerated underwriting skips the exam and leans on external data. What it is, who qualifies, what regulators expect of it, and when to steer a case elsewhere.
Comments
No comments yet — start the conversation.