When to escalate to your manager is when role clarity, priorities, or authority are broken, not when you merely dislike a task. A classic case: a senior colleague keeps adding deliverables on top of your manager assigned work, sometimes even asking you to direct a peer. Escalate as a workload and ownership question. That protects you and gives your manager a problem they can actually solve.
Escalation is a clarity tool, not a snitch button
Managers need signal when work is arriving through unofficial channels, when capacity is blown, or when you are set up to fail. They do not need a character assassination of a senior peer.
The useful question is: what outcome do you want? More capacity, a written priority order, confirmation that peer delegation is in scope, or a stop to shadow management. Pick that outcome before you book the 1 on 1.
When it is time to escalate
- You already have a full load from your manager or project owner, and new work keeps arriving from someone else.
- You tried a capacity pushback and the requests continue or get louder.
- Someone asks you to assign or monitor work for a peer when you have no formal authority.
- Two sources of work conflict and nobody will name the priority.
- Risk, deadline, quality, or customer impact is rising because ownership is fuzzy.
- Your manager was out and returned to a silent pile of side assignments they never approved.
Authority without mandate is especially dangerous. If something goes wrong after you “told him to do it,” you may own blame for power you never had. That alone is enough reason to escalate early.
Try this before you escalate
Talk to the senior colleague first when it is safe:
- Name your current manager assigned priorities.
- Say you do not have capacity without deprioritizing something else.
- Offer to loop your manager so they can trade work explicitly.
- Ask them to send the request in writing with deadline and outcome.
Delegation and dumping are not the same. Delegation can be growth work, capacity sharing, or a task in your wheelhouse. Dumping is boring ownership that stays theirs while the risk quietly moves to you. Either way, volume plus unclear mandate belongs on your manager’s desk once you cannot resolve it peer to peer.
How to escalate without looking like a complaint
Frame curiosity and role design, not accusation. Assume it might be intentional and poorly communicated. If it is not supposed to happen, your manager can correct it. If it is supposed to happen, you get the mandate in the open.
A clean script for your next 1 on 1 with your manager:
- “While you were out / recently, Senior Colleague asked me to take A, B, and C on top of the work you assigned.”
- “I am happy to help if that is the intention. The volume is rising and I want to confirm the balance you want.”
- “They also asked me to delegate work to New Colleague. Is that appropriate for my role, or should that stay with them or with you?”
- “What should I prioritize this week if I cannot do both stacks?”
Another strong structure: update in two blocks. Block one is work assigned by your manager. Block two is work assigned by the other person, plus any ask to coordinate peers. Then ask whether block two is expected.
What managers hear when you escalate well
| Weak framing | Strong framing |
|---|---|
| They dump work on me and it is unfair | I have two sources of work and need a priority order |
| They are lazy and using me | Here is the extra load and the risk if I keep absorbing it |
| Make them stop | Is peer assigned work part of my role going forward? |
| I told the new hire what to do | I was asked to direct a peer without authority; please clarify |
When not to escalate yet
- One small ask you can finish without missing your manager’s priorities.
- Clear growth work that fits your role and timeline.
- You have not stated capacity to the requester once.
- You only want sympathy, not a decision.
Silence has a cost too. If you absorb everything to look easygoing, you teach the org that your calendar is the overflow buffer. Then escalation looks sudden when you finally break.
Manager side note
If you are the manager hearing this, do not force the IC to police the senior alone. Clarify who can assign work, reset the senior if needed, and put prioritization in writing. Use difficult conversation scripts when the senior is using informal power to reshuffle your team.
Bottom line
Escalate to your manager when unofficial work, conflicting priorities, or fake authority put delivery or your role at risk. Lead with curiosity, two work stacks, and a requested decision. That is not being a crybaby. That is how healthy teams keep ownership honest.
Frequently asked questions
When should you escalate to your manager?
Escalate when priorities conflict, someone assigns work outside your agreed role, you are asked to direct peers without authority, risk or quality is at stake, or pushback with the other person did not resolve capacity. Frame it as clarity and prioritization, not a character complaint.
Is it complaining to tell your manager a senior colleague dumps work on you?
It becomes complaining when you only vent about the person. It is professional escalation when you show your assigned work, the extra load, the authority gap, and ask what your manager wants you to prioritize.
Should you talk to the senior colleague before escalating?
Usually yes. Say you are at capacity on manager assigned work and need their request prioritized or looped in with your manager. If they keep assigning anyway, or ask you to manage peers without mandate, escalate.
How do you escalate without looking difficult?
Assume good intent. Present two work stacks, ask whether peer assigned work is expected, and request a priority order. Offer to help if that is the design. Managers trust people who seek norms, not people who only seek blame.
Related: how to prepare for a one on one with your manager, what to talk about in a 1 on 1 with your manager, difficult conversations scripts for managers.
Prefer prepared conversations over memory alone? Explore iSilta features or try the product demo.