Urgent.News

What's breaking now, across thousands of outlets.

Tech

WARN Act and Age Discrimination — Are Older Workers Protected When Layoffs Hit?

A WARN notice tells you a layoff is coming, not why you were chosen. That gap matters: the WARN Act and the laws against age discrimination do different jobs, and a layoff can satisfy one while violating the other. The WARN Act is a notice law: 60 days' warning before a plant closing or mass layoff. It never asks whether the selection was fair. The Age Discrimination in Employment Act (ADEA) is…

The WARN Act and Age Discrimination are two distinct laws that can impact older workers during layoffs. While the WARN Act requires a 60-day notice before a plant closing or mass layoff, it does not address the fairness of the selection process. On the other hand, the Age Discrimination in Employment Act (ADEA) protects workers aged 40 or older from discrimination by employers with 20 or more employees.

When an employer complies with the WARN Act and still selects older workers for layoff, it does not absolve them of age discrimination claims. Older workers can still file claims under either the WARN Act or the ADEA, or both. Disparate treatment involves direct evidence of age being a factor in the decision, while disparate impact focuses on neutral-sounding criteria that disproportionately affect older workers.

The Older Workers Benefit Protection Act (OWBPA) disclosure, mandated by the ADEA amendment, requires employers to provide written information about the decision-making process, eligibility factors, and ages of selected and unselected workers. If an employer fails to provide this disclosure, older workers have 45 days to consider the severance agreement before signing.

To protect their rights during the WARN notice period, older workers should refrain from signing severance waivers immediately, ask for the OWBPA disclosure if not provided, and file an EEOC charge within the appropriate deadlines if they believe age played a role in their layoff. The Layoff Atlas data highlights the number of WARN notices and reported workers in various states, with California leading the list.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Markdown vs. JSON: Which Response Format Should You Use?

When using APIs to get search results, the format you choose can impact how easily your application uses that data. Markdown and JSON both let you work with search results, but they're designed for…

  • Markdown format is ideal for readability and reasoning with data
  • JSON format is suited for processing and manipulating data
  • Both Markdown and JSON supported by SerpApi APIs

JobRequester: I built this free Chrome extension that tracks job applications and am looking for feedback

Hi all, I'm the person who built this, and I'd really like honest feedback from people who are job hunting right now. I've been job searching myself, and two parts of it were pure busywork: copying…

  • JobRequester is a Chrome extension that automates job application processes.
  • It captures job details from platforms like LinkedIn and Indeed.
  • User feedback is requested via the Chrome Web Store.

Why Linear Agent Chains Break in Production Banking (And How We Built Deterministic State Graphs with LangGraph + Redis)

Author: Chaman Shah, Principal AI Systems Architect at Elesium The "Prompt and Pray" Crisis in Enterprise AI If you spend any time browsing GitHub or Twitter, you have seen dozens of AI agent…

  • Linear agent chains prone to infinite loops in production banking
  • State loss during external gateway timeouts causes restarts or duplicates
  • Prompt injection attacks bypass system, gain unauthorized access

One SQL predicate, eleven implementations: unifying them and what our differential harness caught

This is a story about paying down the most expensive kind of technical debt in a query engine — duplicated semantics — and the testing harness that made it safe.

  • Eleven separate implementations of SQL predicate evaluation in MoteDB caused inconsistent results
  • Team wrote characteristic tests to lock current behavior before making changes
  • Differential harness caught seven pre-existing divergences in version 0.17

More from Sunday 8 November →