Where Does a Remote Employee Work for WARN? A Multi-State Site-Attribution Worksheet

The Pivot-Table Error That Hides a 60-Day WARN Liability

Grouping HRIS termination rows by payroll tax state undercounts headquarters concentration. Federal WARN looks at operational tether, not bedroom geography.

Watch how a routine headcount model goes sideways. A 340-person fintech company headquartered in Austin plans to eliminate 68 full-time roles on Friday. Inside the Austin office, only 29 badge-in employees lose their seats out of 110 on-site staff. The other 39 eliminated employees work 100% remotely from 19 different states—four in Texas, six in Washington, five in New York, three in Florida, and one or two everywhere else. People Analytics runs a pivot table by "Work Location = Remote" and "Home State," sees no physical building hit 50 losses, and tells the CFO no WARN notice is owed.

That pivot table just missed a textbook federal WARN trigger. Every one of those 39 remote workers receives sprint assignments from engineering directors seated in Austin and reports up to VP budgets coded to Austin. Add 39 tethered remote losses to 29 on-site Austin losses and your Austin single site just lost 68 out of 204 attributed full-time staff—crossing both the 50-employee floor and the 33% site ratio under 29 U.S.C. § 2101(a)(3)(B). At $500 per day in municipal civil penalties plus 60 days of back wages and medical benefits for 68 employees, one bad column filter costs over $1.3 million.

Applying the Three-Prong Test in 20 CFR § 639.3(i)(6)

Department of Labor regulations assign non-site workers through three concrete operational tethers. Courts split on stationary home offices, so conservative HR math tests the inclusive hub count first.

Congress passed the federal WARN Act in 1988 before cloud engineering existed, leaving 20 CFR § 639.3(i)(6) as the controlling text for workers whose primary duties occur outside a fixed company facility. That subsection assigns outstationed, mobile, and remote workers to whichever single site satisfies one of three tests:

1. Home base: The physical company office to which the employee is formally assigned as their home base (even if they rarely visit).
2. Source of work assignments: The physical site from which their day-to-day work, tickets, or quotas are assigned.
3. Reporting hub: The physical site to which they report for supervision, performance evaluation, and administrative direction.

Federal courts do not read § 639.3(i)(6) identically, and people operations teams must understand both sides of the split before gambling on zero notice:

• The narrow mobile-worker reading: In Meson v. GATX Technology Services Corp., 507 F.3d 803 (4th Cir. 2007), the Fourth Circuit read § 639.3(i)(6) primarily to cover traveling workers (like rail crews, bus drivers, and regional sales reps) rather than stationary regional office managers, though it still examined where supervision originated. Earlier Third and Fifth Circuit cases—Ciarlante v. CSX Corp., 143 F.3d 139 (3d Cir. 1998), and Viator v. Delchamps Inc., 109 F.3d 1124 (5th Cir. 1997)—focused heavily on the "true source of day-to-day instructions" rather than centralized payroll servers.
• The modern remote-inclusion reading: Recent post-2020 federal decisions, including Hoover v. Drivetrain LLC, Adv. Proc. No. 20-50966 (Bankr. D. Del. 2022), held that § 639.3(i)(6) "undoubtedly covers remote employees" and certified classes combining headquarters staff with remote workers whose assignments and reporting lines flowed from that headquarters.

Look closely at the two-way denominator rule! When you attribute remote employees to your Austin or Chicago hub to test whether 50 losses occurred, you also include all non-terminated full-time remote employees tethered to that exact same hub in the denominator when calculating the 33% federal mass-layoff ratio. Never mix an inclusive numerator with an on-site-only denominator, or vice versa.

Where State Mini-WARN Laws Override Federal Hub Math

Passing the federal single-site check does not clear New York, New Jersey, or Washington. Each of those three states runs a distinct statutory rule for remote staff.

After running your federal hub attribution, run a second pass sorted by both supervising hub state and employee physical work state across the strictest mini-WARN jurisdictions:

