WARN Act Notice Files: The Four Versions 20 CFR 639.7 Requires and the Service Records That Decide a $500-a-Day Question

A WARN Act notice file should show which version went to each required audience, who received it, and when it was served. A copy of a notice alone does not establish that every recipient received the correct information on time.

This guide focuses on notice versions and delivery evidence. For the Act's broader requirements, see the WARN Act notice overview.

Confirm the notice population and timing

Under 20 CFR § 639.5, the general advance-notice period is 60 calendar days. When employees are separated on different dates, the first individual termination within the applicable 30- or 90-day aggregation period triggers the timing analysis. Employers should review employment actions both before and after the event across those periods.

Under 20 CFR § 639.6, notice goes to each affected employee representative, each affected employee without a representative, the State dislocated worker unit, and the chief elected official of the local-government unit. Where the local unit has an elected board, the chief elected officer of that board receives the notice. Part-time employees do not count toward the statutory thresholds but are entitled to notice if affected.

The four WARN notice versions

Section 639.7 assigns different content to different recipients. Treat these as separate controlled documents or clearly identified versions. A single generic notice should not stand in for all four.

1. Notice to each employee representative

Under § 639.7(c), written notice goes to the chief elected officer of the exclusive representative. It identifies:

• The employment site name and address, and a company contact's name and telephone number.
• Whether the action is expected to be permanent or temporary, and whether the entire plant will close.
• The expected date of the first separation and the anticipated separation schedule.
• Affected job titles and the names of employees currently holding those positions.

The names requirement distinguishes this version from the notice to public officials. Preserve the representative's identity and the exact version served.

2. Notice to each unrepresented affected employee

Under § 639.7(d), each unrepresented affected employee receives a written notice in language understandable to employees. It states:

• Whether the action is permanent or temporary.
• When the closing or layoff is expected to begin, and the expected separation date for that employee.
• Whether bumping rights exist.
• The company contact's name and telephone number.

The notice can also include dislocated-worker assistance information and, for a temporary action, an estimated duration. Retain the employee-specific recipient list alongside the dated notice version.

3. Full notice to the State unit and local-government official

Under § 639.7(e), the State dislocated worker unit and chief elected local official receive notice identifying the site, company contact, permanent-or-temporary status, first separation date, and anticipated schedule.

This version also lists affected job titles and the number of employees in each classification, indicates whether bumping rights exist, and identifies each union representing affected employees. For each union, it includes the chief elected officer's name and address.

Keep separate service entries for the State unit and local official, even when the same document is used. The file should establish that the correct official and unit received it.

4. Alternative short-form notice to government recipients

Section 639.7(f) permits a shorter notice to the State unit and local-government official. It contains the site name and address, contact information, expected first separation date, and number of affected employees.

This option is conditional. The employer must maintain the complete information required by § 639.7(e) on site and make it readily accessible. If that information is unavailable when requested, the regulation treats the employer as having failed to give the required notice. That consequence makes the supporting record, not merely the short form, the decisive evidence.

Keep a recipient-to-version service record

For each recipient, the notice file should connect four items: recipient identity, applicable version, date served, and dated evidence of service. Maintain:

• A final, dated copy of each version actually served.
• A distribution list identifying each employee, representative, State unit, or local official.
• A service log recording the delivery method and date for each recipient or documented batch.
• Available delivery evidence, such as mailing records, tracking events, signed receipts, or personal-delivery records.
• A record of returned, refused, misdirected, or reissued notices and the corrective action taken.

The file should also identify the person responsible for preparing and approving the notices. Keep the distribution list and service evidence linked to the corresponding final version, rather than in separate folders that require reconstruction.

For a related framework, see the audit trail framework for legal notices, the guide to proof of mailing versus proof of notice, and notice record retention.

Select and document a reasonable delivery method

WARN rules require written notice. They do not require Certified Mail. Section 639.8 instead calls for a reasonable delivery method designed to ensure receipt by the required parties on time. The regulation gives first-class mail and personal delivery as examples, with a signed receipt as an option.

Document the method selected, the service date, the destination, and the resulting delivery record. Certified Mail is one available method, not a federal WARN mandate. Its postal records can support the file, but the notice version and recipient record still need to be connected to that mailing.

The local-government recipient warrants specific attention. The Department of Labor's Employment Law Guide states that failure to notify the local-government unit can result in a civil penalty of up to $500 for each day of violation. The penalty can be avoided if the employer satisfies its liability to each affected employee within three weeks after the closing or mass layoff. The penalty is not an automatic charge for every notice defect; the facts and applicable law control.

Record conditional notices and exceptions

Section 639.7(a)(3) permits conditional notice only when a definite event will necessarily lead to a covered action less than 60 days later. The notice must still include the required § 639.7 content. Under § 639.7(a)(4), information is based on the best information available when the notice is served; later changes or minor inadvertent errors are not violations by themselves.

The three exceptions under § 639.9 are narrowly defined: faltering company for plant closings, unforeseeable business circumstances, and natural disaster. When an exception applies, the employer must provide as much notice as practicable and include a brief statement explaining the reduced notice period, along with the other required notice elements.

Preserve the facts supporting the exception, the decision and approval record, the date notice became practicable, and copies of the notices served to each audience.

State mini-WARN laws, including those in New York and California, can impose different thresholds and notice periods, so confirm applicable State requirements separately.

Prepare one retrievable notice package

Before an examination or dispute, the file should allow a reviewer to determine which version went to each required recipient, when it was served, and what evidence supports that date. A complete package links the requirement, recipient list, final notice versions, approval record, service log, delivery evidence, and any exception or corrective-action records.

For organizations managing related notice issuance and records, National Compliance Registry services support controlled records, ownership, and evidence maintenance.

This article provides general compliance information, not legal advice.