Your best candidates ghost you because nobody moves them through the pipeline, and your hiring managers don't know why.
Hiring pipelines don't stall because of malice. They stall because nobody has a system that says "this candidate has been in phone screen for 8 days, and your SLA is 5." By the time a recruiter notices, the candidate has already accepted another offer. Here's how to build an AI-driven SLA enforcement layer that works like a traffic cop for your pipeline: **The core loop:** Every morning, your system checks every candidate in every stage. If they've exceeded the stage duration limit (phone screen: 5 days, technical: 7 days, final round: 3 days—you set these), the system triggers a reminder to the assigned recruiter. If a candidate hits day 10 in phone screen with no movement, the system escalates to the hiring manager with a one-line summary: "Sarah Chen, phone screen, 10 days, no update." **Why this matters:** Candidates don't care about your process. They care about speed and respect. A 2-week hiring cycle with daily touchpoints beats a 3-week cycle with radio silence. SLA enforcement is how you stay competitive for talent. **The workflow in practice:** - Trigger: Daily at 8am, scan all open requisitions - Check: Compare candidate stage duration against your SLA matrix - Action 1 (Day 5): Slack reminder to recruiter: "Move or close Sarah Chen in phone screen by EOD" - Action 2 (Day 8): Email to hiring manager: "Sarah Chen stalled 3 days past SLA. Approve next step or close." - Action 3 (Day 10+): Log breach to a metrics dashboard; flag for post-mortem **The approval gates that matter:** A hiring manager should approve any candidate who gets escalated past SLA. They either move forward, reject, or explicitly extend the timeline (with a reason). This creates accountability and surfaces real bottlenecks—"We're waiting on legal review"—instead of letting them hide. **What breaks:** Recruiters ignore reminders if they're too frequent or too vague. Hiring managers get alert fatigue if every candidate triggers an escalation. Your SLA matrix is wrong if it doesn't account for role complexity (executive search ≠ entry-level). Candidates who are in "hold" status get flagged as stalled when they shouldn't be. And if you don't log breaches, you'll never know whether your hiring process actually improved. **The output:** A weekly SLA breach report showing which stages leak candidates, which hiring managers are slowest to decide, and which recruiters need help. This is your roadmap to faster hiring.
Trigger: Daily at 8am UTC: scan all candidates in active pipeline stages. Compare stage entry date to today's date. If duration exceeds SLA threshold for that stage, fire reminder.
Pull all candidates currently in active pipeline stages from your ATS (Workday, Greenhouse, Lever, etc.). Include stage name, entry date, assigned owner, and candidate contact info. Filter out completed hires and rejected candidates.
For each candidate, compute the number of days elapsed since entering the current stage. Compare against the SLA threshold defined for that stage (e.g., 'Phone Screen' SLA = 3 days).
Flag candidates as 'At Risk' (80% of SLA threshold) or 'Breached' (exceeded SLA). Example: if Phone Screen SLA is 3 days, flag at 2.4 days and escalate at 3+ days. Segment by severity.
Email the assigned interviewer or hiring manager when a candidate hits 'At Risk' status. Include candidate name, stage, days elapsed, SLA deadline, and a direct link to next action (schedule interview, send feedback, move to next stage).
If candidate remains in stage beyond SLA threshold, send escalation email to hiring manager and recruiter lead. Include SLA breach details, candidate risk of disengagement, and request for status update within 24 hours.
Record each SLA breach in a centralized log (Google Sheet, Airtable, or ATS custom field). Include candidate name, stage, days overdue, owner, and reason (if available). Use for weekly talent ops reviews.
Weekly, talent ops manager reviews SLA breach log. Identify patterns (e.g., 'Technical Interview' consistently breaches, specific hiring managers slow to schedule). Document blockers and recommend process changes.
If data shows SLAs are unrealistic for certain stages or candidate types, propose threshold adjustments to recruiting leadership. Approve and update automation rules.
1. Define your SLA matrix: list each pipeline stage (phone screen, technical, final round, etc.) and max duration in days. 2. Connect your ATS (Workable, Lever, Greenhouse, etc.) via API or webhook. 3. Set up Slack channel for recruiter reminders and email distribution for hiring manager escalations. 4. Create a Google Sheet or Airtable as your breach log—columns: candidate name, stage, days overdue, assigned recruiter, assigned hiring manager, action taken, date resolved. 5. Test with 3-5 candidates already in pipeline before going live. 6. Run a weekly sync with recruiting leadership to review breaches and adjust SLAs if needed.