30-60-90 day plan for recruiters

A 30-60-90 day plan for a recruiter should set numbers a manager can pull from the ATS at each phase — req load, submittals, submittal-to-interview ratio — rather than "learn the process." This page is the goal template: what a new recruiter should own, produce and be measured against at each milestone. It is not the training process that gets them there; for the week-by-week onboarding structure (shadowing, reverse shadowing, first solo screens), see how to onboard a new recruiter, which this template is meant to be read alongside, not instead of.

For the general new-hire version of this template across roles, see the 30-60-90 day plan template for new hires.

Why this is a goals template, not a training curriculum

Recruiter onboarding usually fails for one of two reasons: no training process at all, or a detailed training process with no clear finish line, so nobody can say whether the new recruiter is actually ready to own a full desk. This template exists to fix the second problem. It assumes training is happening (via the onboarding guide linked above, or your own program) and answers a narrower question: what should this recruiter be able to point to, in numbers, at day 30, 60 and 90, regardless of how they got there.

The 30-60-90 day plan (agency recruiter)

30-60-90 day plan — [Recruiter name], [desk/specialty]
Manager: [name]        Start date: [date]        ATS: [name]

DAYS 1-30 — Learn the desk on a reduced req load
Owns:
- Carry 1-3 open reqs, chosen for manageable complexity, not the hardest searches on the desk
- Submit [N] candidates per week once sourcing is underway (target: [N] total by day 30)
- Log every submittal, client/hiring manager feedback and rejection reason in [ATS]
- Shadow or co-run [N] client or hiring manager intake calls
Produces by day 30:
- A written intake summary for each active req, in the recruiter's own words
- [N] submittals with a submittal-to-interview ratio the manager reviews weekly

DAYS 31-60 — Full req load, submittal quality under review
Owns:
- Carry a full req load ([N] reqs), including at least one harder search independently
- Hit a submittal-to-interview ratio at or near the desk average
- Run intake calls solo, with notes reviewed by the manager afterward
- Handle one candidate objection or counteroffer conversation independently
Produces by day 60:
- A submittal quality trend the manager can see in the ATS, not just a submittal count
- At least one candidate in a late interview stage

DAYS 61-90 — Own the desk, first placement in the pipeline or closed
Owns:
- Run the full desk process end to end: intake, sourcing, submittal, offer, close
- Hit the desk's standard req load and submittal targets without manager prompting
- Present a self-assessment of desk performance against the ATS numbers
Produces by day 90:
- A placement closed or in final offer stage
- A written 90-day self-assessment comparing this plan's targets to the ATS record

Review cadence: weekly pipeline review using the ATS report, not a subjective check-in;
formal reviews at day 30, 60 and 90 against the numbers above.

A filled example: an invented agency recruiter

The in-house recruiter variant

Swap the agency-specific metrics for the ones an internal talent acquisition team actually tracks. Requisitions owned replaces reqs on a desk; time-to-fill and time-to-first-submittal replace submittal-to-interview ratio as the speed metric; and hiring manager feedback, gathered informally at each phase, replaces the client relationship checkpoints. A day-90 bar for an in-house recruiter might read: owns [N] open requisitions independently, has closed or is in final offer stage on at least one, and has documented feedback from at least two hiring managers on their process, not just their placements. The structure of the plan — reduced load, full load, own the desk — carries over unchanged; only the numbers in the brackets change.

What the manager owes

How the review should read the numbers

Pull the ATS report before every check-in and look at submittal-to-interview ratio and time metrics as a trend, not a single data point, since a slow week early on is normal variance. What matters more than any single number is direction: a recruiter whose submittal-to-interview ratio is improving week over week is on a good trajectory even if the absolute number still lags the desk average at day 60. A ratio that is flat or worsening by day 60, even at an acceptable submittal volume, is worth a direct conversation before day 90 rather than after.

Adapting the plan by desk and specialty

• Contingency desk with fast-moving roles: shorten the reduced-load window; a recruiter can usually take on a full req load by day 30 if the roles are high-volume and low-complexity, and holding them back longer just slows the team down.
• Retained or executive search: extend every phase, since a single search can run the full 90 days on its own. The day-90 bar shifts from "placement in pipeline" to "search progressing through defined stages with the client informed at each one."
• Internal mobility or contract staffing desks: add a specific milestone around understanding the client's or business unit's approval chain, since delays there often look like a recruiter problem when they are really a process one.
• Recruiter moving from agency to in-house, or the reverse: do not assume sourcing and screening skills transfer without adjustment; the stakeholder relationships, the pace, and what "done" looks like for a req are different enough to warrant treating this closer to day one than a lateral move.

Where this plan connects to the interview itself

A recruiter's numbers can look fine at day 60 while the underlying interviews are weak — vague notes, feedback that arrives days later, hiring managers who cannot remember why they passed on a candidate. If submittal-to-interview ratio is healthy but interview-to-offer conversion is not, look at what happens on the call itself before assuming the recruiter is sourcing the wrong candidates. Some new recruiters run their own candidate screens with Interview Signal so they have a transcript and scorecard to compare against what the hiring manager remembers, which is a faster way to tell a sourcing problem from an interviewing one during the first 90 days.

Common mistakes with this plan

The most common mistake is measuring only submittal count in the first 30 days, which rewards a recruiter for submitting more candidates rather than better ones. Pair every volume target above with a quality check (submittal-to-interview ratio, hiring manager feedback) from day one, so a new recruiter never learns that quantity alone is what gets praised. A second mistake is loading a full req list on day one because the desk is short-staffed; a new recruiter spread across five reqs from the start builds a shallow, rushed process on all of them instead of a clean one on a couple, and that habit is hard to unlearn once the full req load actually does show up at day 60.

A third mistake is skipping the written intake summary because the recruiter "already knows what the hiring manager wants" after a quick call. Write it down anyway in the first 30 days, even when it feels redundant, because a written summary is the only artifact a manager can check against the actual submittals later. Without it, a mismatch between what was submitted and what the hiring manager meant gets blamed on the recruiter's judgment when it was really a communication gap from the intake call that nobody wrote down at the time.

A fourth mistake, more common on desks under revenue pressure, is measuring a new recruiter against a tenured recruiter's full numbers from day one. The ramp in this plan exists precisely because a reduced load early on produces a stronger full-load recruiter later; comparing a 30-day recruiter's submittal count directly against a two-year veteran's tells a manager nothing useful and discourages the new hire from building the habits the reduced load was meant to teach.