Single-Client Contractor Dependency and Classification Risk

Every classification dispute eventually comes down to one question: whose business is this, really? The answer depends less on what a contract says than on what a worker does day to day. Regulators and courts call this the substance-over-form principle. They look past the label on the agreement and examine how the arrangement actually functions.

The controlling idea behind nearly every classification framework is economic dependency. Different tests ask different questions, but they all circle the same inquiry. Who controls the work? Whose equipment is used? How integrated is the person into the business? How economically dependent are they on one client? How long has the relationship run? A contractor who invoices one client for years, uses that client's systems, and cannot realistically take other work answers these questions the way an employee would.

The economic reality test, applied at the federal level, and the ABC test, used in more than 20 states, both treat economic dependency as a central factor rather than a secondary one. The IRS Common Law Test evaluates behavioral control, financial control, and the type of relationship, including whether exclusivity clauses or non-compete restrictions exist. The economic reality test asks if the contractor invoices multiple clients and absorbs personal costs, or if the company guarantees payment and provides resources. Single-client arrangements fail these inquiries regardless of contractual language.

When regulators look at the paper trail, they examine signed engagement terms, invoices, and evidence of independence. A signed independent contractor agreement does not override how work is structured or supervised. For delivery companies, the dependency pattern can be structural by design. A driver assigned to a single route, dispatched through one platform, and wearing branded gear is functionally indistinguishable from an employee under these tests even if the contract states otherwise.

How the major classification tests treat single-client work, and where delivery operations are most exposed

The ABC test's B-prong creates the most acute exposure for delivery companies, because core delivery work is hard to argue as falling outside the company's usual business. Under the ABC test, used in more than 20 states, all three prongs must be satisfied for contractor status to hold. The B-prong requires that the work performed is outside the company's usual business activities. The work is the business.

Single-client exclusivity compounds the problem. A driver who works only for one platform and performs that platform's core service fails two prongs simultaneously: the worker is economically dependent on a single entity, and the work performed is indistinguishable from the company's product. This is not a close call. It is the clearest possible failure under the strictest available framework.

In May 2025, the DOL issued Field Assistance Bulletin 2025-1, instructing investigators to stop applying the 2024 independent contractor rule and revert to the prior economic realities test focused on degree of control and opportunity for profit or loss. Factors examined include permanency of the relationship, the worker's investment in tools, skill and initiative, and integration of the work into the business. Audits continue.

California remains the toughest classification environment for last-mile operators. The state's ABC test under AB 5 is the strictest in the nation, and the exemption modifications that have passed do not affect courier and delivery work. Warning signs that apply across all tests include exclusive service clauses preventing contractors from working for competitors, time-based pay instead of deliverables, and use of company-provided systems, branded equipment, or assigned routes. Each of these signals integration into the business rather than independence from it.

Why enforcement is intensifying even as federal rules loosen

The notion that federal flexibility has reduced classification risk is a comfort built on a category error. Federal flexibility does not reduce the practical enforcement risk for delivery operators. It redistributes that risk to state agencies and automated IRS detection, which are simultaneously moving in a stricter direction. The 2024 independent contractor rule remains on the books for purposes of private litigation. Federal DOL investigators apply the more lenient framework, but private plaintiffs can still argue for the stricter 2024 standard. You should still expect scrutiny through audits and state enforcement, even with the pause.

State-level enforcement is tightening on its own schedule. California, Massachusetts, and New Jersey maintain stricter tests than the federal standard, and many states are strengthening enforcement legislation for 2026. The Netherlands ended its enforcement moratorium on 1 January 2025. From 1 January 2026, with full penalty enforcement deferred to 1 January 2027, penalties for intent or gross negligence, called vergrijpboetes, became explicitly available at 10 to 100 percent of back-assessed tax, while standard default penalties remained suspended. Poland moved further still. From 8 July 2026, a district labour inspector can declare a B2B contract to be an employment relationship by administrative decision, after first issuing an unremedied compliance order, without the company first having its day in a civil court.

The quietest and most consequential development is IRS automation. The agency is now cross-referencing 1099-NEC filings against industry benchmarks using automated analysis, flagging businesses whose contractor populations look statistically inconsistent. A worker who reports a single client and logs 40-plus hours a week over an extended period is exactly the pattern that triggers review. The industries facing more enforcement include logistics, gig and app-based platforms, and construction. Those are the precise sectors where delivery IC networks operate.

What misclassification actually costs when a single-client dependency case is found

Misclassification is never a single-line item. A typical finding brings allegations of unpaid overtime, minimum wage violations, failure to provide benefits, and tax exposure, all at the same time. Investors treat employment risk as a balance sheet issue, because every misclassified contractor is potential back pay, tax arrears, and penalties. The exposure runs backward from the date misclassification began, which means the longer a single-client arrangement has been in place, the larger the retroactive liability.

The insurance gap is the most operationally specific consequence for a delivery audience. Occupational accident insurance is the correct product for independent contractors on the job in trucking, courier, and last-mile delivery work. Workers' compensation is the correct product for employees. If a contractor is reclassified as an employee after an injury, the occupational accident coverage was never the right product. Claims can be denied, and the operator faces uncovered back liability. This is the mechanism by which a reclassification finding turns an insured workforce into an uninsured one retroactively.

