Reviewing Independent Contractor Agreements: The Misclassification Trap

The IRS assessed a Texas staffing company $3.6 million in back employment taxes after reclassifying 250 “independent contractors” as employees. The company had contractor agreements in place for every worker. The agreements all said “independent contractor.” The IRS didn’t care.

Worker misclassification is one of the most aggressively enforced labor issues in the United States. The penalties stack fast: back taxes, unpaid benefits, overtime liability, state fines, and interest — routinely reaching six and seven figures. According to the National Federation of Independent Business, the IRS imposes penalties of 1.5% of wages plus 20% of FICA taxes for unintentional misclassification, and up to 100% of FICA taxes plus $1,000 per worker for intentional violations. And enforcement is ramping up at both federal and state levels.

If you handle contractor agreements for clients — or use contractors yourself — you need to know what the classification tests actually look for, which contract provisions create risk, and where the landmines are by state. Try Clause Labs free to run a quick AI risk scan on any contractor agreement and flag misclassification triggers in under 60 seconds.

The Agreement Doesn’t Determine Status — the Relationship Does

This is the single most important concept in contractor classification, and the one most clients get wrong: calling someone an “independent contractor” in a written agreement does not make them one.

Every federal and state classification test looks past the contract label to the actual working relationship. The IRS explicitly states that the determination depends on the facts of the arrangement, not on how the parties characterize it.

A well-drafted contractor agreement helps — it creates a framework for a legitimate contractor relationship. But if the day-to-day reality doesn’t match the agreement, the agreement loses. Every time.

The Three Classification Tests You Need to Know

There is no single “independent contractor test.” Three different federal and state frameworks apply depending on context, and they don’t always reach the same result.

1. The IRS Common Law Test (Right-to-Control)

The IRS uses a three-category analysis examining behavioral control, financial control, and the type of relationship:

• Behavioral control: Does the business dictate how, when, and where work is performed? If a company sets the worker’s schedule, requires them to work on-site, provides detailed instructions on methods, or requires attendance at staff meetings, those are employee indicators.
• Financial control: Does the worker invest in their own tools and equipment? Do they have the opportunity for profit or loss? Can they serve other clients? Employee indicators include company-provided equipment, reimbursed expenses, and guaranteed compensation regardless of output.
• Relationship type: Is the relationship ongoing or project-based? Does the worker receive benefits? Is the work integral to the business or peripheral?

No single factor is determinative. The IRS weighs the totality of the circumstances. But the more employee-like factors present, the higher the reclassification risk.

2. The DOL Economic Reality Test

The Department of Labor applies a different framework under the Fair Labor Standards Act. As of May 2025, the DOL reverted to the traditional economic reality framework from its 2008 Fact Sheet #13, stepping back from the stricter six-factor test introduced in the 2024 Biden-era rule.

The core question: is the worker economically dependent on the business, or genuinely in business for themselves?

Key factors under the current enforcement approach:

• The nature and degree of control over the work
• The worker’s opportunity for profit or loss based on personal initiative
• The worker’s investment in equipment or materials
• The degree of skill required
• The permanence of the working relationship
• Whether the work is integral to the business

The economic reality test focuses more heavily on economic dependence than the IRS test focuses on behavioral control. A worker can pass the IRS test but fail the DOL test — or vice versa.

3. The ABC Test (California, Massachusetts, and Growing)

The ABC test is the strictest classification standard in the country. Under California’s AB5 and Massachusetts law (M.G.L. c. 149 s. 148B), a worker is presumed to be an employee unless the hiring entity proves all three prongs:

• A: The worker is free from the control and direction of the hiring entity, both under the contract and in fact.
• B: The worker performs work 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.

Prong B is the killer. A software company hiring a freelance developer to build its product will struggle with Prong B because software development is the company’s usual course of business. Compare that to the same company hiring a freelance accountant — accounting is outside the company’s usual business, making Prong B much easier to satisfy.

States currently using some form of the ABC test include California, Massachusetts, New Jersey, Illinois, and Connecticut, with more states considering adoption.

10 Independent Contractor Agreement Red Flags

These contract provisions — or the real-world practices they reflect — signal employee status regardless of what the agreement title says.

1. Set Hours or Schedule

The agreement requires the contractor to work specific hours (e.g., “9 AM to 5 PM, Monday through Friday”). A legitimate contractor controls when they work. If you’re dictating schedules, you’re describing employment.

Fix: Specify deliverables and deadlines, not hours. “Contractor shall deliver the Phase 1 report by March 15” — not “Contractor shall work 40 hours per week.”

2. Mandatory Location

The agreement requires the contractor to work on-site at the company’s offices. Contractors should control where they perform work.

Fix: If on-site work is genuinely necessary (e.g., equipment access), limit it to specific tasks and timeframes rather than requiring constant presence.

3. Company-Provided Tools and Equipment

