Ciudad Nezahualcóyotl, Estado de México — June 2026. Twenty-three neighbors sit in a circle of plastic chairs in a concrete courtyard off Avenida Chimalhuacán. The youngest is fourteen. The oldest, seventy-one. Taped to the wall in front of them, a sheet of butcher paper holds a hand-drawn map of Colonia Benito Juárez. Every block is there. Every corner store. Every house where someone died of COVID in 2020. Every lot where a landlord jacked the rent more than forty percent in the last year and a half. By any cartographic standard, the map is a mess. The scale wanders. Streets bend where they ought to run straight. The legend uses three marker colors because that’s what somebody brought. But it is the most accurate record of this neighborhood that exists.
No municipal agency made it. The last official census missed this colonia by at least four hundred households—organizers went door to door with their own clipboards in 2024 and counted the gap themselves. The planning department’s digital map still shows empty lots where families have lived for a decade. When the state refuses to see a place, the people who live there get two choices: accept invisibility and all the harm that comes with it, or build their own record. In Neza, they built.
What the State’s Data Erases
Ciudad Nezahualcóyotl—Neza, if you live here—holds over a million people. It is one of the biggest municipalities in the Estado de México. Residents built most of it themselves, starting in the 1940s, on the drained bed of Lake Texcoco. For decades, the official story treated Neza as a problem: a chaotic periphery, a zone of irregular settlement, a place defined by what it lacked. That story shaped policy. Infrastructure arrived late. Services got negotiated block by block. The municipal cadaster, the official property registry, still does not reflect who actually lives on thousands of parcels.
In 2023, the current administration launched a “digital modernization” of its urban data systems. It hired a Mexico City consulting firm to run a socioeconomic survey. The firm used satellite imagery to estimate housing density and a mobile app to collect household data. The app needed a stable internet connection and a smartphone with a recent operating system. In Colonia Benito Juárez, where plenty of families stretch prepaid data on older devices, the surveyors simply skipped the blocks where the app failed. The resulting dataset showed lower population density exactly where organizers knew overcrowding was worst. That dataset now guides infrastructure investment decisions.
“They showed up with their tablets and their logos,” says Mariana Sánchez, a longtime resident and member of the Colectivo de Memoria Vecinal. “Fifteen minutes on our block. Talked to two people. Left. Then the map said we had half the people we actually have. When we asked the planning office, they told us the methodology was ‘statistically valid.’ Valid for who?”
The Documentation Assembly: A Method Born of Necessity
The Colectivo de Memoria Vecinal came together in early 2024. A wave of rent hikes and eviction threats made one thing clear: the neighborhood’s story—who lived here, for how long, under what conditions—was not recorded anywhere that counted. The group started with a simple question. What do we know that the state does not? The answer turned out to be almost everything.
They developed a practice they now call the Documentation Assembly. It is not a focus group. It is not a participatory mapping workshop run by an NGO. It is a structured, recurring community process that produces a parallel record—one you can cite in policy disputes, share with journalists, and use to pressure municipal agencies. Over eighteen months of trial and error, the method settled into three components.
1. The Collective Timeline Workshop. Every two months, the colectivo holds a three-hour session. Participants sit in a circle. A facilitator—rotated among trained neighbors, never an outside expert—works through a set of prompts: “When did you first notice rents climbing on your block?” “What year did the water pressure drop?” “Who remembers when the colectivo route changed?” Answers go onto large sheets of paper, arranged chronologically, then cross-checked. Disagreements do not get resolved by majority vote. They stay as contested entries. The timeline now reaches back to 1985. It holds entries on infrastructure failures, landlord tactics, police raids on street vendors, and moments of collective resistance.
2. The Voice-Note Archive. Many residents, especially older women and people who work long hours, cannot make it to assemblies. The colectivo set up a WhatsApp line where neighbors can send voice notes describing problems, memories, or observations. A rotating team of three volunteers transcribes each note, tags it by theme—rent, water, transit, health, policing—and enters it into a shared spreadsheet. The archive now holds over six hundred entries. It is searchable by date, block, and topic. When a municipal official claims there is “no record” of a problem, the colectivo can pull a dozen voice-note entries documenting it across multiple years.
3. The Hand-Drawn Block Map. Every six months, small teams walk their assigned blocks and update a paper map. They note changes: a new informal business, a demolished house, a family that moved out, a landlord who subdivided a lot. The maps are not georeferenced. They do not play nice with GIS software. But they are legible to the people who made them, and they carry information—like which landlord owns which properties under which names—that the official cadaster deliberately hides. When the colectivo put its 2025 map next to the official one in the planning office, the discrepancies stared back. The planning staff could not explain why their map showed a vacant lot where the colectivo’s map showed twelve households.
From Memory to Policy Leverage
The colectivo’s first real test arrived in March 2025. The municipality announced a “regularization” program for informal settlements, promising legal titles to long-term occupants of irregular parcels. But the eligibility criteria demanded proof of continuous residence since 2010: utility bills, tax receipts, official correspondence. Many families in Colonia Benito Juárez had none of these. They paid for water through informal arrangements. They never got property tax bills because the cadaster did not recognize their homes. The program designed to help them was about to shut them out.
The colectivo responded by assembling a “community residency dossier” for each affected household. The dossiers pulled together timeline entries, voice-note transcripts, and block map annotations to establish continuous residence. They included sworn statements from neighbors, photographs of family events dated by the clothing and hairstyles visible in them, and records of children’s school enrollments at the local primaria. The colectivo submitted forty-seven dossiers to the municipal housing office. After three months of pressure—including a public assembly where residents read their dossiers aloud—the office agreed to accept community-generated documentation as supplementary evidence of residence. Twenty-three families got titles. The rest are still waiting, but the precedent stuck.
“The policy didn’t change because we asked nicely,” Sánchez explains. “It changed because we showed up with a record that was more detailed than theirs. They couldn’t say the data didn’t exist. It existed. We had it. They just hadn’t collected it.”
The Discipline of Structuring Raw Story
What the colectivo learned through practice is that raw community memory, however rich, is not enough. A hundred voice notes about rent hikes are powerful, but they turn into policy ammunition only when they are tagged, dated, cross-referenced, and retrievable. A hand-drawn map is evocative, but it becomes a counter-document only when it is updated systematically and presented alongside the official version. The work is not just collecting stories. It is structuring them so they can travel—into a housing office, a journalist’s notebook, a lawyer’s brief.
This is the same discipline that makes any story-generation tool useful, whether it is a neighborhood assembly’s butcher-paper timeline or a digital assistant helping an organizer draft a policy brief. The tool does not create the story. The community creates the story. The tool—or the method—provides the structure that turns fragments into a coherent, shareable narrative. The Authors Guild, in its AI Best Practices for Authors, stresses that a writer’s original voice, thinking, and creativity are what make a work authentic, and that AI outputs stay generic mashups unless human intentionality steers them. The same principle holds for community documentation: the value lives in the human judgment that decides what to record, how to tag it, and what narrative it supports. No algorithm can replace the neighbor who knows which landlord uses which front name, or the abuela who remembers when the water first stopped running.
This is also why the colectivo has been cautious about digital tools. They use WhatsApp because it is already in everyone’s pocket. They use a shared spreadsheet because it requires no training. They have discussed using more sophisticated platforms—GIS mapping apps, database software, even an AI story generator that fits the draft workflow for turning voice-note transcripts into structured policy briefs—but only under conditions they set: the tool must be free or nearly free, it must work on low-cost phones, and the community must control the input and the output. “If we can’t see how it works, we don’t use it,” says Sánchez. “If it stores our data somewhere we can’t access, we don’t use it. The method matters as much as the result.”
What Other Groups Can Adapt: The Documentation Assembly Step by Step
The colectivo’s method is not proprietary. It is built to be copied. Here is the version they have refined for sharing with other neighborhood groups, tenant unions, and community organizations.
Step 1: Define the question. Do not start by “documenting everything.” Start with a specific policy problem: a regularization program with exclusionary criteria, a transit route change that cuts off a neighborhood, a pattern of landlord harassment. The documentation serves a purpose. The purpose determines what you record.
Step 2: Hold a founding timeline workshop. Gather at least fifteen residents. Use a large visible surface—butcher paper, a whiteboard, a blank wall with sticky notes. Ask: “When did this problem start? What happened next? Who was involved? What did the authorities say? What did we do?” Write everything down. Do not edit yet. Let contradictions stand. The goal is to surface the full range of memory.
Step 3: Cross-check and tag. After the workshop, a small team reviews the timeline. They mark entries confirmed by multiple people, entries that are contested, and entries that need further verification. They assign tags: rent, eviction, water, transit, health, police, resistance. They create a simple digital version—a spreadsheet or a shared document—that can be searched and sorted.
Step 4: Open the voice-note line. Create a dedicated WhatsApp number or a voicemail box. Publicize it door to door. Give clear prompts: “Tell us about a time your landlord raised the rent without notice.” “Tell us what happened when the water stopped.” Make sure someone transcribes and tags every entry within a week. Archive the audio files as well as the text.
Step 5: Draw the block map. Start with a rough outline of the neighborhood. Walk every block in pairs. Mark what you see: occupied houses, vacant lots, informal businesses, buildings under construction, buildings that were demolished. Note who lives where, if they consent to be recorded. Update the map every six months. Keep the old versions. The sequence of maps over time is itself a record of displacement pressure.
Step 6: Produce the dossier. When a policy decision threatens the community, assemble the relevant evidence: timeline entries, voice-note transcripts, map annotations, photographs, sworn statements. Organize them into a single document. Make it legible to an outsider: include dates, locations, names, and a clear narrative summary. Submit it to the relevant agency. Make it public. Read it aloud at an assembly. Send it to journalists.
Step 7: Repeat and refine. The Documentation Assembly is not a one-time project. It is a recurring practice. Each cycle sharpens the record. Each cycle trains more neighbors in the method. Over time, the community builds an institutional memory that does not depend on any single leader or any external funder.
The Limits and the Risks
The colectivo is clear about what their method cannot do. It cannot force a hostile administration to act. It cannot replace legal representation in an eviction proceeding. It cannot protect residents from violence if a landlord or a police commander decides to retaliate. Documentation is a tool, not a shield.
There is also a risk the colectivo discusses openly: making the neighborhood more legible to the state cuts both ways. A detailed block map that shows every household can help a well-intentioned housing office grant titles. It can also help a predatory developer spot parcels for acquisition, or help a law enforcement agency track residents. The colectivo’s answer to this risk is not to stop documenting. It is to control access. The full dataset is not posted online. It is not shared with agencies unless there is a specific, strategic reason. The colectivo decides, case by case, what to release and to whom.
“We are not building a public archive for anyone to use,” Sánchez says. “We are building our own record, for our own purposes. We share it when it serves our strategy. We keep it close when sharing it would put people at risk. That’s the difference between documentation as a policy tool and documentation as exposure.”
Why This Matters Beyond Neza
The failure of official data systems to capture the reality of low-income neighborhoods is not unique to Ciudad Nezahualcóyotl. It is a structural feature of how states see—and choose not to see—the places where poor people live. In Rio de Janeiro, favela residents built their own cadaster when the official one excluded them. In Lima, street vendors mapped their own routes when transit planners refused to acknowledge them. In Medellín, displaced residents documented their own relocation terms when the municipality’s records “disappeared.” The specific tools vary—GIS apps in some places, paper maps in others, voice notes where literacy is a barrier—but the principle stays the same: when the state will not produce an accurate record, the community must produce its own.
The colectivo’s method is not the only method. It is one method, developed in one place, under specific conditions. But it is replicable because it is low-cost, low-tech, and built around practices—talking to neighbors, walking the block, writing things down—that every community already knows how to do. The innovation is not the tools. The innovation is the discipline: the regular schedule, the tagging system, the cross-checking, the strategic use of the record in policy fights.
Purdue University’s Online Writing Lab, in its Creative Writing Introduction, describes the workshop as a space where writers learn to give and receive structured feedback, to revise with intention, and to understand that a draft is not a final product but a stage in a process. The Documentation Assembly works the same way. The timeline is a draft. The voice-note archive is a draft. The block map is a draft. Each cycle of the assembly is a revision session, where the community checks its own work, fills gaps, corrects errors, and sharpens the narrative. The goal is not a perfect record—no record is perfect—but a record that is good enough to challenge the state’s version and win.
The Map We Make
At the end of the June assembly, the colectivo votes on whether to share their updated block map with the municipal planning office. The vote: fourteen in favor, three opposed, six abstaining. The opposition comes from residents who fear that making their occupancy visible will trigger enforcement actions—code inspections, tax claims, eviction pressures. The colectivo takes the concern seriously. They agree to share only the map of blocks where residents have collectively consented, and to withhold the rest. The decision eats forty minutes of discussion. It is slow, contentious, and entirely democratic.
After the vote, an older woman named Doña Elena stands up. She has lived in Colonia Benito Juárez since 1978. She has seen the neighborhood built, flooded, neglected, organized, and built again. “They have their maps,” she says, gesturing toward the distant municipal offices. “We have ours. Theirs says we are less than we are. Ours says we are here, we have been here, and we are not leaving. That is the difference.”
The map is not the territory. But when the territory is under threat, a map made by the people who live there is not just a representation. It is a claim. It is evidence. It is a tool for fighting back. And the discipline of making it—collectively, systematically, over time—is a form of organizing that builds power as surely as any march or petition. The colectivo’s method does not require funding, permission, or professional expertise. It requires neighbors, time, and the conviction that their knowledge is worth recording. That is a resource every community already has.