Why I Chose a Federated Model Instead of One Big Nonprofit
When people hear that I run eleven separate 501(c)(3) organizations under the TheraPetic® Healthcare Provider Group, the first question is almost always: why not just one organization with departments? I have answered that question hundreds of times. The short version is that one organization with departments shares risk across everything it touches. A liability event in one program can threaten assets in every program. A compliance failure in one grant can freeze funding for unrelated clinical services. A federated model isolates that exposure.
The longer version is that healthcare, animal-assisted intervention, service dog training, and nonprofit housing assistance each operate under different regulatory frameworks. Collapsing them into a single legal entity means your board is simultaneously accountable to HUD guidance, state veterinary practice acts, the Fair Housing Act, ADA compliance requirements, and IRS Form 990 reporting obligations for programs that have almost nothing in common operationally. That is not governance. That is chaos with a shared tax ID.
Federated governance distributes accountability to the program level while preserving coordinated strategy at the group level. I built the TheraPetic® structure to do exactly that, and in 2026, after years of refinement, I can say it works. But not without real failures along the way.
How the Structure Actually Works Across Eleven Entities
Each of the eleven entities in the TheraPetic® Healthcare Provider Group is independently incorporated, holds its own federal tax-exempt status, files its own Form 990, and maintains its own EIN. They are not subsidiaries in the legal sense. They are peer organizations operating under a shared administrative infrastructure and a coordinating agreement that I drafted with nonprofit legal counsel.
The coordinating agreement governs three things: shared services pricing, brand usage rights, and the conditions under which an entity can exit the group. It is not a merger document. It does not create a parent-subsidiary relationship. The IRS does not recognize informal group affiliations the way it recognizes group exemptions under Revenue Procedure 80-27, and I made the deliberate choice not to pursue a group exemption because it requires the central organization to exercise control over member organizations in ways that would compromise their independent board governance.
What actually holds the group together is operational interdependence, shared mission alignment, and frankly, relationships I have built over fifteen years. The legal structure enables the model. The relationships sustain it.
Separate Boards Are Not Optional. They Are Load-Bearing
This is the point where I push back hardest against other nonprofit executives who try to simplify federated governance by cross-appointing the same people to every board. I understand the instinct. Recruiting qualified board members is genuinely difficult, and filling eleven separate boards with eleven separate skill sets feels overwhelming before you start.
Cross-appointing the same individuals to every board does not simplify governance. It simulates governance while actually centralizing control in a small group of people who are legally obligated to act in the best interest of each separate organization simultaneously. That is a conflict of interest by design, and it will surface in the worst possible way. During a grant audit, a legal dispute, or an IRS examination.
Each entity in the TheraPetic® group has a minimum of three independent directors who do not sit on any other entity's board. I apply a strict conflict-of-interest policy that requires annual disclosure, and I conduct orientation for every new board member that covers the fiduciary duty of loyalty specific to their single entity. They are not advisors to the group. They are fiduciaries to their organization.
The practical result is that when one entity's board makes a decision that affects the group, I have to bring that information back to each other entity's board separately and let each board evaluate it on its own terms. That process is slower than unilateral executive decision-making. It is supposed to be.
Shared Operations Without Shared Liability
The operational efficiency of the federated model comes from shared services, not shared legal structures. Across the eleven entities, I run a shared administrative core that handles HR compliance, accounting, IT infrastructure, and clinical documentation systems. Each entity contracts with that administrative core through a written management services agreement that specifies the scope of services, the cost allocation methodology, and the termination rights of each party.
The cost allocation methodology matters enormously for IRS purposes. If shared services are not allocated to each entity at fair market value using a documented, consistent methodology, the IRS can characterize the arrangement as private benefit to the administrative organization or as inurement. I use a three-factor allocation model: headcount, program revenue, and clinical volume. Every year I document the basis for those allocations in a memo that sits in each entity's board minutes.
The officialservicedog.com Training Plus program operates as its own entity with its own board, its own liability insurance, and its own training curriculum. It shares administrative infrastructure with the group but maintains a completely separate trainer credentialing track and incident reporting system. That separation was intentional from day one because service dog training liability has a different risk profile than clinical mental health services, and I did not want one liability event in the training program to affect clinical program assets.
The Failures I Will Not Pretend Did Not Happen
I expanded too fast in year four. I incorporated three new entities in the same calendar year without confirming that each one had the board capacity, the initial funding runway, and the program infrastructure to operate independently from launch. I was thinking about mission growth and not about governance readiness, and those are not the same thing.
Two of those three entities were effectively dormant for eighteen months after incorporation. They held active 501(c)(3) status and were legally obligated to file Form 990-N returns, maintain registered agent status, and hold annual board meetings. They were doing almost none of that. I discovered the gap during an internal audit I commissioned after a grant funder asked for governance documentation across all affiliated entities.
What fixed it was the rule of three, which I will describe in the next section, and a governance readiness checklist I now require every proposed new entity to complete before I will initiate incorporation. That checklist asks eighteen questions. If an entity cannot answer fifteen of them affirmatively before incorporation, we do not incorporate.
The second major failure was assuming that shared values meant shared compliance culture. Two of my entity executive directors were excellent program leaders and genuinely committed to the mission. They were also not trained in nonprofit compliance and did not know what they did not know. One of them accepted a restricted grant without reviewing the grant agreement with legal counsel and committed the entity to reporting obligations that required data collection systems we did not have.
I remediated that by building a compliance review protocol that requires every grant agreement, every major contract, and every new regulatory requirement to be reviewed by both the entity's board and the group's shared legal counsel before signature. It added administrative friction. It also prevented three subsequent compliance failures that I can identify in hindsight.
The Rule of Three for Expansion
After the year-four expansion failures, I developed what I now call the rule of three. Before any new entity enters the incorporation process, three conditions must be independently verified.
First, the entity must have identified and committed a founding board of at least three individuals who are not currently serving on any other group entity's board. They must have completed orientation, signed conflict-of-interest disclosures, and demonstrated understanding of their fiduciary obligations through a written attestation reviewed by legal counsel.
Second, the entity must have secured a minimum of eighteen months of operating runway before it accepts its first client, patient, or training participant. That runway can come from grants, donations, or a formal operating reserve commitment from the group's administrative core. But it must be documented and liquid. Mission enthusiasm does not pay registered agent fees.
Third, the entity's program model must be legally distinct from every existing entity in the group. Not just programmatically different. Legally distinct, meaning it operates under a different primary regulatory framework or serves a population segment that existing entities are affirmatively prohibited from serving under their own organizational documents. If it is not legally distinct, I ask whether it should be a program of an existing entity rather than a new legal organization.
Since implementing the rule of three, I have proposed four new entities. Two passed all three conditions and were incorporated. Two did not pass and became programs within existing entities. That is the right outcome.
Per-Entity Compliance in a Federated Healthcare Nonprofit
Compliance in a federated healthcare nonprofit is not a group function. It is an entity function that the group supports. Each entity is responsible for its own state charitable registration, its own annual reporting obligations, its own HIPAA compliance program if it handles protected health information, and its own professional licensing requirements for clinical staff.
The group administrative core maintains a compliance calendar that tracks deadlines for all eleven entities in a single system. That calendar is reviewed monthly by a compliance coordinator who flags upcoming deadlines to each entity's executive director. The entity is responsible for completing the filing. The group is responsible for making sure the entity knows the deadline is coming.
For entities that provide clinical mental health services, HIPAA compliance is non-negotiable and entity-specific. Each clinical entity maintains its own Notice of Privacy Practices, its own Business Associate Agreements with vendors, and its own breach response protocol. The group can provide template documents and legal review, but the signed agreements are between the entity and its vendors. Not between the group and anyone.
State charitable solicitation registration is the compliance obligation that catches federated organizations most off guard. Each entity that solicits donations in a state must be registered in that state independently. If all eleven entities solicit nationally, that is potentially eleven separate registration obligations per state. I use a third-party registration management service to track and file those obligations, and I build the cost into each entity's administrative budget as a fixed annual line item.
What I Know Now That I Wish I Had Known First
Federated governance is not a growth strategy. It is a governance philosophy that happens to enable growth when implemented correctly. The organizations that run federated models poorly treat the structure as a tool for expansion and end up with a proliferation of shell entities that share a mission statement and nothing else.
The organizations that run federated models well treat each entity as a complete, independent organization that could survive on its own if the group relationship ended tomorrow. That framing changes every decision. From board recruitment to grant strategy to program design. I ask myself that question about each entity at least once a year: if this entity had to operate completely independently starting next month, what would break? Whatever the answer is, that is what I need to fix.
After fifteen years working in service animal training and nonprofit healthcare operations, with a CSDT credential from the International Association of Canine Professionals and executive responsibility for a multi-entity healthcare organization, I can say with confidence that the federated model is the right structure for mission-diverse nonprofit healthcare work. It is also significantly harder than it looks from the outside.
If you are considering a federated structure for your nonprofit, the question is not whether you can incorporate multiple entities. The question is whether you can govern multiple entities simultaneously, maintain compliance independence for each of them, and build boards that take their fiduciary obligations seriously even when those obligations occasionally conflict with group-level strategy. If the answer to all three is yes, the model works. If the answer to any one of them is not yet, start with a single entity and build governance capacity before you build organizational complexity.