Contract Review Series
One of the biggest problems with contract reviews?
Insurance professionals are brought in far too late or in a piecemeal way.
The contract arrives:
- after it’s already been signed
- the day before work starts
- or with only the insurance clauses extracted (and none of the other terms provided).
And that creates problems.
Because risk doesn’t sit neatly inside the “insurance obligations” section of a contract.
It can also sit in:
- indemnity terms
- liability assumptions and caps
- fitness for purpose obligations
- warranties and releases
- limitation and dispute resolution provisions,
and countless other clauses buried deep within the agreement.
Which means reviewing only the insurance requirements creates a very incomplete picture of the client’s actual exposure... and yours.
Nobody wants to discover too late that they've assumed liabilities their insurance doesn’t cover, additional insurance may have been available had the exposure been identified earlier, or the risk may have been approached differently by underwriters had the broader contractual picture been visible from the start.
And once the contract has already been signed? Any leverage to negotiate, or opportunity to assess problematic terms is usually gone.
So what can you do?
In my experience, it's not always an easy fix. But I think it starts with taking control of what you can and ensuring the basics are done right.
Be clear and consistent. Build habits early. And keep reinforcing your message over time (as it's often a 'slow burn' with some clients!)
Ask for contracts before they are signed
Insist on receiving the full agreement, not just the insurance terms
Build contract review discussions into renewal, placement and onboarding conversations
Learn to identify, as well as clearly explain, how and why contracts can materially reshape the exposure being insured (real-life case examples help!)
Be clear on your role when addressing these issues and the boundaries you are not prepared to cross
Ask operational questions about how the customer's agreements actually work in practice
Qualify your remarks by making clear (in writing) your role and that you are not providing legal advice
Don't shy away from 'hard' conversations: if you are unable to assist customers meet obligations they've already agreed to, be clear and confident in that advice.
Where appropriate, encourage clients to obtain professional advice before legal obligations are locked in so they can assess the risks and make informed commercial (and insurance) decisions.
Contract Review Series
Avoiding contract reviews?
I know from the many conversations I've had over the years that some insurance professionals are very reluctant to review customer contracts.
I'm not too sure why.
I suspect it may have something to do with the fear of straying into the realm of legal advice... or perhaps missing something important.
But avoiding contracts altogether isn’t really the answer.
Because whether you work in broking, underwriting, claims or risk management, contractual obligations can fundamentally reshape a client’s exposures and the way their insurance programme responds.
So while there's no call to analyse contracts like a lawyer, there is a need to develop enough knowledge and confidence to:
navigate a contract
recognise, raise or flag potential risk and insurance issues
and source available insurance solutions (or give/obtain clear advice when there are none).
First step
My suggested "first step" for those looking to improve in this area is to start small and spend some time initially becoming comfortable with reading all types of commercial contracts.
Understand their 'anatomy'. Their general structure. Their different parts.
It really isn’t all that different from learning to navigate policy wordings.
After all, insurance policies are commercial contracts too (just with a layer of insurance law over the top!)
Of course, there's no one-size-fits-all approach because contracts are always unique. A lease differs from a service agreement; a service agreement differs from a construction contract... (and so the list goes on!)
The trick is to simply start reading them.
And become comfortable with the bigger picture first.
01.06.26
Contract Review Series
Contractual indemnities can be like wild commercial ‘beasts’.
Untamed. Unpredictable. And from an insurance perspective, far riskier than they first appear.
A NSW case has recently surfaced involving a landlord’s claim for more than $15 Million in damages, following a warehouse fire which spread from its tenanted premises to a neighbouring property.
The fire itself started in an extraordinary way.
Air-conditioning components had been packed in cardboard and stored by the tenant outside the warehouse on pallets, wrapped in clear plastic. Rainwater pooled in the plastic, creating an “aqua lens”. Sunlight concentrated through the water onto the cardboard below, eventually causing it to ignite.
But the real dispute wasn’t about science.
It was about risk allocation.
The lease contained an indemnity promise from the tenant to the landlord. And quite frankly, it was a mess.
Poor drafting led to a trial and an appeal over what the clause actually meant:
- Was the tenant only responsible for damage it substantially caused?
- Or had it assumed much broader risk?
- Did storing the pallets in the open air trigger the indemnity?
- Or was the real culprit a bizarre combination of wind, water and sunshine?
Ultimately, the Court found the tenant’s storage of the pallets did trigger the indemnity. And they weren't 'saved' by the inelegant legal language used in the lease.
But as well as being a brutal financial lesson, cases like this highlight a much bigger issue.
Contractual indemnities can quietly shift risk well beyond a client’s insurance programme.
And these clauses can be dense, confusing, and incredibly difficult to unpack in practice.
But they are only one example.
Commercial contracts are full of terms capable of reshaping and reallocating risk in ways that aren’t always obvious at first glance.
And that creates a real insurance challenge.
Because insurance professionals don’t need to (and shouldn’t!) analyse contracts like lawyers.
But they do need to know enough to recognise and raise:
- when something may be problematic
- when risk may be shifting in unexpected ways
- when insurance programmes may need to be reviewed, renegotiated, or altered in response.
So at this time of renewals, I’ll be sharing some posts about these kinds of contract review issues for insurance professionals.
Not legal advice.
Just practical ways to help spot some of the potential red flags before they become expensive problems for customers (and difficult issues for those advising them).
27.05.26
Words • Context • Coverage
Policy wording disputes often turn on very small changes in language.
And because insurance policies are commercial contracts, there’s a lot to learn from the drafting choices (and mistakes) that lead to other commercial disputes.
Take this recent 2026 case involving a guarantee.
Ms Otto, a director of a sporting goods company, gave a personal guarantee to one of her company’s suppliers, ASICS, back in 2008.
Years later, her company went into liquidation owing ASICS more than $500K. ASICS sought to claw back some of its debt, asserting a claim (under the guarantee) against land Ms Otto had acquired around 5 years after she had signed that document.
So what did her guarantee promise?
The critical term said:
“[Otto] hereby agrees to charge any land in which [s]he has any interest…”
“Has any interest”. Did that refer only to land Otto owned at the time she signed the guarantee in 2008? Or her future-acquired property as well?
ASICS argued those words extended to both present AND future property because the guarantee was a continuing one.
Other terms referred to Ms Otto's “continuing obligations” under the guarantee, her company's “future operations” and “present and future liabilities”.
But this argument ignored something rather big...
ASICS’ interpretation, the Court said, "strained" the meaning of the actual words used in the disputed term. Because that term didn’t actually include any future-facing language.
Instead, the Court said a reasonable person would say Otto's promise simply created a charge on any land she “has” - i.e. land she has at the time the guarantee was given.
No more, no less. No ambiguity. No inconsistency. The words were plain and simple. They did not charge any land she would acquire later.
And ironically, the existence of other terms in the guarantee making express reference to future matters actually strengthened Ms Otto’s position (rather than ASICS).
Because the Court said the change in language mattered.
If the drafter (who had clearly turned their mind to future issues in these other terms) intended future-acquired property to be included in the disputed promise, they could have said so. But they didn't!
So in any insurance coverage dispute, it’s imperative to:
- consider the policy as a whole
- apply the actual words used from the perspective of a reasonable person
- pay close attention to any changes in language
Because when policy language changes, meaning often changes with it.
And where an insurer seeks to limit or exclude cover, or qualify its insurance promises, courts (and customers) expect those intentions to be expressed in clear and explicit terms.
25.05.26
POLICY & CONTRACT Interpretation
Muhammad Ali is said to have quipped, “Don’t count the days. Make the days count.”
But what kind of days?
Because in a contract, (like an insurance policy), that question isn’t philosophical. It can decide the outcome of a claim.
A recent Supreme Court decision turned on exactly this issue, across almost 6,600 residential building contracts.
The contracts used both “Days” and “days”.
- “Day” was defined: Monday to Friday, excluding public holidays
- “day” wasn’t defined at all
Both were used throughout, governing critical obligations like:
- when finance had to be obtained
- when work had to start
- when it had to be completed
So did they mean the same thing?
The builder said yes. Their customers said no: the difference was deliberate.
Ultimately, the Court wasn’t convinced by the builder, despite it being their contract.
Applying established principles of construction, it found the reasonable person would conclude the drafting was simply… well, messy.
“Poorly drafted” the judge said. The terms were used “randomly” throughout the agreements.
But the use of the word ‘day’ wasn’t inconsistent with its ordinary meaning.
And when that happens, the reasonable person doesn’t go hunting for hidden intent. They interpret the words in their ordinary sense, in context.
So “days” meant calendar days. The narrower, defined meaning of “Days” didn’t apply where it wasn’t used.
It’s a good reminder of a practical point: defined terms only work if you use them purposefully and consistently. Otherwise, you can lose control of their meaning.
And in contracts… every “day” really does count.
06.05.26
Policy Interpretation
When it comes to policy interpretation, don’t forget the punctuation.
Sounds simple. But how would you answer this:
A builder’s domestic building policy provided cover when the insured “sustained…loss or damage”
It then said:
“This policy covers loss or damage arising from a non-structural defect occurring during the period [of insurance]…”
So what needs to occur during the period?... The damage or the defect?
[Spoiler alert: Court’s decision below! 🙂]
It’s a tricky one. Because the term could be read either way.
And in this very recent decision, the facts were that the (non-structural) building defects occurred during the policy period. But the damage only emerged around 2 years after that period had expired.
To resolve it, the Court examined not only the text of the policy term, but the context in which it was used. Including punctuation.
Because immediately below it sat another term:
“This policy covers loss, damage or expense, from a cause other than a non-structural defect, occurring during the period [of insurance]…”
Two timing clauses. Each pertaining to the covered causes. One term following the other. Both to be read together.
With the second clause containing two additional, (and very important), commas: [one after 'expense'; the other after 'defect']
Why did that matter?
That punctuation proved to be “a significant aid to clarity” for the Court when it came to deciding how to read the first - somewhat confusing - timing term.
When read 'harmoniously' together, the meaning those commas conveyed made it undeniable that it was the timing of the loss, (and not the particular cause), that was the policy’s intended trigger.
Given the overarching insurance promise gave cover when the insured “sustained…loss or damage”, any doubt about that conclusion was quickly cast aside.
The power of punctuation.
So whether you are drafting or interpreting, don’t overlook punctuation. Or context. A Court won’t.
How words and phrases are expressed and work together, as a cohesive whole, is what matters.
03.04.26
Section 54
Powerful. Important.
But not a universal fairness valve.
Section 54 is an insurance game-changer that’s been around in Australia for 40+ years. But it's regularly relied on for things it was never designed to do.
The other week I wrote about a Federal Court decision involving a claim for TPD benefits under an income protection policy.
Here’s what happened...
- The policy required medical certification to be obtained before any TPD benefits were payable.
- So in 2022, the insured obtained a doctor’s certificate stating she was permanently incapacitated for work.
- The insurer accepted this, and paid out TPD benefits from that 2022 date.
- Six months later, the insured's regular treating doctor issued a second certificate stating — in hindsight — that her incapacity had existed since 2021.
The insured asked that her benefits be recalculated from the earlier date.
When the insurer refused, the insured argued (among other things) that section 54 required them to pay, because it was relying on a “technicality” in the policy to deny the substance of her claim.
AFCA agreed.
It characterised her failure to obtain an earlier certificate as an “omission”, found no prejudice to the insurer if the claim was allowed, and said that refusing to pay her benefits from 2021 was not “fair and reasonable”.
But the Federal Court disagreed. And its analysis of section 54 is a timely reminder of what this remedial provision does — and does not — do.
The Court said:
Section 54 requires an analysis of how the policy operates in respect of the claim actually made. Here, the insured was seeking to recast her claim AFTER the fact — something outside the reach of section 54.
Even if section 54 did apply, there was no “omission”: no evidence was put forward to show a permanent incapacity diagnosis could have been made earlier than 2022.
Section 54 also does not operate to overcome restrictions or limitations inherent in the promise of cover provided. This policy made it clear that TPD benefits were only payable once written certification was given by a doctor. This was not a “mere technicality” extraneous to the claim — it was an essential element of entitlement.
In any event, the insurer would have suffered prejudice (and been entitled to reduce the claim), having already paid temporary disablement benefits for the same, overlapping 2021 period.
Section 54 is a powerful provision — but it is not a universal fairness valve.
Whether you work in claims or at the front-end of policy advice, understanding where section 54 stops is just as important as knowing when it might apply.
22.02.26
Policy Interpretation
Who is this “reasonable businessperson” whose perspective is so critical when interpreting insurance terms?
Applying it in practice is often a challenge.
But the guidance from cases — old and new — is consistent.
The lens they apply is objective
They take into account the context of the policy — its text, its commercial purpose
What an individual 'subjectively' intended — what they thought the words meant — is irrelevant
Instead, the reasonable businessperson places themselves in the position of both parties to the deal, reading the language of their bargain dispassionately and impersonally, to give effect to their common intention.
That’s quite the test.
A recent case provides a useful illustration.
An income protection policy included a trigger for TPD benefits called the “Date of Disablement”. It was defined as:
“… the date on which a Medical Practitioner certifies in writing that the Insured Person is permanently unable to work again …”
The insured lodged a TPD claim when a doctor issued a certificate in August 2022 indicating she was unable to return to work.
Several months later, in February 2023, her regular treating doctor issued another certificate stating that — in hindsight — she had been totally incapacitated since February 2021.
So which date mattered?
The date of certification (2022), or the date of the doctor’s belief (2021)?
It was a $36,000 question.
One the insured fought hard to break her way.
Because, after all, she was permanently incapacitated from 2021 and this was exactly what this policy was designed to cover.
However looking through the lens of the reasonable businessperson, the Court held that the coverage trigger of their policy bargain was certification, not the earlier incapacity identified retrospectively.
Why?
Read objectively, the language plainly:
- pointed to a single point in time
- where a particular event must occur — the issue of a certificate
- which had to state, at the time of certification, the insured had the required level of incapacity.
Context also mattered.
This policy contemplated other, less permanent benefits — often paid based on the insurer’s own opinion (not a medical one) — up to the point at which TPD was established.
It therefore made commercial sense for the policy to adopt a clear, singular event — medical certification — to mark the transition from temporary benefits to those for TPD.
Allowing for a retrospectively identified date of incapacity would disrupt that payment structure, blur the boundary between benefit types, and undermine the commercial operation of the policy.
So while it’s sometimes a tough pill to swallow, it’s important to remember that interpretation is not about hindsight or sympathy.
It’s about how the plain language of the parties’ terms operate — viewed objectively — within the commercial machinery of the policy.
15.02.26
Sometimes the real problem with policy terms and endorsements isn’t what’s written...
It’s what’s missing.
In my post last week about "connecting phrases", several people picked up that the exclusion in the ML policy could have been better drafted.
It read:
“We will not cover… any Claim arising from or in any way whatsoever connected with the insolvency... of the company..., its actual or alleged inability to meet any or all of its debts…”
The insurer and insured spent considerable resources, both in and out of Court, arguing its meaning.
In particular, whether the exclusion was missing a word — whether an “or” should have appeared after the comma and before “its actual or alleged inability to meet… its debts”.
Real time and energy — and presumably lots of money —spent by both parties on just ONE word.
The Court concluded that the exclusion had to be interpreted disjunctively — as if the word “or” were present. There was no other commercially sensible way to read it (and ultimately it applied to knock out the claim).
But there’s a broader lesson here.
If you’re drafting or reviewing endorsements or wordings — or advising on them — the goal should never be to rely on a court (or the 'indulgence' of another party) to fix awkward or incomplete drafting after the fact.
It's to say clearly what you mean at the outset, viewed through the eyes of a reasonable businessperson.
Because when wording is clunky or imprecise, expensive disputes like this can (and do) arise down the track.
And that’s bad for everyone.
✨ Remember: drafting that needs explanation has already missed the mark.
03.02.26
Have you noticed how insurance policy drafters keep using the same connecting phrases?
“Arising out of” — “caused by” — “in connection with”
They look interchangeable. They sound similar. They aren’t.
A 2025 court decision on their use in a Management Liability policy gives us a good example.
A company (through its liquidator) wanted to sue underwriters directly in respect of alleged insolvent trading and breaches of duty by its directors, involving debts totalling more than $2.5M.
Underwriters successfully resisted, relying primarily on this exclusion:
“We will not cover… any Claim arising from or in any way whatsoever connected with the insolvency …of the company..., it’s actual or alleged inability to meet any or all of its debts…”
Plenty of connecting language there.
Think of the drafters using those connectors like a drawstring bag. Pull the cord tight in a coverage term, and only claims with a close causal link fit inside. Loosen it, and the opening widens — sometimes dramatically.
In exclusions, the same movement has the opposite effect.
The Court gave helpful guidance on these phrases:
✨ “in connection with” is a flexible phrase covering a spectrum of relationships, including where one thing is simply ‘bound up with’ or ‘involved in’ another
✨ “in any way whatsoever” broadens that reach even further
✨ “arising from” requires a causal connection, but less strictly than “caused by” (it may simply ‘originate in’, ‘spring from’, or have ‘a foundation in’ the specified matter)
So what does this tell us? Connector language helps control how wide the drawstring opens.
• Broad connectors help insureds in coverage terms and endorsements
• The same words can be fatal in exclusions and conditions
Every endorsement typically tightens or loosens the cord. Make sure you know which way it’s being pulled — and why.
26.01.26
Sometimes litigation reveals little nuggets of insurance gold...
Usually when you’re least expecting them.
Take a multi-million-dollar dispute unfolding in Queensland between the owner of a waste facility and its earthworks contractor.
The contractor was engaged for just under $4M. Heavy rain hit during excavation, the site flooded and turned into a putrid “lake”. That triggered an environmental order against the owner — and now almost $31M in alleged losses are in play, with the contractor, insurers (and a broker) firmly in the frame.
The matter seems nowhere near trial, but it surfaced in 2025 through interlocutory decisions about a contractual indemnity requiring the contractor to indemnify for:
“any loss whatsoever arising in the course of the execution of the Works”.
Broad language, argued the owner. The loss occurred while the contractor controlled the site. That should be enough — indemnity likely triggered.
A Supreme Court judge agreed. The Court of Appeal didn’t.
Among other things, it said a coincidence of time and place isn’t enough. The clause requires a connection between the loss and the "execution" of the works — meaning the contractor’s active performance of the work, not just the existence of an obligation to do it.
One word. EXECUTION. Potentially standing between the contractor and a $31M claim.
Of course there’s much more to it — additional allegations, counterclaims and a potential trial still to play out. But here’s the nugget:
Applying contractual language is hard. Even judges disagree.
But insurance advisers and underwriters can’t shy away from contract terms just because they’re difficult. It’s vital to know what to look for — and to recognise when a clause may be quietly expanding the exposure.
And when the wording is wide, open-ended or absolute:
✨ pause
✨ ask: what risks are really being assumed?
✨ push for legal advice before signing
✨ check whether the insurance being arranged actually meets the exposures being agreed — including “quiet” risks like pollution
✨ lay out the insurance options (and gaps) clearly, so the customer can make informed decisions
Ignoring a contract doesn’t make the risks disappear. It simply turns a $3M job into a potential $30M problem — later.
19.01.26
How far does a liability policy stretch?
A surprisingly long way, if the wording says so.
Take this example from the Victorian Court of Appeal (last week).
The insured was in dispute with a property owner over land it leased and had poured $5M+ into over time. It exercised a $9M purchase option, but the owner tried to unwind the sale when it discovered that a director and shareholder of the insured was also its “trusted” adviser and accountant.
The insured sought specific performance of the sale. The owner counterclaimed, seeking to set it aside — and alternatively compensation for breach of duties and unconscionable conduct.
With a real risk that the counterclaim would succeed, the matter settled.
• The insured now agreed to buy the land for $11M
• There was no mention that this higher figure included compensation
• In fact, the trial judge found the increase did not “result from” the compensation counterclaim (because the likely result of the owner's success was the avoidance of the sale)
The extra $2M paid formed the “loss” the insured claimed under its ML policy.
The insurer resisted, arguing:
• the “loss” was not the result of any underlying liability to compensate (independent of the settlement agreement)
• it was instead a commercially renegotiated price to avoid the sale being set aside
And that sounds reasonable. In general.
But the Court of Appeal disagreed.
Because whatever assumptions we may make about liability cover, a policy's true scope lies in its wording.
And the policy promised:
The Insurer shall pay the Loss of any Company arising from Corporate Liability.
Loss meant:
any amount the Insured is legally liable to pay resulting from a Claim, including settlements.
Claim meant:
a civil proceeding (including a counterclaim) seeking compensation or other legal remedy. It also included criminal proceedings and investigations.
📌Those small phrases — “other legal remedy” and “including settlements” — did a lot of heavy lifting.
Because the Court said:
• “other legal remedy” extended the cover beyond mere claims for monetary compensation
• claims for non-monetary relief, such as setting aside a contract, were also covered
• this was supported by the inclusion of criminal proceedings and investigations in the definition — matters which don't always attract money remedies
'Loss' also expressly included *settlements*
So the insured’s liability to pay was indeed a Loss “resulting from” the Claim —
• even though the counterclaim didn’t simply seek compensation
• even though the liability to pay resulted from a negotiated settlement, rather than an independent or underlying liability to compensate a third party.
It was that broad.
The wording is everything in coverage disputes. Terms will be applied according to their meaning and context. Assumptions and the policy's "vibe” have little place.
Precision in language matters.
15.12.25
When it comes to policy terms, don’t fall foul of “magpie syndrome”
Pun intended :)
You know what I mean – honing in on one ‘shiny’ part of a clause or policy while disregarding everything else.
It never ends well.
Last week’s decision from the NSW Court of Appeal is a perfect reminder. The case turned (in part) on what “building” meant in a Business Insurance policy.
A petrol station operator discovered damaged underground pipes during EPA-required upgrade works. The insurer declined the repair claim on a number of grounds, including that the policy definition of “building” didn’t extend to the underground pipework.
The definition was set out in the usual extensive way and listed numerous subparagraphs explaining what "buildings" included.
One stated that plumbing was only included when it was “within the buildings”.
The trial judge took this and ran with it.
Agreeing with the insurer, he found not only that the ordinary meaning of “building” did not extend to items located underground, but that this subparagraph about plumbing reinforced that conclusion.
But the Court of Appeal disagreed.
Instead of being drawn to one shiny subparagraph, it looked at the broader context, including:
• the full definition — which "included” many listed examples, but was not limited to them
• the purpose of the cover — wide insurance for a wide range of circumstances
• other subparagraph examples — which DID include things typically found underground, like foundations, pools and storage tanks
• the inclusion of “structural improvements pertaining to the buildings” — which could readily encompass underground components
The Court also said the ordinary meaning of “building” would include a basement, which is obviously below ground.
The lesson? Context matters. And so does common sense.
One shiny detail is never the whole story.
So whether you’re drafting endorsements or applying policy terms, remember to take a broad, objective view — and resist the urge to swoop on the nearest shiny thing until you’ve stepped back and looked at the whole picture.
30.11.25
Note to self: noting a contract is NOT the same as noting an insured...
Here’s a lesson for young players.
In my research the other day, I came across a recent Court decision that caught my eye — because it appears the insurance professionals involved fundamentally misunderstood how the policy they placed actually operated.
And their mistake left the insured totally exposed… to the tune of hundreds of thousands of dollars.
Here’s why.
The insured had agreed — in a commercial contract — to take out a public liability policy that noted another party as an “additional insured or a person to whom the benefit of the insurance extends…”.
Not an unusual request these days. But was that requirement met?
Unfortunately, no.
A policy was taken out — but it made no mention of the other party as an insured… or at all.
Not in the schedule.
Not in an endorsement.
Not anywhere in the policy terms.
Instead, the brokers arranged for the contract to be “noted and approved” under the policy.
A good move if your aim is for the insurer to cover any contractual liabilities your client assumes. But that wasn’t what the insured was legally obligated to do.
The Court was very clear: the contract required the policy to be extended to cover the other party. And it wasn’t. It only extended cover to the insured themselves.
We don’t know why the mistake was made, or the experience level of the person who placed the cover. But these issues can be tricky — and you're not alone if you’re struggling to make sense of it all.
Mastering these situations requires a solid understanding of insurance policy terms, commercial contract language, legislation (including sections 11, 45 and 48 ICA), the impact of other statutes, and more.
So don’t sit with the uncertainty — reach out to your senior advisers if you’re ever in doubt. No question is a dumb question when you’re dealing with contract and policy terms.
17.11.25
This endorsement is all kinds of wrong...
It was relied upon by an insurer who said any cover available to ACME (not its real name!) was limited to principal’s cover — that narrow protection typically tied to work performed by an insured for their principal.
But it wasn’t to be. And the drafting lessons are important.
✨ First, the endorsement is, well, confusing — even the court that reviewed it, ever so politely, called it “somewhat poor.”
If the intent was only to offer ACME principal's cover, why include a reference to “interested party”?
Perhaps it was to satisfy a market expectation, since the insured had agreed (in a separate contract) to add ACME as an “interested party"… entitled to the benefit of indemnity under Bright Spark’s insurance.
But that obligation didn’t bind the insurer to do so — the endorsement didn’t seem to match the obligation in any event — and so the inclusion of ‘interested party’ on the schedule just set the stage for future, costly dispute.
✨ Second, according to the policy’s original terms:
• ACME automatically had principal’s cover regardless of any endorsement.
• And significantly, the description of “insured” — which extended to “all parties for whom Bright Spark undertakes to insure” – gave ACME a second, *broader* pathway to cover.
Cover that wasn’t limited to any principal’s extension.
Cover that meant ACME was an insured in its own right — for its own independent acts of negligence (happy to explain why — it's an interesting point!)
✨ And then there’s the sting in the tail: the endorsement was added *after* the policy containing these terms was issued.
But insurers can’t unilaterally reduce cover once they've been bound — any adjustment to their legal promises has to be mutually agreed.
So did this endorsement miss its objective? Did it fail to 'mesh' with the policy’s terms? Did its language and timing invite scrutiny and dispute?
Yes, on all counts.
Good drafting is about clarity, purpose and precision. Shortcuts, assumptions, ignorance of the law, and overlooking how existing policy terms interact always lead to problems.
Before adding any endorsement, it pays to stop and ask:
• What is its true function?
• How will it fit with the wording?
• And what language best articulates that intent?
And for anyone who reviews and accepts endorsements for their customers, the same care and questioning matters just as much — for their sake.
05.11.25
Don't assume with policy terms
Last week I was reviewing a cyber policy… and wow — I’d forgotten just how definition-heavy they can be!
There was concern that the insured might not be covered for a social engineering scam that saw them lose a hefty sum. Devastating, really.
Thankfully, the policy did offer an extension for that type of loss — but the insured hadn’t taken it up. So the only chance of recovery was to fit the claim under a separate, broader coverage section.
The problem? The two coverages were expressed to be mutually exclusive, so at first glance it looked like an automatic decline: (socially-engineered loss + coverage extension NOT taken = no cover!)
But this is a good-news story. Because when we broke down the policy and traced through its defined terms, the detail changed everything.
It turned out that, despite the way the loss occurred, cover under the “scam” extension depended on the transfer of funds having been made by an “employee”.
That term wasn’t defined. So — applying first principles — we gave it its ordinary meaning. The person who transferred the funds wasn’t technically employed by the insured, but was authorised to make the payment.
And on that basis, the claim was paid — despite not having the extension.
It made me wonder 🤔 ...
Was that lack of definition a deliberate choice by underwriters — a quiet way to let some social-engineering incidents fall into another coverage “pot”? Or was it a missed control?
Either way, it’s a reminder that assumptions have no place in policy interpretation.
The policy’s power lies in the words that are used — and sometimes, it’s the ones not defined that make all the difference.
(Oh, and yes — there was also a policy term shown in bold but missing from the definitions list entirely… ⚠️ hopefully that doesn’t cause any trouble later!)
11.10.25
What if you promise insurance that can't be obtained?
If your client agrees to take out insurance for another — and they don’t — the fact that it was difficult, or even impossible, to obtain will typically be no answer to a breach of contract claim.
That was the outcome in a 2024 Supreme Court case involving a serious personal injury.
With A and B both responsible, B turned to A’s broadform policy to cover its liability share (almost $230,000). But the policy only insured A.
So B sued A for breach of contract. Based on the promises you see here 👈
As part of its defence, A’s broker gave evidence that he was unaware of any insurer who would have extended A’s policy to cover B for its own negligence, or would have named B as an additional insured:
“…this segment of the insurance market is small.”
🚨 But the Court gave this evidence short shrift, judging it “irrelevant” and “inadmissible.”
Why? Because whether cover was difficult (or even impossible) to obtain doesn’t matter. What matters is the CONTRACTUAL OBLIGATION agreed to by the parties.
So when reviewing customer contracts (or policy wordings for that matter), remember:
• The actual words of the contract always come first.
• Terms are understood objectively, in light of context and purpose.
• If a clause is unambiguous, it will be given its plain meaning. Evidence of “surrounding circumstances” (like cover availability), or what you think a term should mean, is irrelevant.
B was successful in its breach of contract claim.
A was left to pay not only its own share — but B’s as well (an expensive lesson)!
THE TAKEAWAYS:
⭐ Let your clients know the words they sign up to are critical — and will be given primacy in any dispute.
⭐ Encourage them to involve you early in pre-contractual insurance and risk discussions, so you can advise on coverage availability and terms.
⭐ If you’re only involved after the fact (and contractual obligations point to uninsurable risks), flag them immediately to protect your position and help your client understand the insurance exposures at hand.
26.09.25
How did this end up on a policy?
Here’s an endorsement I came across on a liability policy recently:
“Indemnity to Principal: any Principal to whom the Insured is carrying out work and against such claim is brought arising from an Occurrence arising in connection with the carrying out of such work.”
Ummm… sorry?
I can see what the author was trying to do here. But doesn’t it leave you more confused than certain about what’s being offered?
And that’s a problem—because confusion invites dispute.
A few thoughts immediately come to mind when considering this term:
🔹 𝗪𝗵𝗼 𝘀𝗽𝗲𝗮𝗸𝘀 𝗹𝗶𝗸𝗲 𝘁𝗵𝗶𝘀? In trying to mesh the endorsement with the policy’s main insuring clause— (a good thing!)— the author has unfortunately ended up a bit tongue-tied. Effective drafting communicates—clearly, unambiguously, and using ordinary language harmonious with the wording—what cover is being provided.
🔹 𝗪𝗲𝗿𝗲 𝘁𝗵𝗲𝘆 𝗰𝗹𝗲𝗮𝗿 𝗼𝗻 𝘄𝗵𝗮𝘁 𝘁𝗵𝗲𝘆 𝘄𝗮𝗻𝘁𝗲𝗱 𝘁𝗼 𝗰𝗼𝘃𝗲𝗿? The muddled drafting suggests otherwise. And while they may later claim they never meant to provide “wide” or "narrow" principals cover, subjective intention is typically irrelevant. What matters is what’s written—in black and white—in the policy.
🔹 𝗗𝗶𝗱 𝘁𝗵𝗲𝘆 𝗮𝗽𝗽𝗿𝗲𝗰𝗶𝗮𝘁𝗲 𝘁𝗵𝗲 𝗹𝗲𝗴𝗮𝗹 𝘄𝗲𝗶𝗴𝗵𝘁 𝗼𝗳 𝗰𝗼𝗻𝗻𝗲𝗰𝘁𝗶𝗻𝗴 𝗽𝗵𝗿𝗮𝘀𝗲𝘀 𝗹𝗶𝗸𝗲 “𝗮𝗿𝗶𝘀𝗶𝗻𝗴 𝗳𝗿𝗼𝗺” 𝗮𝗻𝗱 “𝗶𝗻 𝗰𝗼𝗻𝗻𝗲𝗰𝘁𝗶𝗼𝗻 𝘄𝗶𝘁𝗵”? These little words can dramatically narrow or broaden coverage. By departing from usual wording, the scope of cover may also have shifted in a way unintended.
✍️ Good drafting starts with a solid grasp of policy contract fundamentals.
It’s not glamorous, but it’s essential.
And like any skill, it can be learned. The more we practise, the better we get — at writing, negotiating or accepting — endorsements and insurance terms that actually get the job done.
This was a valiant attempt... but it misses the mark.
So let’s keep coming back to the tools that build effective policy terms:
• clarity of intention
• expressed in ordinary language
• consistent with the policy’s context and wording
• judged from the objective (reasonable person’s) viewpoint.
19.09.25
What's in a name?
If you work in insurance, you already know: getting the insured exactly right can be harder — and more important — than it looks.
I saw several brokers and underwriters expressing their frustration last week on LinkedIn about a recurring issue: the number of clients — and insurance professionals — who can’t correctly identify the entities they want insured.
Is it a company or a trust? Who’s the trustee? Do they use an ABN?
“This is insurance 101!”, someone commented.
Another admitted, “I always get confused on this.”
And that got me thinking — this is 𝘧𝘶𝘯𝘥𝘢𝘮𝘦𝘯𝘵𝘢𝘭, but it’s also confusing if no one has ever taken the time to explain the basics.
🤔: But surely if you get it wrong, the insurer will just correct the policy?
Well they might.
Courts can order the later insertion or correction of an insured name that was originally omitted or misstated.
In some cases, the insurer may be ‘estopped’ from denying cover due to the parties’ conduct and shared intent.
⚖️ But would you really want to take that risk?
The starting point for interpreting any policy is always the 𝘸𝘰𝘳𝘥𝘴 in the policy itself.
The law of rectification — especially on the grounds of mistake — is complex and, quite frankly, unforgiving.
Australian courts have been very reluctant to depart from written terms — or rewrite them. When they do, the burden of proof is "very heavy". The party seeking the change must prove there was a clear, common agreement between the parties — and this evidence will be intensely scrutinised.
And they're just some of the issues you face if you do make it to court...
🔥 A recent UK case involving a multimillion-dollar fire claim is a stark reminder of the rest.
The BI insurer declined to cover the corporate operator of a hotel because the policy only named the family company that 𝘰𝘸𝘯𝘦𝘥 the extensively damaged building — not their separate company that actually ran the affected business.
The ‘uninsured’ company SUED BOTH THE INSURER AND THEIR BROKER — and all parties endured over four years of litigation, costs and damage.
✅ The bottom line?
We need to ensure, at the time a policy is placed, that insured details are accurately and precisely captured in the wording.
And that starts with a working knowledge of how business structures — like trusts, companies, partnerships & sole traders — operate as 𝘭𝘦𝘨𝘢𝘭 𝘦𝘯𝘵𝘪𝘵𝘪𝘦𝘴 when it comes to insurance contracts.
If you're ever unsure, don’t guess. Reach out for help.
09.09.25
I'm on a mission...
Over the past few weeks, I’ve been preparing four different insurance training workshops for some fabulous broker groups. Very exciting!
But here’s what my preparation (and a deep dive into recent court decisions) has confirmed for me: having a strong grasp of the legal basics — the principles that underpin every policy transaction — can’t be over-emphasised.
I know what you might be thinking: 𝘓𝘦𝘨𝘢𝘭? 𝘛𝘩𝘢𝘵’𝘴 𝘣𝘰𝘳𝘪𝘯𝘨. 𝘛𝘰𝘰 𝘩𝘢𝘳𝘥. 𝘕𝘰𝘵 𝘳𝘦𝘭𝘦𝘷𝘢𝘯𝘵 𝘵𝘰 𝘮𝘦.
But here’s the truth: policies are commercial contracts — legally enforceable agreements governed by our common law (with a smattering of other law thrown in for good measure).
If we don’t invest early in understanding those fundamentals, it should be no surprise that wording disputes keep showing up in our businesses… or worse yet, in our courtrooms.
And trust me — you don’t want to find yourself, or your wallet, in that position!
So let’s stay curious, keep questioning, and take every opportunity to build our knowledge — especially by supporting those just starting out in the industry.
There are plenty of excellent events and learning opportunities out there to help us improve. The more we engage, the better we can serve our clients, grow our businesses, and protect against costly disputes.
02.09.25
Tempted to read the exclusions first? Here's why that's a mistake
Time and again, I hear insurance professionals admit that the exclusions are where they start when trying to work out what a policy covers.
🔹 Sometimes it’s because there is a claims dispute.
🔹 Sometimes it’s to help give clients pre-claims advice.
On the surface, it feels logical. Go straight to the source.
But here’s the problem: 𝐭𝐡𝐚𝐭 𝐚𝐩𝐩𝐫𝐨𝐚𝐜𝐡 𝐢𝐬 𝐟𝐫𝐚𝐮𝐠𝐡𝐭 𝐰𝐢𝐭𝐡 𝐝𝐚𝐧𝐠𝐞𝐫.
𝐖𝐡𝐲 𝐄𝐱𝐜𝐥𝐮𝐬𝐢𝐨𝐧𝐬 𝐀𝐫𝐞𝐧’𝐭 𝐭𝐡𝐞 𝐖𝐡𝐨𝐥𝐞 𝐒𝐭𝐨𝐫𝐲
Here’s the rub.
Our Courts have been very clear: policy terms – just like those found in any commercial contract – must be read 𝑖𝑛 𝑐𝑜𝑛𝑡𝑒𝑥𝑡.
That means insuring clauses and any limiting terms must be read together, in a “harmonious way”, so that “due effect is given to both.”
If you simply concentrate on a single term, in isolation to all others, you’re not seeing the full picture. And that’s a problem.
𝐓𝐡𝐞 “𝐇𝐢𝐞𝐫𝐚𝐫𝐜𝐡𝐲” 𝐨𝐟 𝐏𝐨𝐥𝐢𝐜𝐲 𝐓𝐞𝐫𝐦𝐬
It can be an even bigger problem where exclusions are concerned. And lead to serious mistakes.
⚖️ The NSW Court of Appeal recently reminded us that with policies: “𝑇ℎ𝑒 𝑠𝑡𝑎𝑟𝑡𝑖𝑛𝑔 𝑝𝑜𝑖𝑛𝑡 𝑖𝑠 𝑡ℎ𝑒 𝑖𝑛𝑠𝑢𝑟𝑖𝑛𝑔 𝑐𝑙𝑎𝑢𝑠𝑒.”
And that’s because there is an inherent hierarchy of terms in an insurance policy.
𝐍𝐨𝐭 𝐚𝐥𝐥 𝐭𝐞𝐫𝐦𝐬 𝐚𝐫𝐞 𝐞𝐪𝐮𝐚𝐥.
Why? Because exclusions and limiting terms are intended to qualify or 𝑐𝑎𝑟𝑣𝑒 𝑏𝑎𝑐𝑘 an underwriter’s initial promises of cover.
So how can you truly understand what an exclusion means – what it’s carving away – if you don’t first stop and appreciate what’s been promised in the first place?
👉 You can’t. It’s putting the proverbial horse before the cart.
𝐏𝐫𝐚𝐜𝐭𝐢𝐜𝐚𝐥 𝐓𝐚𝐤𝐞𝐚𝐰𝐚𝐲𝐬 𝐟𝐨𝐫 𝐈𝐧𝐬𝐮𝐫𝐚𝐧𝐜𝐞 𝐏𝐫𝐨𝐟𝐞𝐬𝐬𝐢𝐨𝐧𝐚𝐥𝐬
✅ Never start (or stop) a policy analysis by considering just one term. Looking at one clause in isolation will never give you the full picture.
✅ Always start with the insuring clauses. Limiting terms like deductibles, some endorsements, exclusions and conditions typically only make sense in their context.
✅ In the face of a claim, exclusions only really matter if cover is triggered. That’s why claims analysis must always begin with the insuring provisions.
✅ Underwriters can (of course!) limit cover – but only if their limiting terms are objectively consistent and work harmoniously with other terms in that policy.
✅ Policy arguments based solely on the language of one isolated clause might be a starting point, but there’s more work to do. Courts will always look at the policy contract as a whole, and so should you.
𝐀 𝐂𝐚𝐬𝐞 𝐢𝐧 𝐏𝐨𝐢𝐧𝐭
A recent case shows just how costly it can be to read policy terms in isolation.
At trial, the judge focused solely on the terms of a deductible clause and concluded that only a single $10K deductible applied to a multi-million-dollar property claim involving 120 homes damaged by a hailstorm.
But on appeal – when the policy was reviewed (and the deductible interpreted in the context of the policy’s insuring promises) – the Court found the correct deductible was actually $𝟣.𝟤 𝑚𝑖𝑙𝑙𝑖𝑜𝑛.
That’s a huge difference, and an expensive reminder of why exclusions and limiting terms can’t be read in a vacuum.
𝐅𝐢𝐧𝐚𝐥 𝐓𝐡𝐨𝐮𝐠𝐡𝐭
Insurance policies aren’t designed to be read term by term in isolation. They are sophisticated contracts that must be interpreted using legal principles, including the need to consider 𝑐𝑜𝑛𝑡𝑒𝑥𝑡.
Insuring clauses are ALWAYS your starting point. Only then can exclusions and limiting terms be seen for what they really are: qualifications on an already defined promise of cover.
📘 If you’d like more practical tips, go to the homepage and download our free Tip Sheet: 𝟣𝟤 𝑇ℎ𝑖𝑛𝑔𝑠 𝑡𝑜 𝐶𝑜𝑛𝑠𝑖𝑑𝑒𝑟 𝑊ℎ𝑒𝑛 𝐴𝑝𝑝𝑙𝑦𝑖𝑛𝑔 𝑃𝑜𝑙𝑖𝑐𝑦 𝑇𝑒𝑟𝑚𝑠.