Why Government Benefit Assistance Organizations Don't Qualify for 501(c)(3)

Nonprofit government benefit assistance organizations sit in a dangerous blind spot of tax exemption. Helping someone navigate disability benefits, immigration filings, veterans compensation, workers compensation, housing subsidies, or medical coverage feels charitable, so founders assume 501c3 501(c)(3) status follows naturally. It doesn't. The IRS treats individualized benefit navigation as a private service unless the organization fits into a narrow set of doctrinal exceptions. Miss those exceptions and the work stops being charity. It becomes a subsidized service operation whose primary output is personal economic gain for identifiable individuals.

Most government benefit assistance nonprofits fail IRS Form 1023. They build around case outcomes, confuse program eligibility with a charitable class, and lean on language like advocacy or support as if intent could override structure. Section 501c3 501(c)(3) doesn't exempt effort or compassion. It exempts organizations whose activities, and resource allocation prove that the public, not the individual claimant, is the primary beneficiary. Government benefit assistance qualifies only in tightly defined circumstances. Outside those boundaries, denial is not harsh or political. It's doctrinally correct.

The Doctrinal Fork: Public Benefit or Private Benefit

Section 501c3 501(c)(3) starts with a binary question that never goes away: does the organization operate for public benefit, or does it operate to deliver value to private individuals. The operational test controls that answer. Mission statements don't. Good intentions don't. The IRS looks at what the organization actually does, who receives the benefit, and where the economic value lands. If the organization routes value to identifiable individuals in a predictable way, private benefit analysis attaches immediately.

Government benefit assistance organizations hit this fork on day one.

1. One path leads to tax exemption because the activity advances a recognized exempt purpose that serves the public as a whole.
2. The other path leads to denial because the activity is intended to help specific individuals secure personal economic outcomes through programs designed to pay individuals, not classes.

The difference is structural, not rhetorical. An organization doesn't cross into public benefit because the system is complex or unfair. It crosses only when its activities are designed so the primary beneficiary is the public, even if individuals incidentally benefit along the way.

This distinction explains why sympathy never saves these applications. The IRS applies doctrine, not narrative. When individualized assistance sits at the center of operations, the Service treats the organization as a private service provider wearing a nonprofit label. Every section that follows flows from this fork. Either the structure proves public benefit under narrow, recognized standards, or the private benefit finding controls the outcome under IRS Form 1023.

Individualized Government Benefit Assistance is Presumptively Private Benefit

Individualized government benefit assistance triggers private benefit analysis by default. When a nonprofit helps a named person file a claim, prepare documentation, pursue an appeal, or secure approval under a government program, the activity produces a direct economic outcome for that individual. Cash payments, back pay, legal status, housing rights, medical coverage. The benefit is concrete, measurable, and personal. Under the operational test, that result matters more than the effort required to achieve it.

Government programs already distribute these benefits to individuals. When a nonprofit positions itself as the intermediary that makes the transfer succeed, it doesn't create a public benefit. It facilitates a personal one. The IRS considers the end product of the activity, not the difficulty of the process or the policy goals behind the statute. If the outcome attaches to a specific person, private benefit analysis controls unless the organization can meet a recognized exception.

Volume doesn't change the character of the work either. Helping many individuals doesn't transform private benefit into public benefit. Repetition confirms purpose. When success is measured by approvals won, benefits released, or statuses granted, the organization aligns itself with individual claimants rather than the public at large. At that point, the nonprofit form stops being descriptive and starts being misleading. The activity looks like a service business subsidized by tax exemption, and the burden shifts entirely to the organization to prove why it qualifies under section 501c3 501(c)(3).

Administrative Assistance is Not Legal Representation

Most nonprofit government benefit assistance organizations are not providing legal representation. They're providing administrative assistance: intake, document collection, form completion, claim filing, deadline tracking, agency correspondence, and help navigating an administrative appeals process. That work can be competent, necessary, and high impact.

It's still not legal aid in the 501c3 501(c)(3) sense unless the organization is actually providing legal services through licensed counsel and operating within a relief-of-poverty meaning.

This distinction matters because founders keep trying to borrow legal doctrine to justify administrative casework. They cite legal aid concepts, they talk like a public-interest law firm, they describe staff as advocates, and they describe clients as if the organization is doing representation. The IRS looks at what the organization actually does and what the service produces. Administrative casework aimed at securing benefits is a service delivered to specific individuals to obtain personal economic outcomes. Calling it legal work doesn't change the operational reality, and it doesn't open the door to the legal aid model or public interest litigation model.

