Checklist · Labor and Employment

Classifying Workers: Employee or Independent Contractor — A Practical Checklist

29 U.S.C. § 203

Type
Checklist
Jurisdiction
National
Date
2023-08-29
Topic
Labor and Employment

Worker classification is not one question but several, because the same person can be an employee under the Fair Labor Standards Act, an independent contractor under a state tax statute, and something else again under the copyright and patent laws. This checklist walks through the four tests that matter most — the FLSA economic-reality test as reshaped by the 2024 Department of Labor rule at 29 C.F.R. Part 795, the IRS common-law test behind Form SS-8, the ABC test of Dynamex and California's AB5, and the ERISA benefits overlay — and explains why a business must satisfy the strictest test that applies to it. It then maps the consequences of getting it wrong: back wages and overtime, employment taxes and penalties, retroactive benefits, and the frequently overlooked intellectual-property trap that a contractor's work is not automatically owned by the hiring party. Using a running example of a startup called Nimbus Labs engaging a freelance developer and a delivery driver, it gives practical, check-item guidance on classifying a role, papering a genuine contractor engagement, and defending the classification if it is ever challenged.

Classifying Workers: Employee or Independent Contractor — A Practical Checklist

Labor and Employment > Worker Classification | Published 29 August 2023 - Updated 24 February 2025 | UpLaw - uplaw.us

The label on the invoice does not decide the question. Whether a worker is an employee or an independent contractor is a legal conclusion the government reaches for you — under whichever test is strictest — and it can reach a different conclusion under the wage laws, the tax code, and the copyright act all at once.

Keywords: worker classification, independent contractor, misclassification, FLSA economic-reality test, DOL 2024 rule, IRS common-law test, Form SS-8, ABC test, Dynamex, AB5, Borello, work made for hire, invention assignment, payroll taxes, wage and hour


Why classification is a multi-test minefield (FLSA vs. IRS vs. state vs. ERISA)

Ask most founders whether their freelancer is a contractor and they will point to the contract, the 1099, and the invoices. None of that controls. Classification is a question of legal status determined by the working relationship itself, and — this is the part that surprises people — there is no single national test. A worker can be a contractor for one purpose and an employee for another at the same time, because different statutes ask different questions and answer to different agencies.

Four regimes matter most:

  • The Fair Labor Standards Act (29 U.S.C. § 203) governs minimum wage and overtime. It uses a multifactor "economic reality" test that asks whether the worker is economically dependent on the business or genuinely in business for themselves.
  • The Internal Revenue Code governs who withholds income tax, pays FICA and FUTA, and issues a W-2 versus a 1099. The IRS uses a common-law "right to control" test (Rev. Rul. 87-41), resolved formally through Form SS-8.
  • State wage, unemployment, and workers'-compensation laws increasingly use the strict ABC test — most famously California after Dynamex Operations West, Inc. v. Superior Court, 4 Cal. 5th 903 (2018) and AB5 (Cal. Lab. Code § 2775).
  • ERISA and benefit-plan law ask, independently, whether the person is a common-law employee entitled to participate in the 401(k), health plan, and equity plan — the lesson of the Vizcaino v. Microsoft "permatemp" litigation.

Because these tests are independent, a compliant business must satisfy the strictest test that applies to it, not the most convenient one. A worker who passes the FLSA test as a contractor can still flunk California's ABC test and be an employee for state wage purposes. Getting comfortable with that reality is the first step.

Throughout this checklist we follow Nimbus Labs, a fictional twelve-person software startup. Nimbus wants to engage two people as contractors: Priya, a freelance developer building a feature module, and Marcus, a driver who delivers Nimbus's hardware units to local customers. As we will see, one of these is a much easier call than the other.

Phase 1 checklist — Frame the question before you answer it

  • [ ] Identify every statute that will judge this relationship: FLSA, the tax code, your state's wage/UI/workers'-comp laws, and any benefit plan.
  • [ ] Determine which state's law governs (worker's location, not the company's).
  • [ ] Assume you must satisfy the strictest applicable test, and classify to that standard.
  • [ ] Recognize that a contract label ("Independent Contractor Agreement") is evidence, not a verdict.
  • [ ] Flag any worker doing work that is central to your core business for extra scrutiny.

