A landlord with dozens of units and dozens of renewal dates is running an insurance back office by accident. How portfolio policies work, what to consolidate, and a checklist for getting there.
A landlord who owns fifty units and insures them one by one is running fifty policies, fifty renewal dates, fifty certificates, and fifty chances a year for something to lapse unnoticed. The fix is old and boring and underused: a portfolio policy — one contract, one renewal date, one schedule listing every property, with units added and removed by endorsement as the portfolio changes. This guide covers when that consolidation makes sense, what to watch in the terms, and how to actually execute the migration.
The one-sentence rule: the moment managing the insurance takes more of your attention than any single property's risk, you have outgrown unit-by-unit buying.
What a portfolio policy actually changes
Mechanically, a portfolio (or schedule) policy insures a declared list of properties under shared terms. The practical differences from a stack of individual policies:
- One renewal event. The whole schedule renews on one date. Lapse risk stops being a function of how many units you own.
- Endorsement instead of purchase. Buying unit fifty-one is a schedule addition — usually pro-rated — not a new procurement.
- Blended pricing. The insurer rates the portfolio's aggregate risk. Good properties subsidise harder ones slightly, but the admin saving and volume pricing typically net in the landlord's favour well before mid-double-digit unit counts.
- One counterparty at claim time. A burst pipe cascading through three units you own is one claim conversation, not three.
- Portfolio-level data. One loss run across all units, which is exactly what the next insurer will ask for when you shop the renewal.
What it does not change
Honesty section. A portfolio policy does not make the underlying risks disappear, and three misunderstandings recur:
- It is not automatic cover for anything you buy. Most schedules require declaration of new units within a set window. Miss the window and the new unit is bare. Put the declaration step inside your acquisition checklist, not in someone's memory.
- Vacancy still matters. Extended vacancy usually restricts cover — theft and water damage especially — whether the unit is on a schedule or not. Portfolio landlords with churn need to know their policy's vacancy clause cold.
- Tenant belongings remain the tenant's problem. Your policy covers the building and your liability as owner. Encouraging or requiring tenants to carry contents cover is complementary, not redundant.
The consolidation checklist
For a landlord (or the property manager acting for one) moving from scattered policies to a schedule:
- Build the asset register first. Address, property type, built-up area, construction type, year, current sum insured, mortgage lender if any, and current policy expiry for every unit. Half the pain of consolidation is discovering nobody has this list.
- Fix the sums insured while you are there. Rebuild cost, not market value, per unit. A migration is the one natural moment every valuation gets reviewed at once — use it.
- Check loss payees. Mortgaged units need the lender named on the new policy from day one. A consolidation that drops a lender endorsement will surface as a compliance letter from the bank.
- Align the dates deliberately. You will either cancel existing policies early (check refund terms) or write the portfolio policy with staggered onboarding as each legacy policy expires. The second is slower and safer.
- Read the loss-of-rent clause. For a landlord, the building claim is often smaller than the income gap while repairs run. Confirm the indemnity period — twelve months is thin if a serious loss means permits and rebuilding; eighteen to twenty-four is more realistic.
- Set the liability limit for the portfolio, not the unit. Owner's liability across fifty units with tenants, visitors and contractors is not fifty small exposures; it is one aggregated one.
- Agree the endorsement workflow. How are units added, in what format, confirmed how fast, priced how? If the answer involves emailing a PDF and waiting, that is where your future lapse lives.
Where platforms come in
The reason this topic belongs on an embedded-insurance blog: the asset register that consolidation requires already exists inside property-management platforms. Units, areas, tenancy status, rent rolls — the data is the platform's core inventory. A property-management system that offers portfolio cover as a feature can generate the schedule from data it already holds, trigger the endorsement automatically when a unit is onboarded, and surface expiring cover next to arrears and maintenance in the landlord's dashboard.
For the platform this is a natural revenue line with real switching-cost gravity; for the landlord it deletes an entire category of admin. The insurance itself is conventional. What is new is that the bookkeeping that made portfolio cover tedious is now a by-product of software the landlord already uses.
Fifty units means one schedule, one renewal date, and one claim conversation — or it means fifty chances a year to lapse.
Start with the register, fix the valuations, mind the lenders and the vacancy clause, and make adding a unit to the policy part of adding a unit to the portfolio. That is the whole trick.