Recruiting SLA with hiring managers: a template both sides can keep
On this page
- What an SLA is for, and the time sink it targets
- What to include: commitments run both ways
- The SLA template
- Setting realistic feedback windows
- Setting windows per role type
- Escalation: what happens when the SLA is missed
- Getting hiring manager buy-in without it feeling punitive
- Reviewing and adjusting the SLA
- Common mistakes
- Questions people ask
A recruiting SLA with hiring managers is a short written agreement covering the response times and commitments both sides make to keep a hiring process moving: how fast the recruiter delivers candidates after intake, how fast the hiring manager gives feedback after an interview, and what happens when either side misses. Most delay in a hiring process is not recruiting effort or hiring manager indifference — it is the absence of a shared, explicit expectation for how fast "fast" is supposed to be.
This is a different document from an intake meeting. Intake meeting questions covers what to ask about one open role. An SLA covers the standing working rhythm between recruiting and a manager across every role, so those response-time expectations do not have to be renegotiated at the start of each new search.
What an SLA is for, and the time sink it targets
The single biggest recoverable time sink on most desks is not sourcing or screening — it is waiting on feedback after candidates have already been presented or interviewed. A candidate held in limbo for a week while a hiring manager "gets around to it" costs the search a strong candidate who accepts elsewhere, and costs the recruiter a week they cannot get back. An SLA exists to make the cost of that wait visible and to set an expectation before it happens, rather than raising it as a complaint after it already has.
What to include: commitments run both ways
An SLA that only lists what the hiring manager owes will be read as a scorecard aimed at them, and resisted accordingly. List recruiter commitments in the same document, with the same specificity.
| Recruiter commits to | Hiring manager commits to |
|---|---|
| Intake meeting scheduled within 2 business days of requisition approval | Attend intake with must-haves and comp range ready, not to be worked out live |
| First candidates submitted within an agreed number of business days | Review submitted candidates within a set window (below) |
| Interview logistics (scheduling, prep material) handled without chasing | Hold interview time on the calendar within an agreed window of a candidate being approved |
| Candidate kept informed of status at each stage | Feedback given within a set window of each interview (below) |
| Weekly or biweekly status update on open requisitions, unprompted | Flag changes to must-haves or comp as soon as they happen, not mid-search |
The SLA template
Recruiting SLA — [Recruiter/Team] and [Hiring Manager/Department]
Effective: [date] Review date: [date, 90 days out]
1. Intake
- Recruiter schedules intake within [2] business days of req approval.
- Manager attends with must-haves and comp range ready.
2. Candidate delivery
- Recruiter delivers first candidates within [X] business days of intake
(role-dependent; agree per role type, see table below).
- Recruiter provides a weekly status update on open requisitions.
3. Feedback
- Manager gives feedback within [48] hours of each interview.
- If feedback will be delayed, manager tells the recruiter why and gives
a new date within the same [48]-hour window.
4. Scheduling
- Manager holds a standing interview block of [X hours/week] where
possible, or responds to scheduling requests within [1] business day.
5. Escalation
- If a commitment on either side is missed twice in a row on the same
requisition, either party raises it directly, then to [manager's
manager / recruiting lead] if unresolved within [1] week.
6. Review
- Revisit this agreement at [90] days or at the manager's request.
Signed (or acknowledged): Recruiter ____ Hiring manager ____
Setting realistic feedback windows
A 24-hour feedback window sounds ideal and is often unrealistic for a manager running a full team alongside hiring. A window that gets kept consistently beats a shorter one that gets missed most of the time, because a consistently broken SLA trains everyone to ignore it. Start with a window the manager will actually hit under normal conditions — commonly 48 hours — and tighten it later once it is being met reliably, rather than starting aggressive and quietly loosening it after the first few misses.
Worked example: the cost of a slow feedback window. An invented search with 4 interview rounds, each candidate waiting an average of 6 days for feedback instead of an agreed 2-day window.
Extra wait per round: 6 − 2 = 4 days. Across 4 rounds in the search: 4 × 4 = 16 extra days added to total time-to-fill from this one cause alone.
If the industry-typical candidate patience for a multi-stage process is roughly two to three weeks before they accept another offer or lose interest, 16 extra days is close to the entire window — meaning slow feedback alone can be the difference between filling the role and losing the finalist to another company.
Setting windows per role type
A single delivery window across every requisition is the most common reason an SLA quietly stops being followed: a window realistic for a high-volume role is unrealistic for a specialized search, so the specialized searches start missing it constantly and the whole agreement loses credibility. Agree separate windows by role type up front.
| Role type | First candidates within | Feedback window |
|---|---|---|
| High-volume / entry-level | 2–3 business days | 24–48 hours |
| Mid-level individual contributor | 5–7 business days | 48 hours |
| Senior or specialized | 7–10 business days | 48–72 hours |
| Executive or highly niche | Agreed per search, often 10+ days | 72 hours, or a set check-in cadence instead of a per-interview window |
These are starting points to adjust with real data from your own searches, not fixed targets — a market with few qualified candidates for a "mid-level" role can behave like a senior search for scheduling purposes, regardless of the job title.
Escalation: what happens when the SLA is missed
Escalation should be a conversation, not a penalty. A missed commitment once is normal — a busy week, an emergency, a fair reason. A pattern of missed commitments on the same requisition is what escalation is for. Keep the first step low-key and direct: the recruiter raises it with the manager, plainly, the same week it happens ("we've missed the feedback window twice on this req — what's getting in the way, and how can I help"). Only move to a manager's manager or a recruiting lead if the pattern continues after that direct conversation, and frame it as a shared problem slowing down a hire the manager wants, not a complaint about the manager personally.
Getting hiring manager buy-in without it feeling punitive
- Lead with the cost they already feel. Most managers who are slow on feedback are not indifferent — they are busy, and do not see the downstream cost of the delay (candidates accepting elsewhere, searches restarting). Show that cost concretely, as in the worked example above, rather than presenting the SLA as a rule.
- Offer the recruiter side first. Show your own commitments before asking for theirs. An SLA that opens with what the recruiter owes reads as a partnership; one that opens with what the manager owes reads as an audit.
- Pilot it on one open requisition, not as a company-wide rollout, so the manager can see it work before being asked to commit to it for every future search.
- Make the review date real. A stated 90-day review, actually held, shows the SLA can be adjusted rather than being a permanent new obligation.
Reviewing and adjusting the SLA
At the review date, look at actual data, not impressions: how often was each commitment met, on which requisitions did it break down, and did time-to-fill or submittal-to-interview ratio move in the period. Adjust windows that were consistently missed rather than assuming they will improve with reminders alone — a target that is never met is not motivating anyone, it is just being ignored.
Keep the review light: a 20-minute conversation looking at three or four requisitions together is more useful than a formal report neither side reads closely. Ask the manager directly whether any window felt unreasonable in practice, and be willing to move it — an SLA that has been adjusted once based on real feedback is more likely to be respected than one imposed unchanged from the start and never revisited.
Common mistakes
| Mistake | Fix |
|---|---|
| Same SLA windows for every role type | Senior or niche searches need longer delivery windows than high-volume roles; set windows per role type, not one blanket number |
| SLA only lists the manager's obligations | List recruiter commitments with equal specificity |
| Escalation used as a first response to a single miss | Reserve escalation for a pattern, not a one-off |
| No review date set | Set one at creation, not "whenever it comes up" |
| Rolled out to every manager at once, unpiloted | Pilot with one or two managers, refine, then expand |
Questions people ask
Is a recruiting SLA a formal HR policy?
It can be, but it works better as a working agreement between recruiting and a specific manager or department, revisited as needed, rather than a rigid company-wide policy enforced the same way for every team.
What if a hiring manager refuses to agree to feedback timelines?
Start with a smaller, specific ask tied to one pain point they already feel, such as candidates going cold during a slow decision. Framing it around outcomes they care about gets further than presenting a document to sign.
Should the SLA include a hard penalty for missed deadlines?
Most working agreements do better with an escalation step (a check-in conversation) than a penalty, since the goal is faster hiring, not a compliance exercise that creates resentment.
How is this different from an intake meeting?
An intake meeting sets requirements for one requisition. An SLA sets the working rhythm — response times, feedback windows, escalation — that applies across every requisition you run with that manager, so it does not need to be renegotiated each time.