Why it matters, and the traps. The single most expensive mistake is answering only the question that is easiest to pass. A California employer that clears the IRS common-law test but ignores the ABC test can owe years of unpaid overtime, meal-and-rest premiums, and waiting-time penalties. The corollary trap is geography: classification follows the worker's state, so a remote contractor in California pulls California law into a Delaware company's lap. Nimbus's driver Marcus works locally; if that locality is California, AB5 is squarely in play regardless of where Nimbus is incorporated. On incorporation and where a startup's legal obligations attach, see Incorporating a Startup the Right Way: A Founder's Legal Checklist.


The FLSA economic-reality test and the 2024 DOL final rule (29 C.F.R. Part 795)

The FLSA does not define "independent contractor." Courts and the Department of Labor built the economic-reality test to decide whether a worker is, as a matter of economic reality, dependent on the employer (an employee) or in business for themselves (a contractor). In January 2024 the DOL issued a final rule, codified at 29 C.F.R. Part 795, restoring a totality-of-the-circumstances analysis and rejecting the prior administration's approach of elevating two "core" factors above the rest.

The 2024 rule weighs six non-exhaustive factors, none dispositive:

  1. Opportunity for profit or loss depending on managerial skill.
  2. Investments by the worker and the employer (are they capital, business-like investments?).
  3. Degree of permanence of the relationship (indefinite/continuous points to employee).
  4. Nature and degree of control the employer has over the work, including scheduling, supervision, price-setting, and the ability to work for others.
  5. Whether the work is integral to the employer's business.
  6. Skill and initiative — does the worker use specialized business skill in a way that reflects independent judgment?

Phase 2 checklist — Run the FLSA economic-reality factors

  • [ ] Profit/loss: Can the worker increase profit through managerial skill (hiring helpers, buying equipment, marketing), or do they just earn more by working more hours?
  • [ ] Investment: Does the worker make capital investments in their own business, or does the company supply the tools, laptop, and software?
  • [ ] Permanence: Is the engagement project-based and finite, or open-ended and exclusive?
  • [ ] Control: Who sets the hours, methods, and rates? Can the worker decline assignments and serve other clients?
  • [ ] Integral work: Is the work part of the company's core product/service, or a genuinely ancillary function?
  • [ ] Skill/initiative: Does the worker market their services and exercise independent business judgment?
  • [ ] Document your factor-by-factor reasoning contemporaneously, before a dispute arises.

Why it matters, and the traps. The FLSA is the statute with teeth on wages: misclassification means unpaid minimum wage and time-and-a-half overtime, and the FLSA allows liquidated (double) damages plus a two-year limitations period that stretches to three for willful violations. The classic trap is the "integral work" factor. Apply it to Nimbus: Priya is writing a feature module for Nimbus's software product — arguably integral — but she is a highly skilled specialist, works on a fixed-scope project, uses her own tools, sets her own hours, and keeps three other clients. Several factors point to contractor. Marcus, by contrast, delivers Nimbus's product to customers on Nimbus's schedule, in Nimbus's branded shirts, using routes Nimbus assigns, with no meaningful profit-and-loss levers of his own. Under the economic-reality test he looks like an employee, and no invoice will change that. When the same workforce also raises handbook, leave, and discipline questions, coordinate this analysis with Building a Legally Sound Employee Handbook and the broader The Employment Law Toolkit: From Hiring to Separation.


The IRS common-law/behavioral-financial-relationship test and Form SS-8

The IRS asks a narrower question than the DOL: who has the right to control the details of how the work is done? Under Rev. Rul. 87-41 the analysis, once a list of twenty factors, is now organized into three categories:

  • Behavioral control — does the business direct and control how the worker does the task (instructions, training, evaluation of methods)?
  • Financial control — does the business control the economic aspects (unreimbursed expenses, investment, method of payment, opportunity for profit/loss, availability to the market)?
  • Type of relationship — written contracts, benefits, permanency, and whether the services are a key aspect of the business.

If a business genuinely cannot tell, it (or the worker) can file Form SS-8, "Determination of Worker Status," and ask the IRS to decide. The catch: an SS-8 filing is not a fast or neutral event. It routinely takes six months or more, and the IRS resolves genuine ambiguity in favor of employee status more often than not. Filing one also puts the question on the government's radar.

Phase 3 checklist — Apply the IRS common-law test

  • [ ] Behavioral control: List every instruction and training you provide. The more you dictate how (not just what), the more it looks like employment.
  • [ ] Financial control: Confirm the worker bears unreimbursed expenses, can realize profit or loss, and offers services to the broader market.
  • [ ] Relationship type: Note whether you provide benefits (a strong employee signal) and whether the work is a key business function.
  • [ ] Decide whether Section 530 relief (Revenue Act of 1978) is available: a reasonable basis for treating the worker as a contractor, consistent past treatment, and 1099 filing.
  • [ ] Only file Form SS-8 when you truly cannot resolve status — and expect the tie to break toward employee.
  • [ ] Issue Form 1099-NEC for contractors paid $600+; collect a Form W-9 before the first payment.