The company provides laptops, software licenses, office space, and supplies. Contractors typically use their own tools.

Fix: The agreement should state that the contractor provides their own tools and equipment. If the company must provide access to proprietary systems, frame it as a limited license rather than equipment provision.

4. Exclusivity Clauses

“Contractor shall devote their full time and attention to Company’s projects and shall not perform services for competing businesses.” This is employment language. Contractors serve multiple clients.

Fix: Remove exclusivity requirements. If confidentiality is the concern, use a targeted confidentiality clause — not an exclusivity provision that destroys contractor status.

5. Detailed Task Instructions

The agreement or the work practices involve telling the contractor how to perform the work, not just what to deliver. Providing step-by-step procedures, requiring specific methodologies, or mandating attendance at training sessions are employee indicators.

Fix: Define the desired outcome and acceptance criteria. Let the contractor determine the methodology.

6. Ongoing Relationship With No Defined Project Scope

The agreement describes an open-ended engagement with no specific project, deliverables, or end date. “Contractor shall provide marketing services as requested” describes a permanent marketing employee.

Fix: Structure the agreement around defined projects or engagement periods. Use statements of work (SOWs) for each project.

7. Integration Into Company Operations

The contractor appears on the org chart, has a company email address, attends mandatory staff meetings, and participates in company events. These practices signal integration into the business — an employee hallmark.

Fix: Keep the contractor relationship at arm’s length. Use separate communication channels. Don’t include contractors in internal organizational structures.

8. Benefits or Employee-Type Perquisites

The agreement provides health insurance, paid time off, retirement contributions, or expense reimbursement. These are employee benefits.

Fix: Contractors should invoice for all costs, including expenses, as part of their service fees. No benefits, no withholding, no payroll.

9. Right to Terminate Without Cause

“Company may terminate this agreement at any time, for any reason, with or without cause.” This mirrors at-will employment. Legitimate contractor relationships tie termination to project completion, deliverable acceptance, or specific cause provisions.

Fix: Tie termination to project milestones, breach of specific obligations, or notice periods. Include payment for work completed through the termination date.

10. Non-Compete Provisions

A broad non-compete restricting the contractor from working with competitors strongly suggests an employment relationship. Why would an independent business operator be restricted from serving other clients?

Fix: If you need protection, use narrow non-solicitation provisions (targeting specific clients or employees) rather than broad non-competes. Better yet, rely on confidentiality provisions instead.

Drafting Contractor Agreements That Withstand Scrutiny

A well-drafted independent contractor agreement won’t save a misclassified worker, but it creates the framework for a legitimate contractor relationship. These provisions are essential.

Status declaration: Clear statement that the worker is an independent contractor, not an employee, with acknowledgment of what that means (no benefits, no withholding, own taxes).

Project-based scope: Defined deliverables, milestones, and completion criteria. Not open-ended services.

Method and manner: Contractor controls how the work is performed. The company specifies what is to be delivered, not how.

Own tools and equipment: Contractor provides their own work tools. Limited exceptions for proprietary system access.

Multiple clients: No exclusivity. The contractor may serve other clients.

Invoice-based payment: Payment upon invoice submission, not on a payroll cycle. No hourly wage — project fees, milestone payments, or deliverable-based compensation.

Tax responsibility: Contractor is responsible for their own federal and state taxes, including self-employment tax.

Insurance: Contractor carries their own liability insurance and workers’ compensation coverage (where required).

Termination tied to deliverables: Termination provisions linked to project completion, breach, or reasonable notice — not at-will.

Clause Labs’s AI reviews contractor agreements against these structural requirements and flags provisions that create classification risk. Upload a contractor agreement to see which provisions in your specific document may trigger reclassification scrutiny.

State-Specific Considerations

Classification rules vary dramatically by state. What passes in Texas may fail in California.

State	Primary Test	Strictness	Key Notes
California	ABC Test (AB5)	Very strict	$5,000-$25,000 per violation for willful misclassification. Prong B is the most challenging. Some exemptions exist for specific professions.
Massachusetts	ABC Test (M.G.L. c. 149 s. 148B)	Very strict	One of the oldest and strictest ABC test states. Attorney General actively investigates and enforces.
New York	Multiple agency tests	Strict	Different agencies (DOL, UI, Tax) may apply different tests. Confusion is a feature, not a bug.
New Jersey	ABC Test (modified)	Strict	Expanded enforcement in recent years. Applies broadly across employment statutes.
Illinois	Multiple tests	Moderate-strict	ABC test for certain purposes; common law test for others. Enforcement increasing.
Texas	Common law (right-to-control)	Moderate	More employer-friendly than ABC test states, but still requires genuine contractor independence.
Florida	Common law (right-to-control)	Moderate	Relatively business-friendly, but state agencies actively investigate complaints.

Jurisdiction note: This table covers only selected states. Every state has its own classification rules, and many apply different tests for different purposes (unemployment insurance vs. wage/hour vs. workers’ compensation). When reviewing contractor agreements, check the specific rules for every state where the contractor will perform work.

