Recruitment SLAs: How to Define, Track and Hit Your Hiring Speed Targets

Why Recruitment Timelines Drift Without SLAs

Most recruitment problems are not sourcing problems. They are process problems. A recruiter screens ten strong CVs on Monday. By Thursday, only three hiring managers have responded. By the following Wednesday, two candidates have accepted offers elsewhere. The role is relisted and the cycle repeats.

This is not an exceptional scenario — it is the default state of recruitment without defined service level agreements. When no one has committed to a specific response time, every delay is justifiable. When an SLA exists, a 72-hour silence becomes a measurable breach that triggers an escalation.

A recruitment SLA is a formal internal commitment that specifies how long each stage of the hiring process should take, who is responsible for each transition, and what happens when a deadline is missed. It transforms recruiting from a loosely coordinated activity into a predictable business process — one where candidates are not left waiting indefinitely and where hiring managers are held to the same standard as recruiters.

How to Define Recruitment SLAs by Role Level

Not all roles move at the same speed, and a single universal SLA creates unrealistic expectations for specialist or executive hiring. The right approach is to segment your SLA framework by role complexity and set targets accordingly.

For entry-level and high-volume roles, the entire process from job posting to offer should be completable within 20 calendar days. The candidate pool is larger, role requirements are more standardised, and delays cost the business directly in operational throughput. For mid-level professional roles — the most common hiring scenario in scaling companies — a 30 to 45-day time-to-fill SLA is realistic and defensible. Senior and specialist roles should have 45 to 60-day targets that reflect longer notice periods, smaller candidate pools, and the need for deeper evaluation.

Within each of these overall targets, you need SLAs for every individual stage. A well-designed stage-level SLA framework looks like this:

• CV review and shortlisting: 48 hours from application receipt for standard roles; 72 hours for specialist roles
• First-stage interview scheduling: 5 business days from shortlisting
• Post-interview hiring manager feedback: 24 hours from interview completion
• Second-stage progression decision: 48 hours from first-stage feedback
• Final-stage interview scheduling: 5 business days from progression decision
• Offer approval and extension: 2 business days from final interview
• Offer negotiation and close: 5 business days from offer extension

These targets should be treated as starting points calibrated against your own historical data. If your ATS shows that hiring managers in the engineering department consistently take 4 days to review CVs, setting a 48-hour SLA immediately creates friction. Start with achievable targets, measure performance, and tighten over time as the process matures.

Setting SLAs That Hiring Managers Will Actually Respect

The most common failure point in recruitment SLA programmes is getting hiring manager buy-in. Recruiters and HR leaders design the framework, communicate it via email, and then watch as it is ignored the moment a manager becomes busy. Getting genuine commitment requires a different approach.

Involve hiring managers in the target-setting process. When managers help define the SLA targets, they feel ownership over them rather than resentment toward them. Present data from past hiring cycles: "Your last three hires took an average of 14 days from shortlist to first interview. Candidates 4 and 7 withdrew during that wait. If we set a 5-day target, we estimate we retain 70% more shortlisted candidates." Data-driven conversations land differently than policy declarations.

Establish escalation paths clearly before launching. The hiring manager needs to know that if they do not respond to a candidate shortlist within 48 hours, an automated reminder goes to them. At 72 hours, a notification goes to their direct manager. At 96 hours, the recruiter can formally flag the open role as "at risk." This is not punitive — it is process hygiene. Frame it that way.

How to Track Recruitment SLAs in an ATS

Spreadsheet-based SLA tracking is unsustainable. By the time a recruiter manually calculates how long each candidate has been in each stage, the data is stale and the breach has already caused damage. ATS-native SLA tracking is the only viable approach at any meaningful hiring volume.

An ATS that supports SLA management will timestamp every stage transition automatically. When a candidate is moved from "Applied" to "Shortlisted," the clock starts on the CV review SLA. When they are moved to "Interview Scheduled," the interview scheduling SLA closes and the next clock begins. Every movement through the pipeline generates a data point that feeds into SLA reporting without any manual entry.

The reports you need from your ATS to manage SLAs effectively are: average stage duration by pipeline stage; SLA breach rate by stage, department, and hiring manager; candidate withdrawal reasons correlated with stage duration; and time-to-fill trend over rolling 90-day periods. If your current ATS cannot produce these reports, you are operating blind.

What to Do When SLAs Are Consistently Breached

SLA breaches are data. They tell you precisely where the process is breaking down and give you the information needed to fix it. A recruiter who consistently breaches the CV review SLA may have too many open requisitions. A hiring manager who never meets the feedback deadline may not have been given a structured scorecard that makes feedback easy to provide. A department that always exceeds time-to-fill may have overly restrictive job requirements that need to be reviewed.

Run a monthly SLA review meeting with the recruitment team and relevant hiring manager stakeholders. Present the data without blame, identify the top three breach patterns, and agree on one change for each. Document the decision. Follow up the following month with before/after data. This creates a continuous improvement cycle that compounds over time — each quarter, the process gets incrementally faster and more reliable.

There are also external factors that cannot be controlled through process improvements. Some specialist roles in competitive markets will always breach standard time-to-fill SLAs because the candidate pool is simply too small. In these cases, adjust the SLA to reflect market reality rather than leaving the team permanently in breach of an unrealistic target. SLAs should be challenging but achievable.

Communicating SLAs to Candidates

Internal SLAs have a parallel opportunity: using them to set candidate expectations proactively. When a candidate submits their application, they deserve to know what happens next and when. An automated acknowledgement email that says "You will hear back from us within 5 business days regarding your application" is not just good practice — it is a recruitment SLA commitment made to the candidate.

Companies that communicate timelines to candidates see meaningfully higher candidate satisfaction scores and lower withdrawal rates. The expectation is set. The candidate is not refreshing their inbox hourly or accepting a competing offer out of uncertainty. If you then meet or beat that timeline, you have differentiated your employer brand in a concrete, experience-based way.

Your ATS can automate this communication entirely. Configure stage-specific email templates that trigger when a candidate is moved through the pipeline: "Your application has been reviewed and we would like to invite you to a first interview within the next 5 days." The candidate receives a commitment. The recruiter receives a self-imposed SLA. Both parties benefit.

Building a Continuous SLA Improvement Culture

The companies that execute recruitment most effectively treat hiring speed as a competitive advantage, not an administrative process. They review SLA data monthly, celebrate when targets are beaten, investigate when they are missed, and update targets annually based on what the data shows is achievable.

This culture does not emerge automatically. It requires a leader who cares about recruitment data, an ATS that makes the data accessible, and a team that understands why SLAs matter — not because HR mandated them, but because top candidates genuinely leave when the process is slow. When the team has seen a great candidate withdraw because feedback took 10 days, the motivation for SLA compliance becomes visceral and personal rather than abstract and policy-driven.

Start with one SLA for one role level. Measure it for 60 days. Share the data publicly within the recruitment team. Then expand. The compounding effect of process discipline applied consistently is one of the most reliable ways to improve overall talent acquisition quality over a 12-month period.