Insurance renewal management that takes the date off the policy itself.
Almost nobody misses a renewal on purpose. They miss it because the date lived in a reminder somebody set a year ago, and the reminder was dismissed while they were with a customer. Insoora reads the expiry date off the schedule and keeps a list, which is a different kind of object: it is still there tomorrow.
- Expiry read from the policy schedule
- A thirty-day list, sorted by date
- Separate third-party dates on motor
- Customers see their own days remaining
On this page
Set the expectation first
This builds a list. It does not send messages.
If what you need is automated SMS or WhatsApp to customers, Insoora is not that, and the rest of this page will not change that.
Insoora has no outbound messaging. It does not email, text or WhatsApp your customers, and it does not run a campaign on your behalf. What it does is make the question "what expires in the next thirty days?" answerable without anybody having maintained an answer.
The distinction is worth more than it sounds. A reminder tells one person about one policy at one moment, and once dismissed it leaves no trace that it ever existed. A list tells you about every policy in a window, in date order, and is still there tomorrow and the day after. Most of what goes wrong with renewals is a reminder being used where a list was needed.
Inside the portal there is an alert bell, which surfaces the policies expiring soon, the extractions still waiting for review, and the policies not yet shared with their customer. That is a notification, not a message to a customer.
- A renewals view of policies ending within the next thirty days, sorted by date
- An in-portal alert count for expiring policies, pending reviews and unshared records
- Policyholders see days remaining on their own cover in their own portal
What it does not do
No email, SMS or WhatsApp is sent to anyone — not to you and not to your customers. Contacting the customer is still a phone call you make.
The dates
Which dates a policy actually has
Expiry is the obvious one and for many agents the only one recorded. Several others change what you should do and when.
| Date | Why it matters | In Insoora |
|---|---|---|
| Policy expiry | The deadline. Cover ends, and for motor, driving after it is an offence as well as a risk. | Read from the schedule. Drives the thirty-day list and the customer's days-remaining figure. |
| Policy start | Establishes the term, and anchors the cycle for following years. | Read from the schedule, stored alongside expiry. |
| Issue date | Distinguishes when cover began from when the document was produced, which differ more often than people expect. | Read where the schedule states it. |
| Third-party cover period | On a long-term motor policy, third-party cover can run three or five years while own damage runs one. Two expiry dates, and only one needs acting on this year. | Stored as its own start and end dates, separate from the policy's. |
| Previous policy expiry | Establishes continuity, which is what a no-claim bonus depends on. | Read where the schedule names the previous insurer and policy. |
| Grace period end | The last point at which cover can usually be restored without underwriting again, and it varies by insurer and product. | Not modelled. It is in the policy wording, not the schedule, and Insoora does not read wordings. |
A grace period is not an extension of cover. For many general insurance policies a claim arising during a lapse is simply not payable even if the policy is later reinstated — never tell a customer otherwise without reading that policy's own wording.
Why the list can be trusted
What keeps a renewal list honest
Four properties, and the fourth is a duty on you rather than on the software.
- 1
The date came from the document
Not from a convention. Software that assumes a policy runs a year from its start date is wrong about exactly the policies that matter most — short-period travel cover, multi-year motor, and anything endorsed mid-term. - 2
Nothing had to be remembered
A policy appears on the list because of what its schedule says, not because somebody set something up when it was filed. A policy uploaded last year and forgotten about still turns up thirty days before it ends. - 3
Re-reading gives the new answer
When a policy is endorsed and the term changes, the revised document can be uploaded and the record follows it. A date typed into a calendar has no connection to the document and cannot be re-checked against it. - 4
Flagged dates get confirmed
If an expiry date was one of the fields the parser could not read confidently, it is flagged rather than guessed — and until a human confirms it, that policy's place on the list is only as good as the extraction. Clearing the review queue is what makes the list reliable, and it is the one part nobody else can do for you.
The customer's view
The policyholder can see their own clock
Half of renewal chasing is a customer who genuinely did not know their cover was ending.
A policyholder with a portal login sees each of their policies with how long it has left, read from the same schedule your list is built from. Cover in force, expiring within thirty days, already expired, and no expiry recorded are the four states, and they can filter to any of them.
What they cannot do is act. The customer portal holds no write permission anywhere in the system: there is no renew button, no payment and no endorsement. It is a window onto their own records, and renewing remains a conversation with you.
That is a smaller feature than an automated reminder and a more honest one. The customer who opens their portal and sees forty-five days left on their car policy is a customer who rings you first.
- Four states: in force, expiring in thirty days, expired, no expiry recorded
- Days remaining on each policy, with the document it was read from
- Strictly read-only — nothing in the portal can change a record
What it does not do
A policyholder sees only what their agent has shared with them. A policy that has not been assigned to a customer appears to nobody but the agency, which is why "not yet shared" is one of the portal's own alerts.
Turning a list into a week
What you can do with the renewals view
The renewals view is driven by the same filters as the policy list, which is what lets it become a working list rather than a report.
Filter by window
Expiring within thirty days is the default view. The same filter applies on the policy list, so a wider or narrower window is one control away.
Narrow by insurer or line
Everything expiring next month from one insurer, or all the health policies, filtered and sorted by date.
Keep the view
Filters live in the URL, so a filtered renewals list can be bookmarked or sent to a colleague with the same access.
Take it with you
Export the list to CSV or Excel to work from on a phone or hand to someone making calls, with the same access rules as the screen.
See last year first
Open the customer and the previous policy is there with its document, which is what a renewal conversation actually needs.
Three alert counts
Expiring soon, waiting for review, and not yet shared with the customer — the three backlogs that quietly become lapses.
What renewal software this is not
The four things it will not do
Each of these is something a product in this category is often assumed to do.
It does not contact anyone
No email, no SMS, no WhatsApp, no automated calls, no templates and no campaign scheduling — to you or to your customers. The list tells you who to ring.
It does not renew
There is no connection to any insurer in either direction. Insoora cannot fetch a renewal quote, submit a renewal, collect a premium or issue cover.
It does not read policy wordings
Grace periods, waiting periods and reinstatement terms live in the wording document, not the schedule. Insoora reads schedules, so those dates are not modelled and must be checked against the policy itself.
It cannot fix a date nobody confirmed
An expiry date flagged for review and left unconfirmed is a policy whose place on the list is uncertain. The software can show you the backlog; it cannot clear it.
Frequently asked questions
Questions this page should answer
Keep reading
Where to go next
The pages that cover the next part of this, with what each one adds.
Upload the book and read the next thirty days.
The policies you had forgotten are the ones this list is for.