I’ve sat through enough zoning hearings to know how they go. A developer’s attorney stands up with renderings, traffic studies, and a story about “blight” and “revitalization.” Slides. Data. A consultant who was paid six figures to argue that your neighborhood needs their project more than it needs you.
Then a resident stands up. “My grandmother lived in that building for forty years, and the landlord never fixed the heat.” Council members nod. The attorney waits. When the hearing ends, the developer’s narrative wins. Not because it’s true. Because it’s documented, organized, and formatted to fit the process.
Facebook groups don’t fix this. Group chats don’t fix this. What fixes this is a neighborhood archive: a structured, collectively maintained body of documentation that captures the history, conditions, and patterns of your block in a form you can actually use at zoning hearings, in court filings, at city council meetings, and in organizing campaigns. Not a scrapbook. Not a nostalgia project. A tool.
What a Neighborhood Archive Actually Is
A neighborhood archive is a systematic collection of documents, oral histories, property records, survey data, and incident logs that together tell the story of a place from the perspective of the people who live there. It is not a Facebook group, though a Facebook group might be where you recruit people to build one. It is not a university oral history project, though a university might try to partner with you. Think carefully before accepting. It is not a municipal historic designation, though the records you collect might support one someday.
An archive is infrastructure. It is the documentation that lets you walk into a hearing and say, “This is not a blighted block. This is a block where three landlords have received 47 code violations in the last five years, and here are the records.” It is what lets you show a reporter that the property at 1847 Maple was a functioning grocery store before the out-of-state LLC bought it, let it rot, and applied for demolition. It is what lets a tenant association present a pattern of harassment across multiple buildings owned by the same shell company.
The difference between a collection of grievances and an archive is structure. A Facebook group full of photos of illegal dumping is a collection of grievances. A spreadsheet that cross-references those photos with dates, addresses, 311 complaint numbers, and council district boundaries is the beginning of an archive.
Why This Matters for Displacement Fights
Developers and city planners work from a specific kind of evidence. Property records. Market studies. Environmental assessments. Traffic analyses. They have the language of “highest and best use” and “underutilized parcels.” When they describe your neighborhood, they use data collected for them, by people who do not live there, to justify changes that will displace people who do.
Your archive is counter-evidence. It documents what the official records miss: that the “vacant” lot was a community garden until the city sold it without notice. That the “distressed property” was distressed because the landlord stopped paying water bills to drive out Section 8 tenants. That the “underutilized” commercial corridor had twelve Black-owned businesses before the tax increment financing district was created.
When you can present a pattern, across buildings, across years, across landlords, you change the conversation. You are no longer one angry resident. You are a neighborhood with a record. And records are harder to dismiss than testimony, especially when they’re organized in a way that maps to the decision-making process.
Step One: Name and Structure Your Project
Before you collect a single document, decide what your archive is for and who controls it. This sounds obvious. It is the step most groups skip. It is the step that determines whether your archive becomes an organizing tool or a folder of files that sits on someone’s laptop until they move.
Start by naming the project. The name should be specific enough to signal that this belongs to your neighborhood, not to a generic initiative. Avoid names that sound like a nonprofit program. “The Eastside Memory Project” is fine. “The 19104 Block Documentation Initiative” is better because it ties the work to a place that people recognize. If you’re stuck, a fantasy name generator adapted for organizational naming can help you brainstorm options quickly, though the final name should come from the people who live on the block, not from a tool.
Then decide three things as a group: What are you collecting? Who has access? What happens to the archive if the core organizers leave? Write these decisions down. They are your archive’s governance document, and they matter more than any filing system you choose.
For access, the default should not be “everyone can see everything.” Some documentation, like tenant surveys, oral histories about unsafe housing conditions, or records of landlord harassment, contains information that could put people at risk if it ended up in the wrong hands. Plan for tiers: public-facing summaries, internal organizing data, and sensitive materials restricted to a documentation team that has agreed on confidentiality protocols.
Step Two: Start With What You Already Have
Before you design a survey or schedule interviews, inventory what already exists. This will save you months of duplicated work and help you identify gaps.
Check these sources first:
- 311 and code enforcement records: File a public records request for all complaints and inspections at specific addresses over the last five years. These records are public. Your city may charge a small fee, but many waive fees for requests under a certain volume.
- Property tax and ownership records: Your county assessor or recorder of deeds maintains records of sales, transfers, tax delinquencies, and ownership. Look for patterns: LLCs registered to the same agent, rapid transfers, tax delinquencies followed by demolition permits.
- Court records: Housing court filings, eviction records, and small claims cases are public in most jurisdictions. Search by landlord name, not just address, to catch patterns across properties.
- Existing community documentation: Tenant association meeting minutes, block club newsletters, mutual aid distribution logs, community garden sign-in sheets. These are already archives. They just need to be organized.
When you pull these records, do not just save the PDFs. Create a tracking spreadsheet that cross-references addresses, landlord names, violation dates, and outcomes. This is where the archive starts to build power: not in the individual documents, but in the patterns they reveal when they’re organized together.
Google’s Site Reliability Engineering practices offer a useful framework here. The SRE book’s approach to tracking incidents and building a “postmortem culture”—systematically documenting what went wrong, when, and why—translates directly to how a neighborhood archive should treat housing violations. Each code violation, each eviction filing, each instance of landlord neglect is an incident. The SRE book’s chapters on incident tracking and data integrity lay out principles for ensuring that what you document is accurate, consistent, and useful for pattern analysis, not just collected and forgotten.
Step Three: Conduct Tenant Surveys That Build Power
A tenant survey is one of the most powerful tools in a neighborhood archive, but most surveys are designed wrong. They collect data without building relationships, and they end up as spreadsheets that no one uses.
Here is what a survey that builds power looks like:
Purpose is stated upfront: “We are conducting this survey to document housing conditions in our building and organize for repairs. Your responses will be shared only with the tenant association. We will not share individual responses with the landlord, the city, or anyone else without your permission.” Say this on the survey itself, and say it out loud when you knock on the door.
Questions are specific and evidence-oriented: Not “Do you have maintenance issues?” but “In the last 12 months, have you submitted a repair request that was not completed within 30 days? If yes, what was the repair, when did you request it, and what happened?” The second question produces documentation you can use in a housing court filing or a code enforcement complaint. The first produces a vibe.
Survey is conducted in person: A Google Form sent to a building where half the tenants don’t have reliable internet is not a survey. It is a filter that excludes the people most affected by the conditions you’re trying to document. Knock on doors. Bring clipboards. Offer to help people fill it out if they want help. Come back if someone isn’t home.
Results are shared back: This is the step that separates organizing from research. After you collect surveys, hold a meeting where you present the findings to the people who participated. “Here’s what we found. Here’s what we’re going to do about it.” This is how surveys build trust and recruit new members. It is also how you catch errors. Someone will tell you that the repair request was actually 90 days, not 30, and that correction matters.
Store the survey data in a way that protects individual tenants. Use initials, not full names. Keep the master file in a shared, access-controlled account that at least two trusted organizers can access, not on one person’s personal computer. Back it up.
Step Four: Record Oral Histories Before They Walk Out the Door
Every neighborhood has elders who remember what the block looked like before the highway came through, before the factories closed, before the first “revitalization plan” displaced the first family. Their memories are archives. And they are leaving, through displacement, illness, and death, on a timeline that does not wait for your organizing capacity to catch up.
Oral history interviews are not complicated, but they require preparation. Here is a basic protocol:
Get consent in writing. The interviewee should know what the interview is for, where it will be stored, who will have access, and whether it will be shared publicly. Give them the option to restrict access for a certain number of years. Respect it.
Prepare questions in advance, but follow the conversation. Start broad: “How long have you lived on this block? What was it like when you first moved here?” Then get specific: “Do you remember when the grocery store on the corner closed? What happened?” Let people tell their own stories. Do not interrupt to fill silences.
Record audio, not just notes. Use your phone if you have to. Test the recording before you start. Keep a backup. Transcribe the interview as soon as possible, within a week, while context is fresh. If transcription is a barrier, there are free tools that can help, but review the transcript yourself for accuracy.
Connect the oral history to the physical records. If someone says, “The landlord started pushing people out in 2003,” go check the property records. If they say, “There used to be a laundromat on Maple,” check the business license records. Oral histories point you to documents, and documents confirm or complicate what people remember. Together, they are stronger than either alone.
Step Five: Organize the Archive So It Can Be Used
An archive that can’t be searched is not an archive. It is a pile. Here is a simple structure that works for neighborhood documentation projects:
Master address file: Every property in your focus area, with columns for owner name, LLC registration, sale dates, code violations, eviction filings, and notes. This is your central reference. Everything else links back to it.
Incident log: A chronological record of specific events. A no-heat complaint. A demolition permit application. A tenant’s eviction filing. A code inspection failure. Each incident links to an address and, where relevant, a landlord. This is where patterns become visible over time.
Oral history collection: Audio files, transcripts, and summaries, indexed by interviewee and topic. Create a simple index that lets you find every interview where someone mentions a specific landlord, building, or event.
Document repository: PDFs of code violations, court filings, property records, 311 complaints, and correspondence. Name files consistently: Address_DocumentType_Date. If you have 200 files named “scan1.pdf” and “doc_final.pdf,” your archive is useless.
Public-facing summaries: One-page briefs that synthesize findings for specific campaigns. “Landlord X owns 14 buildings in our ward and has received 89 code violations in three years.” These are what you hand to a reporter, a council member, or a judge.
Keep the archive in a shared, access-controlled space. Google Drive works if your group is small and trust is high. If you are dealing with sensitive information, like tenant names, immigration status, or details about unsafe conditions, consider whether a commercial cloud service is appropriate. The NIST Cybersecurity Framework offers a structured approach to identifying, protecting, and controlling access to sensitive information, and its Quick Start Guides are designed for organizations that don’t have dedicated IT staff. You don’t need to implement the full framework, but the principles, knowing what data you have, who can access it, and how you protect it, apply directly to a neighborhood archive that contains information about vulnerable residents.
Step Six: Turn the Archive Into Action
An archive that is not used is a museum, and museums do not stop displacement. Here is how to turn your documentation into campaigns:
At zoning hearings: When a developer proposes a project, pull the archive for every property in the footprint. Present the history: what was there, who was displaced, what code violations exist on adjacent properties that the developer’s “market study” ignored. Bring the oral histories. Bring the code violation records. Bring the survey data. Format your testimony to match the hearing structure, written comments, exhibits, speaker sign-ups, but lead with the evidence your archive provides that the developer’s does not.
At city council meetings: Use the archive to identify patterns that council members should be accountable for. “Council member, your district has 23 properties owned by LLCs registered to the same address in Phoenix. These properties have received 156 code violations in the last two years. What is your plan?” This is not a question the council member can answer with a form letter. It is a question that comes from documentation.
In tenant organizing: Use the archive to show tenants in a building that they are not alone. “Your landlord also owns these three buildings. Here’s what tenants in those buildings have documented.” Pattern evidence turns individual complaints into collective action. It is the difference between one tenant filing a complaint and a tenant association filing a petition.
In media campaigns: Reporters need stories, but they also need evidence. When you can hand a reporter a one-page brief with specific addresses, violation counts, ownership records, and quotes from oral histories, you make it easy for them to write a story that names names. Easy stories get written.
What to Watch For
Archives have risks. Here are the ones I’ve seen play out:
One person holds everything. If the archive lives on one person’s laptop and that person moves, gets burned out, or has a falling-out with the group, the archive is gone. Maintain at least two copies with at least two trusted people. Document the structure so someone else can navigate it.
Sensitive information gets exposed. Tenant surveys, oral histories, and incident logs often contain information that could put people at risk. Undocumented residents. Tenants in retaliation-prone buildings. People who have experienced violence. Build access controls before you collect the data, not after.
The archive becomes the organizing. Documentation is a tool, not the goal. If your group spends all its time maintaining files and no time knocking on doors, the archive has become a substitute for organizing, not a support for it. Set a regular cadence: collect, then act. Document, then organize.
Outsiders want to “help.” Universities, foundations, and consultants will offer to partner with your archive project. Some of these partnerships are genuine. Many are extractive: they want your data, your stories, and your community’s legitimacy for their own projects, and they will offer “expertise” in exchange. Before accepting help, ask: Who owns the data? Who gets credit? What happens when the partnership ends? If the answers are not clear and in writing, do not accept.
The Long View
An archive is a bet that your neighborhood has a future worth documenting. It is also a bet that the people who live there now are the ones who should control that story. Not developers. Not consultants. Not a city department that files your history under “blight.”
The neighborhoods that win displacement fights are not always the ones with the most money or the loudest voices. They are the ones with the best records. They are the ones who can walk into a hearing and say, “We know what happened here, and we can prove it.”
Start small. Start with one block, one building, one landlord. Start with the 311 records you can pull tomorrow and the tenant survey you can design this week. Start before the elders who remember leave. Start before the developer’s attorney finishes their slides.
Your neighborhood has a history. The question is whether you will document it on your own terms, or let someone else write it for you.