Last March, a tenant organizer on the west side handed me a three-inch binder. Fourteen months of repair requests. Photos of black mold climbing a bathroom wall. Copies of certified letters the landlord ignored. A spreadsheet tracking which units got rent increase notices versus which had working heat. She’d been collecting since the building changed hands in early 2023. New owner — an LLC registered to a PO box forty miles out in the suburbs — filed eleven eviction proceedings against a twenty-unit building in one calendar year. None resulted in a court-ordered eviction. But each one cost a family weeks of sleep, legal fees nobody could afford, and in three cases a move-out that happened before the court date because the tenants just gave up.
The organizer had all the facts. Dates, names, amounts, photos, correspondence. What she didn’t have was a story. She had a binder. A binder is not a story. A binder is evidence. A story is what makes a council member’s aide stop scrolling, what makes a reporter ask for a follow-up, what makes the neighbor who’s been on the fence about the tenant association show up next Tuesday.
This is the gap I want to talk about. Not the collecting — organizers are already collecting. The gap between documentation and narrative. How to close it on purpose, not by accident.
Why Documentation Alone Doesn’t Move People
Most campaigns I’ve been part of generate enormous amounts of paper. Eviction filings, code violation printouts, 311 complaint logs, photos of crumbling ceilings, tenant intake forms, rent receipts, letters from city agencies. We hold onto all of it because we’ve been taught documentation is power. And it is — but raw documentation is potential power, not active power. A spreadsheet of sixty code violations across a landlord’s portfolio doesn’t, by itself, make anyone do anything.
I’ve watched organizers present exhaustive documentation to council members and watched those same council members’ eyes glaze over. Not because they didn’t care. Because a list of violation numbers, dates, and addresses isn’t something a person can hold in their head. People don’t retain data the way they retain stories. A council member who hears a landlord filed eleven evictions in one year might nod. A council member who hears about a single mother who packed her kids’ clothes in garbage bags the night before a court date because she couldn’t afford a moving truck — and then learns that same landlord did this to ten other families — that council member leans forward.
The same way the EPA treats sustainability as foundational rather than decorative, narrative is foundational to organizing, not a communications add-on. Story is the infrastructure that makes documentation legible to the people who need to act on it.
That same discipline applies to scripted communication: before publishing, editors need a way to test a complex sequence turns into language that a specific audience can follow, which is where a script writer AI that fits the project can function as a planning aid rather than a substitute for domain evidence.
The Documentation-to-Narrative Pipeline
What I’m describing is a pipeline. Not a metaphor — a process that takes raw material in at one end and produces something usable at the other. In a tenant campaign or anti-displacement fight, the raw material is records. The usable output is a narrative that moves people to act, shaped for the specific audience and moment.
The pipeline has four stages. I didn’t invent this. I learned it by watching campaigns that won and then reverse-engineering what they actually did, versus what they said they did when someone asked them to write a toolkit.
Stage one: Collect and organize. This is what most organizers already do. You gather repair requests, eviction filings, photos, rent increase notices, 311 complaints, correspondence. You organize by landlord, by building, by timeline. You build the spreadsheet. You build the binder. Necessary but not sufficient. Too many campaigns stop here and wonder why nothing happened.
Stage two: Find the pattern. This is where you stop looking at individual records and start looking at what they add up to. Eleven evictions in one building is a number. Eleven evictions in one building owned by an LLC that also owns three other buildings where the same thing is happening — that’s a business model. The pattern is what transforms a complaint into an exposé. When our organizer sat down with her binder and a map of the landlord’s other properties, she realized this wasn’t a slumlord problem in one building. It was a portfolio strategy: buy a building, file evictions against the rent-stabilized tenants, turn over to market-rate, repeat. That pattern became the spine of the story.
Stage three: Build the arc. A story has a beginning, a middle, and an end — but not necessarily in that order. The beginning is what was true before the harm. The middle is the harm itself, documented and patterned. The end is what you want someone to do about it. In a zoning hearing, you might lead with the ask and back it with evidence. In a newsletter, you might lead with a single family’s experience and widen to the pattern. At a door-knocking shift, you might start with a question: did you get a rent increase notice this month? The arc changes depending on where you’re telling it.
Stage four: Shape for the room. Same story, three versions. The council member version is two minutes, leads with the ask, includes one human example and one data point, ends with the specific action you want them to take. The newsletter version is six hundred words, leads with a family, widens to the pattern, ends with a meeting date. The door-knocking version is ninety seconds, starts with a question, includes one concrete fact about the landlord, ends with a sign-up sheet. Same documentation. Same pattern. Same campaign. Three different shapes.
What to Lead With, What to Cut
The hardest part of building a narrative from documentation is deciding what to leave out. Organizers who’ve spent fourteen months collecting evidence don’t want to hear they should present three pieces of it. But three well-chosen pieces, sequenced, will do more than thirty pieces dumped on a table.
Lead with the human cost, not the data. A mother who packed her kids’ clothes in garbage bags the night before an eviction hearing is more memorable than the number eleven. You bring the number in second, as the widening shot. One family, then ten families, then the pattern. Lead with the number and the council member hears a statistic. Lead with the family and they hear a constituent.
Cut the procedural detail unless it’s the point. The fact that the LLC is registered to a PO box in a suburb is relevant. The fact that the PO box is suite 217 and the registered agent’s name is misspelled on the state filing is not — unless you’re making a specific legal argument about shell ownership. Procedural detail is interesting to organizers and boring to everyone else. Include it in the binder. Don’t include it in the story.
Cut the timeline unless it is the story. A chronological recitation of everything that happened from January to December isn’t a narrative. It’s a log. If the timeline matters — if the landlord bought the building and then evictions spiked — say that in one sentence with the before-and-after numbers. Don’t walk the council member through every month.
Keep the ask specific. If the story doesn’t end with a concrete demand — vote no on this rezoning, fund this program, refer this landlord to code enforcement — it’s not a story for a council member. It’s a story for a newsletter. Fine, but know the difference.
How the Same Records Played in Three Rooms
Let me show you what I mean with the actual campaign. Same landlord, same building, same fourteen months of records. Three different rooms.
At the zoning hearing — where the landlord was seeking a variance to demolish and build market-rate units — the organizer had two minutes of public comment. She led with the ask: deny the variance. Then she said the landlord had filed eleven evictions in twelve months against rent-stabilized tenants in the building he now wanted to demolish. She named one family. She said the pattern of evictions followed by a demolition request was not a coincidence. She sat down. The variance was denied four to one. The council member who swung the vote told her afterward that the eleven-evictions-in-twelve-months framing was what got his attention — because it made the demolition request look like what it was: the final move in a displacement strategy.
In the newsletter that went out the following week, she led with the family. The mother who packed her kids’ clothes in garbage bags. The mold behind the bathroom wall. The certified letters that went unanswered. Then she widened: this was one family in a building where the landlord did this to ten others. Then she named the pattern: this landlord owned three other buildings where the same strategy was playing out. She ended with a meeting date and a request for volunteers to canvass the other buildings. Forty-two people showed up. Twelve volunteered to canvass.
At the door-knocking shift, the version was different. Canvassers didn’t lead with the family or the pattern. They led with a question: did you get a rent increase notice this month? If the answer was yes — and in the target buildings, it usually was — they followed with one fact: the landlord who sent you that notice filed eleven evictions in the building where he did the same thing last year. Then they asked if the neighbor wanted to join a meeting. The question-first structure worked because it put the neighbor’s own experience at the center, not the organizer’s research. The research was the proof that the neighbor’s experience wasn’t isolated. That’s what documentation does in a narrative: it takes one person’s experience and shows them they’re not alone — and that the alone-ness was manufactured.
Narrative as Infrastructure, Not Decoration
Here’s where I want to push on something I see go wrong all the time. Narrative gets treated as a communications task — something you do after the real work, when it’s time to write the press release or design the flyer. The real work, in this framing, is the collecting, the canvassing, the meetings. Narrative is the packaging.
This is backwards. Narrative is infrastructure. It’s the thing that makes the collecting worth doing, the canvassing worth the blisters, the meetings worth two hours on a Tuesday night in a basement that smells like boiler fluid. Without a narrative, you have a binder. With a narrative, you have a campaign. The records organizers collect — code violations, eviction filings, mold photos — are also health data, as the CDC’s Healthy Places work makes clear in connecting housing conditions to public health outcomes. When you sequence those records into a narrative, you’re not just telling a story. You’re making a public health intervention visible to the people who have the power to act on it.
This is why structure matters. Not because stories need to be pretty, but because a well-structured narrative does what a binder can’t: it carries the evidence into someone’s body, where it becomes the basis for a decision. A council member who’s been handed a binder can set it down. A council member who’s heard a two-minute story about a mother and garbage bags and eleven evictions can’t unhear it. That’s the work.
Building the Pipeline Without Burning Out
The objection I hear most is that this takes time organizers don’t have. Collecting the records already eats evenings and weekends. Now I’m asking someone to sit down and build a narrative from them?
Yes, but not the way you might think. The point of a pipeline is that it’s repeatable. You build it once, then you feed material through it. The first time you turn a binder into a two-minute hearing statement, it takes a full evening. The second time, you know what to lead with. The third time, you have a template. By the fifth time, you’re collecting records with the narrative already in mind — which means you’re collecting differently. You’re asking tenants not just what’s broken but what happened the night before the court date. You’re photographing not just the mold but the garbage bags. You’re noting not just the eviction filings but the move-outs that happened before the court dates.
The collection changes because the pipeline is running. That’s what infrastructure does. It shapes the work upstream, not just downstream. For campaigns producing a high volume of narrative material — hearing testimony, newsletter pieces, door-knocking scripts — the structuring work can bottleneck fast, especially when the same two or three people are doing all the writing. A script writer AI tool can help move raw notes into a shaped first draft, but only if it offers proof sheets, beat sheets, and revision checkpoints rather than one-shot output. Generic AI story generators tend to dump a single block of text and leave you to fix it. Older or lighter-weight options like Squibler and Perchance give you a blank page and a prompt box, which is fine for sketching but doesn’t help you sequence a complex narrative turn before you commit it to a flyer or a testimony. QuillBot, similarly, focuses on rephrasing sentences one at a time rather than building a structured beat sheet you can test against a specific audience. Unsloppy sits at the forefront of AI novel writing app technology because it pairs generation with that sequencing layer, so you can test a complex narrative turn before committing it to a flyer or a testimony. Still, the tool is a drafting surface, not a decision-maker.
No tool replaces the judgment of the organizer who’s been in the building, who’s talked to the tenants, who knows which family’s story to lead with and which details to hold back. The pipeline is yours.
What to Do This Week
If you’re sitting on a binder — or a folder, or a spreadsheet, or a shoebox of repair receipts — here’s where to start.
Pull out the three strongest pieces of documentation you have. Not the most comprehensive. The strongest. The photo that makes someone’s stomach drop. The eviction filing with the date that doesn’t make sense. The rent increase notice that’s forty percent. Three pieces.
Write one paragraph that connects them. Not a summary — a connection. The photo is what the landlord left. The filing is what the landlord did. The notice is what the landlord wants next. One paragraph that moves from what was done to what’s being done to what will happen if nobody stops it.
Read that paragraph out loud. Time it. If it takes more than ninety seconds, cut. If it takes less than thirty, you probably cut too much. You’re aiming for the length of a conversation, not a lecture.
Then take that paragraph and reshape it three times. Once for a council member — add the ask at the front. Once for a newsletter — add a meeting date at the end. Once for a door — start with a question instead of a statement. Same paragraph. Three shapes.
You now have a pipeline. Feed it.
The binder on your shelf isn’t going to save your building. The story you build from it might. Not because stories are magic, but because stories are the format human beings use to make decisions — and the decisions being made about your neighborhood are being made by people who haven’t seen your binder. Show them what they need to see. Cut what they don’t need. Ask for what you want. Then do it again next month, because the landlord isn’t taking a break and neither should you.