Week 8: Law, liability and insurance after a strike

Why "no one is at fault" doesn't mean "no one pays" — and why the payer depends on which document you read, not on fault in the everyday sense.

12 April 2027

Open the slides

“Who’s liable for a kangaroo strike” sounds like one question. It’s actually four, and casual conversation collapses them into each other constantly: who’s at fault, what does insurance cover, who’s contractually liable, and what does it actually cost. Each has a different answer, decided by a different document, and a proposal that treats them as one question will misread all four. This lecture works through each in turn, using one jurisdiction — New South Wales — as the running example throughout, because liability rules for roads authorities are not uniform across Australia and a proposal has to name which one it’s arguing under.

Property damage and personal injury are answered by different schemes#

These are not two flavours of the same claim — they are two entirely separate schemes, triggered by different facts, and a strike that damages a vehicle and injures a passenger produces two claims under two different policies, assessed against two different sets of rules.

Coverage, exclusion, excess and evidence#

Whether a direct animal strike counts as “not-at-fault,” what excess applies, and whether it protects a driver’s no-claim discount are not settled by the fact that an animal was involved — they’re settled by whatever the policy’s own clauses on claim classification, excess, and discount protection actually say, and those vary between insurers and policies. Reading which clause actually applies to what happened, rather than assuming “animal was involved” activates one uniform kind of cover, is the single most useful habit this lecture can give you. Below are two fictional clauses from the same fictional policy, doing two different jobs: one decides which cover applies, the other decides what that means for fault and excess. Treating the first as if it answers the second is a common and avoidable mistake.

Fictional teaching contract excerpt — not a real insurer’s policy:

Comprehensive Motor Policy, cl. 4.2 (Animal Strike). We will pay for loss or damage to Your Vehicle caused by a direct collision with an animal, provided the Vehicle was being driven in accordance with this policy at the time. This cover does not extend to damage arising from an attempt to avoid an animal that results in loss of control, which is covered under cl. 4.1 (Single Vehicle Accident) instead.

Comprehensive Motor Policy, cl. 4.3 (Claim Classification). Where a loss is assessed as falling under cl. 4.2 (Animal Strike), the claim is classified as not-at-fault for no-claim-discount purposes and the standard excess of $500 applies, unless Our assessment finds that You failed to take reasonable care in the circumstances, in which case cl. 5.1 (At-Fault Excess) applies instead.

Notice what these clauses actually do between them: cl. 4.2 decides whether an event is an Animal Strike loss at all (“hit the animal” versus “swerved and crashed avoiding the animal” are the same event from a road-safety perspective and different clauses from a claims perspective); cl. 4.3 is the separate clause that then decides fault classification and excess for an Animal Strike loss. A policy without something like cl. 4.3 would leave those two questions genuinely unanswered by cl. 4.2 alone — which is exactly the gap a careless reading papers over.

Rental vehicles change the document, not the physics#

A rental agreement is not a comprehensive motor policy wearing a different name — it’s usually a separate damage-waiver arrangement with its own excess, its own exclusions, and its own claims process, often administered by the rental company rather than an insurer the driver chose. A driver’s own personal comprehensive policy frequently does not extend to a vehicle they don’t own, which means the rental company’s own paperwork, not the driver’s usual insurer, is the document that actually governs a strike in a hired car.

Fictional teaching rental agreement excerpt — not a real rental company’s terms:

Rental Vehicle Agreement, cl. 9 (Damage Waiver). Subject to payment of the Damage Waiver Fee, Our waiver of Your liability for damage to the Vehicle applies with an excess of $2,750 per incident, except where the damage results from reckless or negligent driving, driving outside the permitted road types listed in Schedule 2, or a breach of any other term of this Agreement, in any of which cases the waiver does not apply and You are liable for the full cost of repair.

Reading this the same way as cl. 4.2 above: it tells you the waiver applies unless one of the listed exceptions is met — it doesn’t, by itself, tell you whether swerving to avoid an animal counts as “reckless or negligent driving.” That’s a factual judgement the rental company’s assessor makes from the specifics of what happened, not something the clause decides in advance.

