Framework Summary

The Escalation Protocol Framework categorises escalation scenarios by severity and defines for each: the trigger condition, who is notified, who is responsible for resolution, the resolution SLA, and the consequence of SLA breach. The framework covers five escalation types: HM unresponsiveness, SLO breach, mandate collapse, client relationship deterioration, and recruiter incapacity. Defining escalation protocols in advance eliminates the delay and confusion that occurs when a crisis is escalated without a pre-agreed path — the most expensive operational failure mode in executive search.

Why Pre-Defined Escalation Paths Save Searches

When a mandate reaches a crisis point — a hiring manager has gone silent for a week, a shortlist has been rejected twice, or a candidate has withdrawn on the day of offer — the response time determines whether the mandate is recoverable. Organisations without pre-defined escalation paths spend 2–3 days identifying who should be contacted, what authority they have, and what they are expected to do. Organisations with the Escalation Protocol Framework act within hours — because the path is already defined.

"An escalation that reaches the right person in 4 hours recovers. An escalation that reaches the right person in 4 days does not. The protocol determines the response time. Define it before you need it."

Escalation Scenario Matrix

ScenarioTrigger ConditionEscalation PathResolution SLAConsequence of SLA Breach
HM UnresponsivenessNo response to 2 shortlist submissions or interview feedback requests within 96 hoursRecruiter → VP People → CEO sponsor24 hours from triggerMandate parked; client notified; search paused until HM re-engagement confirmed
SLO Breach — MandateMandate passes breach threshold with no recovery plan in placeRecruiter → TA Manager → VP People48 hours from breachFormal mandate review; resource reallocation; client communication
Candidate Withdrawal at OfferFinalist declines or withdraws after verbal acceptanceRecruiter → TA Manager → Client call same day4 hours notificationRecovery plan presented to client within 24 hours; backup candidate assessed
Mandate CollapseHealth Score below 15; all active candidates declined or withdrawnRecruiter → TA Manager → Client CEOSame dayFull mandate restart; root cause review; compensation and brief re-assessment
Recruiter IncapacityRecruiter illness, departure, or overload above critical threshold during active mandateTA Manager → replacement recruiter identifiedSame business dayClient notified; transition briefing completed within 24 hours

Frequently Asked Questions

Who has authority to escalate to the client CEO?

Only the TA Manager or VP People level escalates directly to the client CEO — never the recruiter directly without manager involvement. Recruiter-to-CEO escalations without manager awareness create misaligned expectations and damage the client relationship. The escalation protocol defines this boundary explicitly: the recruiter escalates internally first, the manager decides whether and how to involve the client.

What is the standard SLA for a mandate collapse escalation?

Same-day: the recruiter notifies the TA Manager within 2 hours of identifying the collapse. The TA Manager notifies the client contact within 4 hours. A recovery plan — including root cause assessment, restart timeline, and brief revision requirements — is presented to the client within 24 hours. A client who receives a same-day escalation with a clear recovery plan retains confidence in the firm. A client who discovers the collapse independently does not.

How does the Escalation Protocol connect to the Mandate Triage Framework?

The triage framework determines priority across multiple mandates. The escalation protocol determines the response path for a single mandate in crisis. A P1 mandate in the triage stack is the mandate most likely to require escalation — the protocols are complementary. When a P1 mandate escalates, triage typically moves all P3–P4 mandates to park to free capacity for the escalation resolution.