NA 4 · Neighbor Advocate~9 min

A Coalition That Holds: Not Here, and Not There Either

Projects with routes and sites invite every affected community to argue for moving the project onto someone else. It sometimes works, and it reliably breaks the coalition that could have changed the outcome for everyone. NA4 teaches the neighbor's trap and the discipline that answers it: oppose impacts wherever they fall, promote only alternatives that put the burden on no new community, federate rather than absorb the groups already working, give each kind of member the role it can actually play, and speak only for yourself.

A Coalition That Holds: Not Here, and Not There Either

A utility shows three possible routes. Within a month, the town on the northern route has a group, a yard sign and a slogan. So does the valley on the southern route. Each group is right that the line would hurt it. And each one, sooner or later, is tempted by the same sentence: the other route makes more sense.

The sentence is attractive because it sounds constructive. It offers the decision-maker a solution instead of a refusal. It also sets the communities who could have stood together against one another, in public, on the record, where the applicant and the decision-maker can both see it.

The neighbor's trap

Call it route-shifting: one affected community arguing that the burden should move onto another. It happens with power lines, highways, landfills, warehouses, cell towers and shelters, anywhere a project has more than one possible place to go.

Sometimes it works, for one community. Here is what it costs everyone.

  • It splits the opposition into competitors. Every hour each group spends arguing against the other route is an hour it is not spending on the decision itself.
  • It tells the decision-maker the objection is about location, not merit. If every community only wants the project elsewhere, the project looks inevitable and the only question looks like where.
  • It costs credibility. A comment that says "study the impacts on our valley" is answered on its merits. A comment that says "build it on them instead" is read as interest, because it is.
  • It is remembered. Neighbors who were argued against do not forget it when the next fight comes, and there is always a next fight.

The decision-maker does not need to divide a coalition that divides itself.

The discipline that answers it

The coalition position that holds has three parts.

Oppose impacts wherever they fall. Every community describes what the project would do to it, precisely, as NA2 taught. No community argues that its impacts matter more than another's.

Promote only alternatives that burden no new community. A coalition can and should push for alternatives. The ones that keep it together are the ones that do not move the problem onto someone else: using a corridor or site that already carries the same kind of use, upgrading what is already built, or meeting the need another way. Ask that every alternative be studied fully in the environmental review, and argue for the ones that send the project through no one new.

Put it in writing. Ask each member group to agree, in plain words, that it will not argue for moving the project onto another community. A short pledge does two things: it keeps members honest when the temptation arrives, and it gives the coalition a sentence to say to the press when someone asks which route it prefers.

In the running example for this track, the community hub opposing the Golden Pacific Powerlink states the position on its own About page: "Every route crosses someone's community. This hub opposes the line's impacts wherever they fall and does not argue for sending it anywhere else" (stopgoldenpacific.org). That sentence is the discipline in two lines.

Federate, don't absorb

By the time a coalition forms, groups usually already exist: a town's own committee, a park foundation, a fire safe council, a land conservancy, a business association, a few online groups that grew faster than anyone planned. The instinct is to merge them into one organization with one name. Resist it.

Each existing group has its own members, its own credibility and its own relationships. Ask it to give those up and some will refuse, some will leave, and the ones who stay will feel absorbed. A federated coalition keeps every group whole and adds a shared layer on top: one calendar of deadlines, one library of sourced facts, one agreed position, a regular call. Members keep their names and their pages. The coalition is the connective tissue, not a new flag.

Your first alliance (Field 2.7) and coalitions to campaigns (Campaign 4.1) cover how alliances are built and kept. The specific discipline for a project fight is to make the shared layer useful enough that every group wants to be part of it, and light enough that none has to give up who it is.

Roles a coalition needs

Not every member can do the same work, and a coalition that asks the same thing of everyone wastes most of what it has. Map what each kind of member can actually do.

MemberWhat it can do that others cannot
Established organizations (a park foundation, a conservancy, a public-interest group)Become a formal party, hire counsel and experts, sustain a multi-year proceeding (NA5)
Town and neighborhood groupsFill a hall, gather the firsthand facts (NA2), keep neighbors informed
Businesses and working landownersSupply facts about livelihoods and land use that nobody else holds
Local governmentsTake formal positions, write to the decision-maker, take part in the proceeding in their own right
Elected officialsWrite, speak and convene; they do not decide a regulatory proceeding, but the decision-makers listen
Experts who volunteerReview a draft environmental report section, check a number, testify for a party

A coalition with all six, each doing its own part, looks to a decision-maker like what it is: a region that has read the record.

Speak only for yourself

Two kinds of overreach damage coalitions from inside.

Claiming members you do not have. A coalition lists the groups that have agreed to be listed, and no others. Saying an organization "supports" you when it has not agreed is the fastest way to lose it and the press with it.

Speaking for a Tribal Nation. Where a project touches Tribal land or cultural resources, the Tribe is a government with its own voice, its own process and its own relationship with the decision-maker. State a Tribe's position only in its own public words, with the source, and ask before assuming any alignment.

Skill, not side

The mirror image of this trap catches supporters too. A coalition that wants a project built, say a clean-energy line or a housing development, splits the same way when its members fight over which site, which route or whose neighborhood. The discipline is identical: agree on the case for the project, ask that alternatives be studied fully, and do not win by moving the burden onto a neighbor who was not at the table.

Bringing the Foundations toolkit here

Power mapping (F4) shows you who each member can reach. Your first alliance (Field 2.7) is the training for holding groups together. Coalitions to campaigns (Campaign 4.1) takes it to the scale of a long fight. Cross-movement solidarity (Sustain 5.3) is the version for coalitions whose members want different things for different reasons.

What comes next

A coalition that holds can stay in a proceeding for years. NA5 is about those years: when an ordinary participant should become a formal party, how the state can pay for that participation, when to bring in a lawyer, and how to keep people going until the decision comes.

Exercise

Map the coalition you are in, or the one you would need. List every community, organization and interest the project touches, including the ones on routes or sites other than yours. For each, write what it stands to lose, what it can do that no one else can (become a formal party, bring an expert, reach a newspaper, move an elected official, organize a hall), and whether it currently argues for moving the project anywhere. Then write the one-sentence position all of them could sign without any of them arguing the project onto another. If you cannot write that sentence yet, write what stands in the way.

Sign in to write and save your response here — the Library stays free either way.

Downloadables

  • The Coalition Map

    A one-page worksheet for building a coalition across communities that are affected differently: the member map (what each loses and what each can do), the shared position test, the non-displacement pledge, and the roles a coalition needs filled.

Frequently asked questions

If another route really would do less harm, isn't it honest to say so?
It can be, and a decision-maker has to compare alternatives. The trap is a community arguing that the burden should move onto another community. The coalition position that holds is to ask that every alternative be studied fully, and to promote only alternatives that put the burden on no new community: an existing corridor, upgrading what is already built, or meeting the need another way.
Should our group merge into one big coalition with one name?
Usually not. Groups that already exist have members, credibility and relationships of their own. A coalition that federates (shared calendar, shared research, a shared position, each group keeping its name) holds better than one that absorbs them, and it does not hand anyone a reason to quit.
How do we work with Tribal Nations whose land or cultural resources are affected?
As governments, not as members of your coalition. A Tribal Nation speaks for itself, through its own channels, on its own timeline. Never state a Tribe's position except in its own public words, and ask before assuming any alignment.