The IP Problem in Contractor Agreements

Here’s a fact that surprises many clients: under U.S. copyright law, an independent contractor owns the work they create unless the agreement explicitly assigns those rights.

The work-for-hire doctrine (17 U.S.C. s. 101) applies automatically to employees but only applies to independent contractors in nine specific categories of copyrightable work — and only when there’s a written agreement saying so. Software code, for example, doesn’t fall within any of the nine categories. If your client hires a freelance developer without an IP assignment clause, the developer owns the code.

Every contractor agreement should include:

• Explicit IP assignment: “Contractor hereby assigns to Company all right, title, and interest in and to all Work Product created under this Agreement.” Don’t rely on work-for-hire for contractors.
• Prior inventions schedule: A list of pre-existing IP the contractor brings to the engagement that is excluded from the assignment. Without this, disputes arise about what was created during the engagement versus what existed before.
• Cooperation clause: The contractor agrees to execute additional documents needed to perfect the assignment (patent applications, copyright registrations, etc.).
• License-back for general tools: If the contractor uses general-purpose tools or frameworks across multiple clients, grant a non-exclusive license back so the contractor can continue using those tools without infringing on the assignment.

For deeper coverage of IP assignment issues, see our guide on IP assignment clauses and the mistakes that destroy startups.

California note: California Labor Code s. 2870 protects employee inventions created entirely on their own time, without company resources, and unrelated to company business. While this statute technically applies to employees, not contractors, its principles influence how California courts evaluate overly broad IP assignment provisions in any work agreement.

How Clause Labs Reviews Contractor Agreements

Clause Labs’s AI identifies classification risk factors within the agreement text:

• Status language analysis: Flags provisions that describe employee relationships despite “contractor” labels (set schedules, mandatory locations, company equipment).
• Missing provisions: Detects absent contractor-essential elements — no IP assignment, no tax responsibility language, no project-based scope definition.
• Red flag detection: Identifies exclusivity clauses, broad non-competes, benefits language, and at-will termination provisions that signal employment.
• State-specific alerts: Highlights provisions that may create heightened risk under ABC test jurisdictions.

The AI provides a risk score and clause-by-clause breakdown in under 60 seconds. It doesn’t replace the judgment call of whether the actual working relationship matches the agreement — that’s the lawyer’s job. But it catches structural issues in the document itself that create unnecessary exposure.

Frequently Asked Questions

Can a contract make someone an independent contractor?

No. A written agreement calling someone an “independent contractor” is relevant evidence, but every classification test looks at the actual working relationship, not the contract label. If the day-to-day reality resembles employment (set hours, company equipment, direct supervision, integration into operations), the worker will be reclassified regardless of what the contract says.

What happens if a contractor is reclassified as an employee?

The hiring entity faces retroactive liability for unpaid employment taxes (employer’s share of FICA), potential overtime under the FLSA, unpaid benefits the worker would have received as an employee, state unemployment insurance contributions, workers’ compensation premiums, and penalties from the IRS and state agencies. In California, willful misclassification carries fines of $5,000 to $25,000 per violation.

Do I need a contractor agreement for every freelancer?

Yes. Even for short engagements. Without a written agreement, you have no IP assignment (the contractor owns everything they create), no confidentiality protections, no defined scope, and no structural evidence supporting contractor status. The agreement itself isn’t sufficient to establish contractor classification, but the absence of one makes reclassification almost certain.

Can contractors sign non-competes?

Technically, yes — but it undermines contractor status. A non-compete restricting a contractor from working with competitors suggests the company treats the worker as an employee (employees have non-competes; independent business operators don’t). If your client needs protection, use targeted non-solicitation provisions and strong confidentiality clauses instead of broad non-competes. Also note that non-compete enforceability varies dramatically by state — see our guide on contract red flags for jurisdiction-specific issues.

What’s the penalty for misclassification?

Penalties compound across federal and state levels. At the federal level: IRS penalties of 1.5% of wages plus 20% of the employee’s FICA share and 100% of the employer’s FICA share (unintentional), or 20% of wages plus 100% of all FICA taxes plus up to $1,000 per worker (intentional). DOL penalties include back overtime and minimum wage liability. At the state level: California imposes $5,000-$25,000 per willful violation. Massachusetts, New Jersey, and New York all impose separate state-level penalties and actively investigate complaints. Many states allow treble damages for wage violations arising from misclassification.

---

This article is for informational purposes only and does not constitute legal advice. Worker classification is fact-specific and varies by jurisdiction. Consult a qualified employment attorney for advice specific to your situation.

Ready to check your contractor agreements for misclassification risk? Upload any independent contractor agreement to Clause Labs — the AI flags classification red flags, missing IP provisions, and structural issues in under 60 seconds. Start free with 3 reviews per month, no credit card required.