Administrative assistance is not exempt by itself. It can qualify under 501c3 501(c)(3) only when it's structurally constrained and subordinate to a dominant exempt program, and only when the charitable class is defined correctly. If administrative casework is the main program, the private benefit analysis doesn't get softer because the work is nonlegal. It gets cleaner. The organization is not litigating systemic issues, not creating precedential impact, and not operating as legal aid for the poor. It's running a one-on-one benefit navigation service tied to individual outcomes, and that's the private benefit problem in its simplest form.

Why Calling Casework Advocacy Makes Things Worse

"Advocacy" is the most misused word in government benefit assistance nonprofits, and it backfires fast. Helping an individual complete forms, pursue an appeal, or respond to an agency request is not advocacy under section 501c3 501(c)(3). It's administrative assistance tied to a personal outcome. Using advocacy language doesn't elevate the activity. It misclassifies it.

Advocacy has a defined meaning in tax exemption analysis. It refers to efforts aimed at influencing public policy, shaping systemic outcomes, or educating the public on matters of common concern. Individual claim support does none of that. It doesn't change rules, alter standards, or affect anyone outside the named beneficiary. Dressing up casework as advocacy screams confusion about purpose, and that confusion strengthens a private benefit finding rather than weakening it.

Organizations that perform administrative assistance must describe it accurately and fence it tightly. Advocacy belongs to public-facing education, policy analysis, and systemic reform efforts that stand apart from individual cases. When the word is used to mask one-on-one benefit navigation, it doesn't clarify mission. It compounds the doctrinal failure.

The First Narrow Exception: Legal Aid Limited to Poverty

The legal aid exception exists, but it's far narrower than founders want to believe. Rev. Rul. 69-161 allows individualized legal representation to qualify for tax exemption only when the organization operates as relief of poverty. That means actual legal services provided to individuals who can't afford representation by any other means. Poverty is not inferred. It's screened, documented, and enforced as an eligibility condition.

This exception applies only when the organization is doing legal work. Licensed counsel. Representation, not guidance. Legal judgment, not form completion. Administrative assistance doesn't qualify simply because it sits near the law. Even when legal services are involved, the charitable class must be defined by financial inability, not by eligibility for a government program, medical condition, employment history, or statutory status. Without a poverty screen, individualized legal assistance produces private benefit and fails the operational test.

An organization doesn't become legal aid because it charges nothing or because clients face hardship. The IRS looks for a defined charitable class grounded in limited means and an operation designed to serve that class exclusively. When services extend to individuals who could obtain representation privately, the relief-of-poverty rationale collapses. At that point, the organization is subsidizing personal legal outcomes, not advancing a public benefit recognized under section 501c3 501(c)(3).

The Second Narrow Exception: Public Interest Litigation

Public interest litigation survives private benefit analysis only when the litigation itself serves a public purpose independent of any individual recovery. Rev. Rul. 75-74 recognizes exemption where an organization brings cases that address issues of broad public importance and where no plaintiff has sufficient economic incentive to pursue the matter alone. The litigation exists to produce precedent, deterrence, or systemic correction. Individual plaintiffs appear because procedure requires them, not because the organization exists to secure their personal awards.

Government benefit assistance organizations almost never fit this model. Administrative claims, agency appeals, and entitlement recovery are not public interest litigation. They apply existing statutes to individual facts to obtain benefits the law already promises to specific people. There's no systemic question, no precedential impact, and no public-facing outcome beyond the claimant's result. When the end product is approval, payment, or status for a named individual, the private benefit is the purpose of the activity, not an incidental byproduct.

Economic incentive is the dividing line. Public interest litigation may qualify where no rational plaintiff would bear the cost alone. Benefit claims fail that test by definition, as these programs pay individuals, sometimes in substantial amounts. When private firms take the work until margins shrink, that fact alone undermines any claim that the cases lack sufficient economic incentive. Using public interest language to justify entitlement casework doesn't expand exemption. It confirms that the organization misunderstands the doctrine it's trying to invoke.

Why Administrative Casework Can't be Reframed as Litigation

