Typhoon weeks need a different ops narrative

Hong Kong operators know typhoon weeks by feel. Boards still ask for numbers. The mistake is forcing those numbers into the same monthly operations reporting template used for calm weather.

Frame the window first

A seasonal disruption report should lock start and end timestamps against the weather markers your ops desk already tracks. Without that lock, recovery hours leak into the following week and the story becomes a blame map.

Tell recovery separately from cancellation

Cancellation totals alone do not show whether the base recovered with overnight banks, cancelled second waves, or borrowed capacity. Recovery hours deserve their own ledger line so directors can see cost in operational time, not only in flights lost.

Crew duty spillover is optional — and powerful

When duty data is available, spillover after the weather clears often explains the second-day mess better than the storm itself. When it is not available, say so; inventing spillover is worse than omitting it.

Content Nesthub writes typhoon packs as event narratives first, scorecards second. If you are briefing a live window, mark the contact form accordingly so we acknowledge the same day.