Cities Are Racing to Build Equity Dashboards. Most Will Look the Same.

Cities and public agencies are publishing more tools to help people explore inequities. The interface often starts to look familiar: a map, filters, charts, and a menu of indicators.

That format can make information easier to find. It does not, on its own, make information easier to understand, or worthy of trust.

The difference is in the decisions behind the screen. Which questions does the dashboard answer? Who helped choose the measures? Can a resident see what the data leaves out? And is there a clear connection between a pattern on the map and a public decision?

Recent work from Washington, DC, Seattle, and the U.S. Department of Health and Human Services offers useful examples. Each tool takes a different approach. Together, they show why equity dashboard design is not decoration around the data. It shapes how people read the data and what they can do with it.

Three tools, three useful choices

Washington, DC, added resident stories to its Racial Equity Dashboard. The September 2026 update increased the number of key indicators from 29 to 37 and added a Racial Equity Stories page. The District says community input helped shape eight new measures, including household wealth, childcare affordability, access to banking, and access to full-service grocery stores. The stories bring residents' experiences alongside the quantitative indicators.

That pairing matters. A measure can show where a condition appears or how it varies. A resident's account can help explain what that condition means in daily life. Neither replaces the other. Read the District's announcement and explore the DC Racial Equity Dashboard.

Seattle's Racial and Social Equity Index takes a shared, geographic approach. The city says it created the index in 2017 through collaboration across departments. It combines demographic information with measures of socioeconomic and health disadvantage, mapped at the census-tract level. City departments use it to identify geographic priorities for programs, planning, and public investment. In August 2026, Seattle announced that the index had received Esri's Special Achievement in GIS award.

The award recognizes the work; it does not, by itself, prove that a tool has improved community outcomes. The more practical lesson is that the index was built for use across departments and connected to resource decisions. See Seattle's description of the index and award.

The HHS Office of Minority Health launched OMH DRIVE in September 2026. It uses American Community Survey data to present indicators related to education, housing, economics, language, and resources. Users can filter by population group and geography, compare data across groups, locations, and years, and export charts. Its user guide documents the available measures and filters; the launch announcement explains its purpose.

These examples do not prescribe one ideal dashboard. They make different choices about context, collaboration, and exploration. That is the point: a useful dashboard is built around the decisions its audience needs to make, not around a default set of charts.

The same interface can tell different stories

A map can focus attention on a neighborhood. It can also make a rough estimate look precise. A filter can let someone explore a dataset. It can also leave that person to guess what a category means.

A chart can compare two measures. Without a clear definition, it may not tell a reader whether they are looking at a count, a rate, or an estimate. A map shaded by a single index can be easy to scan and hard to interpret if the components, geographic unit, or limitations are hidden.

These are design questions with real consequences for how the information is read. Before publishing, make the essentials visible:

• Name the measure. Define what it counts and how it is calculated.
• Show the geography and date. Make clear what area and time period the display covers.
• Explain uncertainty and missing data. Don't present a proxy or incomplete measure as a direct observation.
• Offer more than color. Use labels, patterns, or text so that meaning does not depend on color alone.
• Make the source easy to check. Link to the data and the method, not just a summary of the result.

These are practical checks, not a promise that every limitation can be solved in the interface. Some data will be incomplete. Some measures will be too broad to answer a local question. The reader should be able to see those limits before drawing conclusions.

Trust starts before the map

People are more likely to question a dashboard when they cannot tell who selected its indicators, whose experience is missing, or what happens after a disparity appears on screen. A polished interface cannot answer those questions for you.

Start by asking community members which conditions they want to understand and what local terms they use for them. Then document why each indicator was selected, where the data came from, and what the measure does not capture. Build in a way for people to add context or point out a mismatch between the display and their experience.

DC's new indicators were shaped by community input, and the Stories page brings resident experience into the tool. That is a concrete example of adding context to data, rather than expecting a chart to speak for itself. It does not mean a dashboard captures every perspective. The same question applies to any project: whose experience is represented, and how can someone correct or add to the picture?

Design for the people who need to use it

For community builders and organizers, a dashboard may need to serve residents, advocates, agency staff, and decision-makers. They may arrive with different questions and different levels of familiarity with the data. A tool designed for one expert user may be difficult for everyone else to use.

A useful first test is to ask someone outside the project team to answer three questions:

1. What does this measure show?
2. What does it not show?
3. What could someone do with this information?

If they cannot answer, the next step may not be another chart. It may be a clearer label, a short explanation, a different comparison, or a conversation with the people the data describes.

Language access belongs in this test, too. A language toggle is a start, but the explanations, chart labels, navigation, and source notes should all be usable in the languages your audience needs. In English and Spanish, that means writing for clarity in both, not simply swapping words.

A map should leave room for questions

At TresPies, we build equity data and mapping projects with attention to sources, confidence, and how people will use the work. The Madison Equity Data project includes an atlas and policy maps for Dane County. Its maps cite sources, carry confidence ratings, and are available in English and Spanish.

That approach is one way to make the choices behind a map more visible. A confidence rating does not remove uncertainty; it helps show where it exists. A source link does not settle every question; it gives readers a place to start checking.

An equity dashboard should help people see a pattern, understand its limits, and decide what question to ask next. A map can open that conversation. It cannot replace it.

If you are building an equity atlas, neighborhood map, or public data tool, bring the question you need it to answer and the data you have. TresPies can help assess the sources, shape the design, and identify what needs to be clear before the work goes live. Our research and equity data work includes neighborhood maps, equity atlases, and bilingual design for community builders.