Learn › Recruiting unit economics
The 30-minute recruiter week time audit — where the hours actually go
Most TA leaders and recruiting managers have a working estimate of how their recruiters' weeks break down: maybe 40 percent on sourcing and list-building, 30 percent in candidate meetings, the rest split across pipeline management, admin, and client work. The estimate is almost always wrong in the same direction, and the gap matters. This is the 30-minute audit method that lets you find the real number, what to do with the answer, and why it tells you which lever to pull next.
Walk back through two weeks of a recruiter's calendar in 30-minute granularity. Don't ask the recruiter to log forward; that produces an estimate, and the estimate is the thing you're trying to correct. Bucket each block against the artifact it produced: candidate list, meeting, write-up, client conversation, admin. The audit takes about 30 minutes per recruiter. The pattern is consistent: teams guess list-building takes 40 to 50 percent of the week; audits land at 60 to 70. Recovering 20 to 30 percent of that budget through AI sourcing is equivalent to adding 0.2 to 0.3 of a new recruiter at zero headcount cost. That math is the entire case.
Why the working estimate is consistently wrong
Recruiters are not bad at estimating their own time. They're estimating a different thing than what's actually happening. When a recruiter says "I spend about 40 percent of my week on sourcing," they're describing the deliberate, named blocks of time on the calendar with "sourcing" written across them — Tuesday morning's sourcing block, the Wednesday afternoon list session. Those blocks exist and add up to roughly 40 percent.
What the estimate misses is the unscheduled list-building. The fifteen minutes between a meeting and a debrief that go to "let me check if anyone else fits." The half-hour before a client call when the recruiter is "just looking at a few more profiles." The Friday-afternoon stretch where the calendar shows nothing scheduled and the recruiter is working on a list nobody asked them to make. None of this shows up as a named block. All of it adds up.
When you walk back through the calendar with 30-minute granularity and ask "what did this block produce" — not "what was the recruiter doing," but what artifact emerged — the unscheduled hours surface. Most of them turn out to have produced candidate names. The 40 percent estimate moves to a measured 60 to 70 percent. That gap is the audit's whole point.
How to run the audit, in concrete steps
This is meant to be runnable today, not a methodology consultancy engagement. The minimum viable version is two weeks of calendar data per recruiter and 30 minutes of an auditor's attention.
-
Pick two recent, representative weeks.
Not a vacation-affected week, not the week of a big client kickoff. A normal pair of weeks with the usual mix of open reqs and pipeline candidates. The audit needs enough range that the unscheduled time shows its pattern.
-
Pull the recruiter's calendar at 30-minute granularity.
Anything finer is overkill; anything coarser misses the small unscheduled blocks. Most calendar tools export in 30-minute increments natively. The cleanest source is the recruiter's primary work calendar including the meetings, blocks, and gaps; supplement with the ATS or sourcing tool's activity log if it timestamps candidate-list builds or scout-mail sends.
-
Bucket every block against the artifact it produced.
Six buckets are usually enough: list-building (candidates added to a list, scout mails drafted, sourcing tool sessions), candidate meeting (the meeting itself, prep, write-up), pipeline management (debriefs, second-round prep, scheduling, offer support), client conversation (intake calls, debriefs, business development), admin (CRM updates, internal reporting, expense), and unknown (the recruiter doesn't remember, no artifact found). Be especially careful with the unknown bucket — it usually maps to list-building once you check the timestamp of the next candidate list that appeared.
-
Sum the buckets and compare to the recruiter's pre-audit estimate.
This is the diagnostic moment. If the recruiter estimated list-building at 40 percent and the audit produces 65 percent, the gap is real, and it's the largest gap you'll find in the audit. Share the numbers with the recruiter; the conversation that follows is usually the productive one.
The typical pattern, in numbers
Across the agencies and in-house teams we've worked with on this audit, the distribution lands in a recognizable shape. The exact numbers vary by team and season; the rank order doesn't.
| Bucket | Recruiter's estimate | Audit result |
|---|---|---|
| List-building & sourcing | 40–50% | 60–70% |
| Candidate meetings (incl. prep & write-up) | 25–30% | 12–18% |
| Pipeline management | 15–20% | 8–12% |
| Client conversations | 8–12% | 5–8% |
| Admin & internal | 5–8% | 5–8% |
The pattern is internally consistent. List-building's audited share is bigger than the estimate by 20 to 25 percentage points; every other bucket loses some share to make up the difference. The buckets that lose the most are candidate meetings and pipeline management — which is to say, the buckets that actually produce revenue. Recruiters intuit that they're spending too much time on list-building. The audit gives them the number.
What to do with the answer
The right move depends on which bucket is over-allocated. The audit is diagnostic, not prescriptive — same number, different fixes depending on context. Three patterns repeat across teams we've audited.
-
List-building is 65 percent and meetings are 12 percent.
This is the most common pattern. The recruiter is producing the meetings the desk can run, but the time budget is consumed by getting to them. The fix is at the list layer: AI sourcing collapses the list-building budget from 4 to 6 hours per role to roughly 90 seconds. The recovered hours, in our cohort data, move roughly half to additional candidate meetings, a quarter to deeper client conversations, and a quarter to pipeline work. The +38 percent meetings-per-recruiter figure that shows up downstream is mostly this.
-
List-building is 55 percent and pipeline management is 18 percent.
The recruiter is at meeting capacity but the placement-track candidates are eating the residual hours. The fix is usually about pipeline-stage handoffs, not list quality — though list quality helps indirectly by ensuring the placement-track candidates are actually the right ones (fewer interview-loop failures, fewer offer-stage withdrawals). Audit the pipeline-management bucket itself: how much is candidate-side relationship work versus internal coordination versus scheduling.
-
List-building is 70 percent and meetings are 8 percent.
The recruiter is in a sourcing trap — building lists that aren't converting to enough meetings to justify the time. This pattern usually means the lists are noisy (the candidates contacted aren't responding) or the segment is overworked (the recruiter is contacting the same candidates as five other agencies). The fix is harder; it's not just list-building speed, it's list quality and segment selection. AI sourcing helps because list quality lifts in parallel, but the diagnostic also points to upstream questions about which segments the recruiter is being asked to work.
What the recovered hours are actually worth
The case for recovering recruiter hours has to land on revenue, not on the recruiters' subjective relief. The dollar math is direct and works the same way for agency and in-house teams, with one substitution in the final step.
Recovered 20–30% of week: ¥60K–¥90K of recruiter time recovered weekly
Expected meeting value: ¥107,676 per qualified meeting (Hub 06 cornerstone)
Recovered hours produce ~4–6 additional meetings/recruiter/week
→ +¥430K–¥650K expected revenue per recruiter per week
The numbers above assume the recovered hours actually convert to meetings. In production they do, but not at 100 percent. Some recovered hours go to pipeline work (which produces revenue at a lag), some to client debriefs (revenue through better close rates), some to admin that should have been done anyway. The conversion rate from recovered hours to additional meetings is roughly 50 percent in our cohort — the +38 percent meetings-per-recruiter figure is partially this and partially the reply-rate lift from AI-built lists. Halving the expected-revenue number above to be conservative still leaves a six-figure weekly delta per recruiter.
Why teams resist running the audit
The audit is cheap, fast, and produces actionable answers. Most teams that hear about it do not run it. The pattern is worth naming because the resistance is rational, not lazy.
The first reason is that the audit is unflattering. Recruiters who learn that they spend 65 percent of their week on list-building feel that the number reflects on them, even when the structural explanation is obviously not their fault. The TA leader who runs the audit ends up with conversations about whether the recruiter is being judged. The way out is to frame the audit before running it: this is a diagnostic on the workflow, not on the recruiter, and the goal is to find out which lever moves the most revenue.
The second reason is that the audit's recommended fix — adopt AI sourcing — is a procurement decision the TA leader may not have authority over. The audit produces a clear answer; the answer requires budget approval the leader doesn't hold. In that context, running the audit is creating evidence for a fight you may lose. The workaround is to pilot first: a small AI sourcing credit pack costs less than a procurement cycle, and the pilot produces the second piece of evidence — does the AI's list actually contain candidates your team is missing? — that the audit alone can't produce.
Frequently asked
Why do teams consistently underestimate how much time list-building takes?
Because list-building doesn't sit on the calendar as a single block. It happens in fifteen-minute slices between meetings, in late-afternoon stretches that don't get formally scheduled, in the half-hour before a client call when the recruiter is "just looking for a few more profiles." On the calendar it shows up as gaps; in reality it consumes those gaps. When you actually count the hours by walking back through the calendar and timestamping the work, the unscheduled list-building hours surface — and the team's intuitive 40 percent estimate moves to a measured 60 to 70.
What's the difference between this audit and a regular time-tracking exercise?
Time-tracking asks recruiters to log their hours forward — write down what you're doing each hour. The result is mostly fiction because recruiters fill in time-tracking the same way they think the week went, which is the estimate the audit is trying to correct. The audit walks back through the calendar after the fact, in 30-minute granularity, against the actual artifacts produced — a candidate list, a meeting, a write-up, a client conversation. The bias is in the opposite direction: instead of asking what the recruiter remembers doing, the audit asks what evidence the calendar can produce. The recruiter says "I don't know what I was doing on Tuesday 2:30 to 4"; the audit calls that an hour-and-a-half of list-building, because nothing else is on the calendar and the next artifact is a candidate list created Wednesday morning.
What if my team's audit shows list-building is only 30 to 40 percent of the week?
Two possibilities. The first is that you've already optimized this part of the workflow — either by hiring researchers who do list-building so the named recruiters don't, or by adopting an AI sourcing tool earlier than most teams. If that's the case, the addressable list-building budget is smaller, and the audit's recommendations apply less directly. The second possibility is that the audit was self-reported rather than calendar-evidenced; recruiters who fill in the audit are systematically biased to underreport list-building because it doesn't feel like the work they think they should be doing. If the 30 to 40 percent number came from self-report, run the audit again from the calendar artifacts.
What do recruiters actually do with the recovered hours?
In production data on the agencies we work with, the recovered hours move up the funnel rather than disappearing. Roughly half go to additional candidate meetings — the +38 percent meetings-per-recruiter lift we see in our Q1 cohort is mostly attributable to this. Roughly a quarter go to deeper client debriefs and qualification conversations, which improves the meeting-to-placement ratio rather than the meeting count. The remaining quarter spreads across reference checks, candidate-side closing conversations, and training. Notably, the recovered hours don't generally go to "thinking time" or "strategy work" — that's the answer recruiters give when asked aspirationally, and it's not what they do when the time becomes available.
Should the recruiter-side audit also examine in-house TA teams or just agency recruiters?
Both, with different framings. Agency recruiters are output-paid (placements drive variable comp), so the audit's frame is "recovered hours equal recovered revenue." In-house TA recruiters are typically salary-paid, so the framing is "recovered hours equal recovered capacity" — meaning fewer agency placements outsourced, faster time-to-fill on the open req book, more bandwidth for candidate-side relationship work. The mechanics of the audit are the same. The downstream interpretation differs. We treat the in-house TA economics in detail in our in-house TA versus agency spoke; the audit is the front-end diagnostic for both.
Sources
The audit method is the operational version of the calendar-discipline framing in Briefing 09; the underlying production figures (recovered 20 to 30 percent of recruiter week, +38 percent meetings per recruiter, +13.5 percent interview pass rate, +14 percent offer acceptance) are drawn from Headhunt.AI raised our replies by 78 percent. The expected revenue per qualified meeting (¥107,676 in our cohort) is derived in the meeting unit-economics cornerstone. The capacity-ceiling framing — why recruiter hours are the binding constraint on agency revenue once list-building is solved — is treated in The recruiter capacity ceiling. The in-house TA vs agency interpretation is unpacked in In-house TA vs agency — when one internal recruiter outperforms three agency seats.
Run the audit on one recruiter this week
Two weeks of calendar data, 30 minutes of attention, one diagnostic conversation. The answer changes how you allocate budget. If you want a templated audit worksheet to use internally, contact us — we provide it free.