WARN Act and Project Completion: When a Temporary Job Needs No Layoff Notice

A construction crew finishes a bridge and goes home. A film crew wraps a shoot and disperses. A harvest crew finishes the season. Dozens stop work the same day, and no WARN notice is filed. That is not a violation. Under the WARN Act, the end of a project workers were hired to finish is not the kind of layoff the law covers.

This matters because project-based work shows up constantly in layoff data: the Layoff Atlas registry currently holds 667 WARN notices covering 61,284 reported workers in the 90-day window. Knowing which endings required a 60-day notice — and which did not — is the difference between a missing notice and a lawful one.

What the law actually says

The exemption is written into the statute. The WARN Act "shall not apply to a plant closing or mass layoff if the closing is of a temporary facility or the closing or layoff is the result of the completion of a particular project or undertaking, and the affected employees were hired with the understanding that their employment was limited to the duration of the facility or the project or undertaking." That is 29 U.S.C. § 2103(1).

The Department of Labor's regulation, 20 C.F.R. § 639.3(c), adds two conditions, and both must be true: the layoff must result from completing a particular project or closing a temporary facility, and the employees must have been hired understanding their employment was limited to that project's duration.

"Clearly understand at the time of hire"

The regulation puts the emphasis on what workers understood when they were hired — not what the employer says after the fact. "Employees must clearly understand at the time of hire that their employment is temporary." Whether that understanding existed is judged by reference to employment contracts, collective bargaining agreements, or the employment practices of an industry or a locality. The burden of proof sits with the employer: the employer has to show the temporary nature of the project was clearly communicated. A signed offer letter stating the job ends when the project ends is strong evidence. A manager's after-the-fact claim that everyone knew is not.

The regulation names the industries where this comes up most: agriculture and construction, where employers "frequently hire workers for harvesting, processing, or for work on a particular building or project." That work may be seasonal but recurring, and it still falls under the exemption — if the workers understood at hire that their work was temporary.

Completion is not cancellation

The sharpest edge of the rule is the word "completion." The exemption applies when the project is finished — the bridge is built, the film is shot, the harvest is in. It does not apply when a project is cancelled early for business reasons.

If a developer pulls funding halfway through a building and the crew is sent home, that is not the completion of a project. It is a layoff, and the normal WARN rules apply: a covered employer — generally one with 100 or more full-time employees — owes 60 days' notice. An unfinished project is not a completed one.

Employers also get into trouble by relabelling. The Department of Labor's guidance is blunt: an employer cannot label an ongoing project "temporary" to evade its obligations under WARN. If the work is really open-ended, calling it a project does not make it one.

California narrows the rule further

California's version of this exemption is much narrower than the federal one. Under California's mini-WARN law, Labor Code § 1400(g), the project-completion exemption applies only to employers subject to Wage Orders 11, 12, or 16 — the orders covering the motion picture industry and the construction, drilling, logging, and mining industries. A California employer outside those industries cannot use the project-completion argument at all.

What to do if you got no notice

If your job ended with a project and no WARN notice arrived, start with what you were told when you were hired. Check your offer letter, employment contract, or union agreement for language about the job's duration, and ask whether the project actually finished or was cut short. Check whether your state has a mini-WARN law that treats project work differently from the federal rule.

Three points are worth keeping in mind. First, no WARN notice does not mean no unemployment benefits: project workers who understood their jobs were temporary are still generally eligible for unemployment insurance when the work ends. Second, a cancelled project is different from a completed one: if the work ended early because funding dried up or a contract was pulled, the exemption likely does not apply, and a covered employer may owe notice — or back pay and benefits for the shortfall. Third, keep the paperwork: the offer letter and any written description of the job's duration are the evidence that decides whether the exemption applies.

One caveat about the numbers. The WARN figures here — 667 notices and 61,284 reported workers, with California (22,043) and Washington (17,333) far ahead of every other state — describe reported plans, not confirmed job losses. Project completions that need no notice never enter those counts at all, which is one more reason the registry understates how many jobs actually end.

The WARN Act is a notice law, not a job-protection law, written for permanent jobs ending unexpectedly. It deliberately leaves out jobs that were temporary by design. The test is simple in principle and often contested in practice: was the work always meant to end, and did everyone know that on day one?

Data source: Layoff Atlas.