Fiscal Sponsorship: Legal Structure, Risks, and Best Practices
Fiscal sponsorship is usually presented as a shortcut: an emerging initiative needs charitable infrastructure, an established nonprofit agrees to receive donations or administer funds, and everyone moves forward under the fiscal sponsorship label. That framing is useful but incomplete. Fiscal sponsorship is not a legal status created by statute. It is a contractual relationship built on a narrow IRS foundation: a 501(c)(3) organization may support work carried out by another organization or project only if the sponsor retains discretion and control, limits funds to its own exempt purposes, and keeps records showing charitable use.
Two IRS Revenue Rulings built the legal foundation, but neither created a freestanding fiscal sponsorship regime. Rather, they require the sponsor to remain the charitable decision-maker, not a conduit for earmarked funds. That is why the sponsorship agreement is critical. With no statutory default rules, the agreement must answer who controls funds, employs staff, owns assets, reports to funders, bears liability, and manages exit.
For boards, fiscal sponsorship is a governance decision, not a back-office convenience. A sponsor may be accepting responsibility for employment, restricted funds, insurance exposure, multistate solicitation compliance, donor communications, grant obligations, and the project’s public conduct. A project seeking sponsorship faces the mirror-image question: how much control it will give up, what assets and donor relationships it may own, and how it can exit if it later becomes independent.
In comprehensive Model A, the project usually becomes a sponsor program, and the sponsor often becomes the legal employer. In pre-approved grant Model C, the project usually remains separate, but the sponsor must still make and document an independent charitable grant decision. Both can work, but they create different consequences for liability, employment, tax reporting, fundraising compliance, asset ownership, and exit planning.
This article focuses on the harder board question: whether the sponsor is prepared to own the legal, employment, insurance, fundraising, and exit consequences of the model it chooses. Fiscal sponsorship can be effective infrastructure. But without a documented model, preserved discretion and control, mapped liability, and clear mission fit, it becomes unmanaged governance risk.
The Legal Basis for Fiscal Sponsorship
The fiscal sponsorship structure works because the IRS has recognized that a 501(c)(3) organization may use charitable funds to support a project carried out by another party, including a non-exempt party, if the sponsor remains the charitable actor and not a pass-through conduit.
In a revenue ruling, the IRS held that a 501(c)(3) organization may distribute funds to non-exempt organizations if (1) the distributions are limited to specific projects that further the sponsor’s exempt purposes, (2) the sponsor retains control and discretion over the funds, and (3) the sponsor keeps records showing use for 501(c)(3) purposes.
That rule sits inside the broader 501(c)(3) operational test. A sponsor must operate primarily for exempt purposes and cannot let charitable assets inure to insiders or serve private interests more than incidentally. A sponsor that rubber-stamps transfers, lets project insiders control funds, or lacks a real charitable role can look less like a grant-maker and more like a conduit.
That is the legal core: discretion and control. The sponsor must be able to approve, deny, condition, monitor, stop, or redirect use of the funds. If donors or project leaders are promised that funds will automatically be turned over regardless of charitable use, the sponsor is no longer exercising discretion; it is functioning as a conduit.
Another IRS ruling reinforces the same point. Contributions to a charity supporting a charitable project may be deductible where the charity reviews and approves the project, retains control and discretion over the funds, requires accounting, and can withdraw approval or redirect funds. The IRS respected the structure because the charity remained the decision-maker.
The agreement between sponsor and project is the operating law of the relationship. It must preserve the sponsor’s authority to approve the project, control funds, require reports, stop payments, redirect unused or misused funds, and terminate without allowing restricted charitable assets to drift into private or non-exempt use. Sponsors are protected so long as they behave like the charitable actor responsible for the program or grant decision. Without an agreement – or with an inadequate one – sponsors may struggle to prove discretion, control, and charitable use.
The Models of Fiscal Sponsorship
Fiscal sponsorship appears many ways. Gregory Colvin’s taxonomy gives the field a useful vocabulary, but the two models most boards encounter are Model A, or comprehensive fiscal sponsorship, and Model C, or pre-approved grant sponsorship. Other models exist, including independent-contractor and group-exemption variants, but the board’s first task is simple: do not approve “fiscal sponsorship” without approving a specific model. Note that these are not hard-and-fast rules—the sponsorship agreement could be a hybrid of the various models.
In Model A, the project becomes a program of the sponsor. The sponsor receives funds as its own charitable assets, pays expenses, hires or contracts with workers, carries legal responsibility, and reports the project as part of its operations. If the project has employees, they are generally the sponsor’s employees. Model A can be useful infrastructure, but legally, the sponsor is operating the project.
In Model C, the project remains legally separate, and the sponsor acts more like a grantor. The sponsor receives charitable contributions as its own assets, pre-approves the project as furthering its exempt purposes, and makes grants while retaining IRS-required discretion and control. The project remains responsible for its own tax reporting, contracts, employment, insurance, and operations.
Model C fails when the sponsor is not making a real grant decision. The sponsor should review the project; approve budgets and requests; condition disbursements on charitable use; require reports; and retain authority to withhold, redirect, or terminate funding. If project insiders effectively control the funds, Model C becomes a conduit arrangement.
The choice of model determines who owns assets and intellectual property, who employs staff, whose insurance must respond, where revenue and expenses appear, and what happens at separation. In Model A, assets and IP often belong to the sponsor unless the agreement says otherwise. In Model C, they usually remain with the project entity, subject to grant conditions or negotiated license terms.
Exit planning is especially important in Model A. Because the project is legally a sponsor program, cash, contracts, donor records, grant agreements, equipment, data, branding, and IP may sit with the sponsor. A departing project may need an express transfer, assignment, license, or funder consent before anything follows it.
Consider and compare the consequences of each:
| Issue | Model A — Comprehensive | Model C — Pre-Approved Grant |
|---|---|---|
| Legal structure | Project becomes a program of the sponsor. | Project remains separate from the sponsor. |
| Liability | Sponsor assumes legal and fiduciary responsibility for project activity. | Project retains primary liability for its own operations; sponsor retains oversight responsibility for charitable fund use. |
| Employment | Project staff are typically employees or contractors of the sponsor. | Project maintains its own employment and contractor relationships. |
| Tax reporting | Project activity is reported as part of the sponsor's operations. | Project remains responsible for its own tax reporting, if applicable; sponsor reports grants and sponsorship activity consistent with its own reporting obligations. |
| Assets and intellectual property | Assets and IP often belong to the sponsor unless the agreement creates transfer or license rights. | Assets and IP generally remain with the project entity, subject to the agreement. |
| Exit rights | Exit can be complex because funds, assets, staff, contracts, donor lists, and IP may sit legally with the sponsor. | Exit is usually simpler because the project has remained legally separate, though unused restricted funds and grant conditions still must be addressed. |
Model D and Model B are different enough to flag but not confuse with Models A or C. Under Model D’s group exemption, subordinate organizations may have their own recognized exemption under a central organization. Under Model B, the charitable project is carried out by an independent contractor. Neither is the same as a sponsor receiving charitable contributions as its own assets and supporting a project while retaining discretion and control.
For the sponsor’s board, the practical point is simple: the model is the legal architecture. The board should approve a specific model, document why it fits, and make sure the agreement follows through. If the documents say Model C but the sponsor manages staff and operations, or say Model A but the project controls funds and donor commitments, the board has not approved a coherent structure.
The Sponsor’s Risk Exposure
If the arrangement is loosely drafted, incompletely disclosed, or operated outside the sponsor’s mission, employment claims may land on the sponsor, insurance may not respond, restricted funds may trigger charitable-trust enforcement, and exemption risk may arise if the project does not further the sponsor’s charitable purposes.
Employment liability is the first risk, especially in Model A. If the project is a sponsor program, project staff are typically sponsor employees or contractors. Claims for discrimination, harassment, retaliation, wrongful termination, wage-and-hour violations, leave disputes, benefits disputes, and worker misclassification come to the sponsor. The board may think it is approving a mission-aligned project; legally, it may also be approving a new workforce.
Insurance mismatch is the second risk. Fiscal sponsorship should be disclosed to the sponsor’s broker and carriers before launch. General liability, D&O, EPLI, workers’ compensation, and any professional or cyber coverage should be checked against the project’s activities, staff, locations, payroll, and fundraising. If the project was not disclosed, a carrier may argue the exposure is outside the underwritten risk or excluded.
Restricted-fund liability is the third risk. Funds raised for a sponsored project are not interchangeable with general operating dollars merely because the sponsor holds them. Donor communications, grant agreements, board approvals, or accounting records may restrict the funds to a particular charitable program. Misuse can become a charitable trust violation, breach of fiduciary duty, or misuse of charitable assets.
ZeroDivide is the concrete cautionary example. In 2022, the California Attorney General announced a stipulated judgment resolving allegations that a nonprofit fiscal sponsor misspent approximately $606,000 in restricted donations intended for two charitable programs and used those funds for unrelated salaries, benefits, and expenses. The judgment required dissolution, more than $460,000 in damages, penalties, and fees, and temporary leadership restrictions for two officers. This was a severe result, but the point is that donor intent and program restrictions can become enforceable governance obligations.
Mission drift is the fourth risk. The IRS discretion-and-control standard assumes the sponsor is using assets to further its own exempt purposes. A project can be well-run and popular but still be a bad sponsorship candidate if it does not align with the sponsor’s exemption and programs.
Model C does not eliminate that risk. If the sponsor receives donor funds, takes a fee, and forwards the balance to a non-exempt project without meaningful review, the arrangement can resemble a private-benefit conduit. The key question is whether the sponsor is operating a charitable grant program or facilitating the financial objectives of another party.
For boards, the risk review should be mechanical. Before approval, the board should identify who employs staff, which insurance line covers each claim category, how restricted funds will be tracked, who can stop payments, what donor or grant restrictions apply, what duties the agreement creates or disclaims, and why the project furthers the sponsor’s mission. If those answers are missing, the review is incomplete.
The Employment Layer: What “Employer of Record” Actually Means
If the project is a sponsor program, project staff are sponsor staff. That means the sponsor’s handbook, wage-and-hour practices, benefits rules, anti-discrimination policies, leave policies, payroll systems, workers’ compensation coverage, and employment records all have to cover them. If a project director mishandles a termination, ignores overtime, misclassifies a worker, or allows a hostile work environment, the claim does not stay neatly with the project.
Worker classification does not get easier because the work is charitable. Federal wage-and-hour law looks to economic reality, not labels. Calling someone an “independent contractor,” “project consultant,” or “community organizer” does not control if the person is economically dependent on the sponsor or project, integrated into the work, directed closely, and not operating an independent business.
Massachusetts is especially unforgiving. Its independent-contractor statute presumes employee status unless the employer satisfies all three parts of the ABC test. The second prong — work outside the usual course of the employer’s business — is hard in fiscal sponsorship, because the project must further the sponsor’s mission in order to be sponsored.
The same discipline applies in D.C., Connecticut, and New York. Charitable status and project autonomy do not avoid wage notices, lawful pay practices, anti-discrimination rules, workers’ compensation, unemployment insurance, payroll withholding, or state employment registrations. The questions are where the work is performed and who is functioning as the employer.
Fiscal sponsorship can quietly become a multistate employment platform: a Massachusetts sponsor, a Connecticut project lead, a New York coordinator, and D.C. programming. Each state may bring its own wage, leave, unemployment, workers’ compensation, withholding, and posting rules. The sponsor should confirm those obligations before hiring.
Insurance must follow the same map. EPLI may cover discrimination, harassment, retaliation, and wrongful termination, but wage-and-hour claims are often excluded or limited. Workers’ compensation depends on correct payroll, classifications, and state coverage. General liability may matter for events, field work, public programming, or physical spaces. The sponsor should disclose project staff, locations, activities, and payroll before launch.
Under Model A, a project hire should be treated as the sponsor’s own hire. The sponsor should approve the position, confirm funding, classify the worker, identify the work state, include the worker in payroll and benefits analysis, update insurance disclosures, and ensure the supervisor follows sponsor policies.
The Jurisdiction Layer: Multistate Charitable Registration
Charitable solicitation registration is easy to miss because it does not track the sponsor’s headquarters. It tracks solicitation activity and often donor location. A Massachusetts sponsor raising funds online for a project with supporters in Connecticut, New York, or D.C. may create registration obligations outside Massachusetts even if it is incorporated, governed, and staffed there.
The model affects the analysis but does not eliminate it. In Model A, the sponsor is generally the charitable organization soliciting and receiving contributions for its program. In Model C, the project may remain separate; if the sponsor solicits and receives funds, the sponsor has registration exposure, and if the project solicits directly in its own name, the project may also have exposure. The analysis follows who asks, who receives, what names are used, and where donors are located.
For a non-501(c)(3) project, the registered fiscal sponsor is usually the compliance owner when it solicits, receives, and controls contributions. The project is the beneficiary of the solicitation unless it independently solicits in its own name.
| Jurisdiction | Core trigger | Fiscal sponsorship issue |
|---|---|---|
| Connecticut | Soliciting charitable contributions unless registered or exempt. | Small-organization threshold looks to annual contribution activity, not just a single Connecticut campaign; project names used in solicitation may need to be disclosed. |
| District of Columbia | Soliciting in D.C. without an applicable exemption. | No general dollar threshold automatically excuses solicitation; sponsor must hold the certificate when it solicits for a non-501(c)(3) project and must report contributions, expenses, and use of proceeds after the registration period. |
| Massachusetts | Soliciting contributions in Massachusetts or having contributions solicited on the charity's behalf. | Sponsor needs a valid Certificate of Solicitation before project fundraising begins and must renew annually. |
| New York | Soliciting contributions from persons in New York unless exempt. | $25,000 exemption is tied to New York-source contributions and no professional fundraiser; annual reporting and audit thresholds can be triggered by sponsor-level revenue. |
The best practice is to include multistate registration in the project approval. Before fundraising starts, the sponsor should identify the solicitation states, public-facing names, professional fundraisers or consultants, project entity status, available exemptions, filing and renewal dates, post-solicitation reports, and whether project revenue affects financial-reporting thresholds. A sponsor operating across Massachusetts, D.C., Connecticut, and New York is managing four compliance questions.
Drafting the Agreement
A formal fiscal sponsorship arrangement is critical. If the parties never agree on limits, transfer rights, or exit mechanics, the sponsor often holds the stronger legal position because the funds are its charitable assets and its exemption is at risk.
MobilizeGreen v. Community Foundation for the National Capital Region illustrates the point. The D.C. Court of Appeals treated the relationship as contractual, declined to impose fiduciary duties beyond the agreement, and looked to the contract to decide who bore the obligation to transfer the sponsorship. Informal expectations did not control once the written terms did.
At minimum, the agreement should identify the model, describe how the project furthers the sponsor’s exempt purpose, state services and fees, restrict fund use, preserve discretion and control, require reporting, address insurance and employment responsibility, and set termination terms. Exit provisions should separately cover charitable funds, noncash assets, donor data, intellectual property, contracts, grants, federal awards, third-party consents, and post-termination communications.
For a full agreement-drafting checklist mapped to these risk areas:
The Decision Framework: Should an Established Nonprofit Sponsor?
For an established nonprofit, the sponsorship decision should start with the same question the board would ask before launching a new program: does this project further our mission, and can we govern it responsibly? Mission fit is the threshold legal condition that allows the sponsor to treat the project as part of its exempt activity.
The mission question must be specific. The board should be able to explain how the project advances the sponsor’s charitable purposes, how it will monitor that fit, and who can stop or redirect the work if the project drifts.
Reputational exposure also runs mostly to the sponsor. Donors give to the sponsor, grants may be awarded to the sponsor, and registrations and annual reports may be filed by the sponsor. If the project mishandles funds, staff, donor communications, compliance, or public controversy, the sponsor’s name is usually the first one donors and regulators see.
Capacity is equally important. The sponsor must have the infrastructure to exercise the control it reserves on paper: fund accounting, grant restrictions, payroll, HR compliance, insurance coordination, charitable solicitation registration, contract review, budget monitoring, and project reporting.
That does not mean established nonprofits should avoid sponsorship. For a board with meaningful budget, staff, controls, and governance infrastructure, sponsorship can be a legitimate way to incubate a new program, support a coalition, house a time-limited initiative, or advance mission-aligned work.
A practical board review should include these questions:
· Does the project directly further the sponsor’s exempt purposes?
· Which fiscal sponsorship model is being approved, and why?
· Who will approve budgets, expenditures, fundraising language, contracts, staffing, and material changes in scope?
· Does the sponsor have the finance, HR, insurance, and compliance capacity to administer the project?
· Where will the project solicit funds, employ staff, hold events, or deliver services?
· What donor, grant, or legal restrictions will apply to project funds?
· What happens if the project runs out of money, violates policy, creates liability, or no longer fits the sponsor’s mission?
· What happens when the project ends?
· Can the project separate, spin off, or move to another fiscal sponsor, and what assets or obligations follow it?
For Model C, the board should add one more question: are we making an independent charitable grant decision, or simply providing tax-exempt infrastructure for someone else’s project?
Fiscal sponsorship can be a strong tool for mission-aligned work, but the sponsor should decide as the legal owner of the risk, not as a service provider doing a favor. If the board cannot articulate mission fit, capacity, insurance coverage, employment responsibility, solicitation compliance, independent grantmaking judgment, and exit mechanics, it is not ready to sponsor.
Conclusion
Fiscal sponsorship is legally sound when it is done correctly. The IRS has long recognized that a 501(c)(3) organization may use its charitable assets to support work carried out by another organization or project. But that recognition has boundaries: the sponsor must retain discretion and control, ensure charitable use, and keep records proving that use. Those requirements are the legal foundation, not optional formalities.
Most problems do not begin with the concept. They begin with an arrangement that was never fully documented: no clear model, no decision on donor data, no employment allocation, no insurance review, no exit terms, and no multistate solicitation analysis. The missing provisions become the dispute.
ZeroDivide shows that restricted-fund misuse can produce real consequences, including monetary liability, governance restrictions, and dissolution. The multistate registration layer adds another practical risk: a sponsor or project with donors, staff, campaigns, or programming across Massachusetts, D.C., Connecticut, and New York is managing several compliance regimes, not one.
For boards, fiscal sponsorship should be approved as a governance, employment-law, insurance, tax, and charitable-solicitation decision. The sponsor should know the model, mission fit, fund controls, staffing responsibility, insurance response, fundraising footprint, restricted-fund tracking, and exit mechanics before it signs.
The organizations that get burned are usually not the ones that chose the imperfect model. They are the ones that never wrote down which model they were using, never aligned the agreement with the model, and never checked whether insurance and state registrations matched the real footprint. Before signing, the board should have counsel review the agreement, confirm preserved discretion and control, and review the sponsor’s insurance program with the broker or carrier. That review is far cheaper before launch than after a wage claim, donor dispute, restricted-fund problem, or regulator inquiry.
This article is for general informational purposes only and does not constitute legal advice. Reading this article does not create an attorney-client relationship. For advice specific to your organization's situation, contact Commonlight Legal LLP.
Alex Booker is the Managing Partner of Commonlight Legal LLP, a boutique law firm serving nonprofits in Massachusetts, DC, New York, and Connecticut. He advises executive directors and boards on employment law, governance, and general nonprofit counsel.
Before founding Commonlight, Alex adjudicated federal employment cases at the U.S. Merit Systems Protection Board, where he researched and advised on novel issues in federal personnel law, and he litigated whistleblower, wage and hour, and civil rights cases on behalf of employees at a DC employment firm. He is admitted to practice in Massachusetts and Washington, DC.