Why Grassroots Advocacy Needs Better Infrastructure

When I first started organizing in rural Scotland, our biggest obstacle wasn’t opposition from powerful interests or a lack of willing volunteers. It was something far more mundane: we couldn’t reliably reach the people who wanted to help. Phone trees went untested until the night they were needed. Email lists lived on personal accounts that volunteers guarded like family silver. Meeting spaces were borrowed on a prayer and a handshake. We had passion, we had numbers, and we had right on our side—but we had no scaffolding to hold any of it together.

That was two decades ago. The landscape has shifted in many ways, but the infrastructure problem persists. Grassroots movements still rise and fall on the strength of ad hoc systems, reinvented wheels, and institutional memory that walks out the door when a single organizer takes a break. If we are serious about lasting change, we need to talk honestly about what our movements are built on—and what they deserve.

Community members gathered around a table discussing advocacy strategy

The Problem Isn’t Passion—It’s Plumbing

Grassroots advocacy attracts people who want to act. We are doers by temperament, and that is a strength. But it also means we tend to undervalue the unglamorous work that makes action possible. Infrastructure—the shared systems, tools, and agreements that let people coordinate at scale—is rarely the thing that gets anyone out of bed in the morning. Yet without it, even the most committed groups find themselves re-solving problems they solved six months ago.

Consider a typical scenario. A local coalition forms around a housing issue. They hold public meetings, generate press coverage, and build relationships with sympathetic council members. Then the lead organizer moves to another city. The shared documents live on her personal laptop. The relationships with local officials were hers. The institutional knowledge about what worked and what didn’t exists only in her head. Within months, the coalition is a shell, and the next group that forms around a similar issue starts from scratch.

This is not a failure of will. It is a failure of architecture.

What Better Infrastructure Actually Looks Like

When I say “infrastructure,” I am not talking about buying everyone the same software platform. Technology is part of the picture, but it is far from the whole of it. Better infrastructure means building systems that survive individual departures, scale with participation, and lower the cost of entry for new volunteers. It includes three things:

1. Shared Knowledge Repositories

Every grassroots group generates hard-won practical knowledge—what messaging worked, which council members are receptive, how to navigate local permitting rules, what coalitions have already tried and failed. This knowledge should live somewhere accessible, not in the private files of whoever happens to be most organized. A simple shared drive with clear naming conventions and regular updates can transform a group’s capacity. So can written process documents that capture not just what happened, but how decisions were made and what the reasoning was. Future volunteers should not have to guess why a campaign chose one tactic over another.

2. Durable Communication Channels

Too many grassroots organizations rely on a single channel—often one controlled by a single person. When that person steps back, the channel goes silent. Better infrastructure means building redundant, community-owned communication pathways. That might look like a discussion platform where multiple admins exist, a phone tree that gets tested quarterly, or a newsletter with more than one person holding the login credentials. The principle is straightforward: no single departure should be able to sever a community’s ability to talk to itself.

Volunteers collaborating on documents and planning materials

3. Governance That Grows

Governance is the least sexy word in advocacy, and perhaps the most important. Who makes decisions? How are new leaders brought on board? What happens when someone wants to step down? Groups that answer these questions in advance—ideally in writing, ideally before conflict arises—survive longer and adapt faster than those that improvise governance under pressure. This does not mean adopting corporate hierarchies. It means being intentional about how coordination happens, how accountability is maintained, and how power is distributed.

The Cost of Neglect

The absence of good infrastructure is not merely inconvenient. It produces real, measurable harm to movements.

Burnout concentrates around the organized. In every under-structured group, a small number of people end up holding everything together. They manage the lists, schedule the meetings, keep the records. These people are not superhuman. They get tired, they get sick, they get other jobs. When they leave, the group often collapses—or limps along at a fraction of its capacity. This is not sustainable, and it is not fair.

