Published with current-versus-historical record controls and no automatic renewal claim.
Why this matters
NIBA describes broker support across the life of a policy, including renewal and adjustment. That makes renewal a distinct operational moment rather than a copy of an earlier case. A previous schedule can show what was in force, but it may not explain changed activities, a new asset, an altered limit or a client concern. A clear preparation view lets the team distinguish 'known from the current record' from 'needs a new confirmation'. It also helps an internal handover: the reviewer sees why a question was asked instead of reconstructing the context from a mix of notes and calendar reminders.
Key points to carry into the work
- Use the current policy record as a starting point, while keeping prior versions clearly dated as historical context.
- List changes, client questions and newly supplied information as explicit renewal-review items rather than silently updating a field.
- Link the renewal timeline to sources and owners so a team member can tell what is waiting on a client, a broker review or another internal task.
- Keep renewal preparation separate from any advice, market approach, acceptance or release decision.
- 01Identify current record
- 02List changes
- 03Separate history
- 04Assign questions
- 05Broker review
Prepare a renewal case with context
Where Insia fits
Quote Desk's private-pilot narrative includes renewal case preparation around current sources, visible gaps and broker review. The broader Broker Workspace story keeps renewal tasks and client context connected, while Insia Intelligence can prepare source-backed context for human inspection.
Keep the boundary clear. Insia does not renew a policy, decide that current cover remains suitable, contact an insurer automatically, accept terms or replace the broker's renewal and advice process.
Checklist
- Is the current policy source identified and dated?
- Are historical documents marked as history rather than current truth?
- Are client changes and questions represented as review items?
- Does every gap have an owner and next action?
- Has a broker review been kept separate from case preparation?
Sources and scope
Sources support the external context in this guide. Current product capability and availability are explained on the linked Insia product page.
Common questions
Can last year's schedule be used at renewal?
It can provide context, but it should be checked against the current record and new client information. It is not a substitute for a current review.
What should a renewal checklist include?
It should identify the current source, changes since the previous record, missing information, client questions, owners and the next broker review point.
Does preparation decide whether cover should change?
No. Preparation organises factual context. Decisions about cover, advice, placement and client communication remain with the appropriate human process.
How can a team avoid duplicate renewal requests?
Keep the source and purpose for each request visible. A new team member can then see what was asked, why it was asked and whether a response already exists.
Is the renewal workflow publicly available?
Quote Desk is a private pilot for selected broker participants. The public guide explains a practical workflow model, not a promise of product access or a public execution service.
Put the context to work
Carry this method into the quote case.
See how Quote Desk brings the fact-find, supporting evidence, gaps, market preparation and comparison into one broker-reviewed case.
Join the Quote Desk pilot