A regional service manager asks a director to approve an urgent contractor outside the agreed allocation. The director replies that the request looks reasonable. The manager believes she can proceed; finance believes the reply was advice pending confirmation of the cost. The contractor has not yet been booked, and the service commitment remains at risk.
The problem is the meaning of the handoff. The manager has raised a choice outside her ordinary remit, but the organisation has not established whether the receiving role accepted and decided it. The remaining work is also unclear: who confirms the price, who commits the resource, and who communicates the revised service position?
Escalation can strengthen accountability by taking a decision to the appropriate authority. It can blur accountability when a request, an acknowledgement, and an authorisation are treated as the same event. The remedy is an explicit account of responsibilities through the whole exchange, rather than a rule that the person escalating either retains everything or hands everything away.
Define What Accountability Requires in This Setting
In his conceptual framework for accountability, Mark Bovens describes an actor’s obligation to explain and justify conduct to a forum able to question, judge, and potentially impose consequences. The paper concerns public governance and offers a particular analytical definition. It does not prescribe a universal private-sector operating procedure.
The distinction is useful because accountability involves more than a name beside an outcome. The regional manager can explain the evidence supplied and actions taken. The director can explain a choice made within the retained mandate. Finance can explain the checks or commitments assigned to it.
Those responsibilities can coexist. The director’s involvement does not erase the manager’s obligation to provide accurate information or implement agreed actions. Equally, the manager should not be assessed as though she made a resource decision that the director retained.
Specify who is expected to answer for which conduct and decisions. A collective decision may be valid under a committee mandate, while individual participants still have defined duties. Accountability does not require making every other participant merely advisory in order to preserve a single person’s responsibility.
Make the Request Specific Enough to Accept
The manager should identify the choice requiring authority: approval to use a named contractor, within a stated cost and period, for a defined service gap. Include alternatives, relevant uncertainties, the consequence of waiting, and the time by which a decision is needed.
Distinguish that choice from a request for advice. The director may be able to help compare options without authorising expenditure. If another role holds the relevant mandate, the request needs to reach that role rather than accumulate supportive comments.
The manager also needs to state what she will continue doing. She might maintain the existing service plan, obtain a confirmed quotation, and prepare the customer update. Escalation of the exceptional resource does not require abandoning the work already inside her remit.
A useful request makes those boundaries visible. It gives the receiver enough information to say whether they can decide, need specific evidence, or must route the issue elsewhere. A general message that the situation is urgent leaves much more scope for incompatible assumptions.
Distinguish Receipt, Review, and Authorisation
Acknowledging an escalation establishes that it was received. It may also identify who will assess it and when. That is valuable, but it is narrower than permission to act.
A usable answer should say what has been decided and under which conditions. The director could authorise the contractor within an agreed limit once finance confirms the quotation. The reply should identify whether that condition is a factual check or a further judgement with its own approval right.
If the receiver declines the request, the operational consequence still needs attention. The existing service promise may no longer be feasible. The manager can explain the options, while the appropriate sponsor decides whether the commitment or resources change.
Silence should follow an established escalation procedure, not be privately interpreted as approval. If the receiving role cannot respond, the organisation needs an authorised route such as a deputy or a further decision point. The manager should know what operating position applies while waiting.
This is different from treating every delay as the receiver’s failure. Essential evidence may still be missing. The record should explain why the choice is pending and which role can resolve the missing condition.
Keep Relevant Evidence Available to the Person Deciding
The manager’s summary should retain the material conditions behind the request. A quoted price may cover only a limited period or exclude a capability the service requires. Omitting that qualification can make an apparently simple approval unsuitable for the actual work.
Provide supporting evidence through an accessible route and bring the relevant specialist into the discussion where necessary. The director needs enough understanding to make the retained choice; the manager need not relay every technical answer through several levels.
The Orange Book’s risk-management guidance addresses responsibilities, escalation, and decision-making as connected arrangements. Its public-sector context matters, but the practical question transfers: can the relevant authority obtain and use the information needed to address the issue?
A decision record should preserve the evidence and assumptions that mattered at the time. It should also distinguish a new fact from information that was available but not considered. That gives a later review a fairer basis than judging the original choice solely from its outcome.
Return the Decision to an Implementable Plan
Once the contractor is authorised, someone must confirm the arrangement, update the schedule, and communicate any changed service commitment. Record those actions and the people responsible. An approval that remains in a director’s inbox has not yet become delivery.
The manager should check that the authorisation fits the final proposal. If the price, scope, or timing changes materially, the decision may need to return. The boundary should be defined through the relevant mandate rather than left to a general instruction to use judgement.
State when the exception ends. Permission to use a contractor for one disruption does not automatically establish continuing authority for future work. If the situation persists, bring back a choice about ongoing capacity and expectations.
The article on growing escalation chains examines how isolated exceptions can become permanent routes. Clear scope and an explicit return to ordinary work reduce the chance of an accidental standing requirement.
Respond When New Information Changes the Approved Position
Suppose the contractor is authorised, but the manager then learns that the required capability will not be available for the full period. The original approval may no longer fit. The manager should identify the changed condition and obtain the relevant decision, rather than assume that earlier authorisation covers a materially different arrangement.
The receiver also needs a way to revise the answer. If the director withdraws funding or changes the permitted scope, that decision should reach the manager before the team relies on the earlier commitment. Responsibilities include communicating material changes in both directions.
Record what changed and which action remains valid meanwhile. The team may continue preparation while withholding an unapproved booking, or follow another authorised interim position. This keeps the handoff responsive to evidence without reopening every settled preference. It also prevents an old approval from becoming a substitute for judgement about the proposal the organisation is actually being asked to implement.
Review the Decisions and the Conduct Separately
If the service still misses its commitment, examine what each role did with the information and authority available. The manager may have escalated in time but supplied an incomplete quotation. The director may have delayed a retained choice. The eventual implementation may have encountered an unforeseeable constraint.
Several findings can be true together. A review should not use the existence of an escalation to absolve the requester of all duties, nor use the requester’s outcome ownership to exclude the retained decision from scrutiny.
Consequences should follow the organisation’s applicable process and the evidence. A learning review can identify a control or resource problem while a separate process addresses individual conduct where warranted. It is unhelpful to assume in advance that every failure reflects either a broken system or a negligent person.
The related distinction between authority and responsibility helps keep those questions specific. Shared outcomes require an account of the actual choices and commitments, rather than an imaginary role controlling every cause.
Make the Next Handoff Easier to Interpret
Use repeated cases to improve the normal arrangement. If managers regularly request the same contractor exception, the organisation may need a revised allocation, a clearer standard route, or a different service promise. The answer is not necessarily to remove all oversight or to retain every past approver.
Test whether people can describe what they would request, who could authorise it, and which duties remain with them. Ask the receiving roles the same questions. Differences reveal a boundary that needs clarification before the next urgent case.
Escalation supports accountability when it makes the retained decision visible and obtains a usable response. It undermines clarity when everyone can point to having sent or received a message while the actual commitment remains unsettled. Keeping the request, decision, implementation, and review distinct allows responsibility to remain specific throughout the handoff.





