Escalation

What question does this solve?

Some problems cannot be solved by trying again or by the resource at hand. The business behaviour is undecided, two evaluations disagree, the next step would exceed the budget, or the work needs a competence nobody on it has. The question has to reach whoever can legitimately answer it, with enough context to decide, while the rest of the work carries on where it can.

Definition and role

Escalation routes a question to the competence or authority it requires when it exceeds the scope available. It is the counterpart of Retry: a retry is a bounded new attempt within the current conditions; escalation takes a question outside them.

Escalation is not limited to a management hierarchy. It can route a question to a specialist, to the business authority, or to whoever can review an economic commitment. The destination depends on the nature of the decision needed, and it can be a person or another system with a sufficient mandate. Escalation does not mean talking to a person. It means reaching sufficient competence and authority.

Why it matters for the hypothesis

A service that runs many small advances cannot afford to stop and ask a person every time something unexpected happens, nor can it afford systems that press on past the limits of their authority. Escalation to the right destination, including other systems where a mandate allows, is what lets autonomy stay within bounds without turning every exception into a human approval.

How it works

What triggers it

Escalation is needed when the current resource or mechanism cannot legitimately resolve a question. That can stem from:

• missing competence, when the work needs a capability the executor lacks;
• a conflict of interpretation, such as two evaluations of the same output that disagree after checking they examined the same output, criteria and context;
• a limit of authority, when the next step would change the scope, the budget, a criterion or an environment beyond the mandate.

It is distinct from waiting for a temporary condition or correcting an output under the criterion in force, which may be handled by a retry.

What to send

The routing should present the question, the context, the known alternatives and the effect of not deciding. Sending only raw records moves the whole effort of diagnosis to whoever receives the question. The destination has to match the need: an economic authority may decide budget without being able to clarify a technical rule; a specialist may propose an alternative without being able to authorize its purchase.

The answer must have an identifiable scope. An exceptional authorization for one action does not change the general policy automatically. If the decision requires a rule change, Governance has to recognize it and the affected work has to be informed.

Continuing while waiting

Escalating does not necessarily stop the whole demand. Independent authorized work may continue while a decision is awaited. Coordination has to bound that: moving ahead on parts that depend on the decision can cause rework or anticipate a choice nobody has made, and available capacity does not change that. The waiting should state who can act and what information is needed; when there is no reliable forecast of an answer, that uncertainty belongs in the estimate and the commitments. There may also be a limit to keeping the demand open under the same conditions; the decision to pause, renegotiate or close belongs to the relevant authorities, and escalation should make that routing possible without promising automatic resolution.

What escalation cannot do

Switching executor can help when the difficulty is capability or context. It does not replace a missing decision: sending the same ambiguity to several resources does not clarify who has authority to resolve it. And an additional evaluation can clarify behaviour without deciding who can authorize expense; a management decision does not change the result of a verification.

In the running example

At the barbershop, suppose the question is which business behaviour should apply, for example how to handle a service whose duration was never defined. A retry cannot settle that. The operation consults the relevant authority. A system with a mandate to choose within stated criteria can resolve it; without that scope, it routes the decision onward, possibly to the barbershop itself.

If a problem needs integration competence the executor lacks, another eligible system or professional can receive the context and take it over. If the barbershop later proposes adding advance payment, that is a question of scope, not an implementation detail: it cannot be absorbed because it is technically possible, and it goes to whoever can authorize a change to the commitment. When no continuation is justifiable under the available conditions, the operation can suspend or close according to the commitment, and the customer receives the situation and its relevant consequences without having to manage each internal attempt.

Boundaries and failure modes

Not every exception needs a person. Escalation must not become a disguised requirement for universal human approval. Where a mandate allows another system to decide, the question can stop there.

Escalation without context is a burden. Forwarding unorganized records, or escalating what the current resource could have handled, moves cost around without resolving anything.

Waiting is not free. Pending decisions hold work, and sometimes reserved capacity. Their effect on the estimate and the commitment should be visible, not absorbed silently.

Connected concepts

• Engine overview
• Previous: Retry, the response within the current conditions
• Next: Governance, which defines who can decide what
• Mandates, which determine when a system can resolve the question
• Glossary