Road authority liability: the actual-knowledge standard#

Whether a road authority itself can be liable for not fencing or signing a known hotspot is governed, in New South Wales, by the Civil Liability Act 2002 (NSW), s45 — “Special non-feasance protection for roads authorities.” Under that section, a roads authority is not liable for failing to carry out, or to consider carrying out, road work unless it had actual knowledge of the particular risk that caused the harm. General awareness that kangaroos exist in a region is not the same as actual knowledge that this specific stretch carries an elevated risk — the standard is particular, not general. This rule only exists in its current form because of Brodie v Singleton Shire Council [2001] HCA 29, the High Court decision that abolished the older blanket “nonfeasance immunity” road authorities used to enjoy and made something closer to ordinary negligence principles apply to them in the first place — s45 is the (narrower) protection Parliament wrote back in afterward. Both the wording of the standard and the fact that it is one state’s statute, not a national rule, matter for anything you argue from it.

Three fictional cases#

Case A — Own vehicle, direct strike. A driver hits a kangaroo on a rural road in their own, comprehensively insured vehicle. Significant vehicle damage, no other vehicle involved. The direct collision plausibly falls under cl. 4.2 (Animal Strike) above — but cl. 4.2 only decides which cover applies, not fault or excess. Nothing in the facts given suggests the driver failed to take reasonable care, so cl. 4.3 above points to a not-at-fault classification and the standard $500 excess. That conclusion comes from reading cl. 4.2 and cl. 4.3 together, not from cl. 4.2 alone.

Case B — Rental vehicle, single-vehicle accident. A visiting driver in a rental car swerves at an animal, loses control, and damages the vehicle without striking anything. This is governed by the rental agreement’s cl. 9 (Damage Waiver) above, not the driver’s personal policy — they may not have one that extends to a hired car at all. Swerving to avoid an animal and losing control isn’t, on these facts alone, the same thing as “reckless or negligent driving,” so cl. 9’s waiver plausibly still applies, subject to its $2,750 excess — but that’s the rental company assessor’s call to make from the specifics, not something this clause settles by itself.

Case C — Alleged authority knowledge. A driver argues the road authority “must have known” about a well-known hotspot on a specific stretch, and that failing to install fencing or signage there was negligent. No record exists showing the authority had particular knowledge of that stretch — only that kangaroos are common in the region generally. Under the s45 standard as described above, general regional awareness is unlikely to meet the actual-knowledge threshold; this is illustrative reasoning about how the test works, not legal advice about how any real dispute would resolve, and the rule described is specific to NSW.

What claims data does and doesn’t tell you#

An insurer’s claims record is a record of who chose to lodge a claim, not a census of every strike that occurred — the same reporting-bias logic Week 3 applied to police and ranger records applies here too, for a different reason (an owner might not claim on a minor scrape to protect a no-claim discount, or might claim on a rental precisely because it isn’t their own excess). Treating claims volume as a direct proxy for true incidence repeats the exposure-adjustment mistake this unit keeps returning to, just wearing an insurance-industry data source instead of a ranger-patrol one.

Where this goes next#

Once a strike has happened, the questions in this lecture are all about apportioning cost after the fact. Week 9 is about the minutes during and immediately after a strike — what a driver should actually do, independent of who ends up paying for anything.

A note on today’s date. This session lands on the same day Assignment 1 is due — 2027-04-12, 12:00, worth 40%. That deadline hasn’t moved and nothing in this week adds to it; it’s mentioned here because it’s real, not because the coincidence is being used to sneak in extra work.

Reading#

Civil Liability Act 2002 (NSW), s45, “Special non-feasance protection for roads authorities” (AustLII, accessed 2026). Brodie v Singleton Shire Council [2001] HCA 29, full judgment via AustLII. Read s45 first — it’s short — then skim the Brodie headnote for why the section exists at all.