Recruitment SLA Framework: Set Standards That Everyone Follows

The hiring manager sends you a message on a Thursday afternoon: "Why is this role still open after six weeks? We're losing candidates to competitors."

You pull the data. The recruiter sourced and shortlisted five qualified candidates within eight days of the intake meeting. Three of them were sent for review. The hiring manager took 12 days to provide feedback on the first batch. By the time he responded, two candidates had accepted offers elsewhere. The remaining candidate went to an interview that was rescheduled three times over nine days because no one on the panel could agree on a slot.

This is not a sourcing problem. It is not a talent shortage. It is an accountability gap — and it exists in almost every company that runs recruitment without a formal service level agreement.

A recruitment SLA defines what each side owes the other. It turns vague expectations into measurable commitments. When done correctly, it eliminates the finger-pointing that drags out time-to-hire and damages the candidate experience. When done poorly — or not at all — both sides operate on assumptions, and the candidates pay the price.

This guide walks through how to build a recruitment SLA framework that both sides actually follow. Not a template you download and forget, but a working agreement that changes how your team hires.

What is a recruitment SLA?

A recruitment SLA (service level agreement) is a formal, documented agreement between the talent acquisition function and the hiring managers it supports. It spells out specific commitments from both sides: what the recruiter will deliver, by when, and to what standard — and what the hiring manager must do in return to keep the process moving.

The concept borrows from IT service management, where SLAs have been standard practice for decades. In IT, an SLA might specify that a support ticket will receive an initial response within four hours and resolution within 24. In recruitment, the equivalent might be: qualified shortlist delivered within five business days of intake; interview feedback returned within 48 hours of the interview.

What separates a real SLA from an informal set of expectations is three things:

• It is written down. Not discussed in passing, not mentioned in a kickoff meeting. Documented, signed (or at least formally acknowledged), and accessible to both parties.
• It is bilateral. Both sides have obligations. If the SLA only contains recruiter commitments, it is a job description, not an agreement.
• It has consequences. When commitments are missed, something happens — a notification, a meeting, an escalation. Without enforcement, an SLA is a suggestion.

According to SHRM's recruitment management toolkit, organisations with formalised recruitment SLAs report 23% faster time-to-fill and significantly higher satisfaction scores from both recruiters and hiring managers. The mechanism is straightforward: when both sides know exactly what is expected, there are fewer delays caused by ambiguity.

Why most recruitment SLAs fail

Before building a framework, it is worth understanding why so many attempts at recruitment SLAs produce a document that nobody reads after the first week. The failure patterns are consistent.

1. Set unilaterally by HR. The most common failure mode. The talent acquisition team drafts the SLA, presents it to hiring managers, and asks them to "comply." The hiring managers did not participate in setting the targets, do not feel ownership over them, and quietly ignore them when their own priorities compete for time. An SLA that feels imposed will always be resented and eventually abandoned.

2. No accountability mechanism. The SLA says feedback is due within 48 hours. A hiring manager submits feedback on day seven. Nothing happens. No notification, no escalation, no conversation. If there is no difference between meeting the SLA and missing it, rational people will deprioritise it whenever something more urgent comes up — which is every day.

3. Unrealistic targets. Copying benchmarks from a LinkedIn report or a CIPD resourcing survey without adjusting for your company's reality is a recipe for failure. If your company has a three-round interview process and a compensation committee that meets biweekly, promising a 21-day time-to-fill is not ambitious — it is fiction. Unrealistic targets erode credibility and make people stop taking the SLA seriously.

4. No differentiation by role type. Treating every open position the same — a senior architect, a seasonal warehouse worker, a C-suite executive — with identical timelines and quality expectations guarantees that the SLA will fail for at least some categories. Different roles require different processes, and the SLA must reflect that.

5. No regular review. An SLA set in January and never revisited by March is a dead document. Markets shift, team capacity changes, business priorities evolve. An SLA that cannot adapt becomes irrelevant.

Building the SLA collaboratively

The single most important factor in SLA success is co-creation. Both parties — talent acquisition and the hiring managers — need to be in the room when the commitments are defined. Here is a practical process for getting there.

