---
name: nonprofit-coalition-building
description: "Builds and runs multi-organization advocacy coalitions: partner recruitment, coalition MOUs and governance structures, shared decision-making rules, message alignment across partners, and joint sign-on letters. Use when a user asks to form or join an advocacy coalition, draft a coalition MOU or governance charter, resolve disagreement between partner orgs on messaging or strategy, coordinate a joint sign-on letter or statement, or design how a coalition makes decisions and shares credit/resources. Covers cross-organizational structure and alignment, not single-org issue research (nonprofit-policy-analysis), not one org's legislator meetings (nonprofit-legislative-advocacy), and not public supporter mobilization tactics (nonprofit-grassroots-mobilization)."
license: MIT
metadata:
  supervision: "review"
  supervision_note: "Coalition MOUs and shared decision rights commit the organization to partners."
  date_added: "2026-09-07"
  date_added_source: "git:1860ed47a83901ff5e6d45abc4a2ef05be8fd4cd"
---

# Nonprofit Coalition Building

## When to Use This Skill

Use this skill when advocacy work spans more than one organization:

- Identifying and recruiting partner organizations for a new advocacy coalition
- Drafting a coalition MOU, charter, or governance document (decision rules, membership criteria,
  exit/dissolution terms)
- Designing coalition governance structure: steering committee, working groups, backbone/lead-org
  model, rotating chair
- Aligning message and strategy across partner organizations with different priorities, risk
  tolerances, or (c)(3)/(c)(4) status
- Drafting and circulating a joint sign-on letter or public statement
- Resolving internal coalition conflict (a partner org breaking from an agreed position, credit
  disputes, funding allocation disagreements)
- Winding down or formally dissolving a coalition at campaign end

**Boundary — hand off when the ask is:**
- Researching/writing the underlying policy content a coalition will use → `nonprofit-policy-analysis`
- One organization's own legislator meetings or testimony (even if done "on behalf of" a coalition,
  the individual-org prep work is that skill) → `nonprofit-legislative-advocacy`
- Turning the coalition's agreed message into public action alerts/petitions to mobilize supporters →
  `nonprofit-grassroots-mobilization`
- Structuring a single org's own (c)(3)/(c)(4) dual-entity lobbying limits → `nonprofit-c3-c4-structure`

## Core Framework: Coalition Governance Models

Choose a governance model deliberately — most coalition dysfunction traces back to skipping this
choice and defaulting to informal consensus, which breaks down once membership exceeds ~5-6 orgs or
disagreement arises on a high-stakes decision.

1. **Backbone/lead-organization model:** One organization holds the fiscal/legal responsibility and
   staffs coordination (often called the "backbone org," per the collective impact literature);
   partners contribute input but the backbone makes final calls within agreed parameters. Fastest to
   act, lowest overhead, but can concentrate risk and credit on one org.
2. **Steering committee model:** A subset of member orgs (5-9 is typical) forms a steering committee
   with defined voting rights; full coalition votes reserved for major strategy shifts. Balances
   speed and buy-in; requires a clear charter defining what the steering committee can decide
   unilaterally vs. what needs full-coalition sign-off.
3. **Consensus model:** All members must agree before the coalition acts publicly. Maximizes buy-in
   and message discipline but is slow and vulnerable to a single blocking member — only appropriate
   for small (under 6 org), high-trust, high-alignment coalitions.
4. **Working-group/task-force model:** Full coalition sets overall strategy; specific workstreams
   (e.g., legislative outreach, communications, research) are delegated to smaller working groups
   with their own leads reporting back — scales well for large coalitions (15+ orgs).

## The Coalition MOU / Charter — Required Sections

A coalition without a written charter runs on assumed agreement that surfaces as conflict at the
worst moment (mid-campaign, under press attention). Draft the MOU before the first joint public
action, covering:

1. **Purpose and scope** — the specific issue(s)/bill(s) the coalition addresses, and explicitly what
   is out of scope (prevents "scope creep" fights later)
2. **Membership criteria and process** — who can join, how, and any values/screening criteria
   (e.g., excluding orgs with conflicting funding sources)
