Somewhere in the request for proposals is a sentence that changes the shape of your application: preference will be given to collaborative approaches. Funders increasingly require or prefer collaborative proposals, because they want problems solved holistically by multiple organizations working together rather than by siloed organizations competing for the same funding to do overlapping work. That preference is reasonable, and it puts a specific demand on you. A coalition proposal is not a solo proposal with partner logos added to the cover page. It is a document that has to describe a working arrangement between independent organizations, with governance, a divided budget, and a plausible answer to what happens when one partner underdelivers. This lesson covers when collaboration is worth the overhead, the three structures coalitions actually use, the documents you sign before applying, how the proposal itself is written, and how the grant is managed once it lands.

Why Collaborate, and What It Costs

The case for collaboration is easy to make and easy to overstate, so it is worth holding the benefits and the costs side by side before deciding. On the benefit side, a coalition lets you reach more people, if the organizations serve different populations or geographies, and cover more services, so that one organization does youth mentoring while another provides job training. It demonstrates systems thinking to a funder, which is increasingly what they are evaluating. It increases organizational capacity without solo expansion, meaning you can deliver a larger program without hiring for every function yourself. It opens access to funding that is only available to coalitions. And it shares the administrative burden of budget management and reporting across more than one back office.

The costs are structural rather than incidental. Decision-making gets more complex, because three or more organizations reach consensus more slowly than one. Governance questions arrive immediately and have to be answered before you submit: who leads, and who reports to the funder? Budget coordination is contentious, since somebody has to decide who gets which funds. And accountability becomes genuinely difficult, because the funder holds one party responsible for results that depend on organizations it has no contract with. If one partner fails, the consequences do not stay with that partner.

When Collaboration Makes Sense

The decision is rarely close once you write it down honestly. Both columns below describe real situations, and the right-hand one is where most failed coalitions started.

The hardest of these to apply to yourself is the existing-relationship test. Every coalition assembled shortly before a deadline feels, at the time, like a group of organizations that get along well and could work together. What is missing is any evidence of how they behave when something goes wrong, which is precisely the information a funder is trying to infer from your application. Partners who have already run a program together, shared data, or resolved a disagreement have something to describe. Partners who have only had a promising meeting do not, and the proposal will read that way.

Coalition Structure: Three Models

Structure determines who holds the money, who signs the report, and where the authority sits when partners disagree. Choose it before writing, because it changes what the proposal has to say.

The lead organization model is the default for good reasons: it is legible to funders, it puts accountability in one place, and it requires the least new machinery. Its weakness is that it converts partners into subcontractors in practice even when the proposal describes them as equals, which is a slow source of resentment. The co-leader model addresses that at the cost of speed, since every significant decision now needs two organizations to agree. The fiscally sponsored model exists because at a certain number of partners neither of the first two works: no single organization can credibly hold the money without dominating, and shared leadership across many parties becomes unworkable.

Coalition Governance: The Documents You Sign First

The Memorandum of Understanding. Signed before applying, not after the award. The MOU is where the coalition's real design gets settled, and the discomfort of writing it is the point: every question it forces you to answer now is a question that would otherwise be answered during a crisis. It should document:

• Each partner's role and responsibilities
• The decision-making process, whether by consensus or majority vote
• Budget allocation, meaning how the money is divided
• Timeline and deliverables for each partner
• Dispute resolution
• What happens if a partner leaves mid-grant
• Intellectual property and data ownership

The detailed budget breakdown. Show exactly which partner does what, and what it costs. A coalition budget that reads as a single organizational budget with a note about partners tells the funder nothing about how the work is divided. Break it out by partner and by function: one partner on program delivery, another on data collection, a third on external evaluation, and the lead organization on budget management and funder coordination, each with its own line. This is also the document that surfaces disagreements about money while there is still time to resolve them.

Subcontracts, in the lead organization model. These are formal contracts between the lead and each partner specifying deliverables, timelines and payment. They are not a sign of distrust; they are what makes the lead organization's accountability to the funder enforceable downstream. Without them, the lead has promised the funder outcomes it has no contractual means of obtaining.

Writing a Coalition Proposal

