The Consultant Arrives: Field Notes on Being Restructured

The badges are the first tell. Not the meeting invites, not the closed door — the badges, because a consulting team on-site for six weeks needs building access, and building access means a print run at the front desk, and a print run at the front desk means the receptionist knows two full weeks before your director does.

I've watched this happen at three different companies now, close enough to see the same choreography each time, different enough that I stopped believing it was a coincidence around the second one. Nobody announces a restructuring. A restructuring arrives the way weather arrives — pressure first, rain later, and by the time anyone says the word out loud you've already reorganized your whole understanding of the building around it.

This is a field report on the pressure.

The shape of it, before anyone says the word¶

Here's what actually happens, roughly in order, and I'd bet money you'll recognize at least four of these if you've been anywhere near a restructuring.

New people appear who don't have your company's laptop stickers. They sit in a conference room that used to be called something like "Innovation Lab" and is now booked, recurring, under a name like "Q4 Ops Review" — vague enough to mean nothing to anyone scanning the calendar, specific enough that everyone eventually learns not to book it. Department heads get pulled into individual sessions and asked to rank their own direct reports against each other, framed as "capability mapping" or "talent calibration." Org charts that haven't been updated in two years suddenly need updating, urgently, with dotted lines clarified — the same dotted lines that were never really the map of power to begin with, now getting redrawn by people who don't work there. HR's door, usually open, starts closing for meetings that go long. Sometimes the ranking exercise doesn't produce a layoff at all — it produces a sudden run of performance improvement plans for a specific list of names, which is the slower version of the same decision.

None of this is proof of anything. Each piece has an innocent explanation, and companies genuinely do run benchmarking exercises that go nowhere. That's exactly why it works as a diffusion mechanism instead of an announcement — every individual signal is deniable, and only the pattern is legible, and by the time the pattern is legible to you it's usually already been legible to the consultants for a month.

Push this vocabulary hard enough and it stops being a euphemism and starts being its own genre — a fictional earnings call built entirely out of this dialect reads as satire mainly because nobody would actually say the quiet part that clearly out loud in one sitting, not because the individual phrases are exaggerated.

The statute that had to see this coming¶

Here's the fact that anchors this piece, and it's a genuinely useful one to know cold: there is a federal law that defines, in numbers, exactly how big a layoff has to be before your employer owes you formal warning — and the law's own text proves that companies have been trying to stay just under that number for as long as the number has existed.

The Worker Adjustment and Retraining Notification Act — WARN, passed in 1988 — requires covered employers to give 60 calendar days' written notice before a plant closing or mass layoff. It applies to employers with 100 or more employees. A "mass layoff" is defined, in the statute's own words, as a reduction hitting at least 33% of the workforce at a single site and at least 50 employees, or 500 employees regardless of percentage, within any 30-day period.

Read that threshold like a consultant would read it, and the temptation is obvious: cut 49 people at a 148-person site and you owe nothing. Cut 48 the following month and technically, on paper, you've run two separate small reductions rather than one reportable event.

Congress anticipated this. Section 2102(d) of the Act states that employment losses spread across two or more smaller groups at one site, each below the reporting minimum, are still counted as a single mass layoff or plant closing if they occur within any 90-day period —

“

...unless the employer demonstrates that the employment losses are the result of separate and distinct actions and causes and are not an attempt by the employer to evade the requirements of this chapter.

”

Sit with that clause for a second. It is not a hypothetical protection against a theoretical abuse. Lawmakers wrote an explicit burden-shifting rule — the employer has to prove the waves were unrelated — specifically because the pattern of staging layoffs to stay under the line was common enough, in 1988, to require a legislative patch. The badges-and-vague-conference-room choreography I opened with isn't paranoia. It's downstream of a documented incentive that's been on the books for going on forty years.

What the consultant is actually for¶

I don't think most restructuring consultants are cartoonishly cynical people executing a script they know is hollow. Most of them are doing competent, specific, technical work — cost modeling, span-of-control analysis, process mapping — and the analysis is frequently real.

What's worth separating out is the analysis from the function, because they're not the same thing. The function is to make the number nobody's fault.

Consider what a headcount reduction looks like without an outside firm attached to it. A specific VP has to sit down, look at a specific spreadsheet with specific names on it, and decide that this person stays and that person doesn't. That VP has to live in the building afterward. They have to make eye contact in the elevator with people who report to people they cut. The decision is theirs, attributable, and it will follow them into every future conversation about who they are as a manager.

Now consider the same reduction with a consulting engagement in front of it. The number comes from a "benchmarking exercise" against "peer organizations." The framework was applied consistently. The rankings came from a "capability calibration" process that multiple people signed off on. By the time anyone has to deliver the actual news, the decision has been laundered through enough process that no single person inside the building made it — a framework did, and frameworks don't have to make eye contact with anyone in the elevator.