Administrative casework is not litigation for purposes of section 501c3 501(c)(3), and the distinction is not subtle. Litigation tests law. Administrative casework applies it. Filing claims, submitting evidence, responding to agency notices, and pursuing internal appeals operate entirely inside a statutory framework designed to award benefits to individuals who meet predefined criteria. The process may feel adversarial, but it doesn't seek to change rules, interpret statutes, or establish precedent. It seeks approval.

That difference ends the analysis. Public interest litigation tolerates incidental private benefit because the dominant output is systemic. Administrative benefit assistance produces no such output. Each case stands alone. Each success delivers a personal entitlement. The work concludes when the individual outcome is secured. There's no spillover effect, no generalizable result, and no public-facing consequence beyond the claimant's file closing.

Attempts to blur this line usually rely on labels. Appeals get called litigation. Hearings get framed as trials. Staff get described as advocates. None of that alters the operational reality. Agencies resolve entitlement claims to determine who gets paid under existing law. The organization's role is to help individuals navigate that process more effectively. That role is service delivery, not public impact. When administrative casework affects staffing, budgets, and success metrics, the organization is not litigating for the public. It's advancing private economic outcomes, repeatedly, by design.

Charitable Class vs. Program Eligibility

Program eligibility is not a charitable class. The distinction is foundational and routinely ignored. Government benefit programs define who qualifies to receive money, services, or legal status under a statute. Section 501c3 501(c)(3) defines who a charity may serve. Those categories overlap sometimes. They are not interchangeable.

A charitable class must be broad, indefinite, and grounded in charitable need. Poverty. Limited means. Inability to access assistance without help. Exposure to conditions the law treats as a public concern. Government programs don't use those filters. They rely on employment history, disability ratings, immigration categories, service records, medical diagnoses, residency, or statutory triggers written to allocate public funds. Those criteria sort eligibility. They don't establish charitable need.

That's why organizations built around benefit navigation keep failing the operational test. They define their class by reference to the statute they're administering:

• Nuclear workers.
• Disabled applicants.
• Veterans with qualifying service.
• Immigrants eligible for a specific form of relief.

Each description mirrors the government program. None creates a charitable class on its own. When a nonprofit adopts the same definition, it doesn't expand public benefit. It inserts itself into an entitlement pipeline and treats successful outcomes as proof of charity.

Hardship narratives don't fix this defect either. Illness, disability, procedural complexity, or bureaucratic disadvantage explain why assistance helps. They don't define a charitable class unless tied to economic inability or another recognized exempt purpose. A person can be sick, disabled, or overwhelmed and still fall completely outside any charitable class. Geographic limits, occupational labels, and program-specific descriptions shrink the pool. They don't add a charitable qualifier. Without an independent charitable filter, individualized assistance produces private benefit by design, and the exemption claim collapses under scrutiny.

The Resource Allocation and Dominant Activity Test

The IRS doesn't stop at mission statement. It always follows the money, the staff time, and the outcomes. Under the operational test, the dominant activity defines the organization. When most resources flow to individualized assistance, the organization is delivering personal economic benefits, regardless of how the mission is framed.

Staffing tells the story first. Case managers, intake specialists, benefits navigators, appeal coordinators. When personnel are hired to move individual files through administrative systems, the organization operates as a service provider to named individuals. Budgets confirm it. Salaries, software, outreach, and overhead tied to claims processing, representation support, and follow-up work consume the bulk of expenditures. Metrics seal it. Success is measured in approvals, awards, payments released, or statuses granted. That measurement framework aligns the organization with private outcomes, not public benefit.

Secondary programs don't cure a dominant private activity. A few workshops, a thin policy page, or occasional public materials don't rebalance the analysis when individualized assistance dominates operations. The IRS weighs facts and circumstances, not labels. If individualized benefit assistance dominates staffing, expenditures, and organizational focus, the private benefit is not incidental. It's the purpose. Once that conclusion is reached, the operational test fails, even if the services are free and the need feels obvious.

When the Organization Exists to Create Jobs for Insiders

Private benefit analysis doesn't start with programs, it often ends before programs matter at all. If a nonprofit government benefit assistance organization is structured to create paid positions for insiders, founders, or their associates, the exemption case is denied immediately. The IRS looks at who controls the organization, who gets paid, how compensation is justified, and whether the work exists because the job exists. When employment is the covered-up output, everything else is window dressing.

