Somewhere around eighteen months into most jobs, there's a quiet moment where you realise you're doing a role nobody actually hired you for. You picked up the client onboarding calls because the person who used to run them left and nobody backfilled the post. You started drafting the quarterly deck because your manager was drowning and you were "just helping out." Eight months later, the deck is yours, the calls are yours, and your job title still says the same three words it said on day one. Nobody sat you down and expanded your role. It just grew, the way ivy grows over a wall — a bit at a time, until one day the whole thing looks different and you can't quite point to when it changed.
This is scope creep, and it's one of the least-discussed problems in British workplaces because it doesn't look like a problem. It looks like being helpful. It looks like being trusted. Managers rarely frame it as "I am now expecting you to do two jobs" — they frame it as a series of individually reasonable requests, each one small enough that saying no would seem petty. The trouble is that reasonable requests, stacked over a year, add up to an unreasonable job. And by the time you notice, you're the person everyone assumes will handle it, which makes the conversation about pulling it back feel far riskier than it actually is.
How to tell the difference between growth and creep
Not every addition to your job is scope creep. Genuine role growth — taking on more strategic work because you've earned it, moving from execution to decision-making — is something you generally want, and it's usually accompanied by a conversation, even an informal one, about where you're headed. Creep is different. It tends to arrive without a conversation, it tends to be lateral rather than upward (more admin, more firefighting, more coverage for gaps left by other people's departures), and it tends to sit invisibly on top of your existing workload rather than replacing anything.
The clearest diagnostic is this: pull up your original job description — most people still have the one from their offer letter or the internal posting saved somewhere — and count how many of your current weekly tasks aren't on it. If it's one or two, that's normal evolution. If it's a third of your week or more, you're not doing the job you were hired for anymore, and your employer is getting that extra third for free, because your pay review conversations are still anchored to the old description.
Why managers let it happen — and why it usually isn't malicious
It's worth saying plainly that most scope creep isn't a calculated attempt to extract free labour, even though it functions exactly like one. Managers are usually under their own pressure — a headcount freeze, a resignation nobody's replaced, a target that went up without the team growing to match it — and delegating quietly to whoever's competent and won't complain is the path of least resistance. You are, in that sense, a release valve for someone else's staffing problem. That doesn't make it fair, but it does change how you approach the conversation: this is rarely personal, and treating it as a systems problem rather than an accusation gets you further than treating it as a grievance.
There's a smaller number of cases where it is more deliberate — where a manager has learned that a particular person will absorb extra work without pushback, and keeps testing that boundary because nothing has stopped them yet. If that's your situation, the diagnosis matters less than the fix, which is the same either way: you need to make the informal arrangement visible and formal, because informal arrangements are the ones that never get compensated.
Building the case before you open your mouth
Walking into your manager's office and saying "I feel like I'm doing too much" is the fastest way to get a sympathetic nod and no actual change. Feelings are easy to acknowledge and easy to forget. Evidence is harder to wave away, and it's the only thing that survives past the meeting itself.
- List every recurring task you now own that wasn't part of your original role, with roughly how many hours a week each one takes.
- Note who used to own each task, if anyone did, and whether that role was ever backfilled.
- Pull two or three concrete outcomes you've delivered specifically in the added scope — a client retained, a deadline hit that would otherwise have slipped, a process you built that didn't exist before.
- Check what a role that actually covers this full scope pays elsewhere — Glassdoor and LinkedIn salary data are rough, but a recruiter you trust will give you a sharper number in a five-minute call, and that's worth doing before the conversation, not after.
That last point matters more than people expect. A manager who hears "I'm stretched" can offer sympathy. A manager who hears "the market rate for what I'm currently doing is roughly £6,000 above what I'm paid for what I was hired to do" has a number to respond to, and numbers get escalated to budget conversations in a way that feelings don't.
The conversation: three ways to frame it
You have three real options once the case is built, and which one you pick should depend on what you actually want out of the next twelve months, not just on getting the meeting over with.
Option one: ask for the title and pay to catch up
This is the right move if you like the expanded role and want to keep doing it — you're just doing it at the wrong price. Bring the evidence, name the gap between your current title and the work you're actually doing, and ask directly for a formal scope change with a corresponding pay adjustment. This is a stronger ask than a standard pay rise conversation because you're not asking for more money for the same job — you're pointing out that the job itself has already changed and the paperwork hasn't caught up. Many companies would rather formalise and pay for work already being done well than risk losing the person doing it and having to hire externally at a higher rate than they'd have paid to retain you.
Option two: hand pieces back
If the expanded scope isn't work you want long-term — it's just work nobody else picked up — this is often the better route, and it's the one people are most reluctant to take because handing work back feels like admitting failure. It isn't. Pick the two or three lowest-value additions (the ones costing you the most hours for the least visibility or skill development) and propose specifically who should own them instead, or propose that they go back to being unowned until the company decides to resource them properly. Vague "I can't keep doing all this" statements get absorbed and forgotten. Specific handbacks — "the weekly reconciliation report should sit with finance, not with me, because I don't have the systems access to do it properly anyway" — are much harder to wave off.
Option three: negotiate a timeline, not a permanent fix
Sometimes the honest answer is that the extra work is temporary — covering a maternity leave, bridging a hiring gap — and permanent restructuring isn't the right ask. In that case, the useful move is naming an end date and a compensation bridge: "I'll cover this through the end of Q3 while the role is backfilled, and I'd like a temporary allowance for the extra scope in the meantime." This works because it removes your manager's biggest incentive to let the informal arrangement drift indefinitely, which is exactly what happens when there's no deadline attached to "just for now."
None of these three options is universally right, and it's worth being honest with yourself about which situation you're actually in before you pick one — asking for a permanent pay bump on work that genuinely is short-term tends to backfire, just as accepting an open-ended "temporary" arrangement tends to become permanent by default.
What to do if the answer is no
Not every version of this conversation ends with a raise or a formal title change, and it's worth preparing for that honestly rather than assuming good evidence guarantees a good outcome. If your manager agrees the scope has grown but says there's genuinely no budget to reflect it — which does happen, particularly in the current climate for mid-sized UK employers — ask for something that doesn't cost money immediately: a written acknowledgement of the expanded scope, a commitment to revisit at the next formal pay review with that acknowledgement attached, or additional annual leave in lieu of a pay rise, which several employers will grant more readily than a salary increase because it doesn't touch the ongoing pay bill.
If the answer is a flat no with no acknowledgement at all — no written record, no promise to revisit, nothing — that's useful information in itself. It tells you the company either can't or won't formalise informal overwork, which means the next time it happens, it will happen again exactly the same way. At that point, the evidence you've already built for this conversation becomes the starting point for either a job search or a formal conversation with HR about job description accuracy, which in the UK carries more weight than it might seem — persistent, unaddressed mismatch between contracted duties and actual duties is something ACAS guidance explicitly treats as relevant to constructive dismissal claims in the most serious, prolonged cases, though that's a last resort, not a first move.
The mistake most people make: waiting for the annual review
The instinct to save this conversation for your scheduled annual or mid-year review is understandable and usually wrong. Annual reviews are backward-looking by design — they're built to assess what you did against what you were meant to do, and if what you were meant to do is quietly out of date, the review will keep grading you against the wrong baseline every single time. Raising a scope conversation as its own separate meeting, on its own timeline, signals that this is a structural issue worth structural attention — not a line item to be squeezed into fifteen minutes alongside eleven other topics.
Book the meeting specifically. Call it what it is in the invite — "role scope discussion" is fine, nobody needs euphemism here — and bring the evidence. The version of this conversation that happens on your terms, with your paperwork, at a time you chose, lands very differently from the version that gets squeezed into the last five minutes of someone else's agenda.