Step 1: Run an intake audit. Before writing anything, collect data on your current performance. How long does it actually take your team to produce a shortlist? How long do hiring managers actually take to return feedback? Recruitment metrics form the foundation of any SLA — you cannot set targets without knowing your baseline. Use your ATS data to calculate median values for each metric over the last two quarters.

Step 2: Hold a joint workshop. Bring together the head of talent acquisition and 3–5 hiring managers who represent different functions (engineering, sales, operations). Present the baseline data and ask: "Given our current capacity and these numbers, what targets would be ambitious but achievable?" This is where negotiation happens — and that negotiation is exactly what creates buy-in.

Step 3: Define commitments for both sides. For every recruiter commitment, there must be a corresponding hiring manager commitment. This is non-negotiable. If the recruiter promises a shortlist in five days, the hiring manager must commit to a thorough intake briefing upfront and timely feedback on candidates. A one-sided SLA is a mandate, not an agreement.

Step 4: Agree on measurement and reporting. Decide how compliance will be tracked (ideally through the ATS, not manual spreadsheets), how often reports will be shared, and who receives them. Treegarden's reporting dashboard can automatically track most SLA metrics based on candidate stage transitions and timestamps — removing the manual tracking burden that kills SLA adoption.

Step 5: Pilot before scaling. Start with two or three departments. Run the SLA for one quarter, collect feedback, adjust targets, and then roll out to the full organisation. Attempting to implement across all departments simultaneously increases the risk of failure because you will not have time to address the inevitable first-quarter issues.

Essential SLA metrics

Not every recruitment metric belongs in an SLA. The SLA should focus on metrics that are within someone's control, measurable through the ATS, and directly connected to hiring speed and quality. Here are the five that matter most.

Time-to-shortlist. The number of business days from the intake meeting (or requisition approval) to when the recruiter presents a qualified shortlist to the hiring manager. This is the primary measure of recruiter responsiveness. For standard roles, five business days is a common target. For niche or executive positions, 10–15 days may be more appropriate. This metric is distinct from time-to-hire, which measures the full process from end to end.

Feedback turnaround. The number of hours or business days a hiring manager has to provide structured feedback after reviewing a shortlist or conducting an interview. This is the single biggest source of delay in most recruitment processes. A 48-hour target for interview feedback and 72 hours for shortlist review is typical. Track this metric per hiring manager to identify chronic bottlenecks — a recruiter scorecard can make these patterns visible.

Interview scheduling speed. The number of business days from when a candidate is approved for interview to when the interview is scheduled (not conducted — scheduled). This metric captures coordination efficiency between the recruiter, the hiring manager, and the interview panel. Three business days is a reasonable target for most roles. Beyond that, candidates start accepting other offers.

Offer approval time. The number of business days from the hiring manager's verbal decision to extend an offer to the moment the formal offer letter is sent to the candidate. This captures internal bureaucracy: compensation reviews, legal sign-offs, budget approvals. If this consistently exceeds three days, the problem is usually process design, not individual performance.

Candidate communication frequency. The maximum number of business days that can pass without a candidate receiving an update on their status. Regardless of whether there is news, candidates should hear from the company at defined intervals. Five business days is the standard ceiling. This metric protects the employer brand and reduces candidate drop-off. Maintaining a regular cadence also supports better hiring manager collaboration because it forces status awareness on both sides.

Recruitment SLA template

The table below provides a starting framework. Adjust the targets based on your baseline data, company size, and industry. Every cell should be negotiated between HR and the hiring manager — not filled in by one side alone.

This template can be adapted and extended. Some organisations add rows for rejection notification speed (how quickly rejected candidates are informed), requisition accuracy (percentage of hires that match the original spec), or panel availability (percentage of scheduled interviews that proceed without rescheduling).

SLAs by role type

A single set of targets across all role types is one of the most common SLA design mistakes. Different roles have fundamentally different talent markets, interview processes, and decision-making structures. Your SLA framework needs role-type tiers.

Standard roles (individual contributors, mid-level professionals). These are the majority of open positions in most companies. The talent pool is reasonably deep, the interview process is typically two to three rounds, and the hiring manager has direct authority to make the offer decision. Targets: 5-day shortlist, 30-day time-to-fill, 48-hour feedback turnaround. These roles should also have the strictest enforcement — if the SLA cannot work here, it will not work anywhere.

