Guided account-manager tour · 5 steps
How to review insurance renewal premium increases
Begin with the premium scheduled to renew, then narrow the queue to material changes against the prior term. The goal is not to turn a percentage into an automatic verdict. It is to give the responsible account manager enough time and context to review the change, record follow-up, and complete authoritative service work in the AMS.
KEELRIDGE SOFTWARE · REVIEWED · Screens come from a fictional, read-only agency.
Account manager viewOpen this page in the live demo →
Captured from the fictional Keelridge Demo Agency.
The short answer
Plan the load, isolate material changes, and keep human review in control.
See when premium comes due.
A 12-month heatmap makes seasonal concentration visible before the nearest renewals become urgent.
Filter to the work that needs attention.
Expiration, term premium, prior-term change, carrier, and responsibility belong in one review queue.
Return to the system of record.
Keelridge can organize review state; licensed judgment, client communication, and policy transactions stay with the agency and AMS.
Start with premium at risk over the next 12 months.
Renewal count alone hides account size. Read policy count and term premium together, and look for months where workload clusters. A six-month policy can renew twice inside a 12-month horizon, so both terms belong in the capacity view.
This is planning context—not a forecast that every displayed policy will renew unchanged.
Explore the renewal calendar as an account manager →
Account manager viewOpen this page in the live demo →
Filter the worklist to material premium changes.
A premium-shock filter compares the current term with the prior term and brings the largest changes into a shorter queue. Combine the threshold with an actionable horizon—such as the next 60 days—so the list represents work the account manager can actually address.
Sorting by expiration first prevents a large but distant account from hiding a smaller renewal due tomorrow.
Open the filtered worklist in the live demo →
Account manager viewOpen this page in the live demo →
Treat the percentage as a signal, not a diagnosis.
A 20% change can reflect carrier rate, payroll or sales exposure, vehicles or property values, coverage and limit changes, audits, or a different policy mix. The Book record can identify the change; it cannot prove the cause or decide whether the renewal is appropriate.
Keep customer, carrier, line, prior-term comparison, and assignment visible so the responsible person can investigate without reconstructing the queue elsewhere.
Account manager viewOpen this page in the live demo →
Keep lightweight review state beside the renewal.
Reviewed, snoozed, and follow-up states help an account manager return to a queue without losing the operating context. They are not substitutes for service notes, coverage documentation, or policy transactions.
The public demo keeps these controls visible but never saves changes. In the product, the queue supports human-owned review and links back to the AMS for authoritative work.
Walk the read-only renewal workflow →
Account manager viewOpen this page in the live demo →
Refresh the queue from the regular Book feed.
After initial mapping, the recurring Book export updates renewal dates, term premium, prior-term comparisons, and account responsibility. The account team receives a current queue without an owner assembling separate employee reports or asking each person to rebuild the same spreadsheet.
See how recurring source files become role-specific work →Interpretation boundaries
What the renewal review can—and cannot—do.
- It can surface material changes.Upcoming premium, prior-term movement, and responsibility stay in one queue.
- It can help plan capacity.Monthly premium concentration shows when work is likely to cluster.
- It cannot explain every change.Rate, exposure, coverage, audits, and policy mix require human review.
- It does not replace licensed work.Advice, communication, documentation, and policy transactions remain with the agency and AMS.
Questions from account teams
Before turning a premium-change flag into a workflow.
How should an insurance agency review renewal premium increases?
Start with the premium renewing inside a defined horizon, then filter to policies whose current term premium changed materially from the prior term. Review the largest and nearest changes first, but keep carrier, line, customer, and prior-term context beside the percentage.
What is a premium shock?
A premium shock is a renewal whose term premium changed by more than the agency's configured review threshold. It is an attention signal, not proof of a carrier error, coverage problem, or service failure; rate, exposure, limits, coverage, and mix can all contribute.
How far ahead should account managers review renewals?
Use a horizon the team can act on consistently—often 30, 60, or 90 days—and compare it with the premium load in later months. Keelridge supports multiple horizons so agencies can match the queue to their service process and capacity.
Does Keelridge replace the renewal work in the AMS?
No. Keelridge identifies and organizes work from the recurring Book record, while policy changes, coverage advice, client communication, and authoritative service documentation remain in the AMS and with licensed agency staff.
Continue the tour
Walk the fictional renewal queue as an account manager.
The demo is read-only and uses synthetic customers, policies, renewal dates, and premium. Account-manager entry opens a premium-shock worklist scoped to that person's Book.