Why it matters, and the traps. Misclassification here means the business failed to withhold income tax and to pay its share of FICA and FUTA. The IRS can assess back taxes, interest, and penalties; if the failure is intentional, Trust Fund Recovery Penalties can reach responsible individuals personally. Two traps recur. First, providing benefits — health insurance, paid time off, a 401(k) match — is one of the loudest "employee" signals you can send, and it undercuts a contractor position across every test at once. Second, Section 530 relief is a genuine safe harbor but a fragile one: it evaporates if you ever treated someone in a substantially similar role as an employee, so consistency is everything. For Nimbus, Priya's arrangement (she invoices, bears her own costs, serves other clients, gets no benefits) fits the contractor mold; the moment Nimbus adds Priya to its health plan "as a perk," it has begun to dismantle its own classification.


The ABC test: Dynamex, California AB5, and the state patchwork

Many states have abandoned the flexible multifactor approach for state wage law in favor of the ABC test, which flips the presumption. Under the ABC test a worker is presumed to be an employee unless the hiring entity proves all three of the following:

  • (A) The worker is free from the control and direction of the hirer in connection with the performance of the work, both under the contract and in fact; and
  • (B) The worker performs work outside the usual course of the hiring entity's business; and
  • (C) The worker is customarily engaged in an independently established trade, occupation, or business of the same nature.

California adopted this test for wage-order claims in Dynamex Operations West, Inc. v. Superior Court, 4 Cal. 5th 903 (2018), and the legislature codified and extended it in AB5 at Cal. Lab. Code § 2775. Where a statutory exemption applies, California reverts to the older, more flexible multifactor test of S.G. Borello & Sons, Inc. v. Dept. of Industrial Relations, 48 Cal. 3d 341 (1989). Massachusetts and New Jersey use similarly strict ABC formulations; other states use their own variants for unemployment insurance. The result is a genuine patchwork: the same facts can pass in Texas and fail in California.

Phase 4 checklist — Run the ABC test where it applies

  • [ ] Confirm whether the worker's state uses an ABC test for the relevant purpose (wages, UI, workers' comp).
  • [ ] Prong A (control): Prove freedom from control both on paper and in practice.
  • [ ] Prong B (outside usual course): This is the killer. Ask honestly whether the work is part of what you sell. If it is, prong B fails and the analysis ends.
  • [ ] Prong C (independent business): Verify the worker actually operates an established business — separate entity, other clients, own tools, business licenses, marketing.
  • [ ] Check for a statutory exemption (many professions and B2B relationships are carved out); if one applies, run the Borello factors instead.
  • [ ] Remember the burden is on you to prove all three prongs; failing any one makes the worker an employee.

Why it matters, and the traps. Prong B is where most contractor arrangements die. Return to Nimbus: Marcus delivers Nimbus's product, and if Nimbus is a delivery-dependent hardware business, delivery is plausibly within its "usual course" — prong B fails and Marcus is an employee for California wage purposes, full stop, no matter how the other factors look. Priya writes software for a software company, which also sounds "inside the usual course" — but she may fall under a professional-services or bona fide B2B exemption, dropping her back into the more forgiving Borello analysis where her independence carries the day. The trap for national employers is assuming one classification decision travels across state lines. It does not. Non-compete and restrictive-covenant enforceability follows the same patchwork logic; see The Future of Non-Competes: FTC Rulemaking and the State-Law Patchwork.


Consequences of misclassification: wages, taxes, benefits, penalties

Misclassification is not a paperwork foot-fault; it is a stack of overlapping liabilities, and a single misclassified worker can trigger all of them at once:

  • Wage-and-hour liability (FLSA + state): unpaid minimum wage and overtime, liquidated (often double) damages, and attorneys' fees. California adds meal-and-rest premiums, itemized wage-statement penalties, and waiting-time penalties.
  • Tax liability (IRS + state): unpaid employer FICA/FUTA, failure to withhold, interest, penalties, and potential personal Trust Fund Recovery Penalties.
  • Benefits liability (ERISA): retroactive eligibility for the 401(k), health, and equity plans — the Vizcaino v. Microsoft problem, where "permatemps" won the right to plan benefits they were told they could not have.
  • Unemployment and workers'-comp exposure: back UI contributions and uninsured-injury liability.
  • Statutory and class exposure: in California, PAGA representative actions; elsewhere, class and collective actions that aggregate small individual claims into large ones.