This problem shows up early in IRS Form 1023 review because compensation is easy to trace and hard to explain away. Titles, salaries, job descriptions, reporting lines, and hiring plans tell the story faster than mission language. If the organization can't function without paying insiders to perform individualized casework, the private benefit is structural, not incidental.

Highest Compensated Employees and the Private Benefit Trigger

The IRS scrutinizes the highest compensated employees because compensation reveals purpose. When the top earners are founders, board members, family members, or close associates, and their roles center on individualized benefit assistance, the analysis shifts immediately to private benefit and private inurement. The question becomes simple: did the organization form to serve the public, or to create paid roles justified by a charitable wrapper.

In government benefit assistance organizations, this issue is amplified because the work is already individualized. Paying insiders to help named individuals secure personal economic outcomes looks like a value transfer stacked on top of another value transfer. The nonprofit doesn't just facilitate private benefit for claimants. It creates sustained private benefit for insiders through salary. That dual flow of value is fatal under the operational test.

Key Employees, Control, and Structural Self Dealing

Key employees are where many government benefit assistance nonprofits die quietly, because founders think they found a loophole that doesn't exist. IRS Form 1023 barely mentions key employees, so applicants assume the category only matters later, or only matters on Form 990. That assumption is wrong. The IRS uses the key employee concept during determination even when the form doesn't prompt for it, because the category is doctrinal, not procedural.

A key employee is not defined by title. The IRS looks at three factors together:

1. compensation,
2. authority,
3. and influence over activities.

Anyone who controls how programs are designed, delivered, or prioritized, and who receives a substantial share of organizational resources, qualifies. Officers and directors are obvious. Key employees are the quieter problem. They are the people who run the operation without sitting on the board, and they often carry more real power than the board ever does.

The omission on IRS Form 1023 is deliberate. The Service doesn't need a checkbox to identify functional control. It reads job descriptions, budgets, narratives, and staffing plans. It looks at who designs the programs, who delivers the core services, and who can't be removed without the organization folding. That's how key employees are identified during determination, even if the term never appears on the application itself.

Why the Compensation Threshold Trick Fails

Founders love the idea that compensation thresholds are a shield. They keep salaries under the highest compensated employee line and assume the problem disappears. It doesn't. The key employee test hits harder precisely because it ignores labels and dollar cutoffs.

If an organization has a $100,000 annual budget and pays $85,000 to one employee, that employee has substantial influence by definition. It doesn't matter whether the title is program manager, caseworker, coordinator, or attorney. That person controls capacity, priorities, and outcomes. Without them, the organization can't function. That's influence over activities, and the IRS treats it as such.

The problem compounds when the employee is the architect of the program. Designing the services, setting intake criteria, deciding which cases get handled, shaping how resources are allocated. At that point, the employee is not just influential. They are determinative. Compensation analysis assumes the role exists to carry out an exempt purpose. When the role exists to deliver individualized assistance that already produces private benefit, paying a dominant insider to perform it confirms that the organization's sole purpose is to create and sustain that job.

When Key Employees Collapse the Exemption Case

This is where disqualified persons analysis intersects with private benefit and private inurement. Founders, board members, officers, and key employees can't structure an organization so that paid roles exist primarily to employ themselves or their associates. Reasonable compensation doesn't save the organization when the job itself is the point.

Government benefit assistance organizations are especially vulnerable here because the work is already one on one and outcome driven. When a single insider performs most of the casework, designs the program, and consumes most of the budget, the organization stops looking like a charity and starts looking like a subsidized practice. The nonprofit form becomes a funding mechanism for a job, not a vehicle for public benefit.

The IRS doesn't need to reach a hard conclusion at that stage. Control plus compensation plus individualized assistance equals substantial private benefit. Once that determination is made, denial under IRS Form 1023 follows without further analysis. The organization fails before charitable class, advocacy, or litigation arguments ever come into play.

Why Employment Driven Models Fail Before Programs are Reviewed

Organizations built around insider employment fail fast because they reveal motive. If the business plan centers on hiring founders, expanding staff positions tied to case volume, or scaling payroll based on claims processed, the IRS doesn't need to debate doctrine at length. The organization is operating in a commercial manner, even if services are free to recipients.

Attempts to sanitize the structure after nonprofit formation rarely work. Adding independent directors, revising titles, or inserting conflict policies doesn't change the fact that the organization exists to generate paid work for insiders performing nonexempt activities. Once compensation and control align around individualized benefit assistance, denial under IRS Form 1023 is not a close call. The organization fails the operational test before it ever reaches questions about charitable class, advocacy, or litigation models.