A coalition proposal carries all the usual sections plus the burden of explaining an arrangement the reviewer cannot see. Take each section in turn.

The executive summary introduces the coalition and says why the partners together are stronger than any of them alone. If you cannot answer that in the summary, the reviewer will assume the coalition is an artifact of the RFP requirement.

The partners and roles section describes, for each partner: the organization's mission and history, its specific role in this coalition, its relevant expertise and capacity, and what it will deliver. Concrete deliverables per partner are what distinguish a coalition from a list of supporters.

The problem statement has to show why this problem needs a multi-organization response at all. The structure to aim for is: youth need mentoring AND job skills AND family support; Organization X provides mentoring, Y provides skills training, and Z provides family counseling. The problem, described properly, should make the coalition look inevitable rather than convenient.

The solution and partners section describes the integrated approach and shows how the services coordinate rather than merely coexist: youth work with an Organization X mentor, participate in Organization Y job training, while their families receive support from Organization Z. Coordination is the claim a funder is most skeptical of, so describe the handoffs.

The coalition decision-making section explains governance in plain terms: the coalition leadership team meets monthly, decisions are made by consensus, and the lead organization coordinates the overall budget. A few sentences of this kind do more for reviewer confidence than a page of partnership language.

The outcomes and evaluation section shows integrated outcomes rather than a stack of separate organizational metrics. Something in the shape of: by a given date, 80% of youth will achieve a specified outcome, with family engagement measured by Organization Z's metric. The budget then follows with a clear breakdown by partner and a narrative that matches the roles you described.

Common Coalition Pitfalls

Partners added just for the grant. Including an organization to strengthen the proposal when there is no real working relationship. Funders can tell, usually because the partner's role is described more vaguely than everyone else's. Only include genuine partners.

Unclear roles. "Organization A and B will work together" is too vague to be assessed. Say instead: Organization A recruits and mentors youth, at 20 hours per week; Organization B conducts skills training, at 10 hours per week per participant. Specificity is also what makes the arrangement manageable later, since a role no one can measure is a role no one can be held to.

Unequal power dynamics. The lead organization dominates and the partners come to feel like subcontractors rather than equals. Where an imbalance genuinely exists, name it rather than papering over it: Organization A leads fiscal management, while B and C are equal program partners. Reviewers are more persuaded by an honest asymmetry than by an implausible claim of perfect equality.

No contingency plan. What happens if a partner leaves? The proposal should address it directly: if Partner X leaves, Partner Y is trained to take over those responsibilities. This is the question a skeptical reviewer asks silently about every coalition, and answering it unprompted is a signal of maturity.

Budget conflicts. Partners disagree about how the money is divided, usually after the award, when the amounts are real. Have the hard conversations BEFORE applying and document the outcome in the MOU. A coalition that cannot agree on the budget under the low-stakes conditions of an application will not agree on it under the high-stakes conditions of an award.

Managing a Coalition Grant

Winning the grant converts a proposal into an operating arrangement, and the arrangement needs maintenance. Monthly coalition meetings coordinate progress, troubleshoot problems and share data; 1-hour meetings are standard, and the discipline is to spend that hour on problems rather than on status reports that could have been circulated in writing. Data sharing works on a simple division: partners collect data on their own activities and the lead organization aggregates it for reporting. Establish data-sharing agreements up front that respect confidentiality, because participant data crossing organizational boundaries is the compliance exposure most coalitions overlook.

Budget coordination means the lead organization processes partner expenses and reimbursements, which only works if partners are on the same accounting and reporting timeline. Agreeing that timeline early prevents the familiar situation where the lead cannot close its own books because one partner submits expenses late. Unified reporting is the visible output: individual partner reports are aggregated into one coalition report, so the funder sees an integrated narrative and integrated outcomes rather than three organizations describing three programs. Partner communication is what holds the rest together. The lead organization is responsible for ensuring partners feel valued and informed, with regular updates on funder communications, changes and new requirements. Partners who hear from the lead only when something is needed from them stop treating the coalition as theirs.

Sustainability Beyond the Grant

