The Mandate Health Monitoring Framework establishes a two-tier monitoring cadence: a daily automated signal check (response rate, stage velocity, Health Score update, SLO countdown) and a weekly structured human review (mandate status, recovery playbook status, next actions, client communication). The framework defines the owner, the input data, the decision criteria, and the escalation protocol for each tier — ensuring that every active mandate is monitored at the right frequency by the right person with the right decision framework.
The Monitoring Cadence Problem
Most search teams review mandate status weekly at best — often less. A mandate that enters signal degradation on Monday may not be reviewed until the following Monday, by which point the recovery window has narrowed significantly. The Mandate Health Monitoring Framework closes this gap by separating automated daily signal checks from human weekly reviews — giving the system 24-hour monitoring latency for automated signals and 7-day review latency only for the strategic judgment decisions that require human involvement.
"A mandate that degrades on Monday and is not reviewed until Friday has lost four days of recovery window. Automated daily monitoring doesn't replace human judgment — it ensures human judgment is applied before the window closes."
Monitoring Cadence Matrix
| Tier | Frequency | Monitored Signals | Owner | Decision Output | Escalation Trigger |
|---|---|---|---|---|---|
| Automated Daily | Every 24 hours | Health Score; response rate; stage velocity; SLO countdown; recruiter load | System | Alert if any metric crosses threshold; no action without human confirmation on Tier 2+ items | Any Tier 1 metric at critical threshold |
| Recruiter Daily | Every morning | Previous day actions; alert queue; candidate replies; scheduled interviews | Recruiter | Clear alert queue; confirm or dismiss recommendations; update stage timestamps | Any P1 or P2 mandate alert |
| Manager Weekly | Monday (or fixed day) | All active mandate Health Scores; SLO status; recovery playbook progress; recruiter load summary | TA Manager / VP People | Triage decisions; escalation approvals; resource reallocation | Any P1 mandate; repeated P2 mandate alerts |
| Client Weekly | Weekly (fixed day) | Mandate status vs. SLO; pipeline summary; next milestones; any delays flagged | Recruiter / TA Lead | Weekly status report sent to client; escalation flagged if SLO at risk | SLO breach pending; mandate at risk |
Frequently Asked Questions
What does a daily automated health check actually look like in practice?
In Majhi OS, the daily health check runs at 6:00 AM and produces a ranked mandate list sorted by Health Score (lowest first). Each mandate shows its current score, the primary contributing signals, any breached SLO stages, and the recommended action. The recruiter reviews this list first thing in the morning and clears the alert queue before beginning active work. Total time: 5–10 minutes.
How detailed is the weekly client status report?
The weekly status report covers: (1) current mandate stage and milestone status, (2) pipeline depth and candidate stage breakdown (without candidate names unless the client has signed an NDA covering candidates), (3) next scheduled milestone and timing, (4) any delays flagged with explanation and recovery plan, (5) one upcoming action item requiring client input if applicable. Total length: one page or under.
What happens if the TA Manager misses a weekly review?
The mandate monitoring continues — automated daily checks don't stop. The alert queue accumulates, and if any Tier 1 alerts remain unaddressed for 48 hours, the system escalates to the next level: VP People or the mandate sponsor. The framework is designed so that a single missed review does not cause mandate failure — but two consecutive missed reviews on a degrading mandate will trigger a formal escalation.