Skill.re
Decision Rules: Explicit Criteria for Escalation
Overview
Lecture URL: https://skill.re/learn/recruiting/decision-rules-explicit-criteria-for-escalation.php
TRANSCRIPT: Decision Rules: Explicit Criteria for Escalation
Course: AI for Recruiters - Professional Credential
Module: Level 3: Independent Practice
Section: Chapter 16 -- Judgment Calibration And Escalation
Theme: judgment-calibration-and-escalation
Lecture: 16.2
Duration: 75 min
Format: Workshop + Case Studies
Audience: Experienced recruiters applying AI independently
Prerequisites: L2 Certification
What you will learn: Build explicit decision rules that clarify when to escalate decisions and when to proceed independently with confidence.
Decision rules are silent until you need them. You're evaluating a candidate. Something doesn't fit. Do you escalate or move forward? If you don't have clear rules, you either over-escalate (everything goes to a senior person) or under-escalate (you make decisions you shouldn't).
This session builds decision rules that clarify judgment. When should a decision be escalated? When can a recruiter or hiring manager decide independently?
- *Understanding Decision Authority**
Most organizations don't explicitly define who decides what. This creates ambiguity, slows hiring, and introduces inconsistency.
Better: clear rules. For different decision types, define:
- Who decides
- What information they need
- What triggers escalation
- What timeline applies
Example Rule Set:
- *Standard Rejection:** A recruiter can reject a candidate if they don't meet explicit role requirements (required technical skills, required experience level). No escalation needed.
- *Borderline Case:** A candidate is missing a key skill but has strong potential to learn it. Escalate to hiring manager for judgment call.
- *Offer Decision:** Up to hiring manager with budget authority. If offer exceeds budget parameters, escalate to director/VP.
- *Difficult Candidate:** If a candidate discloses information that raises fairness/legal concerns, escalate to HR before proceeding.
- *Rejected for Behavioral Concern:** If rejecting based on behavioral assessment or reference concerns, require two-person review before communication.
- *Building Your Rules**
Start by mapping current practice. For recent hires and rejections, who made the decision? Why? Was that the right decision point?
Identify decision types in your recruiting process:
- Initial screen pass/fail
- First interview pass/fail
- Technical screen pass/fail
- Debrief decision (hire/reject/hold)
- Offer negotiation
- Decisions involving concerns (fairness, legal, behavioral)
For each, document:
- Who has authority to decide
- What information they need
- What escalates the decision
- What timeline applies
- What documentation is required
Example for Debrief Decision:
- *Authority:** Hiring manager with recruiting team input.
- *Information Required:** Structured interview feedback from all panelists, candidate assessment results, reference check summary, any background check findings.
- *Escalation Triggers:** Disagreement among panelists (all-in vs. hesitant voices); behavioral or legal concerns; offer would exceed budget parameters; candidate is external referral from executive.
- *Timeline:** Debrief within 2 business days of final interview. If escalation needed, decision within 5 business days.
- *Documentation:** Debrief notes including rationale. If escalated, escalation notes.
- *The Escalation Criteria**
Good escalation criteria are specific, not vague. Vague escalation criteria:
- "If you're not sure, ask."
- "If it's a senior role, escalate."
- "If there's any concern, escalate."
These create over-escalation. Everything becomes uncertain. Nothing gets decided at normal levels.
Better criteria are specific:
- "If the candidate doesn't meet two or more explicit role requirements, escalate."
- "If roles are director-level or above, hiring VP has final authority."
- "If there's a fairness or legal concern, escalate to HR before any action."
- *Speed vs. Escalation**
More escalation = slower hiring. Clear rules enable speed.
If every offer goes to VP approval, you're slow. If only offers above 30% of target salary need approval, you're faster while maintaining control.
Design rules that maintain quality while enabling speed.
- *Common Decision Rules**
Here are templates:
- *Technical Screen Pass:** Candidate demonstrates required technical competencies in coding assessment or technical discussion.
- *Escalation:** If technical abilities are borderline (weak in one required area but strong in others), escalate to hiring manager.
- *Final Interview Decision:** Hiring manager decides based on team feedback. If team consensus is strong (all strong yes or all strong no), manager decides independently. If mixed feedback, escalate to director.
- *Offer Authority:** Hiring manager within approved salary band. Offers at band ceiling require director approval. Offers above band require VP approval.
- *Fairness-Related Decision:** Any decision involving concerns about fairness, bias, or legal compliance requires HR review before finalization.
- *Documenting Rules**
Write rules down. Share with your team. Post them in your hiring process documentation.
Most teams that build decision rules report that they:
- Make faster decisions
- Make more consistent decisions
- Have clearer accountability
- Catch fairness issues earlier
- Reduce second-guessing
ANTI-PATTERNS
- *Anti-Pattern 1: The Default Escalation**
- Description:* Every decision gets escalated to senior people, removing authority from those who should have it. *Why:* Risk-averse. Senior approval feels safer. *What goes wrong:* Slow hiring. Underutilized junior recruiters. VP spends time on decisions they shouldn't make. *How to avoid:* Define clear authority. Only escalate when criteria are met.
- *Anti-Pattern 2: The Vague Criteria**
- Description:* Escalation criteria like "if you're not sure" or "if it seems risky." *Why:* Specific criteria feel limiting. Vague criteria feel prudent. *What goes wrong:* Everything escalates. Nothing is decided. *How to avoid:* Make criteria specific. "If candidate is missing two required skills" is clear. "If something feels off" is not.
- *Anti-Pattern 3: The Inconsistent Authority**
- Description:* Sometimes a hiring manager decides independently. Sometimes they escalate. No clear pattern. *Why:* Inconsistent. Ad hoc. *What goes wrong:* Similar decisions get different outcomes. Unfairness emerges. *How to avoid:* Document rules. Apply consistently. Audit for consistency quarterly.
PRACTICE PROMPTS
- Current Practice Audit: Take five recent hiring decisions. For each, write: Who decided? Why? Was that the right person to decide?
- Decision Type Mapping: List all decision types in your recruiting process. For each, write: Who should decide? What information do they need? What escalates it?
- Escalation Criteria: Write specific escalation criteria for your most common decision types. Avoid vague language.
- Authority Documentation: Create a simple document mapping decisions to authority. Share with your team. Get feedback.
- Consistency Audit: Check recent hiring decisions. Were similar decisions made at similar authority levels? Identify inconsistencies.
KEY TAKEAWAYS
- Clear decision rules enable speed and consistency. Vague rules create bottlenecks and inconsistency.
- Escalation criteria should be specific, not vague. "Missing two required skills" is clearer than "if you're not sure."
- Authority should be defined by role and decision type. Recruiters decide standard screenings. Hiring managers decide debriefs. VPs decide above-budget offers.
- Fairness and legal concerns should always escalate to HR. Everything else can have clear authority assigned.
- Document rules and apply consistently. Consistency is a fairness requirement.
- Audit your decision-making regularly. Are similar decisions being made at similar authority levels?
GLOSSARY
- *Decision Rules:** Explicit, documented criteria for who decides what.
- *Escalation Criteria:** Specific conditions that trigger moving a decision to a higher authority level.
- *Authority Matrix:** Documentation of who has authority for different decision types.
- *Consistency:** Applying the same decision rules across candidates and time.
- *Standard Decision:** A decision that can be made independently within documented authority.
- *Escalation Event:** A situation meeting specific criteria that requires moving a decision to higher authority.
[SYNTHESIS AND APPLICATION]
Decision rules are the scaffolding of fair, efficient recruiting. When you're clear about who decides what, you make faster decisions, more consistent decisions, and catch fairness issues earlier.
The practice: map your decisions, define who should decide, document escalation criteria, apply consistently, audit for fairness.
[REFLECTION EXERCISE]
- What decision type creates the most uncertainty in your recruiting process?
- Are there decisions currently being escalated that could be made at lower authority levels?
- Do similar hiring decisions consistently get made at similar authority levels?
- What fairness concerns trigger escalation to HR?
- How do you audit decision consistency?
[CLOSING REMARKS]
Decision rules enable confident, fast, fair hiring.
AI for Recruiters Certification Program
Level 3: Independent Practice | Judgment Calibration And Escalation | Lecture 16.2
A SkillsClinic initiative.
Duration: ~75 minutes | Word Count: ~2200