Guided tour for account managers and their managers · 5 steps
Which renewals need attention next?
See where renewal work is building, read how much each premium moved at its last renewal and give the responsible person the context to investigate. Keelridge brings dates, prior-term comparisons and review state together so the team can decide what to follow up next.
KEELRIDGE SOFTWARE · REVIEWED · Screens come from a fictional, read-only agency.
Account manager viewOpen this page in the live demo →
The short answer
One agency context. The right renewal view for each responsibility.
Where is the work building?
Read the calendar to plan capacity. Account managers review their own book; department managers review the team they are responsible for.
Which changes deserve a closer look?
Read each renewal's last premium change beside its date, then inspect the amount and policy context before drawing a conclusion.
What should happen next?
People choose the next action. Keep review state beside the queue and complete authoritative service work in the AMS.
Where will renewal work cluster?
Where: My Book, Renewals. The page has Renewals by month for the next 12 months, then the list of renewals due.
Read policy count and current term premium together across the next twelve months. A busy month may need earlier preparation or a conversation about team capacity. The calendar helps make that decision before the nearest renewals dominate the queue.
The view carries current term premium forward for planning. A six-month policy can appear twice in the year. Check the source date and distinguish recorded expirations from projected second events; neither predicts the next price or guarantees renewal.
Explore the renewal calendar as an account manager →
Account manager viewOpen this page in the live demo →
Which premium changes deserve attention?
Every renewal row shows its last renewal change: how far the current term premium moved against the same policy's prior term, marked up or down. Read it alongside urgency and the premium involved, within a workable horizon such as the next 60 days.
The change needs usable prior-term history and compares premiums already in the book record. It is the change the client met at the last renewal, not a forecast of the next one, and the list stays in expiration order: the responsible person decides which changes deserve a closer look.
Inspect the renewal worklist in the fictional demo →
Account manager viewOpen this page in the live demo →
What do we need to understand before acting?
Inspect the client, carrier, line, current premium and prior comparison. Bring the agency's source records and account knowledge into the review: what changed in the exposure, limits, coverage or carrier terms, and what should the client conversation address?
Keelridge keeps the available policy context beside the change so the responsible person can investigate without rebuilding a separate list. The percentage identifies a change; the agency establishes the reason and decides whether further review or remarketing is appropriate.
Account manager viewOpen this page in the live demo →
Decide what needs follow-through.
Keep the review state with the renewal so the team can return to it without starting over. From the Actions menu on each row, mark it reviewed, snooze it until the right date or flag it for follow-up, and find it later under Handled.
Department managers use their authorized team view to see where help is needed. Account managers work within their own book. People own the next actions, client conversations and authoritative service documentation in the AMS.
Walk the read-only renewal workflow →
Account manager viewOpen this page in the live demo →
Refresh the figures. Keep the review moving.
The renewal review should not have to be assembled by hand every time the team meets. After mapping, the owner, or someone the owner authorizes, uploads supported AMS reports, reviews the checks and confirms the update. Dated book records bring renewal dates, current premium, available prior-term comparisons and account responsibility into the same review.
Management and account teams work from the same agency context, with the views and context each role needs. People decide where to focus and complete service work in the AMS. Reports can be refreshed whenever a supported new export is available.
See how recurring source files become role-specific work →Before drawing a conclusion
Put the change in its agency context.
- Check the dates and comparison.Read current term premium against usable prior-term history. The calendar is planning context; the AMS export contains no next-term premium.
- Investigate the reason.A premium change is a signal, not a diagnosis. Rate, exposure, limits, coverage and audits need source records and human judgment.
- Keep access appropriate to the role.Account managers see their own book; department managers see their authorized team. Commission, payout and profitability stay outside both views.
- Keep insurance work with the agency.People decide what to do. Advice, client communication, documentation and policy transactions remain with licensed staff and the AMS.
Questions from account teams
Before acting on a premium change.
How should an insurance agency review renewal premium increases?
Start with the renewal load inside an actionable horizon, then read how much each policy's premium moved at its last renewal. Keelridge shows that change on every renewal row, in date order; the agency decides which changes deserve a closer look. Read the expiration date, premium, carrier, line and client context together before deciding what needs investigation or follow-up.
Read the note →What is the last renewal change?
It is how much a policy's premium moved when it last renewed: the current term premium against the same policy's prior term, whoever looked after it then. The change is current premium minus prior premium, divided by prior premium, shown up or down on every renewal row. A usable positive prior premium is required; without one the row shows a dash, which does not mean the premium was unchanged. It is the change the client already met, not an estimate of the next term's premium, and it does not reorder the list.
How far ahead should account managers review renewals?
Choose a window your team can act on: the worklist shows the next 30, 60, 90 or 120 days, with 90 days as the default. Use the twelve-month calendar for the broader load, and check the source date before relying on the queue. The calendar carries current term premium forward for planning, including a second renewal event for six-month policies; it does not predict prices or whether a policy will renew.
Does Keelridge replace the renewal work in the AMS?
Keelridge organizes renewal review from supported book snapshots. People decide what to investigate, mark as reviewed, snooze or flag for follow-up. Coverage advice, client communication, policy transactions and authoritative documentation remain with licensed agency staff and the AMS. The fictional public demo shows these controls but never saves changes. Its AMS launch opens the vendor website, not a verified policy-record link.
Your agency’s renewal review
Start with the work your team needs to see.
Keelridge is free for five design partners until February 15, 2027. It starts with a 20-minute fit call, where we walk through Keelridge using fictional agency data. Discuss how the team reviews renewals today, where the queue gets rebuilt by hand and who needs the context to follow through. No agency files are needed for the conversation.