| Signal137 | What did the event actually change, net of what would have happened anyway? | Gross activity through counterfactual, displacement, and leakage to attributable retained value | The legacy figure is built to survive the first hard question |
| Signal137 | How much of the spend left the local economy? | Leakage through non-local suppliers and contractors, traced and stated | The share the local-benefit test cares about is known, not assumed |
| Signal137 | Did the event grow the economy or rearrange it? | Displacement against known local spending patterns | Growth and reshuffling are two numbers, not one |
| Signal137 | How do we report the legacy to funders, council, or the public? | A result stated as attributable, with the counterfactual made explicit | A claim an auditor or journalist cannot unpick in one question |
| Signal137 | Can this be done for a first edition with no baseline? | Comparable events, markets, and destinations, with a wider uncertainty range stated | The result says so rather than hiding behind false precision |
| Signal137 | How does this event compare with others in the calendar? | Attribution on one consistent method across every event | Events compared on a shared basis, feeding the portfolio decision |
| Signal137 | What if the result shows less than was claimed? | The result reported as found | A bounded, defensible result is worth more to a funding decision than an inflated one |
| Demand137 | Whether to host again, or renew the agreement | The next edition modelled on the last one's attributed result, with the counterfactual stated | The renewal negotiated from evidence, not precedent |
| Demand137 | What would the next bid deliver? | Base, downside, and legacy-backed cases, net of displacement | The funding position set before the announcement |
| Both | Who holds this, and where? | Model, data, and a trained team inside your jurisdiction | The capability survives the change of official or consultant |