The Mandate Triage Framework applies clinical triage logic to a portfolio of active executive searches: when recruiter capacity is finite and multiple mandates show degradation signals simultaneously, the framework defines a priority stack using three variables — mandate Health Score, days remaining to SLO, and client revenue impact. Critical mandates (below 25 Health Score, under 7 SLO days remaining) receive immediate attention. Stable mandates are parked to protect capacity for critical intervention. The framework prevents the equally-distributed attention pattern that leaves all mandates at medium risk rather than resolving the highest-risk mandate fully.
The Equal-Attention Trap
When multiple mandates show problems simultaneously, the instinctive response is to distribute attention equally — spending time on each one in turn. This produces a portfolio where every mandate moves slightly but none recovers fully. The Mandate Triage Framework prescribes the opposite: concentrate intervention capacity on the critical mandate until it stabilises, then move to the next. Partial intervention on five mandates recovers zero. Full intervention on one mandate recovers one — and then the recruiter moves to the next.
"Equal attention is the worst triage strategy. It produces partial interventions on every mandate and full recovery on none. Triage means making hard decisions about where to apply finite capacity."
Triage Priority Stack
| Priority | Health Score | SLO Days Remaining | Client Impact | Action Protocol |
|---|---|---|---|---|
| P1 — Critical | Below 25 | Under 7 days | Revenue-critical seat | Immediate: drop all P3 activity, activate recovery playbook, escalate to sponsor |
| P2 — Urgent | 25–49 | 7–14 days | Core leadership seat | Same-day: assign specific intervention actions, daily monitoring |
| P3 — Elevated | 50–64 | 15–21 days | Important but recoverable | This week: scheduled review, specific action plan |
| P4 — Monitor | 65–74 | 22–30 days | Standard progress | Weekly: Health Score monitoring, no active intervention |
| P5 — Stable | 75+ | 30+ days | On track | Routine: standard operating cadence |
Frequently Asked Questions
Who performs the triage classification?
In Majhi OS, triage classification is performed automatically by the system based on Health Score, SLO data, and client priority settings. The recruiting lead reviews the triage stack daily and can override classifications. In a manual implementation, the recruiting lead performs triage at the daily stand-up using the same three criteria.
What happens to P3–P5 mandates when a P1 crisis requires full attention?
P3 mandates are temporarily parked — outreach pauses, no new candidates are screened, the client is notified of a brief hold with an estimated return date. P4 and P5 mandates continue on their standard cadence with reduced recruiter touch. The park is never indefinite — maximum 72 hours before the P1 mandate must be stabilised or escalated to additional resource.
Can a client mandate ever be permanently deprioritised?
Yes, in one scenario: when the role is determined to be a ghost job, a wish-list hire with no approved budget, or a mandate where the hiring manager is not engaged. In these cases, the mandate is not triaged — it is exited, with a clear conversation to the client about the conditions required to restart. Running a low-priority, low-engagement mandate to its natural failure wastes recruiter capacity and produces a poor client experience.