How Downtowns Are Telling the Impact Story

Outlook

How downtowns are starting to tell the impact story.

Even when the numbers don’t fully add up yet.

If you work in a downtown district, you probably already know this feeling. You wrap up an event, you pull together the numbers, attendance looks solid, foot traffic is up, everything seems like it went well, and then someone asks you what the actual impact was. That is usually where things get a little uncomfortable, not because there was no impact, but because it is surprisingly hard to explain it in a way that feels clear and complete.

Visitor enjoying a downtown district event in the evening

Why this matters

The basics still answer the easier question, not the harder one.

Attendance, foot traffic, and online performance are the easy half. Whether people actually spent money, whether they were already going to be there, and whether the event changed how they see the district sit in the harder half. That gap is where the work is now.

Why This Matters

Where Teams Are Three Shifts What Is Hard, What Is Working FAQs

Why This Matters

Where Teams Are Three Shifts What Is Hard, What Is Working FAQs

Why this question is getting harder

Most teams already have the easy half of the answer.

Across districts, the question around ROI is coming up more often, and in a much more direct way than it used to. People want to understand what changed because of an event, what value it created, and whether it actually made a difference beyond simply bringing people in for a few hours.

Most teams already have a strong handle on the basics. They can tell you how many people showed up, how busy the area was, and how things performed online. The trouble is that the answer most stakeholders want sits one layer below that. Did people actually spend money. Were they already planning to be there anyway. Did the event change how they see the district. Did it give them a reason to come back.

A lot of this comes back to how people experience a place, whether they feel comfortable, whether they feel like they belong, and what they take away from it. There is not always a clean way to measure that, and yet it is often the layer that decides whether a stakeholder calls a season successful.

A downtown street after an event, where the question of impact starts to surface

Where most teams are right now

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.

Colleagues discussing belonging survey results in a meeting

Three shifts

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.

Shift 01

From a single number to a range

The familiar approach gives you one figure for total impact. It usually comes from multiplying attendance by self-reported spending, with a few assumptions stacked underneath. The number looks precise. The uncertainty behind it is invisible.

•A range names the conservative estimate and the upper bound out loud.
•It separates new visitor spending from spending that was going to happen anyway.
•It changes the conversation from defending a figure to explaining what it means.

Shift 02

From one signal to many

No single signal carries the whole story. Foot traffic, surveys, online behavior, search trends, website visits. None of them is decisive on its own. Read together, when they all start pointing in the same direction, they become a sturdier picture than any one of them could be alone.

•Build a shortlist of three or four signals you can pull every time.
•Treat agreement across signals as the read, not any single line item.
•Note when signals disagree. That is usually where the real story is.

Shift 03

From a number to a number with a story

A number on its own can mislead if no one explains the conditions around it. Weather, timing, budget, what else was happening in the city. All of these reshape how a result should be read. A short paragraph of context does more for credibility than a third decimal place ever will.

•Put the conditions into the report alongside the number.
•Use prior years as orientation, not as a target to beat.
•If a result needs an asterisk, put the asterisk there. People notice when you do.

What is hard, what is working

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.

Make impact reporting feel doable, not heavy.

We help downtown teams set up the signals, the surveys, and the context that turns a number into a story stakeholders trust.

Walk through your reporting setup

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.

Where this leaves us

The work is not just collecting the data. It is explaining it.

Numbers do not speak for themselves. They need context, they need explanation, and they need to sit inside a larger story that the people reading the report can actually follow. If you are working through this in your own district, you are very much not alone in it.

What is the one figure stakeholders are going to ask about, and what context does it need to land?

Which two or three signals can you pull every time, so they can be read together?

Who on the team is going to write the paragraph of context that travels with the number?

Frequently asked questions

A lot of teams build a sturdy enough story without one. A short, well-designed visitor survey gets you self-reported spending with a known caveat. Pair it with foot traffic, business outreach, and a year-over-year comparison, and you have a defensible read for most stakeholder conversations. The third-party feed is nice to have. It is not the line between credible and not credible.

It can feel that way at first, but the experience of teams that have switched is that stakeholders generally read it as honesty rather than weakness. The range gives you room to name the assumptions out loud, and it shifts the conversation from defending a figure to explaining how it was built. Most stakeholders are not asking for false precision. They are asking for something they can stand behind.

Three or four is usually right. Foot traffic, a short visitor survey, one online signal (search trends, website visits, or social), and a business pulse if you have the relationships. The discipline is to use the same shortlist each time, so trends become readable. Adding signal number five rarely helps if it makes the others harder to maintain.

Almost always through relationship rather than a survey link. Tell them in advance you will be following up. Tell them what you are asking for and what you will do with it. Show them what came of the last round. Aggregate and anonymize before anything goes external. The first ask is the hardest. The second is much easier if the first one was handled well.

Usually it has three things. A short range or set of figures rather than a single decimal-place number. A paragraph of context underneath each figure naming the conditions that shaped it. A short closing section that says, in plain language, what the team thinks the result actually means and what they plan to do differently next time. The report is shorter than people expect, and it is read more carefully than a longer one would be.

Continue reading.

Outlook · Global

WCUDF 2025: Key Insights & Global Urban Trends

READ NOW

Outlook · Operations

Hidden Costs of Not Using a District-Specific CRM

READ NOW

Outlook · Events

Key Placemaking & Downtown Conferences to Attend

READ NOW

Working through this in your own district?

Tell us where it is getting stuck. We will share what is landing for others.

TALK TO AN EXPERT