It starts with a practical problem. A nonprofit needs a grant writer for a six-month project. Or a graphic designer to refresh a website. Or a trainer to deliver a workshop series. The work is real and time-limited and hiring a full-time employee feels like more than the situation requires.
So the organization brings someone on as an independent contractor. Issues a 1099 at the end of the year. Moves on.
That arrangement is entirely appropriate — when the classification is correct. The problem is that many nonprofits are not sure whether it is.
And the cost of getting it wrong — in back taxes, penalties, benefits liability, and legal exposure — consistently exceeds the cost of getting it right the first time.
Worker classification is one of the most common HR compliance gaps in the nonprofit sector. Here is what determines how someone should be classified, and how to make that call with confidence.
Why This Matters More Than Most Organizations Realize
Misclassification is not a technicality. When an organization classifies a worker as an independent contractor who should legally be an employee, it is avoiding — knowingly or not — a set of obligations it is legally required to meet: payroll taxes, workers' compensation, unemployment insurance, and in some cases, benefits.
The IRS and the Department of Labor both have enforcement authority over worker classification, and they use it. An audit that finds misclassified workers can result in back payroll taxes, interest, and penalties for every year the misclassification occurred. State agencies add another layer of exposure — and California, in particular, operates under one of the most stringent classification frameworks in the country.
None of this disappears because the worker never complained. None of it disappears because the person signed an agreement calling themselves a contractor.
The label on the arrangement does not determine its legal character. The actual nature of the working relationship does.
The IRS's Three-Factor Test: What Actually Determines Classification
The IRS uses a three-category framework to assess whether a worker is an employee or an independent contractor. Courts and agencies refer to this as the common law test, and it focuses on the degree of control and independence in the relationship.
1. Behavioral Control
Does the organization control how the worker performs the work — not just what the outcome is, but how they get there? This includes whether the organization sets the work schedule, requires the worker to use specific methods or tools, provides training on how to do the job, or directs the sequence and process of the work. The more control the organization exercises over the how, the more the arrangement looks like employment.
2. Financial Control
Does the organization control the economic aspects of the working relationship? This includes whether the worker can work for other clients, whether they have invested in their own tools or business infrastructure, whether they are paid by the hour or by the project, and whether they have the opportunity for profit or loss. A worker who is economically dependent on one organization — who cannot realistically work for others and has no investment in an independent business — looks more like an employee than a contractor, regardless of the label.
3. Type of Relationship
Does the arrangement have the characteristics of an employment relationship? This includes whether there is a written contract, whether the organization provides employee-type benefits such as health insurance or paid leave, whether the relationship is permanent or indefinite rather than project-based, and whether the services performed are central to the organization's regular business activity. A long-term, ongoing arrangement doing the core work of the organization is a harder sell as independent contracting than a time-limited, project-specific engagement.
⚠️ Watch for: The most common misclassification pattern in nonprofits: a contractor who started as a specific project engagement, completed it, and then simply continued working — often indefinitely, often doing ongoing operational work — without anyone revisiting the classification.
The ABC Test: California and Other States Go Further
For nonprofits operating in California — or in other states that have adopted similar frameworks — the IRS test is not the only analysis that applies. California's AB 5 established the ABC test as the standard for worker classification, and it starts from a different presumption: a worker is an employee unless the hiring entity can affirmatively demonstrate all three of the following:
A. The worker is free from the control and direction of the hiring entity in connection with the performance of the work, both under the contract and in fact.
B. The worker performs work that is outside the usual course of the hiring entity's business.
C. The worker is customarily engaged in an independently established trade, occupation, or business of the same nature as the work performed.
Part B is where many nonprofit arrangements fail the ABC test.
If a nonprofit's core work is providing legal services, and it engages someone to provide legal services, that worker likely cannot be classified as an independent contractor under California law — regardless of how the IRS would view the relationship. The work is not outside the usual course of the organization's business. It is the business.
💡 Tip: California AB 5 includes exemptions for certain professions and business-to-business arrangements. But those exemptions have specific criteria and do not apply broadly. If your organization operates in California and regularly engages contractors for work central to your mission, a classification review is worth doing now — not after an audit.
Practical Signals That a Contractor May Be Misclassified
Beyond the formal tests, a set of practical signals tends to appear in arrangements that are functionally employment even when labeled as contracting:
The worker follows your organization's schedule rather than setting their own hours
They work primarily or exclusively for your organization over an extended period
They use your organization's equipment, software, or workspace to do the work
They are supervised day-to-day by a staff member rather than working independently toward a deliverable
Their work is central to what your organization does — not a specialized, peripheral service
They have been doing this work for more than a year with no defined project end date
They receive reimbursement for expenses in a way that resembles an employee expense policy
None of these factors is automatically determinative on its own. Classification is a totality-of-circumstances analysis. But the more of these signals are present, the more vulnerable the arrangement is.
Getting It Right From the Start
The most effective way to avoid misclassification is to make the classification decision deliberately — before the engagement begins, not after a relationship has developed informally over months or years.
That means asking the right questions at the point of engagement:
Is this a defined project with a clear scope and end date, or is this ongoing operational work?
Will this person work independently toward a deliverable, or will they be integrated into your team's day-to-day operations?
Does this person operate as an independent business — do they have other clients, their own tools, their own business infrastructure?
Does your state have a classification framework more stringent than the IRS test, and does it apply here?
If the answers point toward employment, the right path is to classify the worker as an employee — with all the obligations that entails. The cost of getting this right is real. The cost of getting it wrong is almost always higher.
When to Get HR Support
Worker classification decisions are not always straightforward. The line between a legitimate contractor arrangement and a misclassified employee is genuinely fact-specific, and it shifts depending on state law, the nature of the work, and the structure of the engagement.
Organizations that engage contractors regularly — for program delivery, communications, fundraising, or operations support — benefit from having those arrangements reviewed by an HR professional with nonprofit-specific experience. Not as a one-time compliance exercise, but as a standard part of how engagements get structured.
The goal is not to avoid using contractors. Contractor relationships are legitimate, useful, and appropriate in many contexts. The goal is to use them correctly — so that when the IRS or a state agency asks, the answer is confident and defensible.
Contractor Classification Self-Check
◯ Worker classification reviewed before the engagement begins, not after
◯ IRS three-factor test applied: behavioral control, financial control, type of relationship
◯ State-specific framework reviewed if organization operates in California or other ABC test states
◯ Contract language reflects the actual nature of the relationship — not just the desired label
◯ Contractors are not working indefinitely on core operational functions
◯ No contractors are following organizational schedules, using org equipment, or supervised like employees
◯ Classification reviewed when the scope or duration of an engagement changes significantly
Mission Edge's nonprofit HR team helps organizations review contractor arrangements, apply the correct classification frameworks, and build the documentation that protects against audit exposure.
If your organization regularly engages contractors and has not reviewed those arrangements recently, now is the right time to do it.