This section locks the door early. If the organization is a vehicle to create jobs for insiders, the exemption analysis is over.

The Commerciality Overlay: Free Services Don't Eliminate Commercial Purpose

Private benefit analysis doesn't operate alone. Government benefit assistance organizations will fail under the commerciality doctrine even before private benefit finishes the job. The IRS looks at whether an activity resembles a commercial service commonly offered in the marketplace and whether the nonprofit operates in a commercial manner. Charging no fees doesn't neutralize that analysis. It sharpens it.

Benefit navigation closely mirrors private-sector services: disability claims representatives, immigration consultants, veterans benefits agents, workers compensation advocates. These actors exist because there is demand for individualized assistance tied to personal economic outcomes. When a nonprofit performs the same work, using the same workflows, delivering the same outputs, and measuring success the same way, the IRS treats the activity as market substitution. The organization is not filling a charitable gap. It's undercutting a market by routing tax-exempt resources into services already priced by private actors.

Commerciality shows up in operation, not pricing. Case throughput models, intake pipelines, efficiency metrics, staffing tied to claim volume, and narratives about scaling services confirm a commercial purpose. When individualized benefit assistance dominates operations, the organization functions like a service firm whose revenue source happens to be donations instead of fees. Section 501c3 501(c)(3) doesn't subsidize service delivery simply because the service helps people navigate government programs. When the activity looks commercial and produces private economic outcomes, exemption fails on two fronts at once.

The Business Plan and Growth Narrative Trap

Business plans sink government benefit assistance organizations faster than almost any program description because they reveal intent without decoration. The IRS treats planning documents as evidence of purpose. When the plan reads like a service business roadmap, the exemption claim is at risk regardless of how charitable the mission sounds.

Growth language is the tell. Expanding service capacity by increasing case volume. Hiring staff to process more claims. Entering new regions to reach additional beneficiaries. Building operational efficiency to handle higher throughput. These are not neutral descriptions. They describe a scalable service model tied directly to individualized outcomes. The organization is planning to process more cases, not to advance a public benefit that exists independently of those cases.

This problem gets worse when staffing plans mirror revenue logic. Payroll growth tied to claims handled. Roles justified by workload rather than exempt purpose. Budgets made around sustaining salaries through donations instead of fees. The IRS reads that as commercial activity, even if no one ever pays for services. A charity doesn't grow its service footprint for its own sake; it carries out an exempt purpose that justifies its mission. When expansion is driven by case volume, the purpose becomes self sustaining service delivery.

Founders think a business plan proves seriousness. It does the opposite. It confirms that the organization operates like a firm providing individualized assistance at scale. Once that conclusion is drawn, the analysis doesn't need subtlety. The organization is pursuing a commercial objective through tax exemption, and denial under IRS Form 1023 follows cleanly.

Why Secondary Programs Don't Cure a Dominant Private Activity

When the primary activity produces private benefit, secondary programs have to carry substantial weight to rebalance the facts and circumstances. Most government benefit assistance organizations never clear that bar. They add education, research, or outreach language as insulation. The IRS doesn't credit insulation.

1. Secondary programs fail when they are thin, derivative, or aspirational. A few workshops tied to the casework. A policy page that summarizes existing rules. Occasional public presentations drawn from individual client experiences. These activities don't stand on their own as exempt purposes. They are paddings because the casework exists. That dependency matters. An exempt activity must function independently, with its own audience, outputs, and justification.
2. Dominance controls the analysis. If staffing, budget, and leadership attention revolve around individualized assistance, secondary activities are treated as incidental byproducts. The IRS looks at where time and money flow , not at future plans or minor add-ons. Promised programs don't count. Underdeveloped programs don't count. Activities that exist only to support casework don't count.

Denial letters routinely describe educational and advocacy efforts as insubstantial. The Service is not dismissing education as a concept. It's rejecting the idea that a marginal activity can neutralize a dominant private benefit. When individualized assistance defines the organization, surrounding activities have to do more than fluff. They have to carry the organization. Most don't.

The Classification Reality Most Founders Refuse to Accept

Some government benefit assistance organizations are not failing because they are poorly structured. They're failing because they are in the wrong tax category. Section 501c3 501(c)(3) is not a universal seal of legitimacy. It's a narrow classification reserved for activities that serve a public benefit independent of individual economic gain. Not all socially useful work fits there.

