Week 5 · Physical climate risk

Portfolio edition: Kith Climate cohort case, fictional client. Report date 16 October 2026.

Supporting evidence

Small grey tags are references to the project record: A- an assumption (assumption ledger, page 08), DR- a data request (page 11), D-5- a decision, DP- a data-plan item.

Physical climate risk for Northwood: method note (v1)

This note explains how the Week 5 physical-risk figures are built, so that Northwood can check, update or re-run them without Kith. It goes with the dashboard (my-work/week-5/fund-level/physical-risk-dashboard-v1.html), the assumption ledger (my-work/week-5/fund-level/leave-behind/assumption-ledger-v1.csv), the reference-data index (my-work/week-5/fund-level/leave-behind/reference-data-index-v1.csv), the result files in data/, and the re-run note (my-work/week-5/fund-level/leave-behind/re-run-note-v1.md). Every number on the dashboard is a row in one of those files; this note does not restate them.

1. What question each figure answers

The work answers Sarah Mitchell's three investment-committee questions for all ten portfolio companies:

  1. What could one bad event cost before exit? Gross loss in a named event, who pays it (insured, retained, next renewal), and what it does to covenant headroom.
  2. What does physical risk cost on average each year, and is that rising? Expected loss over each company's hold, and the recurring cost at exit on today's climate and on the buyer's horizon.
  3. Will the companies stay insurable at an acceptable price? The premium path above a 3% non-climate trend, in the current and a hardened market, and the retained loss a captive could pool.

For each material risk the lever library gives a dollar value protected, a cost, the timing against the exit date, and a named Northwood owner.

2. Dating convention

3. The chain: hazard, exposure, vulnerability, cost

The analysis starts from what each company depends on, not from hazard scores.

Vulnerability register. One row per dependency: each own site, each supplier, each client base, the workforce where heat matters, and shared infrastructure (Bowling Green's water). Each row carries:

The data room's 1 to 5 hazard scores are the "before" picture only.

Hazards and regions. There are seven hazards: hurricane, flood, winter and ice, extreme heat, wildfire and smoke, drought, and severe convective storms. There are six regions: Gulf coast, Southeast Atlantic, Central Valley, Southwest, Mountain West, and Ohio Valley and Mid-Atlantic.

Exposure rules.

Vulnerability.

Cost. Loss is contribution never recovered, plus the cost of recovery.

4. Who pays

No insurance schedules are in the data room (data request DR-1), so each company has a programme synthesised by rule (A-17 to A-21):

A hardened-market toggle doubles deductibles, sets the named-storm deductible to 5%, halves flood sublimits and removes contingent cover. After a claim, the next renewal steps up by 10 to 25% (A-23).

Insured and retained each report their own range, because cover only triggers in the worse cases. Gross = insured + retained holds within each case.

Covenants.

5. Recurring cost and exit value

Recurring cost a year at exit is the sum of four parts:

It is shown on two horizons: the hold, to each exit, and the buyer's horizon (about 2035 to 2040). It is also multiplied by each company's exit multiple, as value a buyer may normalise away. One-off event cash and recurring cost times the multiple are always shown apart.

6. Presets, the do-nothing figures and the builder

Presets. Seven presets are fixed settings of the same engine:

  1. Gulf landfall
  2. Southeast Atlantic landfall
  3. Sterling superalloy supplier outage, 26 weeks (D-5-67)
  4. Central Valley drought, two seasons
  5. Ohio Valley and Mid-Atlantic winter storm
  6. Southwest heat summer
  7. Hold-period "do nothing"

The do-nothing preset shows two figures that are never added together:

Why events more frequent than 1-in-10 are left out. The hazard intensities, downtime and supplier-outage ranges are only defined at 1-in-10, 1-in-50 and 1-in-100, so anything more frequent would be extrapolation with nothing to calibrate it. Routine weather that recurs every year is already in the trailing-twelve-month EBITDA the model measures against, so counting it again would double-count. The companies' own reported events were replayed at 1-in-10 severity and the seven tested all passed, so the 1-in-10 point matches the size of the events they actually have. And it is the rarer events that drive covenants and value at exit. The result is a lower bound: the frequent band and the tail beyond 1-in-100 would both add to it.

The builder reads a precomputed grid. Hazard-led settings cover hazard × region × severity × length × market (768 plausible settings). Dependency-led settings cover each site and supplier × 2 to 26 weeks × market (2,020 settings). The page looks results up and does no arithmetic of its own (D-5-12).

7. Calibration

Nine events the companies reported for 2023 to 2026 were replayed through the engine with their actual sites, hazard, storm length and a severity fixed before the replay (1-in-10). Modelled lost-plus-delayed revenue was compared with the reported figure. A pass is 0.5 to 2 times (A-33). The results are in my-work/week-5/fund-level/leave-behind/data/calibration-groups-v1.csv.

An independent check (my-work/week-5/checks/chk_calibration_band.py) re-derives every replayed figure without using the engine.

8. Levers

Each lever in my-work/week-5/fund-level/leave-behind/data/levers-v1.csv names the input it changes and a cost range (A-35 to A-39, A-50; Akron's HVAC cost is seeded). The engine is re-run with each lever applied, for the lever's companies only (my-work/week-5/fund-level/leave-behind/data/lever-results-v1.csv).

For each lever:

Two portfolio overlays sit beside the levers:

9. How far to trust it

10. Limitations

11. Portfolio edition addendum: the arithmetic the dashboard v3 adds (November 2026)

Sections 1 to 10 are the method as frozen on 16 October 2026, and every figure they describe is unchanged. For the portfolio edition, Daniel Vetsko lifted the no-recalculation rule for Week 5 only (P-30) and approved new views on the dashboard (P-31 to P-33). Each view is a stated step on figures the engine already stored. None of them feeds back into a stored figure.

To re-run all of it, run python3 my-work/portfolio/week-5/build-week5-portfolio-v2.py from the repository root. It reads the frozen Week 5 files and the data room, never edits them, and rebuilds delivery-v2/. The dashboard's Appendix B shows how the build fits together, the controls at each step and where there are none, and the flagged assumptions.

Checks and review. my-work/portfolio/week-5/checks/chk-v3-derived-v1.py recomputes every figure above independently in Python, from the frozen data and the data room, and compares it with the text the page renders (review/render-text-v1.py). The portfolio-edition judgments (the buyer's years, city-centre placement, the break-even hold fallback, headcount weighting) are listed in dashboard-v3/portfolio-assumptions-v1.csv. The November 2026 fact-check, client-voice and process reviews, with what was done about each finding, are in review/review-findings-v1.md.

Review round 1 additions (November 2026, decision P-37).

Provenance: rendered for reading from my-work/week-5/fund-level/leave-behind/method-note-v1.md (frozen at G2/G3 on 16 October 2026; sha256 108627d5feb0), with the portfolio wording fixes listed in the portfolio changelog. Raw file: data/method-note-v1.md.