Use case
Building insurance tracked as its own control, not a filed PDF
A building's own insurance policy — distinct from any vendor's insurance — is one of the 14 controls in Meridian's compliance engine, tracked with an expiry date and a status like every other control.
The problem
Building insurance renewals are often tracked by whoever set up the policy originally, with no structured reminder before the next renewal date.
Why it matters
A lapsed building insurance policy is a direct exposure for the property owner — and one that's often only discovered when a claim is needed and it's too late.
How Meridian helps
- Insurance tracked as its own control within the 14-area compliance engine, separate from vendor insurance tracking
- Expiry status — pending, compliant, attention, breach — reviewed the same way as every other compliance control
- Renewal action items assigned an owner and a due date well ahead of expiry
- Policy documents stored in the document vault with AI-extracted expiry dates
FAQ
Is this the same as vendor insurance tracking?
No — vendor insurance tracking covers a vendor's own liability cover; this control covers the building or asset's own insurance policy.
Can I see insurance status across the whole portfolio at once?
Yes — the compliance dashboard shows insurance status per building, rolling up to a portfolio-wide view.