Executive and senior leadership roles. These require longer timelines, more stakeholders, and often involve confidential searches. The shortlist phase may include active headhunting, not just responding to applications. Targets: 10–15 day shortlist, 60–90 day time-to-fill, 72-hour feedback turnaround (more stakeholders need to align). Escalation triggers should be calibrated higher — a 90-day fill for a VP role is normal, whereas it would be a crisis for a mid-level hire.

High-volume roles (seasonal, retail, entry-level, warehouse). Speed is the priority. The talent pool is large but perishable — candidates often accept the first offer they receive. Shortlists should be ready within 1–2 days. Time-to-fill targets of 14–21 days are appropriate. The interview process should be one round, and the hiring manager should be empowered to make an offer on the same day as the interview. SLA enforcement here is about speed above all else.

Niche and specialist roles (data scientists, security engineers, compliance officers). These roles have small talent pools and often require passive sourcing. The recruiter may need to approach 50–100 candidates to generate 3–5 interested ones. Shortlist targets of 10–15 days are realistic. Time-to-fill can extend to 45–75 days. The SLA should include a recruiter commitment to provide weekly sourcing progress reports, and a hiring manager commitment to flexibility on requirements if the market data shows the spec is unrealistic.

Establishing role-type tiers also improves recruiter productivity measurement. A recruiter filling ten high-volume roles in a month is not necessarily outperforming a colleague who filled two niche engineering positions — but without role-type differentiation, raw numbers would suggest otherwise.

Enforcement mechanisms that work

An SLA without enforcement is a wish list. But heavy-handed enforcement — public shaming, punitive measures, career consequences — creates resentment and game-playing. The goal is a graduated system that encourages compliance through visibility and early intervention, reserving harder measures for persistent non-compliance.

Tier 1: Automated notifications. The first line of enforcement should require zero human effort. When a metric approaches its target deadline, the ATS sends an automated reminder to the responsible party. "Interview feedback for [Candidate Name] is due in 12 hours." Most missed deadlines are caused by competing priorities, not deliberate avoidance. A timely nudge resolves the majority of cases.

Tier 2: Escalation to direct manager. If the target is missed by more than the defined buffer (e.g., 48 hours past deadline), an automatic notification goes to the responsible person's direct manager. This is not punitive — it is informational. The manager may not know that their direct report is sitting on candidate feedback, and bringing it to their attention is often enough to get it resolved.

Tier 3: Mandatory review meeting. When the same person misses the same SLA target two or more times within a quarter, a meeting is triggered between the recruiter, the hiring manager, and the TA lead. The purpose is diagnostic: Why is this happening? Is the target unrealistic? Is there a workload issue? Does the process need to change? This meeting should produce a documented action plan.

Tier 4: Executive escalation. Chronic non-compliance (an entire quarter of missed targets) is escalated to the VP or department head level and included in the quarterly business review. At this level, the conversation is about whether the hiring manager is prioritising recruitment appropriately and whether the TA team has the resources it needs. This should be rare — if you reach Tier 4 frequently, the SLA design itself is the problem.

Reporting cadence. Enforcement only works if compliance data is visible. Establish a regular reporting rhythm:

• Weekly: Automated email to each recruiter and hiring manager showing their personal compliance rates for the past 7 days.
• Monthly: Departmental compliance summary shared with department heads. Includes average response times, breach counts, and trends.
• Quarterly: Full SLA review meeting between TA leadership and business leadership. Reviews compliance, discusses adjustments, and sets targets for the next quarter.

Measuring SLA compliance

Compliance measurement needs to be specific enough to drive action but simple enough that people actually read the reports. Here is a practical measurement framework.

Overall SLA compliance rate. The percentage of SLA-tracked interactions that met the agreed target within the reporting period. Formula: (Number of on-time interactions / Total SLA-tracked interactions) × 100. A target of 85% overall compliance is realistic for the first year. Mature programmes typically operate at 90–95%.

Compliance by metric. Break down the overall rate by each SLA metric (time-to-shortlist, feedback turnaround, scheduling speed, etc.). This reveals which specific commitment is weakest. If feedback turnaround compliance is 60% while everything else is above 90%, you know exactly where to focus.

