Skip to content

Under-insurance is a portfolio-wide risk hiding in a spreadsheet — here’s how to catch it before a claim does

4 min read
Toy robot inspecting miniature houses with a magnifying glass and abstract insurance renewal panels

Property management firms are used to managing lots of small deadlines. Renewals, inspections, certificates, service charge cycles, contractor visits and client queries all compete for attention.

Insurance renewal and sum-insured reviews can look like just another admin task until something goes wrong.

If a building policy lapses, or if a reinstatement value has not been reviewed for years, the risk is not just inconvenience. It can become a serious financial exposure for the freeholder, RMC, landlord or managing agent.

The problem is that the information is often split across systems. One spreadsheet has the property list. Another has policy details. The broker’s schedule sits in a PDF or portal. Valuation dates are held somewhere else. Nobody intends to miss a renewal or leave an old sum insured unchecked, but the risk grows quietly across the portfolio.

An example AI workflow: insurance renewal and sum-insured flagging

This is an example workflow, not a real client case study. It is a flagging and prioritisation tool, not an insurance decision-maker.

A script takes an export from the property management system and cross-references it with current insurance schedule data. The portfolio export might include address, building value estimate and last valuation date. The insurance data might include policy number, renewal date and sum insured.

The assistant then applies clear rules. For example:

  • flag any policy with a renewal date within the next 60 days;
  • flag any property where the sum insured has not been reviewed in the last three years;
  • highlight records where the address, policy reference or valuation date appears incomplete;
  • rank items by urgency and likely financial exposure.

The output is a prioritised action list for the property manager. Each flagged property includes the relevant policy details and a suggested next step, such as chase broker quote, instruct a reinstatement valuation, or notify the freeholder or RMC.

An LLM can help draft the plain-English summary and next-step suggestions. The actual checks, however, should be based on simple dates, thresholds and source data.

Why this is a good use of automation

This is exactly the kind of work where a small assistant can be valuable. It is repetitive, rule-based and easy to overlook when the team is busy.

For a portfolio manager, manually cross-checking spreadsheets and policy schedules every month can take several hours. It is also the kind of task where attention naturally drops because most records will not need action most of the time.

Automation changes the workflow from “someone must remember to check everything” to “the system produces a short list of exceptions for a human to review”.

That is a much better fit for busy teams. The assistant does the scanning. The property manager applies judgement.

The guardrails matter

This is a medium-risk use case because the consequences of bad data can be significant. The assistant should never decide that a policy is adequate, that cover should be changed, or that a valuation is unnecessary.

All renewal and valuation instructions should go through a human. The data should also be checked periodically against broker records, especially after portfolio changes, property works or new instructions.

It is also worth being explicit about the limits of the tool. It can flag that a sum insured has not been reviewed within a set period. It cannot guarantee that the current figure is right. That remains a professional judgement and, where appropriate, a valuation issue.

What you need to start

A first version does not need to connect to every system on day one. You need a reliable property list, current insurance schedule data, renewal dates, sum insured figures and last review or valuation dates.

If those are currently in separate spreadsheets, that is still workable. The first step may simply be creating a repeatable monthly report from clean exports.

Once the structure is proven, API access or broker-portal integration can come later.

A practical first step

Choose a sample of 20 managed properties and ask: can you quickly identify renewal date, policy reference, sum insured and last reinstatement review for each one?

If that takes longer than expected, the risk is not only admin inefficiency. It is visibility.

If you manage a property portfolio and want help designing a safe flagging workflow, book a short call with Stuart Cole Consulting. We can map the data, thresholds and approval points before anything is automated.

Want help putting AI to work?

If this article sparked an idea, let's have a short call about what AI could do in your business — no jargon, no obligation.