A client rang me on Tuesday about a contract hire that's been running smoothly for two years. Fifteen minutes into the call, it was clear he had no idea the ground was about to shift under it.
He runs IT for a mid-sized logistics firm in the Midlands. The contractor in question has been keeping a warehouse management system alive since before most people had heard of hybrid working. Good day rate, clean notice period, everybody happy.
What he hadn't clocked, because why would he, is that the engagement sits inside IR35 and runs through an umbrella company. And that combination is exactly where a rule change now working its way through Whitehall could cause real trouble.
Or, more accurately, it's where a rule change built for an entirely different problem could cause trouble by accident.
Nobody drafting this reform was thinking about a devops contractor in the Midlands.
What's actually changing
The government's zero-hours contract reform was built to stop the worst of gig-economy exploitation, guaranteed hours for people on unpredictable rotas, that kind of thing. Sensible enough on its own terms. But the current drafting doesn't cleanly separate a zero-hours retail shift from a fixed-term inside-IR35 engagement run through an umbrella company.
Eight industry bodies, among them the FCSA, REC and APSCo, wrote to the employment minister this month warning exactly that.
ContractorUK covered the letter on 14 September, and the argument is straightforward.
If an umbrella company inherits a duty to guarantee ongoing hours on an assignment that was only ever meant to run for a fixed project, something has to give. Either the client offers a permanent role it wasn't planning to offer, or the assignment gets shortened before the obligation can bite.
Neither outcome is great for an IT hiring manager who just wanted a devops lead for six months to get a migration over the line.
Why does this affect senior IT contracts specifically?
Because that's where the bulk of inside-IR35 engagement actually sits. Since the 2021 off-payroll reforms moved IR35 status decisions onto end clients, most senior contract and interim IT roles have quietly moved through umbrella arrangements rather than personal service companies. Devops leads, solution architects, interim CTOs brought in for a specific transformation, all of it.
It's the model that lets a business bring in scarce, expensive expertise for a defined piece of work without committing to a permanent head count. That's precisely the flexibility this reform risks eroding. Not because anyone in government intended it to, but because the rules weren't written with this corner of the labour market in mind.
But the effect on the ground would be the same either way. A hiring manager who currently has a straightforward choice between permanent and contract for a senior technical role could find that choice quietly narrowing over the next year, without anyone in his organisation ever deciding it should.
There's a timing problem underneath all of this too. The government's own agency-worker consultation, which closed back in June, still hasn't had its response published. So the zero-hours reform is moving ahead of the regulation it's meant to sit alongside.
One industry group put it as the cart going before the horse. Fair summary.
The part hiring managers usually miss
It's easy to assume this is a contractor problem, not a client one. It isn't. If your umbrella provider gets spooked by an obligation it can't realistically meet, the sensible commercial response is to tighten what it will accept, or push back on assignment length, or simply decline new engagements in the categories most at risk.
Or they raise their margin to cover the risk, which lands back on your day rate within a quarter or two. Either way, the bill for a rule aimed at zero-hours retail shifts ends up on an IT budget line nobody expected to move.
That's a hiring problem landing on your desk. Not theirs.
Worth adding some context, because it cuts against the instinct that all flexible work needs fixing by default. The government's own research, published in May 2026, found that 72% of people working in these more flexible arrangements said the setup actually suited how they wanted to work.
For a lot of senior IT contractors, that flexibility isn't a compromise. It's the whole point of going contract in the first place. A blunt rule change risks taking that choice away from people who never asked for it to be taken away.
What should IT leaders do about it now?
Start by working out which of your current contract engagements are actually inside IR35 and running through an umbrella company. A surprising number of hiring managers can't answer that with confidence when asked directly. Then have a proper conversation with whoever supplies that contractor about how exposed the arrangement is.
Treat it as an IR35 senior IT contractor compliance question now, while there's still time to plan, rather than a scramble once the regulations actually land.
- Map every live inside-IR35 engagement and who employs the contractor
- Ask your umbrella or agency partner how they'd respond if guaranteed-hours duties applied to that role
- Build a fallback plan, permanent conversion, a different engagement model, or an earlier natural end date, for the roles most exposed
None of that is complicated. It just needs doing before the rules change rather than after. Most businesses leave it far too late because nobody flags it as urgent until it already is, and by then the options have narrowed.
And worth saying plainly: this isn't a reason to panic and pull every contractor in-house tomorrow. It's a reason to know exactly where you stand, so the decision is yours to make rather than one that gets made for you by a nervous umbrella provider in six months.
This is the sort of thing our IT recruitment team ends up untangling fairly regularly. Partly because we sit across enough contract and permanent placements at once to see where the friction actually shows up first, often weeks before a client notices it themselves.
We're watching this consultation closely, and not just out of professional interest. A fair few of our own contractor relationships run through exactly this kind of umbrella arrangement, so we've got skin in this too.
If you've got a contract IT hire running right now and you're not entirely sure how exposed it is, that's worth a conversation before the regulations land rather than after. Send us the details of the role and we'll talk you through what we're seeing, no obligation attached.
We've also pulled together some broader hiring guides covering contract versus permanent engagement, if you want the wider picture before you pick up the phone.
