Filter:
Overlays: | Marker color = top issue at that property. Marker size = count of interviews.
In partnership with
Howard County Community Voices

Interviews from your neighbors

Everyday Canvassing knocked on doors across Howard County and listened. This is a map of what renters and neighbors told us about housing, schools, safety, costs, and community life, gathered from hundreds of face-to-face conversations. It is built with the hope that anyone can explore it. But we are always trying to improve, so please email us at tino@everydaycanvassing.org if you think we can make it better. This is a living site: interviews still in review join the map as they are approved.

Why we made this

People’s real experiences are powerful evidence for what Howard County needs. We made this site so residents, neighbors, and decision-makers can see those experiences clearly: what people are worried about, what is going well, and where things differ from one community to the next.

How we used AI

We removed names, phone numbers, emails and addresses from interview records before any AI was used, and caught and removed the few that residents said out loud during cleaning, before anything was published.

We used Claude, a large language model, to help in two ways with this work. Everyday Canvassing’s Howard County team checked Claude’s work before anything went online.

Coding this site: Our team decided what the site should show and how it should work, then Claude wrote the code for this site, and Everyday Canvassing reviewed each version before it was published.

Preparing the interviews: People at Everyday Canvassing checked each interview 4 - 6 times. Claude was one of the checks in our interview cleaning process. It suggested details to remove that could allow someone to identify a resident just from their anonymous interview, made formatting and punctuation consistent, and drafted summaries of long interviews. Our admin team reviewed every interview and summary against the original and rewrote anything where Claude had changed a resident’s story or way of speaking. Absolutely none of our interviews were AI generated. You can read each step of our interview editing process under “How we cleaned it,” further down this page.

How to use it

Map
See every apartment community we visited as a dot on the map. Bigger dots mean more conversations there. The color shows the topic people talked about most. Click a dot to read what neighbors said at that location. When you pick a topic from the filter at the top, the dots resize and recount to show how many conversations at each place were about that topic, and places with none fade back.
Find a property
Looking for your own community? Use the “Find a property” box to search by name and jump straight to it.
Stories
Read the conversations as individual stories, in residents’ own words. You can filter to a topic you care about.
Insights
See the big picture: which topics came up most, and how people felt about each one. Each bar shows the mix of concern, mixed, and positive feeling, plus a gray part for people who raised the topic without saying how they felt about it. The length of the whole bar is how many interviews raised the topic at all. Click a bar to see the exact numbers.
Distinctive Voices
A closer look at individual perspectives that add something important to the picture.
Policy Asks
What Everyday Canvassing believes the data points toward. These are our reading of what we heard, to be checked and prioritized together with the people most impacted. They are not words we are putting in residents’ mouths.
Note: the topics and the “concern / mixed / positive” labels are Everyday Canvassing’s interpretation of what people said. Someone else might sort them differently. The residents’ own words are theirs; the labels are ours.
What is on the map right now. Our canvass dataset holds 721 records. 573 published interviews appear on this site today. Of the rest: 15 are awaiting final review and will join when approved, 2 are held for translation review, 55 were excluded or withdrawn (duplicates, non-interviews, and requests we honored) but stay in our internal count, and 76 are contacts that produced nothing to publish, such as declined conversations or flyer-only visits. We publish these numbers so our map does not claim more than or less than we collected.
Is your interview on this site? Every story carries two links: one to be named publicly if you want credit for your words, and one to have your interview taken down. We verify every request before acting on it. You can also write to tino@everydaycanvassing.org.
Media inquiries: Tino Fragale (he/him), tino@everydaycanvassing.org.
How the data was collected, cleaned, and categorized

How we collected it

Everyday Canvassing went door to door across apartment communities in Howard County and talked with residents in person. Canvassers asked open questions about life in the county, such as housing, schools, safety, costs, transportation, and what people would change. People answered in their own words, and a few basic details were noted when residents chose to share them, like age range and whether they rent. Taking part was voluntary, and many conversations happened in languages in addition to English.

How we cleaned it

Before anything went online, every interview was prepared so it would be safe to publish. We removed personal details that could identify someone, such as names, phone numbers, email addresses, and apartment or unit numbers. Where a resident said their own name, we still removed it, because a stranger reading the site should not be able to attach a name to a story. When we took something out, we left a marker in its place, like “[name removed],” so you can see that a detail was protected without seeing the detail itself. Where a passage of a recording was hard to hear, we say so in the text with markers like “[unclear]” rather than guessing. Interviews held in other languages are translated by people, not just software, and labeled. When what you are reading is a canvasser’s written summary rather than a recorded conversation, a badge on the story says so.

We also separated canvassers’ own side notes from what residents actually said, so the published text is the resident’s voice and not staff observations. We corrected the spelling of apartment community names so each place shows up once on the map instead of several times, and we placed each community using a verified address unassociated with a person’s home. Age was recorded two different ways during collection, as ranges and as exact numbers, so we put everything into the same set of age ranges.

