I wrote the forecast change note to `output/drivers-note.md`. It uses the script's figures, saved in `output/drivers.json`. The script's check passed: the six driver deltas sum to the EBITDA change.

**Headline:** Current EBITDA is $303K against $452K in Prior, a change of ($149K), or (32.9%).

**Walk:**

| Step | Amount |
| --- | --- |
| Prior EBITDA | $452K |
| Active customers | ($133K) |
| Revenue per customer | $0 |
| Gross margin | $39K |
| Headcount | ($54K) |
| Cost per head | $0 |
| Other opex | $0 |
| Current EBITDA | $303K |

**What changed:**
- **Active customers** fell from 46 to 44 in all 12 months. This is the largest move, and it also takes revenue down by ($509K).
- **Gross margin** rose from 26.2% to 26.6% in all 12 months, which gives back $39K.
- **Headcount** rose from 23.00 to 23.75 FTE in 9 months, which costs ($54K).
- **Revenue per customer, cost per head and other opex** did not change.

The data shows how much each driver moved EBITDA, but not why. The note asks the owner of each changed driver which documented assumption supports the change. It gives no reasons of its own.

The note's data line reads `drivers_fy2026.csv, 144 rows, sha256 704c929028e8`.