• New York (90 days' notice · 12 NYCRR § 921-1.1(p)): New York amended its WARN regulations in June 2023 to explicitly state that employees who work remotely but are "based at the employment site" count as employees of that New York site. If 20 on-site Manhattan employees and 12 out-of-state remote employees supervised out of Manhattan are laid off (32 total out of 90 Manhattan-based full-time staff), New York's 25-employee / 33% site trigger fires—requiring 90 days' advance notice (plus NY's AI/automation portal checkbox; see our NY and CA WARN AI-checkbox guide).
• Washington (60 days' notice · SB 5525, effective July 27, 2025): Washington's Securing Timely Notification and Benefits for Laid-Off Employees Act covers employers with 50 or more full-time employees in Washington. Crucially, a Washington mass layoff triggers at 50 or more employment losses in Washington within 30 days with zero 33% percentage requirement and aggregates in-state losses rather than shielding dispersed Washington home offices. Worse, SB 5525 generally bars including an employee currently on Washington Paid Family and Medical Leave (PFML) in a mass layoff absent narrow exceptions.
• New Jersey (90 days' notice + mandatory severance · N.J. Stat. § 34:21-1 et seq.): New Jersey counts 100+ employees nationwide (including part-time workers) for employer coverage, aggregates 50 or more terminations across all establishments in New Jersey (no 33% floor), requires 90 days' advance notice, and mandates one week of statutory severance per full year of service automatically—rising by an extra four weeks if full 90-day notice is missed.

What If Your Company Is 100% Virtual With Zero Leased Offices?

Having no physical headquarters lease does not make a 250-person distributed company immune from WARN. Executive residence concentrations, co-working hubs, and statewide mini-WARN counts still bite.

Fully distributed startups often point to a single PO Box in Delaware and assume § 639.3(i)(6) cannot tether anyone to a physical site. Test three hidden anchors before relying on a "virtual-only" defense during restructuring turning points:

1. De facto executive or enterprise co-working hubs: If your CTO and four engineering directors work out of a dedicated multi-desk suite in San Francisco or Brooklyn and assign sprints from there, plaintiff counsel will frame that suite as the § 639.3(i)(6) assignment and reporting site.
2. Managerial home offices acting as regional assignment hubs: If a VP of Sales assigns quotas and reviews pipeline for 65 remote account executives from a registered corporate entity address, litigants test whether that address serves as the administrative hub.
3. Statewide domicile aggregation in WA and NJ: Even if no physical brick-and-mortar hub exists anywhere in the country, laying off 52 remote employees who live and work across Seattle, Tacoma, and Spokane triggers Washington's statewide 50-loss SB 5525 rule on its own.

Copy-Ready HRIS Remote Attribution Schema & Pre-RIF Audit Log

Populate these six columns for every active US employee before running any 30-day or 90-day WARN simulation. Never rely on a generic "Remote - US" location string in your HRIS.

HRIS WARN SITE-ATTRIBUTION AUDIT LOG (RUN AT T-95 DAYS BEFORE TARGET RIF)
Lookback Window Checked: [Target Date - 90 Days] to [Target Date + 90 Days]
Part-Time / Tenure Exclude Cutoff (<6 of last 12 mos or <20 hrs/wk avg): Verified per 20 CFR § 639.3(h)

REQUIRED EMPLOYEE-LEVEL ATTRIBUTION FIELDS (EXPORT ALL ACTIVE + 90-DAY PRIOR INVOLUNTARY EXITS):
1. employee_id             : Unique HRIS identifier
2. ft_warn_status          : FULL_TIME (≥6 mos of prior 12 & ≥20 hrs/wk) | PART_TIME_SHORT_TENURE
3. physical_work_state     : State where employee physically performs work (controls WA/NJ/CA resident tests)
4. assigned_home_base_site : Formal company facility on offer letter / HRIS (Prong 1: 20 CFR § 639.3(i)(6))
5. work_assignment_hub     : Physical facility where direct task/sprint/quota issuer sits (Prong 2: Ciarlante/Hoover)
6. direct_reporting_hub    : Physical facility where direct supervisor of record sits (Prong 3: NY 12 NYCRR § 921-1.1(p))

FOUR-PASS THRESHOLD GATE:
[ ] Pass 1 (Federal Hub Max): Group all FT losses by MAX concentration across Fields 4, 5, and 6. Flag any hub ≥ 50 FT losses AND ≥ 33% of total FT staff attributed to that same hub (or ≥ 500 FT).
[ ] Pass 2 (NY 90-Day Gate): Sum FT losses physically at NY site + remote staff (in-state or out-of-state) with Field 5 or 6 = NY site. Flag at ≥ 25 FT & ≥ 33% (or ≥ 250 FT).
[ ] Pass 3 (NJ 90-Day + Severance Gate): Sum ALL losses (FT + PT) physically in NJ or reporting into NJ (Field 3, 5, or 6 = NJ). Flag at ≥ 50 statewide.
[ ] Pass 4 (WA 60-Day + PFML Gate): Sum losses with Field 3 = WA. Flag at ≥ 50 in 30 days; verify zero WA PFML-active employees are on the involuntary list per SB 5525.