In total, we checked and cleaned each interview 4 - 6 times. The first check occurred when each interview was first collected. Our team of staff canvassers flagged sensitive information and corrected mistyped notes. The second check came from our admin team where we redacted flagged sensitive information, corrected more mistyped notes, deleted notes that were not captured well enough to be understood, and deleted all contact info, names, and address info before proceeding to check 3. The third check ran the double-checked interviews without contact info, names, or addresses through a large language model to suggest further removals of information that may look harmless but when pieced together could reveal enough information about any individual that they could be identified by a neighbor, co-worker, boss, or otherwise. When information is pieced together to identify and target a person, this is called “mosaic re-identification.” The third check also standardized formatting and punctuation across all our interviews so they were easier to read, and helped us build short summaries of the long-form interviews where we did not already create them. In the final fourth check, our admin team studied each interview adjusted by a large language model to make sure each interview still maintained the original stories and conversational style of each person we interviewed. When the large language model did not maintain the original story or style well, our admin team revised each interview to make sure they used the original wording of the people we interviewed. We also removed or generalized sentences in interviews in order to reduce the possibility that any person we interviewed could be identified by anyone who is not themselves. Some interviews went through several re-checks of our admin team to ensure the people we interviewed could not be easily identified by the pieces of info they shared in their interview, and that the interview maintained what the people interviewed actually said.

How we categorized it

To make patterns visible, we tagged each interview with the topics it touched on. There are 29 topics, grouped into 8 broader areas. For each topic in an interview, we also marked whether the resident’s assessment of that topic came across as concern, mixed, or positive. Where a resident expressed no view on a topic, we record no sentiment rather than guessing. Our rule was simple: if we could not point to specific words in the interview that supported a tag, we did not apply it.

Note: The topics and the concern, mixed, and positive labels are Everyday Canvassing’s reading of what people said. Another person might sort the same words differently. The residents’ words are theirs; the labels and groupings are our interpretation, which we think makes the bigger picture easier to see.

Who we spoke with

What Howard County Residents Are Saying

Themes and clusters across 573 published interviews (from 721 records collected), with sentiment distribution. Tap a bar for the exact counts.

Four sections below. Each one opens and closes. Click the section, or the Hide / Show button at the right of the heading.
How Howard County residents feel about each topicHideShow

These charts answer to the filters below. Turn on a race and ethnicity, language, or age filter to redraw them for that group; the outline behind each bar stays at the rate across all 573 interviews. The same filters also move Explore Stories and Top issues by property below, and the controls are repeated there. They are one set of filters, shown in three places.

Cluster Prevalence with Sentiment

Clusters are groups of related themes. The number counts every interview that raised at least one theme in the cluster, so a cluster is always at least as large as any single theme inside it. Because residents often raise several themes at once, the clusters add up to more than 573.

concern mixed positive raised, no sentiment recorded
Theme Prevalence with Sentiment

The same eight clusters again, opened up: each heading below is a cluster, and under it are the themes it is made of. Themes are counted the same way as the clusters, so the number is every interview tagged with that theme. A cluster's own count is smaller than its themes added together, because one person often raises several themes inside it. Gray means the person raised the topic but no sentiment was recorded for it, which is why the colored part of a bar can be shorter than the whole.

concern mixed positive raised, no sentiment recorded
Compare who raised each topic by race and ethnicity, language, or ageHideShow

Pick a topic and a way of grouping people. Each row is the share of that group who raised it, so groups of different sizes can be compared; the vertical line is the rate across all interviews. This is the one section on the page the filters do not move: it compares the groups to each other, so filtering it to one group would leave nothing to compare.

concern mixed positive rate across all interviews

Groups smaller than 10 people show their count but no percentage, and a sentiment split needs 10 rated mentions before it is drawn. A share built on a handful of people looks precise and is not. Every group is listed either way, including the small ones, because leaving communities out of the picture is its own kind of error.

Explore Stories by Theme and Property NameHideShow

Open a theme to see which communities raised it and how residents felt. Open a community to read the stories behind the numbers. Prevalence is shown as “interviews raising this theme, out of all interviews at that community.” With a filter on, every count and every denominator here is that group only, and opening a theme or a community after changing a filter shows the rebuilt list.

Top issues by propertyHideShow

The issues raised most often at each community. With a filter on, each card counts only the interviews that match it. Communities with two or fewer interviews are grouped into one card per city.

Distinctive Voices

Fourteen interviews that carry disproportionate analytical weight, selected from the expanded 2026 dataset. Each represents a specific policy frame or finding. Tap any voice for the full narrative.

Policy Asks by Cluster

The most actionable findings, organized by issue cluster. Each ask traces to specific respondent language in the dataset. This is our reading of what we heard, to be checked and prioritized together with the people most impacted.

About the highlights

Asks marked Priority are the ones the Horizon Foundation and Everyday Canvassing believe should be tackled first.

A highlight does not mean more residents asked for that specific remedy. Counting how often each individual ask came up is a separate piece of analysis we have not done yet. The asks within each cluster are not ranked.