How downtowns are starting to tell the impact story.

Most districts are still figuring this out.

One thing that came up openly in this conversation is that most teams are somewhere in the middle of working it out. Some feel they can partially quantify impact. A few have a more defined approach. Most are in between, with numbers in hand that do not fully answer the question they are being asked.

That gap, between what we can measure and what we actually want to understand, is where most of the work is happening right now. It is less a tooling problem than a translation problem. It changes how you write the report, who reads it, and what gets done with it next.

Three shifts that are quietly changing how impact gets reported.

None of these are dramatic. They are quiet adjustments in how districts present numbers, and how stakeholders read them. Together they are doing the work that a single, more precise figure used to be asked to do alone.

The shifts only land when the practical side is set up for them.

Once a district decides to report a range, pull multiple signals, and add context, the next problem is operational. Some of the data you most want is the hardest to get, and the workarounds are quieter and more relational than they look from the outside.

A lot of the friction here is not effort or attention. It is access. Spending data from third-party providers is expensive and often lagging. Surveys depend on people remembering and reporting accurately. Local businesses are often hesitant to share their own numbers, even when a stronger collective story would benefit them too. That tension makes it tempting to either chase the perfect dataset or give up on the harder questions and stick to what is easy to count, and most teams sit somewhere uneasily between those two.

What you are usually up against in practice:

• Third-party spending data that is expensive, lagging, or both.
• Self-reported numbers that drift from what people actually spent.
• Businesses that worry about what gets shared, even anonymized.
• Internal pressure to deliver a clean figure for stakeholder decks.
• The temptation to over-explain uncertainty until the report stops landing.

What is actually working in the field is unfussy, and that is part of why it works. Asking simpler questions. Making it easier for people to respond. Letting businesses know in advance that you will follow up, so the email does not feel like an audit when it lands. In many cases, just building the relationships so that information starts flowing without needing to be pulled. The teams that get clean reads year after year are usually the ones who have done that relationship work upstream, before any survey ever went out.

What tends to land:

• Short surveys with three or four questions, repeated across events.
• A heads-up email to businesses a week before you ask for numbers.
• A standing thank-you back to people who shared, with what you did with it.
• Trend reads across multiple events, not single-event one-shots.
• A short paragraph of context attached to every figure that goes external.

Want to explore this further?

This was the second part of our roundtable series, where we moved from measuring perception to talking through how to communicate impact.

You can watch the first session here and the second session here. If you want to go deeper on this, Josh Yeager from Bright Brothers has put together a thoughtful white paper on the topic that is worth a read.