| Demand137 | Where the next edition should sit in the rotation | Delegate yield forecast for each candidate host, tied to the delegate base's actual travel patterns | A host sequence built on demand, not convenience |
| Demand137 | How big a room block to commit to before registration opens | Forecast delegate volume by origin, stay length, and price sensitivity | A room-block negotiation backed by a tested forecast, with rate leverage kept |
| Demand137 | Whether to keep, retire, or relocate a recurring congress | The next edition modelled under each option, with the counterfactual stated | A renewal decision the board can defend to members and sponsors |
| Demand137 | What relocating will cost in returning delegates | Repeat-attendance patterns by host, edition over edition | The relocation is priced before it is agreed |
| Demand137 | What happens if nothing changes? | Base, downside, and supported scenarios with a stated counterfactual | The cost of habit is visible alongside the cost of change |
| Signal137 | What did the last edition deliver, and to whom? | Attributed delegate spend, room nights, GVA, and sponsorship value, net of displacement | The board sees attributable value, not gross activity |
| Signal137 | Did the programme change buy anything, or was it the venue? | Edition-over-edition comparison on one method, with the driver named | The next programme decision is made on what worked |
| Signal137 | What do we tell sponsors and members the congress delivered? | A traceable path from registration data to attributable value and stated legacy | A sponsorship pitch that survives the first hard question |
| Signal137 | What did the host city gain, in terms the city will recognise? | Room nights, GVA, tax, and jobs attributed to the congress, on the method cities use | The bureau and the board read from the same number |
| Both | Who holds this, and where? | Model, data, and a trained team inside your jurisdiction | The evidence survives the change of PCO or board |