The insurance article of a commercial lease receives less attention than the rent provisions and far less than the operating expense mechanics, which is understandable and occasionally expensive. Buried in it is a mutual waiver of subrogation, a clause whose purpose is to stop the parties’ insurers suing each other after a loss, and whose effectiveness depends on conditions nobody checks until something burns.
The commercial logic is sound and worth restating. Landlord and tenant occupy the same building and will keep dealing with each other after a fire or a flood. Allowing each insurer to pursue the other party for recovery turns an insured loss into litigation between people who need a working relationship. A mutual waiver removes that, with each party agreeing to look to its own policy.
What makes the clause fragile is that it depends on three things being true at once: the insurance article requiring the cover the waiver assumes, the policies permitting the waiver, and the waiver running in both directions. Any one of those failing leaves a gap that is invisible on paper and expensive in practice.
Five reasons the waiver does not do what the lease says
These are the failure modes that show up when a loss is actually being adjusted. None of them are exotic and all of them can be identified from the lease and the certificate before anything happens.
- No supporting endorsement, the lease waives subrogation but neither policy carries a waiver endorsement, so an insurer may treat its recovery rights as prejudiced rather than waived.
- Asymmetric drafting, the waiver runs in one party’s favour only, usually the landlord’s, which leaves the other exposed to the claim it believed had been eliminated.
- Uninsured property in scope, the article does not clearly require anyone to insure tenant improvements, so the waiver reaches property that may have no cover behind it.
- Entity mismatch, the certificate names a different entity from the lease counterparty, commonly after a corporate reorganisation or an assignment nobody updated.
- Lapsed evidence, the policy renewed, the certificate did not, and the compliance position for the intervening period cannot be demonstrated.
Read together these describe a portfolio that looks compliant in a tracker and is not compliant in substance. The tracker usually records that a certificate exists, which is a weaker statement than it appears, because the question after a loss is what the certificate said and whether the endorsement was in place on that date.
A waiver of subrogation clause in a lease is an agreement between landlord and tenant. It does not bind their insurers. The control is a waiver of subrogation endorsement on each policy, obtained in advance and shown on the certificate. Collecting certificates that confirm the endorsement, rather than certificates that confirm a policy exists, is the single change that converts a paper position into a real one.
What to hold as lease data
The insurance article generates a small number of fields and one recurring obligation. Held properly these make a portfolio-level compliance position reportable rather than anecdotal.
- Required cover per party. What each party must insure, on what basis and against which perils, recorded as fields rather than left in the article text
- Waiver direction and scope. Whether the waiver is mutual, which losses it covers and whether it extends to affiliates, agents and mortgagees as the lease may require
- Endorsement requirements. Waiver of subrogation and additional insured requirements recorded per policy type, so certificate review has a checklist rather than a judgement call
- Certificate expiry and entity. Expiry date as a tracked obligation with an owner, and the named insured recorded so an entity mismatch is caught at collection
- Event triggers for re-verification. Assignment, subletting, entity change and major alteration recorded as triggers, since each changes who should be insuring what
A five-step roadmap for the insurance article across a portfolio
Step 1, abstract the insurance article, not just the critical dates
Most abstraction projects capture rent, term and option dates and summarise insurance in a sentence. Capture the required cover per party, the waiver direction and the endorsement requirements as fields, because those are the values a compliance check needs.
Step 2, compare certificates against requirements
Run the comparison across the portfolio and expect three findings: certificates not evidencing the required endorsements, entity mismatches, and expired or missing certificates. The endorsement gap is usually the largest and the least known.
Step 3, fix the direction problem in the template
For landlords, confirm the standard waiver is genuinely mutual and that the insurance article requires both sides to carry the cover it assumes. For occupiers, make mutual direction a standard review point rather than a negotiated concession.
Step 4, instrument certificate expiry as an obligation
Hold expiry dates with role owners and an escalation path, so collection happens before lapse rather than during an annual sweep. This is the control with the shortest payback in the whole exercise.
Step 5, add the event triggers
Wire assignment, subletting, entity change and alteration events to an insurance re-verification task. These events change the insured interest and are the most common cause of a mismatch that was correct at signature.
Hold insurance terms where the lease lives
Aavenir records required cover, waiver direction, endorsement requirements and certificate expiry as fields and obligations on each lease.
Why this is worth the effort on a quiet portfolio
The honest answer is that most portfolios never test the clause, and the ones that do test it discover the gap at the worst possible time. A significant property loss with an unenforceable waiver produces a subrogation claim against a counterparty you still need, legal costs on both sides, and a relationship problem that outlasts the repair. The preventive work is a few fields during abstraction and one tracked date per lease, which is a small cost against an exposure that is binary rather than gradual. The same discipline already applied to CRE vendor service contracts, where certificate expiry is routinely tracked, transfers directly to the lease population.
Condition, test and evidence
The table sets out the three conditions the waiver depends on, plus the two administrative checks that keep them true. The evidence column is what a portfolio compliance report should be able to produce per lease.
| Condition | Test | Owner role | Evidence |
|---|---|---|---|
| Article requires the cover | Field comparison against requirement set | Lease administration | Abstracted requirement fields |
| Policies permit the waiver | Endorsement confirmed on certificate | Risk or insurance | Certificate showing endorsement |
| Waiver is mutual | Direction recorded from clause text | Lease administration | Waiver direction field with clause reference |
| Certificate current | Expiry date obligation with escalation | Property management | Current certificate with dates |
| Entity correct | Named insured matched to lease party | Lease administration | Entity match confirmation |
The waiver of subrogation is a good example of a clause that works perfectly in theory and conditionally in practice. Its value comes entirely from conditions outside the lease document: whether the policies carry the endorsement, whether the article requires the cover, whether the certificate is current and names the right entity. Abstracting those conditions as fields and tracking one date per lease is unglamorous portfolio hygiene with a large downside avoided, which is the usual profile of the controls nobody gets credit for. Owners and occupiers already running critical date and lease obligation management have the mechanism in place and only need the fields.
For related guidance, see ASC 842 and IFRS 16, the lease data auditors test, Property vendor service contracts, a controls datasheet and Continuous operation covenants in retail leases.