For the litigation math on what these claims are worth once they mature into a lawsuit, see Damages in Employment Litigation: Back Pay, Statutory Caps, and Punitive Awards.

Phase 5 checklist — Size the downside before you decide

  • [ ] Calculate the overtime exposure: reconstruct hours the "contractor" actually worked and price the unpaid time-and-a-half.
  • [ ] Add liquidated/double damages and attorneys' fees to the wage figure.
  • [ ] Estimate back employment taxes plus interest and penalties.
  • [ ] Assess retroactive benefit exposure across every plan the worker would have joined.
  • [ ] Multiply by the number of similarly situated workers — misclassification is rarely a party of one.
  • [ ] Weigh the modest savings of a contractor label against this aggregate downside.

Why it matters, and the traps. The trap is arithmetic. A contractor who costs $80,000 a year "saves" the employer roughly the 7.65% employer FICA, some benefits, and administrative overhead — call it low five figures. If that worker is reclassified, the exposure for that one person, across wages, taxes, benefits, penalties, and fees, can dwarf the savings, and the same defect usually infects an entire class of workers hired the same way. Classification is one of those areas where a small upfront investment in doing it right prevents a catastrophic aggregate liability. Small businesses working through this alongside their other formation and compliance obligations should anchor to The Small Business Legal Toolkit.


The IP trap: independent-contractor work is not work made for hire (CCNV v. Reid)

Here is the consequence founders miss most often. When an employee creates a copyrightable work within the scope of employment, the employer owns it automatically as a work made for hire under the Copyright Act, and no assignment is needed. When an independent contractor creates a work, the default flips: the contractor owns the copyright unless (a) the work fits one of nine narrow statutory categories and there is a signed work-for-hire agreement, or (b) the contractor signs a written assignment of the copyright.

The Supreme Court settled this in Community for Creative Non-Violence v. Reid, 490 U.S. 730 (1989), holding that a sculptor hired to create a work was an independent contractor under common-law agency principles, so CCNV did not own the sculpture despite paying for it. The classification you fought so hard to establish for wage and tax purposes — "she's a contractor!" — now works against your ownership of what she built.

The mirror-image problem exists for patents: absent a written assignment, an inventor (employee or contractor) owns their invention, and an employer's rights may be limited to a nonexclusive "shop right." So the very freelancer you correctly classified as a contractor can walk away owning the copyright in her code and the rights in any patentable invention unless you papered assignments.

Phase 6 checklist — Close the IP gap for every contractor

  • [ ] Include an express copyright assignment in every contractor agreement — do not rely on "work made for hire" language alone.
  • [ ] Add belt-and-suspenders work-made-for-hire language for works that fit the statutory categories, backed by a present assignment fallback.
  • [ ] Include a present-tense invention/patent assignment ("hereby assigns"), plus a further-assurances clause.
  • [ ] Confirm the assignment is signed before or at the start of work, not after delivery.
  • [ ] Verify the contractor has the right to assign (no conflicting employer or prior client owns the work).
  • [ ] Capture moral-rights waivers where applicable and pre-existing-IP carve-outs with a license back to you.

Why it matters, and the traps. For Nimbus this is existential. Priya writes a core feature module. If Nimbus's contractor agreement lacks a copyright assignment, Priya owns her code, and Nimbus holds at most an implied license — a fatal diligence finding when investors or an acquirer examine the cap table and the IP chain. Run the classification analysis and the ownership analysis together: whether a work qualifies as work made for hire is its own inquiry, walked through in Determining Work Made for Hire: A Practical Checklist, and the assignment mechanics — including the state-law limits on what employees can be made to assign — are covered in Employee Invention Assignment Agreements: Securing Clean Title Across Jurisdictions. Clean IP title is one of the pillars investors probe in The Startup Legal Document Stack: What Founders Need and Why.


Structuring and papering a genuine contractor engagement

You cannot contract your way out of a true employment relationship — but where a role genuinely is independent, the paperwork and the day-to-day operation must match that reality. Substance controls, and inconsistent conduct (a "contractor" who is on the org chart, uses a company badge, and attends daily standups as a supervised report) will sink the classification no matter how good the contract reads.

