Skip to main content
Independent public-records databaseSource methodology
WARN Act Tracker

Research note: Coverage varies by state. Verify critical details in the linked agency record. This directory is independent and is not legal advice.

WARN research guide

Remote Workers and WARN: Finding the ‘Single Site of Employment’

How federal WARN assigns remote, traveling, and hybrid employees to a worksite—and why a nationwide virtual layoff is not necessarily one legal event.

By WARN Act Tracker Editorial Team · · 9 minute read

A remote worker typing on a laptop at a home desk
Photo: Vlad Bagacian / Pexels

A remote employee’s home is where the work happens, but it is not necessarily the employee’s “single site of employment” under federal WARN. That phrase is a legal sorting rule. It determines which employment losses are grouped together when testing the thresholds for a plant closing or mass layoff.

For a distributed workforce, the site question can decide whether 20 workers are counted in five separate groups or 100 workers are counted together. Neither a corporate headquarters address nor a home address answers it automatically.

Why the single-site rule matters

Federal WARN applies its plant-closing and mass-layoff thresholds at a single site of employment. For a typical factory or store, that may be a straightforward physical location. For people who sell on the road, service a territory, drive routes, or work from home, the connection is less visible.

The governing definition appears in 20 CFR § 639.3(i). For workers whose primary duties require travel, who are outstationed, or whose primary duties occur outside the employer’s regular sites, it points to the site:

  • to which the worker is assigned as a home base;
  • from which the worker’s work is assigned; or
  • to which the worker reports.

The Department of Labor’s current WARN Advisor glossary repeats this framework, and its WARN frequently asked questions expressly includes teleworkers among employees whose work occurs outside a regular employment site.

The regulation was written before modern work-from-home arrangements became ordinary, but the Department applies its outstationed-worker framework to teleworkers. The result remains fact-specific.

A home office is not automatically its own site

Treating each residence as a separate worksite would often prevent remote employees from ever being grouped, even when they belong to the same operational hub. The federal rule instead asks where the employment relationship is organizationally anchored.

That does not mean every remote employee is assigned to headquarters. A company may direct work through regional offices, client teams, call centers, or separate business units. Two employees living on the same street could be assigned to different sites. Employees living in different states could be assigned to the same one.

The correct answer depends on evidence, not the address that is most convenient to put in a spreadsheet.

The three connections to investigate

The regulation’s phrasing produces three practical lines of inquiry.

Assigned home base

Look for an express organizational assignment. Offer letters, HR systems, payroll records, remote-work agreements, office-access credentials, internal directories, and cost-center records may identify an office or facility as the employee’s base.

A “remote” label alone is incomplete. It describes the work arrangement, not necessarily the WARN site.

Where work is assigned

Identify where decisions about the employee’s day-to-day work originate. That may be the location of a dispatch operation, scheduling team, sales office, call-center management group, or supervisor. The physical location of a server is generally less informative than the people and operation actually assigning the work.

For a fully distributed management team, this question may be difficult. The regulation also recognizes that “truly unusual organizational situations” may not fit its ordinary categories, while rejecting arrangements designed to evade WARN.

Where the employee reports

“Reports” can describe an organizational relationship, not just swiping a badge. Relevant facts may include the location of the manager or operating unit receiving the worker’s reports, where performance and attendance are administered, and where the employee is expected to appear for meetings or equipment.

No single email signature, org-chart box, or occasional office visit should be treated as conclusive without the surrounding facts.

Hybrid employees may require a different starting point

The special rule is written for workers whose primary duties involve travel, outstationing, or work outside regular sites. A hybrid employee who regularly performs primary duties at an employer office may fit the ordinary physical-site rules more naturally.

Those rules can themselves be nuanced. Contiguous locations can form one site. Nearby non-contiguous facilities may be combined when they are in reasonable geographic proximity, serve the same purpose, and share staff and equipment. Conversely, even contiguous buildings can be separate sites when they have separate management, products, and workforces.

The analytical order should therefore be:

  1. establish what the employee’s primary work arrangement actually was;
  2. determine whether the ordinary physical-site rules or the outstationed-worker rule fits;
  3. identify the organizational site using contemporaneous records; and
  4. only then group the employment losses and test the threshold.

A distributed-layoff example

Imagine a software company eliminates 120 fully remote customer-support positions on the same day. The employees live across 30 states.

If all 120 were assigned to, received work from, and reported through one support center, their geographic spread does not necessarily create 120 separate sites. The common organizational site could be central to the WARN count.

Now change the facts. Forty employees belong to a western support center, 45 to a central center, and 35 to an eastern center, with separate managers and work-assignment systems. A company-wide announcement still does not automatically turn those groups into one single site. Each organizational connection needs to be assessed.

This example does not decide coverage. Employer size, part-time status, what counts as an employment loss, the 30- and 90-day windows, and state mini-WARN rules still matter. It shows why counting “remote layoffs nationwide” as one federal event—or 120 home-office events—can both be wrong.

State location and federal site are different questions

A worker’s state of residence can affect unemployment insurance, wage law, taxes, and possible state mini-WARN protection. The federal single-site analysis serves a narrower purpose: grouping employment losses under the federal Act.

Do not assume the state where a remote employee lives is the state whose WARN register will contain the notice. State filing rules and agency practices vary. A filing may appear where the assigned site is located, in several states, or under a corporate address. The absence of a row in a worker’s home-state database does not prove that no notice exists.

Our guide to federal WARN and state mini-WARN laws explains why the federal analysis should not be used as a substitute for a state-law review.

What to preserve if a remote layoff is announced

Remote workers and researchers should preserve records that reveal the organizational connection as it existed before the layoff:

  • the offer letter and remote-work agreement;
  • the assigned-office field in the HR profile;
  • the manager’s and team’s locations;
  • records showing who assigned and scheduled work;
  • cost center, department, and operating-unit names;
  • required in-person reporting locations;
  • equipment-shipping and office-access records; and
  • the notice and any list of affected sites.

Capture these records lawfully and do not retain confidential employer information you are not entitled to keep. The goal is to document your own assignment, not to take company data.

How to read remote-work entries in public WARN data

When a public notice lists a headquarters or regional office, describe it as the reported worksite unless the source explains more. Avoid rewriting it as the residence of every affected employee. If one notice spans several sites, do not duplicate the total across each location unless the filing provides site-level counts.

Most importantly, do not infer that workers were excluded from WARN merely because they worked from home. The federal regulations supply a method for assigning outstationed workers to a site. Applying that method requires facts a public register may not contain.