Why Collaborate?

Funders increasingly require or prefer collaborative proposals. They want problems solved holistically by multiple organizations working together, not siloed organizations fighting for funding.

Collaboration benefits:

  • Reach more people (if organizations serve different populations/geographies)
  • Cover more services (one org does youth mentoring, another provides job training)
  • Demonstrate systems thinking
  • Increase organizational capacity without solo expansion
  • Access funding only available to coalitions
  • Share administrative burden (budget management, reporting)

Challenges:

  • Complex decision-making (3+ orgs = slower consensus)
  • Governance questions (who leads? who reports?)
  • Budget coordination (who gets which funds?)
  • Accountability (what if one org fails?)

When Collaboration Makes Sense

Collaborate when:

  • RFP explicitly requires coalition (non-negotiable)
  • Problem is complex and needs complementary services
  • Partners have deep existing relationships (not forming just for grant)
  • Organizations serve connected populations (e.g., youth + families)
  • Grant amount justifies coordination overhead

Don't collaborate when:

  • Partners are competitors (will undermine grant)
  • There's no real working relationship (just adding names)
  • Grant is small ($10k or less—coordination cost exceeds benefit)
  • Organizations are geographically disconnected

Coalition Structure: Three Models

Model 1: Lead Organization (Most Common)

One nonprofit is fiscal lead. They:

  • Receive all grant funds
  • Distribute to partners via subcontracts
  • Manage overall budget and reporting
  • Hold funder accountability

Partners deliver specific services and report to lead org.

Best for: Small coalitions (2-3 partners), clear service division, one org with strong capacity

Model 2: Co-Leaders

2+ organizations share leadership. Decision-making is collaborative. This is more complex but more equitable.

Best for: Equal-capacity organizations, existing strong partnership

Model 3: Fiscally Sponsored Coalition

Separate nonprofit (fiscal sponsor) creates and hosts the coalition. Allows independent governance without one partner dominating.

Best for: Large coalitions (5+ partners), complex governance needs

Coalition Governance: Essential Documents

1. Memorandum of Understanding (MOU)
Signed before applying. Documents:

  • Each partner's role and responsibilities
  • Decision-making process (consensus, majority vote?)
  • Budget allocation (how is money divided?)
  • Timeline and deliverables for each partner
  • Dispute resolution
  • What happens if a partner leaves mid-grant
  • Intellectual property/data ownership

2. Detailed Budget Breakdown
Show exactly which partner does what and costs:

  • Partner A: Program delivery, $X
  • Partner B: Data collection, $X
  • Partner C: External evaluation, $X
  • Lead org: Budget management and funder coordination, $X

3. Subcontracts (if lead organization model)
Formal contracts between lead and each partner specifying deliverables, timelines, and payment.

Writing a Coalition Proposal

Proposal Structure:

Executive Summary
Introduce the coalition and why partners together are stronger than alone.

Partners & Roles Section
For each partner, describe:

  • Organization mission/history
  • Specific role in this coalition
  • Relevant expertise/capacity
  • What they'll deliver

Problem Statement
Show why this problem needs multi-organization response. Example: "Youth need mentoring AND job skills AND family support. Organization X provides mentoring, Y provides skills training, Z provides family counseling."

Solution & Partners
Describe integrated approach. Show how services coordinate: "Youth work with Org X mentor, participate in Org Y job training, while families receive support from Org Z."

Coalition Decision-Making
Explain governance: "Coalition leadership team meets monthly. Decisions made by consensus. Lead org coordinates overall budget."

Outcomes & Evaluation** Show integrated outcomes: "By [date], 80% of youth will [outcome], with family engagement measured by [Org Z metric]."

Budget
Clear breakdown by partner with narrative.

Common Coalition Pitfalls

Pitfall 1: Partners Added Just for Grant
Including "Partner X" just to strengthen proposal, with no real working relationship. Funders can tell. Avoid this—only include genuine partners.

Pitfall 2: Unclear Roles** "Organization A and B will work together" is too vague. Say: "Organization A recruits and mentors youth (20 hours/week). Organization B conducts skills training (10 hours/week per participant)."

Pitfall 3: Unequal Power Dynamics** Lead org dominates. Partners feel like subcontractors, not equal partners. If imbalance exists, name it: "Organization A leads fiscal management; B and C are equal program partners."

Pitfall 4: No Contingency Plan** What if a partner leaves? Proposal should address: "If Partner X leaves, Partner Y is trained to take over those responsibilities."

Pitfall 5: Budget Conflicts** Partners disagree on how money is divided. Have hard conversations BEFORE applying. Document in MOU.

Managing Coalition Grants

Monthly Coalition Meetings
Coordinate progress, troubleshoot problems, share data. 1-hour meetings are standard.

Data Sharing
Partners collect data on "their" activities. Lead org aggregates for reporting. Establish data-sharing agreements that respect confidentiality.

Budget Coordination
Lead org processes partner expenses and reimbursements. Partners should be on same accounting/reporting timeline.

Unified Reporting** Individual partner reports are aggregated into one coalition report. Funder sees integrated narrative and outcomes.

Partner Communication** Lead org ensures partners feel valued and informed. Regular updates on funder communications, changes, or requirements.

Sustainability Beyond the Grant

Best coalitions continue beyond the initial grant. Strategies:

  • Jointly pursue additional grants once first is proven
  • Formalize partnership through shared data systems and governance
  • Build coalition brand separate from individual orgs
  • Create shared outcomes and impact reporting

Frequently Asked Questions

Who should be the lead organization?

Usually the organization with strongest administrative/finance capacity, or the org that initiated the coalition. Sometimes the largest org by budget. Important: all partners should agree it's the right choice. Resentment over lead selection destabilizes coalition.

How is grant money divided among partners?

Based on what each partner will actually do. If Partner A does 60% of service delivery, they get ~60% of service delivery funds. Budget allocation should align with roles. This prevents resentment.

Can partners be competitors?

Rarely works well. Competing organizations may undermine each other or jockey for control. Collaborative grants work best when partners see themselves as complementary, not competitive. If you must partner with a competitor, be very clear on roles and non-overlapping service areas.

What if a partner's performance is weak?

This is the hardest coalition issue. Address it quickly and directly: "We notice X isn't happening. What's the barrier?" Problem-solve together. If partner can't improve, the MOU should outline what happens—they may step back from that function, or you may need to find replacement.