Newcomers face invisible barriers. Without clear onboarding processes and accessible records, new volunteers must rely on informal introductions and word of mouth to find their footing. This disadvantages people who are not already connected to existing members—precisely the people grassroots movements most need to welcome. A well-documented group with clear entry points can onboard someone in an afternoon. A group without them may lose a willing volunteer after a single confusing meeting.

Repeated mistakes waste limited resources. Every grassroots organization operates under resource constraints. When institutional memory is lost, those scarce resources get spent rediscovering what previous groups already learned. A coalition that could have built on its predecessor’s work instead replays old debates, reattempts failed strategies, and reestablishes relationships from scratch.

Community rally with participants holding signs and banners

Practical Steps Forward

Principle without practice is just sentiment. So here are concrete steps that grassroots groups can take right now, with limited budgets and volunteer labor:

Start a shared drive today. Use whatever platform your group can agree on—Google Drive, a shared folder, anything that keeps documents out of individual silos. Create a simple folder structure: campaigns, governance, templates, meeting notes. Set a recurring reminder to review and update the contents quarterly.

Write down your decision-making process. Even a one-page document that says “we make decisions by consensus at monthly meetings, with a two-person steering committee handling urgent matters between meetings” is better than nothing. Make sure new members can find it and understand it.

Assign at least two people to every critical role. Every coordinator, every admin, every key contact should have a backup who is informed and prepared. This is not redundancy for the sake of redundancy; it is resilience. According to the National Council of Nonprofits, leadership transitions are among the most common causes of organizational failure for small nonprofits and advocacy groups. Simple co-leadership structures can prevent this.

Invest in relationships, not just campaigns. Infrastructure is social as much as it is technical. Regular check-ins between coalition partners, even when there is no active campaign, build the trust and familiarity that make rapid mobilization possible when it matters. The Transnational Institute has documented how movements that sustain relational infrastructure between campaign cycles adapt more quickly to emerging opportunities and crises.

Build a template library. Every time your group creates a press release, a flyer, a public comment template, or a meeting agenda, save a clean version that the next campaign can adapt. Over time, this library becomes one of your most valuable assets—and one of the easiest to start building.

The Principle Behind the Practice

There is a deeper reason to care about infrastructure. Grassroots advocacy is, at its core, an assertion that ordinary people deserve a voice in the decisions that shape their lives. If we believe that, we must also believe that the tools of participation should be durably available—not dependent on any single person’s goodwill, energy, or presence.

When infrastructure is fragile, power concentrates around whoever happens to hold the keys. When infrastructure is shared, power distributes more evenly. This is not just practical. It is a matter of principle. A movement that claims to stand for democratic participation should practice it internally, building systems that make participation possible for everyone—not just the unusually persistent or the already connected.

I have watched too many good campaigns falter not because their cause was weak, but because their scaffolding was. We owe it to the communities we serve to build something that lasts—not just in the policies we change, but in the organizational capacity we leave behind for the next fight.

Frequently Asked Questions

Isn’t formal infrastructure only for large organizations?

Not at all. A group of five people can benefit from shared documents, clear roles, and written agreements about how decisions happen. In fact, small groups often need these structures more, because they have less margin for error. When only two people know how something gets done, losing one person cuts your capacity in half. Simple infrastructure protects small groups from that kind of fragility.

What if our group values informality and spontaneity?

Informality and infrastructure are not opposites. You can build lightweight systems that support spontaneity rather than stifling it. A shared calendar, a group chat with clear guidelines, and a basic onboarding document do not make a group bureaucratic—they make it easier for new people to show up and participate. The goal is not red tape. The goal is making sure the door is unlocked when someone knocks.

How do we fund infrastructure improvements when we can barely fund our campaigns?

Many of the most effective infrastructure improvements cost time rather than money. Setting up a shared drive, writing down your processes, and designating backup roles for key positions require effort, but not budgets. When funding is available, investing in infrastructure—training, tools, documentation—often produces more long-term impact than an equivalent spend on a single campaign. Think of it as the difference between buying groceries and learning to cook: both feed you, but one builds lasting capacity.