Match RIF Notice and Termination Dates

The gap is the compliance test

When you set a RIF notice date, the controlling date is the earliest actual separation date. Essendant's Aug. 3 notice said covered terminations were expected on or after Oct. 3. The WARN notice identified 510 job losses at Essendant's Lincolnshire headquarters and 134 at its Carol Stream distribution center as the company closed both sites.

Federal WARN law requires covered employers with at least 100 employees to give 60 days' notice before significant layoffs or plant closings. Illinois law imposes a 60-day advance notice requirement on employers with at least 75 employees when they close a plant or conduct a mass layoff. A RIF involves several dates, and at least one of them can move.

On Aug. 27, Essendant let go of hundreds of workers, mostly based at the Lincolnshire headquarters, during a mass video call layoff. A follow-up letter dated Aug. 28 gave Aug. 31 as the final workday for employees cut early and included no severance pay or other benefits. The Illinois Department of Labor began an investigation into the layoffs.

When the gap is shorter than the required period, the shortness is the legal problem. A short gap can create avoidable notice exposure for the missing days.

Set the date from the real plan, not the preferred one

Managers often build a RIF around a target date: the end of a quarter, the end of a lease, or the date a replacement system goes live. That target is useful for planning, but the date you must defend is the earliest date on which any covered employee will actually be separated.

If some employees are cut earlier because of site access, payroll, or a facility shutdown, the record should show why. A note saying the company expected to move the date is weaker than a note explaining the business trigger, the decision date, and the people affected.

Documenting uncertainty is a record that the date moved for a real business reason, not a drafting error. That distinction matters when a regulator or a plaintiff asks why the notice did not match the termination.

The law requires the full period; the record makes that period defensible when the business reason for the date is questioned.

The checklist catches date changes before they become liability

The checklist below is the minimum. Each item is a date check, not a legal opinion.

• Identify the covered employer. Confirm the applicable employee-count threshold and notice period.
• Set the earliest actual separation date. Use the first date any covered employee will stop working, not the target date for the whole group.
• Verify the 60-day gap by counting from the notice date to that earliest separation date.
• Document bona fide uncertainty. Record the business reason the date could move and the date you made the decision.
• File the state notice. Make the required state filing if state law applies.
• Update if dates move. If the earliest separation date changes, recheck the gap and issue a corrected notice if needed.

Use the list as a pre-send check. The first two items keep the threshold and the date accurate, the third is the actual compliance test, the fourth turns a bad surprise into a defensible record, the fifth keeps the state informed, and the sixth catches the moment a plan changes.

Before sending the notice, ask one question: if the first covered employee leaves tomorrow, does the notice still give the full required period? If not, the date is wrong. Fix the date, document the reason, and send the notice from the real plan.