{"id":23437,"date":"2026-10-27T02:05:00","date_gmt":"2026-10-27T02:05:00","guid":{"rendered":"https:\/\/www.youragecalculator.com\/blog\/?p=23437"},"modified":"2026-10-27T02:05:00","modified_gmt":"2026-10-27T02:05:00","slug":"how-union-seniority-determines-layoff-order","status":"publish","type":"post","link":"https:\/\/www.youragecalculator.com\/blog\/how-union-seniority-determines-layoff-order\/","title":{"rendered":"How Union Seniority Decides Who Gets Laid Off First"},"content":{"rendered":"
\n

When a union shop announces a reduction in force, the order of layoffs is usually fixed before anyone is called into an office. Most collective bargaining agreements specify that employees are laid off in inverse order of seniority within a defined unit, and the arithmetic behind that ordering is where most disputes begin. Two workers hired the same month can end up on opposite sides of a cutoff because their seniority is measured from different dates, or because the agreement uses a different seniority type for the layoff than it does for bidding shifts.<\/p>\n

Seniority in a union setting is rarely a single number. It is a set of clocks, each started by a different event, and the contract tells you which clock governs which decision. Getting the layoff order right means knowing which clock the layoff article points to.<\/p>\n

The Three Seniority Clocks<\/h2>\n

Company seniority<\/strong> generally starts on the date of hire and continues through transfers between departments and often through unpaid leaves. Classification or department seniority<\/strong> starts when the employee entered their current job classification and resets on promotion into a different classification. Plant or location seniority<\/strong> starts when the employee began working at that specific facility.<\/p>\n

These three run on different schedules for the same person. A worker hired in 2011 who transferred into maintenance in 2018 has 15 years of company seniority and 8 years of classification seniority. If the contract says layoffs within the maintenance classification are by classification seniority, that worker is ranked as an 8-year employee against colleagues who may have only 6 years in the classification but 20 years at the company.<\/p>\n\n\n\n\n\n\n\n\n
Seniority type<\/th>\nStarts on<\/th>\nTypically governs<\/th>\n<\/tr>\n<\/thead>\n
Company<\/td>\nOriginal date of hire<\/td>\nVacation accrual, pension service credit, some benefit tiers<\/td>\n<\/tr>\n
Classification \/ department<\/td>\nDate entering current classification<\/td>\nLayoff order within a classification, shift preference, job bidding<\/td>\n<\/tr>\n
Plant \/ location<\/td>\nDate beginning work at the facility<\/td>\nLayoffs where the unit is defined by facility, recall rights at that site<\/td>\n<\/tr>\n
Super-seniority<\/td>\nVarious (union office, military leave)<\/td>\nProtects stewards and returning service members from layoff<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Why the Layoff Article Matters More Than the Seniority List<\/h2>\n

Seniority lists are posted and grieved over constantly, but the list alone does not tell you who is laid off. The layoff article defines the unit<\/em> \u2014 the group of employees ranked against each other \u2014 and the unit is often narrower than the whole bargaining unit. A company may lay off by classification within a department, which means an employee with 18 years of company service can be laid off while someone with 4 years in a different classification is untouched.<\/p>\n

The agreement also usually sets a tie-breaker. Common provisions use the last four digits of the Social Security number, the date of birth, or a lottery. Because the tie-breaker is arbitrary by design, employees hired on the same day can be separated by an administrative rule they never noticed. Remembering that a tie-breaker is not a merit judgment prevents a lot of unnecessary grievance filings.<\/p>\n

A Worked Example With Real Numbers<\/h2>\n

Consider a maintenance unit of five employees facing two layoffs. Seniority dates in the classification are: A, March 2014; B, September 2016; C, January 2019; D, January 2019; E, June 2021. The contract lays off in inverse order of classification seniority, with ties broken by earliest date of birth. C was born in April 1985 and D in November 1991, so C outranks D. The two lowest-ranked are E (2021) and D (2019, later birth date). A, B, and C are retained even though B has less company seniority than D, because the layoff article points to classification, not company, seniority.<\/p>\n

Change one word in the contract \u2014 from classification seniority to company seniority \u2014 and B may become the person laid off. That is why reading the layoff article before computing anything is the only reliable method. Computing a total years-of-service figure and assuming it drives the layoff is the single most common analytical mistake in these cases.<\/p>\n

Bumping Rights Change the Order After the Fact<\/h2>\n

Many agreements let a laid-off employee “bump” a junior employee in another classification or shift, provided they can perform the work. Bumping can cascade through several classifications, and the arithmetic becomes a chain rather than a list. An employee with 12 years of company seniority who is laid off from a classification they held for 2 years may be entitled to bump into a classification where they have 10 years. Modeling this properly requires tracking seniority per classification for every affected employee, not a single ranked column.<\/p>\n

Recall rights work the same way in reverse. Laid-off employees are typically recalled in inverse order of layoff for a set period \u2014 commonly 12 to 24 months \u2014 and the clock starts on the layoff date, not the date the employee learns of it. If you are reconstructing dates to establish recall eligibility, a date difference calculation between two events<\/a> avoids the off-by-one and leap-year errors that show up in grievance exhibits.<\/p>\n

Documenting the Calculation<\/h2>\n