Compliance by stakeholder. Measure compliance rates per recruiter and per hiring manager. This is where accountability becomes personal. Share individual compliance rates in 1:1 meetings, not in public forums — the goal is improvement, not humiliation. However, aggregated department-level data can and should be shared broadly.

Trend analysis. A single month's compliance rate tells you very little. Track the trend over quarters. Is compliance improving, stable, or declining? A declining trend, even from a high baseline, signals that the SLA is losing relevance and needs a refresh.

Impact correlation. The ultimate validation of an SLA programme is its impact on outcomes. Correlate SLA compliance rates with time-to-hire, candidate drop-off rates, and offer acceptance rates. If high-compliance roles consistently fill faster and with better candidates, the SLA is working. If there is no correlation, the targets may be measuring the wrong things.

According to LinkedIn's Global Talent Trends report, companies with formalised recruitment processes (including SLAs) see 20% higher offer acceptance rates compared to those without. The data supports what common sense suggests: when the process moves predictably, candidates are more likely to accept.

Adjusting SLAs based on data

An SLA that never changes is an SLA that will eventually fail. Markets shift, company priorities change, team capacity fluctuates. The adjustment process matters as much as the initial setup.

When to tighten targets. If a metric consistently achieves 95%+ compliance for two consecutive quarters, the target may be too easy. Tighten it by 10–20%. For example, if the shortlist target is 5 days and recruiters are consistently delivering in 3, move the target to 4 days. The SLA should always feel slightly ambitious.

When to loosen targets. If compliance is consistently below 70% despite genuine effort, the target is probably unrealistic for your current capacity or market. This is not failure — it is calibration. Loosen the target, but document the reason and set a plan to eventually reach the original ambition (perhaps through additional headcount, better tools, or process changes).

When to add or remove metrics. After the first two quarters, you may discover that some metrics are not adding value. Perhaps interview scheduling speed is consistently met because your organisation uses shared calendars effectively — it does not need SLA oversight. Meanwhile, you may notice that a new bottleneck has emerged (e.g., background check turnaround) that was not in the original SLA. Add and remove metrics based on where the actual friction points are.

Seasonal adjustments. Some industries have predictable hiring surges. A retail company hiring for the holiday season should have different SLA targets in September–November than in February–April. Build seasonal variations into the SLA framework rather than maintaining a single set of year-round targets that are too tight during peak season and too loose during slow periods.

Market-driven adjustments. When the talent market shifts — a recession that increases the applicant pool, or a boom that makes candidates scarce — SLA targets should reflect reality. Use external benchmarks from SHRM research and your own sourcing data to calibrate. An SLA that ignores market conditions will either be too easy (wasting potential) or too hard (creating frustration).

Common mistakes when implementing recruitment SLAs

Even with a sound framework, implementation pitfalls can undermine the programme. These are the ones to watch for.

Making it too complicated. An SLA with 15 metrics, each with three sub-metrics, will overwhelm everyone involved. Start with 4–6 core metrics. You can always add more later. Complexity is the enemy of adoption.

Treating it as an HR project. If the SLA is perceived as something HR created for HR's benefit, hiring managers will treat it as optional. Frame it as a business initiative that benefits everyone: faster hiring for the business, less frustration for hiring managers, better candidate experience, and clearer expectations for recruiters.

Ignoring the recruiter side. SLAs that only hold hiring managers accountable while giving recruiters a free pass will not survive. Recruiters must also have measurable commitments. If the shortlist is late, the recruiter should face the same escalation process as a hiring manager who delays feedback.

Not connecting it to the ATS. Manual tracking kills SLAs. If someone has to maintain a spreadsheet to know whether targets are being met, it will stop being maintained within weeks. The SLA measurement must be embedded in your ATS workflow. Treegarden, for example, captures candidate stage transitions with timestamps, making compliance measurement automatic rather than manual.

Skipping the pilot. Rolling out an SLA across the entire organisation simultaneously is risky. Start with two or three departments that are willing participants, iterate based on what you learn, and then scale. The pilot departments also become internal advocates when the broader rollout begins.

Getting started: a 90-day implementation plan

If you do not currently have a recruitment SLA — or if the one you have is not working — here is a realistic timeline for building one that sticks.