Regulatory consequences extend beyond financial penalties. Regulators can suspend or restrict operating licenses when employment compliance fails, and a misclassification pattern signals weak internal controls. Glovo was fined in Spain for wrongly classifying delivery riders as self-employed. DoorDash faces a class-action lawsuit in California for allegedly misclassifying drivers under the California Labor Code. FedEx and Microsoft both settled independent contractor misclassification claims, and those settlements are widely cited as illustrations of what sustained misclassification across large contractor populations eventually costs.

How single-client dependency is created operationally — and how delivery companies often build it in without realizing it

Delivery companies rarely set out to create classification risk. They set out to run an efficient operation, and the dependency pattern is what efficient operations look like in practice. Regulators examine whether the arrangement is exclusive and how long it has run. A multi-year route assignment to a single platform is exactly the pattern that triggers scrutiny.

The operational signatures are recognizable because they are so ordinary. Requiring branded uniforms, branded vehicles, or branded equipment removes one of the clearest markers of contractor independence: the contractor's own tools and presentation. Scheduling contractors into regular recurring slots, daily or weekly, creates the same shift-based dependency that exposes managed service providers and similar IC-heavy operations.

Platform integration operates as an unintentional dependency builder. When contractors receive assignments, communicate, and log activity exclusively through one company's app or platform, they are functionally embedded in that business's operations. IT contractors face the same risk when they use a single company's internal systems. The longer this integration continues, the more the arrangement resembles a permanent employment relationship rather than a project-based engagement.

The reason this accumulates undetected is a governance gap. Contractors are tracked in spreadsheets, invoices, and whatever each hiring manager remembers agreeing to. When no one has a complete view of how many contractors work exclusively for the company, how long they have done so, and on what terms, the dependency pattern is invisible until a regulator or acquirer looks.

What the classification tests actually allow — and the operational space that remains for compliant IC relationships

Requiring contractors to carry insurance, meet safety standards, and maintain credentials is not the kind of control that triggers reclassification. Understanding this distinction is what separates compliance-minded operators from those who either over-control or under-manage their contractor networks. The February 2026 proposed DOL rule clarified that requiring a contractor to follow safety standards, carry insurance, or meet legal obligations does not prove employer control. This carves out meaningful space for operators who mandate credential verification and occupational accident coverage. A delivery company can require drivers to hold a valid commercial license, maintain current insurance, and pass a background check. Those requirements need not become evidence of the employment relationship the company is trying to avoid.

Genuine contractor independence in a delivery context has recognizable features. The contractor controls how the work is performed: route decisions, time of day, pace. The company specifies outcomes, such as a package delivered by a certain time, not method. Substitution rights, even if rarely exercised, mark genuine independence. The contractor bears financial risk: absorbing costs when something goes wrong, providing a personal vehicle and equipment, and earning variable amounts based on personal choices.

California Proposition 22 demonstrates that compliant IC structures in delivery are legally recognized even in the strictest jurisdiction. The California Supreme Court upheld Proposition 22 in July 2024, affirming that app-based transportation and delivery drivers can remain classified as independent contractors if the law's conditions are met. Documentation is the mechanism that preserves the distinction. Supporting evidence of independence includes business licenses, proof of separate entity status, contractor insurance, marketing materials, and invoices issued to multiple clients. The paper trail that survives a challenge is not the label on the contract. It is the signed engagement terms, the invoices, and where work product matters, the rights assignment behind them.

Structural practices that reduce single-client dependency risk in IC delivery networks

Reducing classification exposure from single-client dependency requires structural changes to how IC relationships are designed, documented, and monitored. Contract language and one-time audits are not enough. The contract structure itself must preserve independence. Avoid exclusivity clauses or language that prevents contractors from working for other clients. The structural option to multi-client must exist even if not exercised. Define engagements by outcomes and deliverables rather than schedule and method. Specify what must be delivered, not when the driver must be available or how the driver must drive. Set defined engagement terms rather than open-ended arrangements. Indefinite single-client engagements accumulate the permanency and economic dependency factors that all classification tests weigh heavily.

Credential and compliance verification belongs at onboarding, not after the fact. Verifying insurance certificates, driver's licenses, and background checks at the point of activation, before work begins, establishes the compliance baseline without creating operational dependency. An unverified driver who causes an incident after the fact creates both liability and a documentation gap.

Real-time compliance monitoring matters more than periodic audits. Automated alerts for upcoming expirations and a complete audit trail serve both operational continuity and the evidentiary record that a classification challenge would examine. Auditing all contractor relationships to ensure they demonstrate true independence, control over work methods and schedules, opportunity for profit or loss, and multiple business clients should be a regular process, not a response to a complaint.

Payment structure is evidentiary as well as financial. Pay structures tied to deliverables and output, rather than time-based regular amounts, reinforce the contractor's financial independence and opportunity for profit or loss. Fast payment through same-day ACH or instant debit is both a contractor retention tool and a documentation detail. The governance gap, contractor records living in spreadsheets and individual managers' memories rather than a unified system, is what makes misclassification invisible until a regulator looks. An audit-ready documentation system covering every active contractor, their credentials, their insurance, their engagement terms, and their payment history is the evidentiary foundation that determines whether a classification challenge succeeds or fails. Platforms that automate the full contractor lifecycle, from onboarding through credential verification, compliance monitoring, and payments, eliminate the manual back-office gap while generating the audit trail that demonstrates compliant IC management at scale.