Week 5 of 6, Climate Work Residency

Physical climate risk

What could hurricanes, floods, drought, heat and storms cost Northwood's ten companies before each exit, and what should Northwood do about it?

$18.2M'Do nothing' over the hold, range $6.6M to $40.7M: a stress scenario of two severe events plus chronic cost to each exit, with no return period; ranges do not add across columns or companies
$6.04MExpected loss a year, range $1.95M to $13.1M: events at or rarer than 1-in-10 on today's climate; likely understated, since routine weather already in earnings is left out
$11.1MLargest single-scenario loss, range $4.66M to $21.0M: a two-season Central Valley drought at Harvest Ridge; flags a modelled covenant breach in the central and high cases (covenant assumed)

Highlights

Dashboard

Seven scenarios a reader can step through, from the event to the dollars and the buyer's years, with case and insurance switches.

Open (opens in a new tab)

The four answers

Our number and its range, what Northwood does next, our weakest assumption and the data we would ask for first, in a few pages.

Open (opens in a new tab)

Lever results

Each possible action re-run through the engine, with value protected, cost, timing against exit and a verdict.

Open (opens in a new tab)

The case

Northwood needed a defensible number for physical climate risk before each exit. I built a register of 223 dependencies across all ten companies, a scenario engine and a dashboard where a reader can step from an event to what a buyer would see.

The answer is three ranges that are never added together: $18.2M if Northwood does nothing over the hold (a stress scenario), $6.04M a year of expected loss (likely understated) and $11.1M for the largest single scenario. The weakest assumption is the insurance programme, so the first ask is each company's insurance schedule. Gross loss does not depend on it; who pays does.

All deliverables

Each opens in a new tab, in the Kith Climate style it was delivered in. Some pages open with a key to small grey record tags (A- for an assumption, DR- for a data request, D-5- for a decision); they let a reader trace each statement to the project record.

Show all 13

Data and method

The method notes, data and re-run steps that let the client reproduce the work without us.

Show all 14

How it was built

My part

  • I challenged the builder's claim that the 138 coordinates were only city-level; the course slides said otherwise. I reversed the call, and 13 conflicts between company statements and flood maps became findings.
  • I set the scope to all ten companies, asked for a scenario builder alongside pre-set scenarios, and ruled that upside and downside are shown gross and never netted.
  • I decided which hazards to include (adding convective storms) and which switches the builder needed.
  • For this portfolio, I had the expected loss restated as a lower bound (likely understated) and the $18.2M as a stress scenario, not a probability.

The AI's part

  • Claude built the register, the scenario engine, the dashboard and the twelve pages.
  • Claude synthesised the insurance programme and the other missing inputs, and listed each as an assumption or data request.
  • Claude wrote the independent check scripts and ran the reviewers.
  • Claude's own wrong premise about the coordinates and some claims it added itself (for example that each step was checked before the next) were caught in review and corrected.

Across the engagement

From Week 4. Week 4's exit timing and hold years per company set the periods over which Week 5 adds up loss. Week 5 covers physical hazards only; Week 4's $13.5M a year covers all exposure lines including customer what-ifs, so the two headlines are not comparable.

Into Week 6. Week 6 took the expected loss over the hold ($12.6M, range $4.0M to $26.8M) into the LP (investor) climate report and the board pages. The $18.2M stress scenario is a different measure and is not used there.

Week 4: Materiality and initiativesWeek 6: Disclosure as a service