Contractor survival series
It creeps up on you.
You're brought in to do one role; let's say project management. But there's no business analyst, so you start writing the requirements. There's no QA, so you start managing the testing. There's no technical architect, so you find yourself trying to hold a shape the build never had. None of this was in the brief. It accumulated, one reasonable-seeming step at a time, until you looked up and realised you were doing the work of three people and being paid for one.
And here's the part that keeps you doing it: it feels like the professional thing. The client needs it. The deadline's real. You're capable, so you absorb it. Evenings, then weekends, quietly subsidising roles the organisation chose not to hire.
If this is you right now, the first thing worth saying is: it's not a failing on your part. It's a structural problem you've been handed, and recognising that is the whole game.
How the squeeze actually works
Organisations that run this way usually aren't doing it maliciously. They've sold something complex, they're under-resourced to deliver it, and the gap has to go somewhere. The contractor is the most elastic thing in the system: no notice period to manage, no HR process, no permanent headcount on the books. So the gap flows to you.
The mechanism is almost always the same. The foundational roles that make complex delivery possible (analysis, architecture, testing) are the expensive, unglamorous ones, and they're the first to be cut or never hired. The work those roles do doesn't disappear, though. It just lands, unannounced, on whoever's closest and most competent. That's you.
And because it arrives gradually, there's never a single moment where you can point and say "that's not my job." Each individual ask is small. The cumulative load is enormous.
Why "just absorbing it" makes it worse
The instinct, especially for a contractor who wants the renewal and the reference, is to absorb the gap quietly and overdeliver. It feels safe. It's the opposite.
When you silently do three jobs, you achieve two things, both bad. You make the structural problem invisible, because the work is getting done, so from the outside nothing looks broken. And you set the expectation that this is the normal level of output, which means the moment you stop, you look like the problem, not the missing roles. You've quietly become load-bearing for a structure that was never sound, and the day you step back is the day it visibly cracks, with your name on the crack.
The unpaid evenings don't buy you goodwill. They buy you a higher baseline you're then trapped at.
Holding the line without torching the contract
The move isn't to down tools or make a speech. It's quieter and firmer than that.
Make the missing work visible rather than absorbing it. When a task lands that belongs to a role that doesn't exist, name it as such: calmly, factually, in writing. "This is the analysis work that would normally sit with a BA; I can cover it, but it's not PM scope and it has a time cost — here's what it pushes." You're not refusing. You're making the invisible visible and letting the people who own the budget make an informed decision.
Then hold the people who do have roles to them. If there's a head of delivery, delivery problems are theirs to lead on, not yours to silently solve. Forcing a role to actually do its job isn't aggression. It's accuracy.
And document it. Not to build a case for war, but to keep an honest record of what was scope, what wasn't, what you flagged, and what happened. A calm paper trail isn't paranoia; it's the thing that protects your reputation when the structure finally strains and someone goes looking for somewhere to put the blame. (Keeping that record is its own discipline, and it's the difference between being remembered as the person who delivered against the odds and the person who was conveniently nearby when it went wrong.)
The reframe that changes everything
You are not responsible for fixing an organisation's decision not to resource its own work.
You're responsible for doing your role well, being honest about where the gaps are, and protecting your own sustainability and reputation in the process. That's it. The competence that makes you good at the job is the same competence that gets exploited when you let it quietly cover for missing infrastructure. So the discipline is to deploy it visibly, on your actual scope, and to name the rest rather than swallow it.
The contractors who last aren't the ones who absorbed the most. They're the ones who stayed clear about what was theirs to carry, and walked away with their reputation, their rate, and their evenings intact.
I'm Steve. I spent fifteen years contracting before building ka-do, a task manager for people who run their own working lives. If you want the practical side of staying on top of contract work, I've written about that too.