3. **Decision-making rules** — which governance model (above), what threshold constitutes a decision
   (simple majority, supermajority, consensus), and which decisions are delegated vs. reserved for
   full membership
4. **Spokesperson and messaging protocol** — who can speak publicly on the coalition's behalf, the
   process for approving joint statements, and what happens when a member org wants to say something
   individually that differs from the coalition line
5. **Resource/cost-sharing** — how staff time, event costs, or shared materials budgets are split
   (often proportional to org size/capacity, sometimes flat per-org)
6. **Credit and visibility** — how member org logos/names appear on materials, press mentions, and
   funder reporting — an under-specified area that causes real friction when press coverage
   disproportionately names the largest or best-connected member
7. **Exit and dissolution terms** — how a member can leave, what happens to shared materials/funds,
   and a sunset review date to decide whether the coalition continues
8. **Legal/lobbying disclosure note** — if any member's participation counts toward its own 501(h)
   lobbying ceiling, that member is individually responsible for its own tracking (see
   `nonprofit-legislative-advocacy`); the MOU should say so explicitly rather than implying the
   coalition absorbs that risk

## Message Alignment Process

1. Draft a **one-page shared message framework**: the core ask (single sentence), 3 supporting
   points every member can say verbatim, and a list of topics/framings explicitly out of bounds
   (e.g., partisan framing, unrelated issues).
2. Circulate for member comment with a firm deadline and a default-approve clause ("no response by
   [date] = approved") to prevent one slow-moving member from stalling the whole coalition.
3. Distinguish **"coalition says" vs. "members may individually say"** — give explicit permission for
   member orgs to go further/add their own framing in their own channels as long as they don't
   contradict the shared ask.
4. For joint sign-on letters: circulate a locked final draft, set a signature deadline, and publish a
   dated, versioned final so a late "one more edit" request from a single signer doesn't hold the
   letter hostage.

## Common Failure Modes

- **No written decision rule.** Informal consensus works until the first real disagreement, at which
  point the coalition either freezes or a dominant member unilaterally acts, damaging trust.
- **Undefined spokesperson protocol.** A member org going to press with an off-message quote is the
  single most common coalition blow-up; the MOU's messaging section exists specifically to prevent
  this.
- **Ignoring 501(h)/lobbying asymmetry among members.** A 501(c)(4) or non-501(h)-elected member may
  have very different legal risk tolerance for an activity than a 501(h)-elected (c)(3) member;
  surfacing this early avoids a member being blindsided into an activity it can't legally do at scale.
- **Credit imbalance.** Press and funders gravitate to the largest/most visible member; without an
  explicit credit-sharing norm, smaller members disengage feeling used.
- **No sunset/review point.** Coalitions that never formally ask "should we continue?" often persist
  past their usefulness, draining member staff time on a fading campaign.
- **Recruiting for size over alignment.** A coalition with many loosely-aligned members is often
  weaker than a smaller, tightly-aligned one — vet prospective members against the shared message
  framework before inviting them, not after.

## Practitioner vs. Advisor Application

- **As the practitioner (coalition coordinator or founding-org staff):** Draft the MOU before the
  first public action, run the message-alignment circulation with a hard deadline and default-approve
  clause, and keep a living decision log so new members can see how past disagreements were resolved.
- **As an advisor/consultant:** When brought in to fix a struggling coalition, first diagnose whether
  the root problem is governance (no decision rule) or alignment (real strategic disagreement no
  governance process can paper over) — recommend a governance-model change only for the former; for
  the latter, help members narrow scope or split into parallel coalitions on sub-issues rather than
  forcing artificial consensus.

## Example

**Input:** "Six housing nonprofits want to push back on a proposed zoning bill together — help us set
up how we'll work as a coalition."

**Output approach:** Recommend a steering-committee model (appropriate for 6 members); draft the MOU
covering purpose/scope (this bill and directly related amendments only), decision rule (simple
majority of steering committee for tactical decisions, full-coalition majority for public position
changes), spokesperson protocol, and a sunset review at end of legislative session; draft the
one-page shared message framework with the single ask and 3 supporting points; note that each
member's own lobbying-hour tracking for this bill remains its individual responsibility under
`nonprofit-legislative-advocacy`.