The best coalitions continue past the grant that created them, and that outcome is planned rather than lucky. Once the first grant has proven the working relationship, jointly pursue additional grants on the strength of it, since a coalition with a delivered program is a substantially stronger applicant than one with a promising plan. Formalize the partnership through shared data systems and governance, so that the arrangement no longer depends on the individuals who negotiated it. Build a coalition brand that is distinct from the individual organizations, which gives funders and the community something to recognize. And create shared outcomes and impact reporting, because a coalition that can describe its combined effect has an argument no single member could make alone.

Anti-Patterns

• The MOU after the award. Applying first and negotiating roles, budget splits and dispute resolution afterwards, when the money is real and positions have hardened.
• Logos as partnership. Naming organizations in the proposal without a specific deliverable attached to each, which reviewers read as padding.
• Equality by assertion. Describing all partners as equal when one holds the money and makes the decisions, instead of naming the asymmetry honestly.
• Handshake subcontracts. Operating the lead organization model without formal contracts, leaving the lead accountable to the funder for work it cannot enforce.
• Status-report meetings. Spending the monthly hour on updates that could have been circulated in writing, rather than on the problems only the group can solve.
• Aggregating data without agreements. Collecting participant data across organizational boundaries before anyone has settled confidentiality and ownership.
• Mismatched books. Letting partners run on different accounting and reporting timelines, so the lead cannot close a reporting period on schedule.
• Extractive communication. Contacting partners only when the lead needs something from them, until the coalition belongs to the lead alone.
• Letting it end with the grant. Treating the coalition as a funding vehicle rather than a relationship, and dissolving the strongest asset the grant produced.

Practice Prompts

• Take a coalition you are considering and test it against both columns of the collaboration table. Write down which row you are relying on, and whether an outside reviewer would agree.
• For each proposed partner, write the single sentence describing what they will deliver. Any partner whose sentence you cannot write is a partner you are adding for appearances.
• Draft the MOU section on what happens if a partner leaves mid-grant, before any other section. It is the one most often omitted and the one most often needed.
• Build the budget breakdown by partner and function, then circulate it. The disagreement it produces is information you need before submission, not after.
• Write the governance paragraph for the proposal in three sentences: who meets, how often, and how decisions are made.
• Choose your structure deliberately from the three models, and write one paragraph explaining why the other two are wrong for this coalition.
• Sketch the data-sharing agreement: who collects what, who aggregates it, and what confidentiality protections travel with the data between organizations.

Reflection

Think about the last partnership your organization entered, whether it was funded or not. Was it built on an existing working relationship, or assembled because an opportunity appeared with a requirement attached? If it was the second, consider what actually happened after the submission, and whether the collaboration continued in any form once the funding question was resolved. Consider also where your organization sits in the power structure of the coalitions it joins. If you are usually the lead, ask whether your partners would describe themselves as partners or as subcontractors, and whether you have ever asked them. If you are usually a partner, ask whether you have ever raised a budget concern before an application went in, or whether you waited, as most organizations do, until the money was awarded and the conversation was harder. The habits that make coalitions work are mostly habits of saying uncomfortable things early.

Glossary

• Coalition proposal: a grant application submitted by multiple organizations working together, which must describe governance, divided budget and coordinated services, not just shared intent.
• Lead organization: the nonprofit acting as fiscal lead, receiving all grant funds, subcontracting to partners, managing the budget and reporting, and holding accountability to the funder.
• Co-leaders: a structure in which two or more organizations share leadership and make decisions collaboratively, gaining equity at the cost of speed.
• Fiscal sponsor: a separate nonprofit that creates and hosts a coalition, enabling independent governance without any one partner dominating.
• Memorandum of Understanding: the document signed before applying that records each partner's role, the decision-making process, budget allocation, deliverables, dispute resolution, departure terms and data ownership.
• Subcontract: the formal contract between a lead organization and a partner specifying deliverables, timelines and payment.
• Unified reporting: the practice of aggregating individual partner reports into a single coalition report so the funder sees one integrated narrative and set of outcomes.
• Data-sharing agreement: the terms under which partners exchange participant data, covering who collects, who aggregates, and what confidentiality protections apply.

Related Lessons

