Insurance Retention Rate: Measure the Book You’re Actually Keeping
An insurance retention rate should answer a simple owner question: how much of the book you started with did you actually keep?
That answer gets blurry when an agency mixes new sales with renewals, counts customers and policies as if they were the same thing, or changes the treatment of cancellations from one report to the next. A growing book can make the operation look healthy even while a meaningful share of existing customers is leaving.
The fix is a clear definition, a consistent starting cohort, and an operating review that connects each loss to evidence and a next step.
Decide what your insurance retention rate measures
There is no single retention number that answers every question. Before calculating anything, decide what you are retaining: customers, policies, or recurring revenue. Each view can be useful, but each describes a different part of the business.
Customer retention follows the relationship
Customer retention asks whether a customer who was active at the beginning of a period still has at least one in-scope policy with the agency at the end. It is often the clearest owner-level view because it follows the relationship, not just an individual contract.
Suppose a customer replaces one policy with another appropriate policy through your agency. Policy-level reporting may show one policy lost and one policy added. Customer-level reporting can still show that the relationship was retained. Neither view is wrong. They answer different questions.
Policy retention and persistency follow the contract
Policy retention usually asks how many policies eligible to continue or renew remained in force through the defined checkpoint. In some insurance contexts, persistency is used for the same general idea. The exact duration and status rules still matter.
A renewal-based calculation is useful when policies have clear renewal dates. A duration-based view asks how many remain in force after a set number of months. Do not mix a 13-month persistency view with a calendar-year customer cohort.
Policy retention also needs a reliable status source. An agency record may show a submitted or issued policy before carrier confirmation arrives, or may lag a later cancellation or reinstatement. Label the source and timing so the report does not imply more certainty than the data supports.
Revenue retention follows the economics
Revenue retention asks how much recurring revenue from the starting cohort remains. It can expose losses that policy counts miss, but commission timing, advances, chargebacks, and carrier adjustments can make one period noisy. Define which revenue and transactions belong before using it.
How to calculate your insurance retention rate
For a customer-cohort view, use this formula:
Customer retention rate = eligible starting customers still active at the end ÷ eligible starting customers at the start × 100
The word “starting” does important work. New customers acquired during the measurement period do not belong in the retained starting cohort. Track them separately as growth.
Consider a hypothetical agency that begins the year with 1,000 eligible customers. At year-end, 880 of those customers still have at least one in-scope policy with the agency. The agency also added 150 new customers.
Starting cohort: 1,000
Starting customers retained: 880
New customers added: 150
Ending customer count: 1,030
Customer retention rate: 880 ÷ 1,000 = 88%
Net customer growth: 1,030 ÷ 1,000 - 1 = 3%
The agency grew its customer count by 3%, but it still lost 12% of the starting cohort. Looking only at the ending total would hide the amount of new production needed to replace those losses.
Use the same logic for policy retention, with eligible policies as the unit. For a renewal view, the denominator is policies available for renewal during the period and the numerator is those renewed. The Casualty Actuarial Society notes that retention comparisons change when organizations use different inclusion rules, such as whether they count company-initiated nonrenewals. That is why the definition belongs next to the rate.
Write the exception rules before you look at the result
Most retention disputes are really definition disputes. Write the treatment of common exceptions before calculating the rate, then use the same rules across periods.
Cancellations and nonrenewals
Decide whether the measure includes every customer or policy lost, only customer-initiated losses, or a separate view of each. An agency cannot learn much from a combined total if an unaffordable renewal, carrier exit, duplicate record, and service failure all receive the same label.
Keep the top-line calculation stable, then break losses into reason categories. If the reason is unknown, say so. “Unknown” is more useful than a guess because it shows where the follow-up process or source data is incomplete.
Reinstatements and delayed status updates
Choose a close date and a status-lag policy. Decide whether a later reinstatement restates the original month or appears in the next review, then apply that choice consistently.
Avoid silently rewriting prior reports. If a late carrier file changes the result, keep the original close, record the adjustment, and show the revised figure with an explanation.
Internal replacements and product changes
A customer may move from one policy to another while staying with the agency. Customer retention may remain intact even though one policy ends. Policy retention should show the contract-level movement, but the reason code should distinguish an internal, appropriate replacement from a customer lost to another agency.
Retention pressure should never push an agent to preserve unsuitable coverage. The customer’s needs, applicable rules, and qualified human judgment come first. The metric exists to improve the operating process, not to turn every policy ending into a failure.
Duplicate households, transfers, and acquisitions
Duplicate records can overstate cohort size. Producer transfers can look like losses, while an acquired book can create an artificial jump that says nothing about organic retention.
Treat these as data-quality and scope decisions. Deduplicate according to a documented rule, preserve the history of transfers, and report acquired cohorts separately until there is a comparable measurement period.
Pending and newly submitted business
A submitted application is not automatically an in-force policy. Set an eligibility rule for pending, issued, active, canceled, and terminated statuses, and identify which system supplies the authoritative status.
If carrier confirmation is delayed, the honest answer may be a provisional rate with a stated cutoff. Precision is not the same as certainty.
Compare cohorts that belong together
An agency-wide retention rate is a starting point, not a diagnosis. Segment the starting cohort by product, carrier, lead source, customer tenure, writing team, or other fields that reflect how the business actually operates.
Always show the retained count and starting count beside the percentage. A 50% result from two eligible customers is not comparable to an 88% result from 2,000. Small cohorts can swing sharply after one loss, and immature cohorts may not have reached a meaningful renewal or duration checkpoint.
Use segment rankings to find questions, not to assign blame. If one lead source has lower retention, the source itself may not be the cause. Product mix, customer tenure, status delays, onboarding, carrier changes, or a small sample could explain the gap. Review the underlying records before changing spend, compensation, or workflow.
Turn retention reporting into a monthly owner review
A useful review is short enough to repeat and specific enough to produce action. Run it on a fixed cadence with the same definition each time.
Freeze the cohort and cutoff. Record the beginning population, measurement window, status source, and close date.
Reconcile exceptions. Review duplicates, late updates, reinstatements, transfers, and internal replacements before discussing performance.
Read the top line and segments. Show customer, policy, or revenue retention with counts, then examine comparable cohorts.
Inspect losses. For each material loss, capture the reason, supporting evidence, responsible owner, and appropriate next action.
Close the loop. At the next meeting, review whether assigned follow-up happened and whether the loss reason or workflow changed.
This is where connected customer, policy, call, and activity data becomes useful. Onyx’s CRM keeps customer, policy, interaction, and note context together, while its reporting tools support custom views and filters. The agency still owns the metric definition, exception rules, and decisions that follow. Do not assume any platform’s default report matches your chosen cohort without checking it.
Measurement should also lead to better service, not just better reporting. If current policyholders are reaching acquisition queues, the agency can identify and route those conversations more deliberately. Onyx’s guide to recognizing policyholders on sales lines explains that workflow. For customers who are hard to reach synchronously, the article on texting as a service channel shows a different follow-up tactic.
A retention metric-definition checklist
Before an insurance retention rate reaches an owner dashboard, confirm that the team can answer these questions:
What unit are we measuring: customer, household, policy, member, or recurring revenue?
What event makes a record eligible for the starting cohort?
What exact period or duration are we measuring?
What status and source count as retained?
Are new customers excluded from the retained starting cohort?
How do we treat cancellations, nonrenewals, reinstatements, transfers, replacements, and pending business?
How are duplicates identified and corrected?
Which segments are large and mature enough to compare?
Are the numerator, denominator, cutoff date, and later adjustments visible?
Does every material loss have a reason, evidence, owner, and follow-up date?
If those answers change, version the definition and mark the break in the trend.
Protect the book by making losses visible
Retention is not a contest to produce the highest percentage. It is a way to see whether the agency is protecting the relationships and recurring economics it has already earned.
Start with one defensible cohort measure. Keep new production separate. Publish the counts behind the rate. Then use segments and loss reasons to decide where a service handoff, data fix, follow-up process, or owner decision deserves attention.
When the number is trusted, it changes the conversation. Instead of asking whether retention “feels fine,” the team can see what stayed, what left, why it happened, and who is responsible for the next step. If you want to see how connected customer, policy, and reporting data can support that review, book a demo.
