Independent Contractors and the WARN Act: Why Gig Workers Usually Get No Layoff Notice

When a company announces a mass layoff, one group is usually missing entirely: independent contractors. The federal WARN Act requires covered employers to give 60 days' advance notice of a plant closing or mass layoff, but that protection applies to employees. Independent contractors, including most gig workers, fall outside it — so a contractor can lose their work overnight with no WARN notice at all, even when employees doing similar work get two months' warning.

That gap matters for reading layoff data. Layoff Atlas currently tracks 670 WARN notices covering 63,560 reported workers in the 90-day notice window, with 33 notices carrying no worker count. Those figures describe reported plans, not confirmed job losses, and they count only employees named in filings — contractor cutbacks never enter them.

Employees are covered; contractors are not

The WARN Act is an employment law, and its thresholds are written in terms of employees. A covered employer generally means one with 100 or more full-time employees, and a covered event is measured by how many full-time employees lose their jobs. Independent contractors are not counted toward those thresholds, and they are not entitled to the notice itself.

The distinction turns on classification, not job titles. A worker called a "contractor" but treated like an employee in practice may still be an employee in law, while a genuinely independent worker running their own business is not. What matters is who controls how, when, and where the work is done, who supplies the tools, whether the worker can work for others, and how integrated they are into the business.

Why gig workers usually fall outside WARN

Platform and gig work is typically structured as independent contracting. Drivers, couriers, freelance designers, and other platform workers usually sign terms that classify them as independent contractors, set their own hours within the platform's rules, and use their own equipment. Under that structure, a platform reducing work, changing pay rates, or deactivating accounts is not a WARN event — even if hundreds of workers are affected at once, and even if the effect on their incomes looks exactly like a layoff.

The same applies to traditional contracting: ending a vendor agreement or stopping freelance assignments is not, under WARN, a layoff, and the affected workers get no notice period, no WARN back-pay claim, and no filing to look up.

What contractors do get instead

Losing WARN protection does not mean losing every protection. A contractor's rights usually come from the contract and from state law: the contract may set its own notice period or payment terms for completed work — that clause, not WARN, is the first thing to check. State timely-payment laws can also apply, with rules varying by state. Contractors are generally not eligible for unemployment insurance as employees are, though rules and special programs vary.

None of this replaces a 60-day notice: contract notice periods are often short, and many gig terms allow the platform to end the relationship with little warning.

When misclassification changes the answer

The important exception is misclassification. If a worker labelled a contractor is in fact controlled like an employee — set hours, required methods, exclusivity, close supervision, integration into the core business — they may be able to argue they were an employee all along. If that argument succeeds, WARN could apply to them, along with other employee protections such as wage, overtime, and unemployment rules.

Misclassification claims are fact-specific and hard to win on a label alone. Useful evidence includes company-set schedules, instructions on how to do the work, restrictions on working elsewhere, company equipment or uniforms, and regular work that looks like a job rather than a project. Keep contracts, pay records, and schedule messages, and get advice from a state labor agency or employment lawyer before deadlines pass.

Why the data misses contractor cutbacks

Because WARN filings only capture covered employee events, large contractor reductions are invisible in the registry: a company could end work for 500 contractors and file nothing, while laying off 100 employees triggers a public notice. So the national totals — Washington 16,960, California 13,557, Illinois 4,626, Texas 3,652, Georgia 2,492 reported workers in the current window — are a floor for employee layoffs, not a measure of all lost work. The six weeks ahead carry 35,305 workers by effective week, led by the week of November 24 with 9,123; contractor work ending in the same weeks does not appear.

What to check if your work ends

If your work disappears, start with the documents, not WARN. Read the termination clause in your contract or platform terms, check what you are owed for completed work and your state's payment deadline, and save everything: contracts, rate changes, deactivation messages, schedules, and company instructions. If you believe you were treated as an employee, ask a state labor agency or employment lawyer about a misclassification claim promptly, since claims have deadlines.

The WARN Act was written for employees at a single site. As more work moves to contracting and platforms, that design leaves a growing share of workers without WARN's famous protection: advance warning. Knowing whether you count as an employee or a contractor is the first step to knowing what notice, if any, you are owed.

Data source: Layoff Atlas