Days 1–14: Data collection. Pull baseline metrics from your ATS for the last two quarters. Calculate median values for time-to-shortlist, feedback turnaround, scheduling speed, and offer approval time. If you do not have this data, that itself is the first problem to solve — you need an ATS that captures these timestamps. Recruitment SLA management starts with having the right data infrastructure.

Days 15–30: Co-creation workshop. Present the baseline data to hiring managers and jointly define targets for each metric and role type. Document the SLA with clear commitments for both sides. Get formal acknowledgment (an email confirmation is sufficient — you do not need legal signatures).

Days 31–60: Pilot launch. Activate the SLA in 2–3 pilot departments. Set up automated notifications for approaching and breached deadlines. Begin weekly compliance reporting. Hold a check-in at the 30-day mark to address early issues.

Days 61–90: Review and scale. Conduct the first formal SLA review with pilot departments. Adjust targets based on the data. Document lessons learned. Plan the rollout to remaining departments with a department-by-department schedule.

Frequently Asked Questions

What is a recruitment SLA?

A recruitment SLA (service level agreement) is a formal, written agreement between the HR or talent acquisition team and the hiring managers they support. It defines specific commitments from both sides: timelines for sourcing and shortlisting candidates, response windows for interview feedback, maximum days to schedule interviews, and communication cadences throughout the hiring process. Unlike informal expectations, a proper SLA includes measurable targets, escalation triggers, and regular review cycles.

What metrics should a recruitment SLA include?

A well-designed recruitment SLA should cover five core metrics: time-to-shortlist (days from intake meeting to presenting qualified candidates), feedback turnaround (hours or days a hiring manager has to provide interview feedback), interview scheduling speed (days from candidate availability to scheduled interview), offer approval time (days from verbal acceptance to formal offer letter), and candidate communication frequency (maximum days between candidate updates). Each metric should have a target value, a measurement method, and an escalation trigger when the target is missed.

Why do most recruitment SLAs fail?

Most recruitment SLAs fail for three reasons. First, they are set unilaterally by HR without input from hiring managers, creating targets that feel imposed rather than agreed upon. Second, there is no enforcement mechanism — when someone misses a deadline, nothing happens, so the SLA becomes a document that nobody references. Third, the targets are often unrealistic, copied from industry benchmarks without adjusting for the company's actual capacity, market conditions, or role complexity.

How should recruitment SLAs differ by role type?

SLAs must be calibrated to role type. Standard roles might target a 5-day time-to-shortlist and 30-day time-to-fill. Executive roles need 10–15 days for shortlisting and 60–90 days for filling. High-volume roles should have aggressive timelines: 2-day shortlists, 14-day fills. Niche technical roles require the most flexibility: 10-day shortlists, 45–75 day fills, and may need different sourcing commitments from the recruiter side.

Who should own the recruitment SLA process?

The recruitment SLA should be co-owned by the head of talent acquisition and the hiring manager's direct leadership — usually a VP or director level. Neither side should own it alone. The talent acquisition lead owns tracking and reporting. The business leader owns accountability for their managers' compliance. Both participate in quarterly reviews. This dual ownership prevents the SLA from being treated as an HR initiative that hiring managers can ignore.

How often should recruitment SLAs be reviewed?

Review SLAs quarterly at minimum. Monthly reviews are appropriate during the first two quarters after implementation, when targets may need rapid adjustment. Each review should examine compliance rates for both sides, identify metrics where targets were consistently missed, analyse whether missed targets were caused by unrealistic expectations or performance gaps, and adjust targets based on the data.

What happens when an SLA target is missed?

Effective SLAs include a tiered escalation path. A first breach triggers an automated notification to the person who missed the target and their manager. Repeated breaches (two or more within a quarter) trigger a mandatory review meeting. Chronic non-compliance (consistently missing targets for an entire quarter) is escalated to the VP level and included in the quarterly business review. The goal is corrective, not punitive.

Can an ATS help enforce recruitment SLAs?

Yes, an ATS is the most practical tool for enforcing recruitment SLAs because it captures the timestamps needed to measure compliance automatically. When a recruiter moves a candidate to the shortlist stage, the ATS records the date. When a hiring manager submits feedback, the timestamp is logged. Platforms like Treegarden also provide reporting dashboards that show SLA compliance rates by recruiter, by hiring manager, and by department — making compliance visible without manual tracking.