| Demand137 | Is this route viable at launch, and at what frequency? | Demand vectorised by origin, timing, purpose, and price sensitivity for that specific city pair | The route sized to the demand that is there, not the comparator route's demand |
| Demand137 | When to grow, hold, or withdraw an existing route | Current performance against the vectorised demand case, not load factor alone | The network change timed to the evidence, not the review calendar |
| Demand137 | How much destination value does the route deliver? | Route demand connected to accommodation, event, and investment signals in the destination | Incentive funding tied to destination value, not passenger volume |
| Demand137 | Should we commit airport incentive or public co-funding? | A bounded case with a stated counterfactual and downside | Funding committed only where it demonstrably changes the outcome |
| Demand137 | Is the extra daily frequency worth committing now? | The daily case from month six, subject to a load-factor trigger, net of the added capacity cost | The frequency released on a trigger, not a hope |
| Demand137 | Can this work for a route with no comparator anywhere? | Built up from origin-market and destination-side signals, not borrowed from another city pair | No dependence on another route looking similar enough |
| Signal137 | What did the route we supported actually deliver? | Attributed destination value against the case that funded it | The renewal negotiated from evidence |
| Signal137 | Did the incentive buy anything? | The route's result set against the counterfactual of no support | Public money is not spent on demand the market would have delivered anyway |
| Both | Does this need airline booking data we cannot share? | No. Route demand vectorised from destination-side and market signals | The airline's data is not a precondition |
| Both | Who holds this, and where? | Model, data, and a trained team inside your jurisdiction | The capability survives the change of planner or official |