| Demand137 | Where to concentrate or spread visitor demand across districts | Place-level demand and capacity, not a citywide average | Events and marketing go where the place can absorb them |
| Demand137 | Whether a new event, venue, or development is worth the disruption | A public value case stating cost, return, and displacement at district level | A funding position the council can hold under scrutiny |
| Demand137 | When capacity pressure will bite, and where | Forward demand and pricing signals for hotels and short-term rentals, by area | Room to act on licensing or capacity ahead of the peak, not after the complaints |
| Demand137 | What a short-term rental rule would do to the district | The yield, displacement, and fiscal effect of each licensing level | Rules tested against the system before they are signed |
| Demand137 | What happens if we do nothing? | Base, downside, and supported scenarios with a stated counterfactual | The cost of waiting is priced alongside the cost of acting |
| Signal137 | Is growth reaching the local economy, or leaking out of it? | Retained value by district and by sector, with the leakage named | A local benefit case built on the same evidence as the growth target |
| Signal137 | Which neighbourhoods are absorbing the pressure? | Event cadence, accommodation pressure, and resident sentiment, street by street | Growth and pressure weighed where they actually land |
| Signal137 | What did last year's calendar deliver, district by district? | Every event ranked on jobs, tax, GVA, and retained value, on one method | The events that pay back are supported, and the mix is optimised |
| Signal137 | What do I tell the council at year end? | Monthly, seasonal, and annual roll-ups across the whole place | One account of what the visitor economy delivered, not five departments' versions |
| Both | Who holds this, and where? | Model, data, and a trained team inside your jurisdiction | The capability survives the change of officer or consultant |