| Demand137 | Where to add capacity, a route, or room supply first | Demand broken down by origin, timing, and purpose, not a single total | Investment sequenced against where demand is forming |
| Demand137 | When to move on price, promotion, or scheduling | A forecast that updates as source-market and booking-window signals shift | The adjustment made inside the window that still matters |
| Demand137 | How to defend a demand assumption inside a business case | A vectorised forecast with a stated confidence range, not a single-line projection | Demand assumptions a finance committee can stress-test |
| Demand137 | What would change this forecast? | The specific factor behind each vector named: a capacity cut, a rival host, a competing venue | A forecast that can say what would move it is a working model, not a guess with a date on it |
| Demand137 | How far ahead is this reliable? | The horizon stated explicitly for the market and signals available | The decision is scoped to the horizon the evidence supports |
| Demand137 | What happens when a shock hits? | The affected vectors flagged and re-run, not the whole forecast quietly abandoned | The forecast survives the shock because it names which part was hit |
| Signal137 | Was last year's forecast right, and where was it wrong? | The forecast checked against what landed, vector by vector | The discrepancy reported, not backfilled |
| Signal137 | Which of the streams we forecast actually arrived? | Origin, stay, and purpose attributed against the forecast | The next forecast starts from what the last one got right and wrong |
| Both | What data do you need from us? | Much of it built from public, licensed, and third-party signals; yours sharpens specific vectors | Nothing moves until it is scoped |
| Both | Who holds this, and where? | Model, data, and a trained team inside your jurisdiction | The capability survives the change of official or consultant |