A program coordinator has been working for the organization "on contract" for two years now: on the organization's schedule, using its equipment, under the founder's daily direction. One day, the CPA asks a single question: why is this person a contractor instead of an employee?
The founder answers honestly: because it's simpler. That's the worst possible answer, because "simpler" here means "cheaper right now and riskier with every passing month." A person's status is determined by the reality of the relationship, not by what's written at the top of the agreement.
An organization has three worker statuses: employee, independent contractor, and volunteer. Each has its own setup mechanics and its own boundaries, and mixing them up "to keep things simple" plants a quiet landmine under the organization, one that goes off at the first audit or conflict.
An employee is on payroll: the organization withholds taxes, pays employer taxes, and, crucially, controls the process of their work, not just the result. An independent contractor works differently: they decide for themselves how to do the job, often with their own tools, invoice for their work, and answer for the result, rather than following day-to-day direction.
A volunteer works unpaid, but that doesn't mean "with no setup at all": they need a described role, boundaries, and consent, and their hours are worth tracking. What ties all three statuses together: they're determined by the actual reality of the relationship, not the heading on a contract. You can call someone a contractor on paper, but if the organization controls exactly how they work day to day, reality says "employee," and that's what gets examined.
Labeling an actual employee a contractor "for simplicity" isn't a one-time saving, it's a compounding debt. In an audit or a conflict with the person themselves, back taxes, penalties, and disputes surface, and the longer the misclassification lasted, the bigger the bill.
The simple test for telling them apart: whoever controls the process of the work, not just its result, is most likely the employer. If the organization dictates when, where, and exactly how someone works, that's a sign of employment, whatever the contract calls it. Genuinely borderline cases exist, and they get settled with a CPA or an employment specialist before hiring, not after the landmine's already been planted. This is exactly the case where a cheap consultation ahead of time saves you from an expensive one later.
A volunteer with no structure burns out and leaves just like an employee, only faster, since nothing but motivation is holding them there. That's why a volunteer isn't "free labor," it's a role that needs managing: clear boundaries, clear consent about what they do, and tracked hours.
Tracking volunteer hours pays off twice over. It helps you avoid overloading someone and keeps them around longer, and it becomes an argument in grant applications: volunteer hours are a measurable community contribution that shows a funder real people stand behind the organization, not just a budget. What you set up carefully as people management ends up working for you in an application later.
Below is a quiz on three profiles of people working with an organization. In each one, determine the status by who controls the process, not by the label on the agreement.
A map of the people working with your organization, with statuses and notes marked "confident" or "ask a specialist." Go through everyone working with the organization and honestly mark where the status is obvious and where there's doubt that calls for a conversation with a CPA or employment specialist before, not after, a problem shows up.
Can I set someone up as a contractor if they want that themselves?
What the person wants doesn't override the reality of the relationship. If the organization actually controls the process of their work, that's an employee, regardless of mutual preference to label it otherwise.
What does misclassification actually put you at risk of?
Back taxes, penalties, and disputes that surface in an audit or a conflict. The longer the mistake lasted, the bigger the accumulated bill.
How do I read a borderline case where the signs are mixed?
This is exactly what CPAs and employment specialists are for. Mixed signs are a signal to ask a professional before hiring, not to guess on your own and hope for the best.
Do I need a written agreement with a volunteer?
A formal employment contract isn't needed, but describing the role, the boundaries, and getting consent is worthwhile. It protects both the organization and the volunteer from misunderstanding and burnout.
People in an organization are a question of status, but also a question of risk: wherever people work and events happen, something can go wrong. There's protection against that risk, and it gets purchased ahead of time. The next lesson is about insurance, and why a policy gets set up before the question "what if" comes up, not after.
The material in this lesson is educational and drafted for review by your attorney and CPA. This course does not replace professional advice and makes no promise of outcomes.