Phase 7 checklist — Build and operate a defensible contractor relationship

  • [ ] Use a written Independent Contractor Agreement that recites contractor status, no benefits, no withholding, and the worker's control over methods.
  • [ ] Structure the deal around deliverables or projects, not hours, and let the contractor set their own schedule.
  • [ ] Have the contractor invoice you; pay against invoices, not on a fixed payroll cycle.
  • [ ] Require the contractor to supply their own tools, equipment, and workspace where feasible.
  • [ ] Confirm the contractor is free to work for others and does not work exclusively for you indefinitely.
  • [ ] Where possible, engage the contractor's business entity (LLC/S-corp), not the individual.
  • [ ] Collect a W-9, a certificate of insurance, and any required business licenses up front.
  • [ ] Include the IP assignment, confidentiality, and (where lawful) restrictive covenants — but avoid the degree of control that converts the relationship into employment.
  • [ ] Operate consistently with the paper: no mandatory meetings, no performance reviews of method, no company email/badge treating them as staff.
  • [ ] Re-assess status annually and whenever the scope or duration materially changes.

Why it matters, and the traps. The most common failure is drift. A contractor is engaged cleanly for a three-month project, the project succeeds, and eighteen months later they are effectively a full-time team member — same desk, same standups, same exclusivity — still paid on a 1099. The relationship became employment somewhere along the way, and the stale contract is now evidence against the company. Confidentiality and restrictive-covenant terms are worth including, but they cut against contractor status if they impose employee-like control, so calibrate them to the jurisdiction and the role. And remember that reclassifying a contractor to employee later can itself surface earlier misconduct or performance issues that require care; if a dispute or complaint arises during the engagement, run it through Conducting a Workplace Investigation: A Practical Checklist. When a contractor converts to a genuine employee, the full onboarding stack — handbook acknowledgment, at-will terms, and leave and accommodation policies such as those in Accommodating Pregnancy and Nursing Under the PWFA and PUMP Act: A Practical Checklist — comes online, and a compliant handbook (see Drafting an Employee Handbook That Holds Up: A Practical Checklist) should be ready to go.


Common Mistakes to Avoid

  • Trusting the label. A signed "Independent Contractor Agreement" is evidence, not a determination. Every test looks past it to the working reality.
  • Passing only the easy test. Clearing the IRS common-law test while ignoring a state ABC test is the most expensive shortcut in this area.
  • Ignoring geography. Classification follows the worker's state. A remote worker in California drags California law into your company.
  • Providing benefits to a "contractor." Health insurance, PTO, and a retirement match are among the loudest employee signals across every test.
  • Forgetting the IP assignment. Contractor work is not work made for hire; without a written copyright and invention assignment, the contractor keeps the rights.
  • Letting engagements drift. A clean project engagement can quietly become employment. Re-paper and re-assess when scope or duration changes.
  • Misclassifying core-business roles. Work "integral to" or "inside the usual course of" your business is the hardest to defend as contractor work.
  • Filing an SS-8 reflexively. The IRS resolves genuine doubt toward employee status; file only when you truly need the ruling.
  • Assuming national consistency. The same facts can pass in Texas and fail in California. Classify state by state.

Consolidated checklist — worker classification at a glance

  • [ ] Identify every statute that will judge the relationship (FLSA, tax, state wage/UI/comp, ERISA).
  • [ ] Determine the governing state by the worker's location and assume the strictest applicable test.
  • [ ] Run the FLSA economic-reality factors under 29 C.F.R. Part 795 and document the reasoning.
  • [ ] Run the IRS common-law test (behavioral, financial, relationship); consider Section 530 relief.
  • [ ] Run the ABC test where the state uses it; watch prong B (outside usual course) and check exemptions.
  • [ ] Confirm you are not sending employee signals (benefits, exclusivity, org-chart integration).
  • [ ] Size the misclassification downside (wages, double damages, taxes, benefits, penalties, class scope).
  • [ ] Paper a written Independent Contractor Agreement and operate consistently with it.
  • [ ] Secure a written copyright assignment and present-tense invention assignment from every contractor.
  • [ ] Collect W-9, issue 1099-NEC at $600+, and keep classification records.
  • [ ] Re-assess status annually and on any material change in scope or duration.
  • [ ] When in genuine doubt on tax status, weigh Form SS-8 — knowing ties break toward employee.

Primary Authority

Related UpLaw Resources

Related Guides & Articles

Related Checklists

Related Toolkits


This checklist is general legal information from UpLaw (uplaw.us), not legal advice, and does not create an attorney-client relationship. Worker-classification standards vary by statute and state and change frequently; verify current federal and state requirements and consult qualified counsel before classifying a worker or acting on a classification decision.