Many organizations believe they have a recruiting function because they have recruiters.
In practice, they often have something different — recruiting activity organized around individuals rather than recruiting work organized as a system.
Both approaches can produce hires.
Only one produces consistency.
When recruiting lives inside a role
In most teams, a recruiter owns the full lifecycle of a role:
intake → sourcing → screening → coordination → follow-up → offer progression
This structure is straightforward and works well when hiring volume is low or timing is flexible.
But as hiring becomes ongoing, the process starts behaving unpredictably.
Work shifts constantly between responsibilities.
Future pipeline depends on today’s availability.
Timelines stretch during busy periods.
Nothing is broken — yet results fluctuate.
The role performs tasks.
The system doesn’t exist yet.
What a recruiting function actually means
A recruiting function does not describe who performs the work.
It describes how the work continues regardless of individual workload.
In a function, responsibilities are organized so each stage advances continuously:
candidate generation continues during interviews
screening progresses while scheduling happens
coordination advances while sourcing continues
The goal is not to reduce recruiter effort.
It is to prevent progress from stopping when priorities shift.
The difference is subtle but operationally significant:
A recruiter completes steps.
A function maintains movement.
Why activity and outcomes diverge
Teams centered around individual ownership often show high activity and uneven outcomes.
Some weeks move quickly.
Others stall without a clear cause.
This happens because recruiting work competes for the same time block.
When interviews increase, sourcing pauses.
When coordination rises, qualification waits.
When offers are prepared, new candidates stop entering.
The recruiter remains busy.
The pipeline does not remain stable.
The handoff problem
Hiring delays rarely occur during conversations with candidates.
They occur between them.
After an interview ends
Before feedback is shared
Between scheduling attempts
While follow-ups wait
In role-based models, progress depends on the same person returning to move the process forward.
In function-based models, transitions are owned so movement continues without interruption.
Consistency comes from managing the moments between steps.
Capacity vs throughput
Adding recruiters increases capacity — the amount of work that can exist.
It does not automatically increase throughput — the speed at which candidates progress.
Organizations often experience:
more outreach
more interviews
similar timelines
Because the workflow remains sequential, the process simply scales its pauses.
A recruiting function changes the pattern instead of expanding it.
What changes when recruiting becomes a function
When responsibilities are organized around workflow rather than individuals:
future pipeline continues during busy periods
candidate experience stabilizes
feedback cycles shorten
priorities stop resetting the process
Hiring becomes less reactive to daily workload.
Performance depends less on who is available and more on how the process advances.
Where this matters most
The difference becomes noticeable when hiring is ongoing rather than occasional:
repeating roles
specialized positions
multiple stakeholders
changing demand levels
In these environments, effort alone cannot stabilize outcomes.
Continuity of execution does.
Organizations often discover that predictability comes from designing how recruiting runs — not from increasing how much recruiting happens.
Final thought
A recruiter performs recruiting tasks.
A recruiting function ensures recruiting continues.
Both hire people.
Only one produces consistent hiring.
When teams begin evaluating hiring performance this way, the focus shifts from increasing activity to maintaining uninterrupted progression.