- What counts as bankable
- Only money that beats the pilot's control weeks: the same room types, the same weeks of the year, one priced by the engine and one by the old sheet, read from the PMS night audit and the channel manager, never from the engine's own forecast. Until those 8 weeks are read, the tracker banks a fixed share of each claim: ×0.5 on revenue and cost saved, ×0.4 on loss prevented, ×0 on hours.
- When
- Phase 3 of the roadmap: auto-publish on C/D dates with control weeks, gate RevPAR index ≥ 103 against control. A lane moves from claimed to bankable the month finance signs its control-week read-out, and the claimed figure is retired at the same time. Nothing is bankable in shadow mode.
- What never counts
- Hours saved (166 h a year here) stay in hours until a cost line leaves the P&L. A dashboard of steps taken is not value. Revenue the engine would have earned on a night the sheet also filled is not loss prevented; only nights the sheet sells out 2 weeks early qualify.
- Why one AI cost
- ฿450K to build and ฿406K a year to run, charged in full against year one (฿856K) and never spread across the lanes. ROI is contribution ÷ that cost; payback is the months of contribution needed to repay it.
- What is not in here yet
- The deck's package margin (breakfast, Mekong dinner, festival nights) is claimed on the slide but not in this tracker: the engine ranks packages but does not yet model attach rates, so it waits for POS data. Everything on this screen is synthetic until the hotel's exports arrive.
Baselines frozen 20 October 2026 from the hotels' night-audit reports. Blended commission 9.7%; variable cost THB 380 per room sold.