• Collaboration Readiness Assessment: Is Your Organization Ready to Partner?
• How to Write a Memorandum of Understanding (MOU)
• Partnership Models for Nonprofits: From Referral Networks to Legal Mergers
• Power-Sharing in Partnerships: Equitable Collaboration
• Conflict Resolution in Multi-Org Collaborations
• Collective Impact Frameworks: When and How They Work
• The Grant Compliance Toolkit: Monitoring, Reporting, and Closeout

Closing

Coalition proposals reward organizations that did the difficult work before submitting. Almost everything that goes wrong later, the resentment about money, the partner who stops delivering, the vague role that nobody can measure, the coalition that dissolves the week the grant closes, traces back to a conversation that was postponed because the deadline was near and the atmosphere was friendly. Choose your structure deliberately. Sign the MOU before you apply. Give every partner a deliverable specific enough to be assessed. Name the power imbalance if there is one. Answer the departure question before a reviewer has to ask it. Then, once the grant is running, spend the monthly hour on problems and keep the partners informed even when you need nothing from them. Coalitions that operate that way tend to outlive the grants that funded them, which is the only real measure of whether the collaboration was genuine.

Key Takeaways

• Funders increasingly require or prefer collaborative proposals, so the question is usually how to collaborate well rather than whether to collaborate.
• Weigh the benefits, including reach, complementary services and shared administrative burden, against real costs in slower consensus, governance complexity, budget coordination and shared accountability.
• Do not collaborate with competitors, with partners you have no working relationship with, across disconnected geographies, or where the grant is small enough that coordination costs exceed the benefit.
• Pick one of three structures deliberately: lead organization for small coalitions, co-leaders for equal-capacity partners, and a fiscal sponsor for large coalitions with complex governance.
• Sign the MOU before applying, covering roles, decision-making, budget allocation, deliverables, dispute resolution, mid-grant departure and data ownership.
• Give every partner a specific, measurable deliverable in the proposal, since vagueness reads as padding to reviewers and prevents accountability later.
• Answer the contingency question in the proposal: if a partner leaves, who takes over their responsibilities.
• Manage the grant with monthly meetings, agreed data-sharing, a shared reporting timeline, unified reporting and proactive communication with partners.
• Plan for the coalition to outlive the grant through joint applications, shared systems, a coalition brand and shared impact reporting.

Frequently Asked Questions

Who should be the lead organization? Usually the organization with the strongest administrative and finance capacity, or the one that initiated the coalition; sometimes it is simply the largest by budget. What matters more than the criterion is that all partners agree it is the right choice. Resentment over lead selection destabilizes a coalition early, and it rarely surfaces as an explicit objection. It surfaces as slow responses, missed deadlines and a partner who stops volunteering information.

How is grant money divided among partners? Based on what each partner will actually do. If Partner A does 60% of the service delivery, they receive roughly 60% of the service delivery funds. Budget allocation should follow directly from the roles you described in the proposal, which is another reason to write the roles precisely. Allocation that tracks the work prevents the most common source of coalition resentment, which is a partner concluding that their share does not reflect their contribution.

Can partners be competitors? Rarely well. Competing organizations may undermine each other or jockey for control of the coalition, and both behaviors are visible to funders. Collaborative grants work best when partners see themselves as complementary rather than competitive. If you must partner with a competitor, be very clear about roles and non-overlapping service areas, and put that clarity in the MOU rather than relying on goodwill.

What if a partner's performance is weak? This is the hardest coalition issue and the one most often handled too late. Address it quickly and directly: "We notice X isn't happening. What's the barrier?" Then problem-solve together, since the cause is often capacity rather than commitment. If the partner cannot improve, the MOU should already set out what happens: they may step back from that function, or you may need to find a replacement. Having written that clause before the award is what makes the conversation possible without ending the relationship.

Should the coalition continue if the grant is not renewed? Often yes, if the working relationship proved itself. A coalition that has delivered a program together has a track record, shared systems and demonstrated outcomes, all of which make it a stronger applicant for the next opportunity than a group assembling from scratch. Formalizing the partnership through shared governance and data systems is what allows it to survive a funding gap rather than dissolving with the grant that created it.