Raising a concern with your manager does not always resolve it. The manager may understand the problem but lack the authority to decide, the resources to act or the reach to coordinate another part of the organisation. You may still be responsible for work affected by the unresolved issue. In that position, moving it further can be a responsible step, but going straight to a manager's manager is not automatically the right one.
The useful decision is what the issue needs next. Advice may help you understand it. A colleague or manager may help it reach the right person. A decision may belong to a functional owner rather than someone higher in your reporting line. Formal escalation is appropriate when a material responsibility cannot be discharged through the current route. The aim is to get the issue to someone who can resolve or consciously decide it, while keeping the account of what has happened accurate and the working relationship as sound as circumstances allow.
Establish what remains unresolved
Before moving an issue beyond your manager, describe what is still open. Has the concern been heard but left without a decision? Is the work waiting on a resource your manager cannot allocate? Does an important risk or standard remain unaddressed? The answer determines whether you need more explanation, a different decision maker or a formal route for an unresolved responsibility.
Distinguish the substance from the discomfort of disagreement. A manager can choose an approach you would not have chosen without creating an escalation case. If the decision sits within their authority, the evidence has been considered and no material responsibility remains unresolved, going over their head may be an attempt to obtain a preferred answer through hierarchy. It can weaken trust without adding relevant information.
The opposite error is to treat the manager's awareness as closure. A material issue may still affect work you are accountable for even when the manager has listened sympathetically. Ask what action was agreed, who can authorise it and when the issue will be reviewed. If no one at the current level can make the necessary decision, the concern has not been resolved by the fact that it was discussed.
Keep a factual account of the problem and the route already tried. What evidence supports the concern? What is its possible consequence? What has your manager decided, deferred or said lies outside their remit? A concise account helps the next person understand the actual gap. It also guards against turning a complex issue into a complaint that your manager “did nothing” when they may have taken a meaningful but insufficient step.
Separate advice from a decision
Seeking another perspective is not necessarily escalation. You may ask a more experienced colleague how to interpret a requirement, handle a dependency or present evidence. That colleague can help you think more clearly without taking ownership of the issue or overruling your manager. Make the purpose of the conversation clear so an informal request for advice does not become an ambiguous attempt to recruit an ally.
You may instead need sponsorship. A manager or senior colleague who understands the concern can help it reach someone with authority or influence across functions. They might explain the dependency, support a request or bring the right people together. Sponsorship helps the issue travel; it does not automatically transfer the decision to the sponsor. Clarify who will ask whom, what decision is sought and who remains responsible for follow-up.
A higher-level decision is different again. If a resource allocation or organisational priority sits above your manager's authority, someone with that remit must decide whether and how to provide it. The person consulted is not merely advising you; they are being asked to accept, reject or redirect a material request. State the decision needed rather than asking a senior person vaguely to “look into” a problem.
Formal escalation may have its own established route for certain kinds of concern. Use the applicable arrangements rather than inventing a shortcut based on this article. The critical distinction is whether you are seeking understanding, help to reach a decision maker, an actual decision or a governed response to an unresolved issue. Confusing those purposes can leave accountability unclear even when many people have been copied into the conversation.
Find the authority or resource the issue needs
Moving upward in the reporting line can help when the missing authority sits there. It is less useful when the necessary capability belongs to another function. The right destination is the person or route able to provide the decision, resource, expertise or coordination the issue lacks. An organisation chart may show reporting relationships without showing every cross-functional decision right.
Consider a hypothetical technical employee whose team needs a specialist resource to complete a necessary review. The employee's manager agrees with the need but cannot allocate that resource, which belongs to another function. The employee could seek advice about how the review should be scoped. The manager could sponsor a request to the resource owner. If the resource cannot be provided, an authorised role may need to decide the priority or an alternative. Going to the manager's manager solely because that person is more senior might add a step without reaching the person who can act.
The example does not assume that every workplace divides authority the same way. In some organisations the manager's manager may indeed control the resource. In others, a functional leader, project owner or designated decision process is the appropriate route. Find out where the relevant decision right and information sit. If you cannot tell, asking your manager or a knowledgeable colleague about the route may be more productive than making an unsupported guess about seniority.
The escalation request should name the missing capability. “We need a decision on whether this review can be resourced by Friday” is more actionable than “someone senior needs to know”. If the gap concerns authority to accept a risk, say what risk and which decision is required. If the gap concerns information, identify the information source. Clear routing makes it possible for the recipient to act or to redirect the issue to the person who can.
Use the manager relationship where it can work
Your manager is usually the first useful route for an issue within your work. They may resolve it directly, supply context you lack or help reach another decision holder. When the relationship and the circumstances allow, explain what remains unresolved before taking it elsewhere. This gives the manager an opportunity to act and helps prevent an avoidable surprise.
You might agree on a joint next step. For example, the manager could introduce the resource request while you supply the technical evidence and explain the consequence of delay. That arrangement uses each person's role: you know the work and the manager may have access to a wider coordination channel. Clarify who owns the request, the expected response and what happens if the route does not produce a decision.
Using the manager relationship does not mean waiting indefinitely. If a material responsibility remains and a promised response does not arrive, return to the agreed timing and the consequence of further delay. A manager may be trying to help but still lack the ability to resolve the gap. At some point the issue needs a destination with the missing authority or resource. Repeatedly restating the concern at a level unable to act is not a substitute for escalation.
Nor is escalation a way to avoid a difficult ordinary conversation. If you have not explained the issue to your manager and doing so is safe and workable, begin there. A senior recipient cannot assess whether the current route has failed if the relevant discussion never took place. The exception is where that route is inappropriate for the nature or urgency of the concern, or would prevent it from being addressed through the applicable process.
Be transparent when it helps and careful when it does not
Transparency can protect a working relationship when an issue must move beyond the manager. Explaining that a particular decision or resource is needed elsewhere makes the step about resolution rather than status. Where feasible, tell the manager what you plan to raise, with whom and why. You can describe the unresolved gap accurately without asking for permission to discharge a responsibility that requires another route.
The explanation should be proportionate. “We still need a resource decision from the function that owns this work, so I will take the agreed evidence to its owner” is clearer than implying that the manager was ignored or incompetent. If the manager has helped, acknowledge that contribution. If they disagree about escalation, the record should still distinguish their position from the material issue that remains.
Transparency is conditional, not a universal ritual. In some circumstances telling the immediate manager in advance could defeat the purpose of an established confidential or independent route, or delay action on an urgent concern. Use the relevant organisational arrangements and seek appropriate advice where necessary. The principle is to be candid where candour supports responsible resolution, while avoiding disclosure that undermines the route the concern genuinely needs.
Avoid covert hierarchy shopping. Approaching several senior people privately until one agrees with you can blur who is deciding and what evidence they have seen. If you need another perspective, frame it as advice. If you need a decision, identify the accountable decision holder and present the same material facts, including relevant earlier responses. A transparent, accurate account gives the next person a fair basis for action.
Make the handoff capable of resolution
An issue can be passed upward and still remain unresolved. A message that only says you are worried may leave the recipient to discover the evidence, the previous discussion and the decision needed. A useful handoff explains the work affected, the material concern, what has already been tried, why the current level cannot close it and what decision or support is now requested.
Be precise about uncertainty. If the evidence establishes a gap but not its eventual consequence, say that. If there are competing options, explain their implications without pretending one is cost-free. The recipient needs enough information to decide or redirect responsibly; they do not need a long narrative of every frustrating exchange that preceded the escalation.
Agree who owns follow-up after the handoff. Has the recipient accepted the decision, asked for more information or passed it to a different authorised role? When will you know? A forwarded email or an acknowledged meeting is evidence that the issue was transmitted, not that it has been resolved. If the action taken does not address the material responsibility, make that gap visible through the appropriate route.
The outcome may not be the one you preferred. A decision maker may resolve the issue through a different option, accept a consequence within their authority or explain why the concern was based on incomplete information. Your role is to supply a truthful account and understand what decision has been made. If a material obligation still applies to you and remains unaddressed, do not let the appearance of escalation replace the further action the situation requires.
Escalation is responsible when it connects an unresolved material issue to a person or process able to decide or act. Start by defining what remains open. Decide whether you need advice, sponsorship, a higher-level decision or a formal route. Use your manager's help where it can work, be transparent where that supports the purpose and make the handoff decision-ready. The test is whether the responsibility can now be dealt with, not how high the issue has travelled.
