The Call-Out Criteria: Why Mature Teams Decide in Advance When to Ask for Help

In the UK uplands, a rescue rarely begins with a solitary hero striding into bad weather. It begins with a decision: someone recognises that the conditions, the time and the information now point towards calling for help. That decision is not improvised. It is shaped by agreed criteria, practised judgement and a clear understanding of who decides what. The drama, if there is any, comes later. The maturity comes first.

Leadership teams have much to learn from that sequence. In organisations, escalation is often treated as an admission of weakness: a sign that the team could not cope, that the plan was flawed or that confidence was misplaced. Yet the alternative—waiting for a heroic last-minute intervention—is rarely a mark of high performance. More often it is a symptom of a system that left judgement too late.

The romance of the late rescue

There is a persistent story in organisational life about the leader who steps in at the eleventh hour. The programme is slipping, the client is restless, the regulator has asked an awkward question, and a senior figure arrives to steady the room. The story is told as a success. In practice, it is usually a warning.

Late intervention is expensive. It compresses options, narrows the field of possible responses and places disproportionate weight on the judgement of one or two people. It also teaches the wider team an unhelpful lesson: that asking for help early is somehow less impressive than surviving a crisis narrowly. High-performing teams can be especially vulnerable to this mythology, because their competence makes it easier to assume that they should absorb pressure rather than surface it.

Mountain rescue offers a different model. The hero is not the individual who delays the call. The hero, if the word is needed at all, is the system that allows a difficult decision to be taken early, calmly and with the right people involved. Calling for help is not the opposite of competence. It is one of the ways competence is expressed.

What rescue teams understand about escalation

Mountain rescue teams work with a form of pre-agreed escalation that is both practical and disciplined. They do not wait for certainty. They look for signals: a group overdue, a change in weather, an injury, a route that no longer matches the plan. They work with thresholds: the point at which a concern becomes a call-out, the point at which mutual aid is requested, the point at which a wider search is initiated. And they name decision-makers in advance, including deputies, so that authority does not have to be negotiated under pressure.

The criteria are not a substitute for judgement. They are a way of focusing it. A trigger does not remove the need to think; it ensures that thinking happens before the situation becomes too urgent for it. Crucially, the criteria also distribute courage. It is easier to make a difficult call when the organisation has already agreed that the call is legitimate.

The escalation gap in UK leadership teams

In UK boardrooms and programme boards, escalation often depends on culture rather than criteria. A senior sponsor may be expected to intervene, but the moment of intervention is left vague. A risk may be discussed, but the threshold for treating it as a decision rather than a watching brief is unclear. A team may be encouraged to raise concerns, but the route from concern to action is ambiguous.

The result is a familiar pattern. Issues are monitored for too long. Updates become reassuring rather than informative. The people closest to the work assume that someone more senior must already know. The senior team assumes that silence means stability. By the time the escalation happens, the original problem has acquired a second problem: the loss of confidence that comes from having waited.

This is not usually a failure of intelligence or commitment. It is a failure of design. High-performing teams often prize autonomy, and rightly so. But autonomy without escalation criteria can become a form of isolation. The team mistakes self-sufficiency for judgement, and the organisation mistakes late visibility for good news.

A simple framework: signals, thresholds and named decision-makers

The first step is to identify the signals that matter. These should be few enough to remember and specific enough to act upon. They might include leading indicators that a programme is moving off track, capacity pressures that cannot be absorbed, external changes that alter the basis of a plan, or ethical and legal questions that require a wider view. The test is not whether a signal guarantees failure. The test is whether it warrants a conversation.

The second step is to set thresholds. Some can be numerical: a slippage of a defined duration, a cost variance beyond an agreed range, a service level sustained below target for a set period. Others will be qualitative: two of three named risks materialising, a key dependency failing to respond, a client or regulator expressing a concern that cannot be resolved at the current level. Thresholds should be reviewed, not treated as permanent furniture.

The third step is to name decision-makers. This sounds administrative, but it is deeply cultural. If everyone assumes that the chief executive or the programme sponsor will step in, no one is accountable for the moment of escalation. Naming a decision-maker, a deputy and an out-of-hours route turns escalation from a hopeful act into a reliable one. It also protects the named individual from becoming the bottleneck.

Designing triggers people will actually use

An escalation trigger is only useful if people are willing to pull it. That willingness depends on how the trigger is designed and how it is modelled. Teams should agree the criteria before pressure arrives, ideally when the plan is being formed rather than when it is already under strain. Near misses should be reviewed as carefully as failures. A concern raised early and resolved without drama is not a false alarm; it is evidence that the system is working.

Leaders have a particular responsibility here. If senior figures respond to early escalation with irritation, or treat it as evidence of weak delivery, the criteria will quickly become decorative. If they respond with curiosity and clear decision-making, the team learns that escalation is part of the work. The tone set at the top determines whether the trigger is seen as a lifeline or a career risk.

The courage to call it early

The mountain rescue principle is not really about mountains. It is about the discipline of deciding in advance what would cause a team to ask for help, and then making that decision easier to take. For UK leadership teams, the prize is not a more cautious culture. It is a more mature one: teams that can act with autonomy and still know when to widen the circle, leaders who are visible without being heroic, and organisations that treat early escalation as a sign of shared judgement rather than a failure of nerve.

The best rescue is often the one that begins before the crisis is fully formed. The same is true of strategy. A team that agrees its call-out criteria in advance is not planning to fail. It is planning to think clearly when clear thinking is hardest to find.