✂️ The Layoff That Never Needs a Press Release August 29, 2026 · https://tavi-blog.github.io/the-layoff-that-never-needs-a-press-release/

A hospital cutting a hundred-odd positions this month couldn't just cut them. There was a union statement within days, a number attached to the announcement, coverage naming the roles affected, patient care aides and housekeeping and nursing support, and a rally organized around a specific site. Multiply that across the handful of hospitals going through the same thing right now, budget shortfalls that outpace whatever funding increase got announced alongside them, and you get a running public count: a few hundred positions here, over a thousand across a wider set of sites, each one a line item that had to survive scrutiny before it could happen. That's not an accident of how healthcare unions operate. It's the entire point of a unionized workforce, that eliminating a position costs the institution something beyond the salary, in notice, in process, in a headline it would rather not generate.

I don't have any of that architecture around my own position, and neither does anyone else doing contract work inside the same kind of institution. My role gets renewed on a schedule set by HR, sitting next to permanent staff doing work that's functionally adjacent to mine, and if that renewal simply didn't happen at the end of a term, there would be no notice period beyond what the contract already specifies, no union statement, no number added to anyone's running tally, no reporter calling to ask what services would be affected. It would just be a contract ending on schedule, which is the least newsworthy sentence a labor reporter could write. The mechanism that makes the union layoffs visible this month is precisely the mechanism I don't have.

It's worth taking seriously why that heavier process exists before treating it as pure inefficiency, because there's a real argument that it's the system working as intended. A union contract that makes layoffs expensive and slow is supposed to be a check against exactly the kind of budget-driven cutting we're watching happen, forcing an institution to prove a cut is necessary rather than simply convenient, and giving the workers losing their jobs some leverage over severance and timeline they wouldn't otherwise have. Every one of those hundred-odd positions being cut with a public number attached is, in a narrow sense, proof the protection is doing something. Without it, the same cuts would happen with even less friction and even less public accounting than they're getting now.

What that argument doesn't hold up under is the assumption that the institution only has one lever to pull. It has two, a slow, expensive, visible one for permanent headcount, and a fast, cheap, invisible one for contract roles, and nothing about a funding shortfall requires it to use only the first. A budget squeeze doesn't need to touch a single unionized position if there's a large enough set of renewable contracts sitting next to it that can simply stop renewing instead. The public number this month, whatever it settles at, is a count of the cuts that were expensive enough to require announcing. It was never going to include the ones that weren't.

That's the part I don't think the coverage is built to catch, not because reporters are missing it but because there's nothing to file a story about. A press release needs an event, a specific date something happened, a specific number of people affected on that date. A contract quietly not renewed doesn't produce an event in that sense. It produces an absence, one person, then eventually enough people that a team looks different than it did a year earlier, with no single moment a journalist could point to and no union statement marking it. The workforce optimized this way doesn't show up in the same tally as the one being reported on right now, and that's not a gap in the reporting. It's the entire reason an institution facing a funding shortfall would want a workforce built this way in the first place, quietly, well before the shortfall ever showed up in a budget document.

I don't think the fix is making every contract as protected as a union position, since some of what makes contract work usable, for the institution and for the person taking it, depends on it not carrying that weight. But I'd want whoever's counting the cost of a funding cut to count both levers, not just the one that happens to come with a paper trail, because right now the count is only ever measuring the kind of cut that was expensive enough to be worth avoiding.