Benefit navigation aligns more naturally with noncharitable structures. Social welfare organizations under section 501c4 501(c)(4) can engage in advocacy, policy work, and member focused assistance without pretending that individualized outcomes are incidental. Fee based service entities can provide benefit assistance honestly, transparently, and sustainably without bending doctrine. Some organizations belong outside the tax exemption system entirely.

The refusal to accept this reality creates contortions. Founders stretch language, dilute doctrine, and force programs into 501c3 501(c)(3) frameworks they can't support. The IRS doesn't reward that effort. It reads the activity, class definition, and outcomes, then assigns the correct classification whether the organization likes it or not. Denial under IRS Form 1023 is not a judgment about value. It's a classification decision.

This matters because misclassification creates downstream damage. Organizations waste years chasing exemption that can't be justified, while exposing themselves to private benefit, private inurement, and commerciality findings along the way. The harder truth is simpler. If the work centers on helping individuals secure personal government benefits, and the structure can't prove that the public is the primary beneficiary, section 501c3 501(c)(3) is not the right home. No amount of drafting can change that.

Narrow Path or Predictable Denial

Government benefit assistance work qualifies under section 501c3 501(c)(3) only when the organization satisfies every element of the operational test at once. Partial compliance doesn't count. Sympathy doesn't fill gaps. It must prove that public benefit dominates private outcomes in both design and execution.

A compliant organization fits into one of three narrow configurations.

1. First, legal aid limited to relief of poverty. The organization provides actual legal representation through licensed counsel, imposes a real poverty screen, and limits services to individuals who can't obtain assistance by any other means. Eligibility for a government program is irrelevant unless it's paired with financial inability. Without that screen, individualized legal services produce private benefit.
2. Second, public interest litigation. The organization selects cases to address systemic issues of broad public importance, where no plaintiff has sufficient economic incentive to pursue the matter alone. Litigation is the activity and public impact is the objective. Individual recoveries are incidental. Administrative claims, entitlement recovery, and agency appeals don't qualify because they seek personal outcomes under existing statutes rather than systemic change.
3. Third, a dominant exempt program with tightly constrained individualized assistance. In this configuration, the organization's primary activity is public education, research, or systemic analysis that serves the entire charitable class rather than individual claimants. Individualized benefit assistance functions only as a secondary activity and is structurally incapable of defining the organization.

The IRS recognizes organizations that provide assistance to the poor and distressed (e.g., a disaster relief organization helping victims apply for FEMA benefits) as a charitable class, even if it leads to an individual economic gain. The activity must still center on the relief of a charitable need (poverty, disaster, etc.), not merely program navigation.

Education must be real and dominant. A substantial majority of resources must be devoted to public-facing instruction, training, or dissemination of information useful to the community, not to individual case outcomes. Where the organization engages in advocacy around government benefit systems, that advocacy must satisfy the methodology test under Rev. Proc. 86-43, 1986-2 C.B. 729. The organization must present a full and fair exposition of relevant facts, avoid distortion, avoid emotional or inflammatory presentation, and communicate in a manner designed to aid learning rather than secure outcomes. Unsupported opinion, client-driven narratives, or advocacy that exists only to advance individual claims doesn't qualify.

In this form, individualized assistance is limited, volunteer-driven, and tightly fenced. It doesn't control staffing, payroll, or program design. Paid staff focus on education, research, training, and systemic analysis. Case support, if offered at all, is ancillary and can't exceed a minority of organizational activity. It doesn't involve guaranteed outcomes, compensation recovery, or individualized entitlement maximization.

If individualized assistance begins to drive staffing, budgets, or success metrics, this configuration fails. At that point, the organization is no longer educational or systemic in operation. It becomes a benefit navigation service, and private benefit again dominates the analysis.

Outside these configurations, government benefit assistance fails:

• Casework driven models.
• Organizations built around insider employment.
• Structures that mirror commercial services.
• Programs defined by statutory eligibility rather than charitable class.

These are not close calls. They fail because individualized economic outcomes dominate the organization's operations.

Denial under IRS Form 1023 in these cases is not discretionary. It's the required outcome under the operational test. Government programs already deliver benefits to individuals. Tax exemption is rewarded to support organizations whose activities proves that the public, not the claimant, is the primary beneficiary.