That's the turn this piece is built on. The badges, the vague conference room name, the ranking exercise — none of it is really about analysis speed or methodology. It's about making sure that when the number lands, it lands as something that happened to the organization rather than something a specific person chose, and that distinction is worth a great deal of money to the person who would otherwise have to own it.

What to actually do if you see the tells¶

1. 1

   Don't wait for confirmation you're not going to get

   Nobody will tell you a restructuring is coming before it's finalized — the whole design of the process is to prevent exactly that leak. If you're seeing three or more of the tells above, act on the pattern rather than waiting for someone to say the word out loud to you directly. They can't, and in many cases genuinely don't know themselves yet who's affected.

2. 2

   Learn your state's threshold, not just the federal one

   Several states run their own WARN-style laws with lower triggers than the federal 100-employee, 50-worker floor — meaning a reduction too small to require federal notice can still legally require state notice. Check your state labor department's site directly rather than assuming the federal numbers above are the whole picture where you live.

3. 3

   Get anything discussed in a meeting put in writing before you sign anything

   Verbal reassurances about "no immediate plans" are not commitments and aren't meant to be. If you're asked to sign anything — an updated role description, a new reporting line, an acknowledgment of any kind — during a period when the tells are active, it's reasonable to ask for 24 hours and actually read it, ideally against what a contract is actually promising you rather than what the room implies it's promising you.

4. 4

   If a severance offer arrives, the clock in the room is not the real clock

   Severance agreements are typically offered with an internal deadline attached, and that deadline is a negotiating tactic, not a legal one. For workers 40 and older, federal law sets real statutory floors regardless of what the cover email says: at least 21 days to consider an individual severance agreement, at least 45 days if it's part of a group layoff or exit-incentive program, and a further 7 days to revoke the signed agreement afterward. Those are checkable minimums, not suggestions.

5. 5

   Document your own timeline, quietly, as you go

   Dates of the ranking exercise, who ran it, what you were told and by whom. Not for a lawsuit you may never file — for your own clarity later, when the official story of "why" gets written by people whose job was partly to make sure no clean story existed. Your dated notes are more reliable than anyone's memory, including your own in six months.

The elevator, afterward¶

The last time I watched this play out, the actual announcement took four minutes. A framework had been applied. The organization was being aligned to better serve its strategic priorities going forward. Questions could be directed to HR. Someone, somewhere, will eventually translate that memo line by line — they always do, a few days later, in a group chat instead of a conference room.

Nobody in that room had decided anything, according to the room. The decision had been arrived at, the way weather arrives — and everyone who'd been reading the tells for six weeks already knew that "arrived at" was doing an enormous amount of quiet work in that sentence, standing in for a specific person who chose a specific number and then hired six weeks of process to make sure they'd never have to say so out loud.

I still notice new badges at a front desk. I don't think that's paranoia. I think it's just knowing what the weather looks like before it rains.

It's just business.

Sources

1. 29 U.S.C. § 2101 — Worker Adjustment and Retraining Notification Act, Definitions
   +How this was checked

   Defines 'mass layoff' as a reduction in force resulting in employment loss during any 30-day period for at least 33% of the workforce and 50 employees at a single site, or at least 500 employees regardless of percentage. Defines 'plant closing' as a shutdown resulting in employment loss for 50 or more employees within 30 days. Covers employers with 100 or more employees.

2. 29 U.S.C. § 2102 — WARN Act, Notice Requirement and Aggregation Rule
   +How this was checked

   Requires 60 calendar days' written notice before a covered plant closing or mass layoff. Subsection (d): employment losses for two or more groups at a single site, each below the individual reporting minimum, are aggregated and treated as one mass layoff or plant closing if they occur within any 90-day period, 'unless the employer demonstrates that the employment losses are the result of separate and distinct actions and causes and are not an attempt by the employer to evade the requirements of this chapter.'

3. U.S. Department of Labor — Plant Closings and Layoffs (WARN Act overview)
   +How this was checked

   Confirms the 100-employee employer threshold, the 50-employee single-site trigger, and the 60-day advance written notice requirement, and that notice must go to affected workers, employee representatives, and state/local officials.

4. 29 U.S.C. § 626(f) — Age Discrimination in Employment Act, Waiver Requirements (Older Workers Benefit Protection Act)
   +How this was checked

   Subsection (f)(1)(F): a valid waiver requires 'the individual is given a period of at least 21 days within which to consider the agreement' for an individual termination, or 'at least 45 days' for a waiver requested in connection with an exit incentive or other group termination program. Subsection (f)(1)(G): the agreement must provide 'a period of at least 7 days following the execution of such agreement' during which the individual may revoke it.