How long does it take to fill a role on an outsourced recruiting desk?

Published November 8, 2026.

Time to fill is one of the most quoted recruiting measures and one of the easiest to distort. The number depends on when the clock starts, whether the role was open before the requisition was approved, and how open roles are handled. This review sets out a bounded protocol for measuring the interval on an outsourced recruiting desk. It also separates the stages so the client can see where the days actually went.

Question and scope

This review asks how long it takes to fill a role on an outsourced recruiting desk, measured from requisition approval to offer acceptance. The unit is one requisition for one role. The study reports the total interval and the stages inside it. It does not judge the quality of the hire or compare the desk to a national benchmark without a matched role family.

Set the scope to one client, one role family, and one recruiting process. Record the approval path, the sourcing channels, the interview stages, and the offer approval step. If the process changes during the window, keep the earlier definition for requisitions already open and analyze the later cohort separately. A new interview stage can look like a slower desk when it is only a different process.

Define the population as every requisition approved during the window, including roles that were cancelled, put on hold, or still open at the observation date. The unit is the requisition, not the candidate, because one role can have several finalists. A reopened requisition is a new unit linked to the original. Test the definition on two recent roles before collecting the full sample.

Data sources and methodology

Draw the requisition list from the applicant tracking system and the client's approval record. Record the export date, the filters, the row count, and the selection rule. Match the approval date, the first sourcing activity, the first interview, the offer date, and the acceptance date. A missing timestamp should be marked missing, not reconstructed from memory.

Use the requisition approval date as the start of the clock. If the client wants to measure from the date the role was first discussed, report that interval separately as a pre-approval delay. Mixing the two definitions makes the result incomparable across clients. State the definition in the report.

Collect the role family, the seniority, the location, the hiring manager, and the recruiter. These strata matter because a senior engineering role and a frontline shift role have different sourcing and interview paths. Report the result by role family rather than as one desk average. A single average hides the roles that are actually hard to fill.

Why the stage split matters

A long time to fill can come from a slow approval, a thin candidate pool, a scheduling bottleneck, or a slow offer decision. The total number cannot tell the client which one to fix. The stage split shows where the days went and who controlled them. That is the difference between a useful review and a complaint. Measure the days from approval to first qualified candidate, from first qualified candidate to first interview, from first interview to offer, and from offer to acceptance. Use business days for the stage detail and calendar days for the headline. Report both when the two differ by more than a week, such as over a holiday period.

Record the number of interview rounds and the number of reschedules. A role that takes six weeks because of three reschedules is a different problem from one that takes six weeks because no qualified candidates applied. The stage split should make that visible. Report both the round count and the reschedule count beside the stage medians.

Handling open and cancelled roles

Do not drop a requisition because it is still open. Censor it at the observation date and report the open count separately. Dropping open roles makes the desk look faster because the hardest roles disappear from the sample. A censored role is evidence that the clock is still running, not a failure.

A cancelled requisition remains in the sample with a cancellation reason. If the client cancelled because the business changed, the time to fill is not a recruiting failure. If the desk cancelled because it could not source, that is a different finding. Record the reason and report the cancelled group separately. A role that is put on hold and later reopened creates two intervals. Report the active time separately from the hold time. A desk should not be penalized for a client's budget freeze, and the client should see how much of the delay was inside its own decision cycle.

Sampling and data quality

Include every requisition in the window if the volume is manageable. If not, take a random sample within each role family and report the sampling rule. Do not sample only the roles that were filled, because that biases the result toward success. Record the missing timestamps and the number of records excluded. Check the approval date against the client's system, not only the applicant tracking system. A requisition may be created before it is approved, and the difference can be days or weeks. Use the approved date for the headline and note the creation date as context. Note the collection date separately from the requisition window. A role that was approved near the observation date has less time to close and should be censored. Report the number of censored requisitions beside the completed ones.

Analysis and reporting

Report the number of requisitions, the median time to fill, the median by stage, and the share filled within the client's target. Show the counts by role family, seniority, and recruiter. Present the open and cancelled counts separately. Use the same denominator for every rate and show the number of records with missing dates.

Inspect the slowest roles and describe which stage dominated without naming the recruiter. A cluster in scheduling may point to interviewer availability, while a cluster in offer acceptance may point to compensation. Compare the result with the sourcing channel and the number of interview rounds. The owner can then choose the right fix.

A useful additional view is the time from offer to start date. A fast offer acceptance can still produce a slow start if the onboarding paperwork or the equipment takes weeks. Report that interval separately. The client experiences the start date, not the acceptance date.

Limitations and sources of error

The record cannot show whether the hire was good or whether the desk worked efficiently. It can show only the requisition timeline. A fast fill is not proof of quality, and a slow fill is not proof of poor work. The protocol also cannot capture a role that was filled through a referral before the requisition was approved.

Applicant tracking systems can merge candidates, change stage dates, or record an offer before it was approved. A role may be reopened under the same identifier, which hides the second cycle. Record those cases and their treatment. If the client and the desk use different systems, note which one is authoritative for each timestamp.

A small sample can produce a misleading median. Report the count and the range, and describe the roles rather than ranking recruiters. A single hard-to-fill role can move the average for a small desk. The report should say so.

Review cadence and next action

Review the result with the client and the recruiting lead. Ask them to choose one observable change: a pre-approved interview panel, a weekly scheduling slot, a sourcing channel test, or an offer approval window. Record the owner, the effective date, and the measure that will show whether the change worked. Avoid changing the sourcing and the interview process at the same time.

Repeat the protocol with the same definitions for the next cohort. If the total time fell but the offer stage did not, the gain may be in sourcing. If the offer stage fell but acceptance did not improve, the change may have moved the problem to compensation. Close the review when the owner accepts the finding and the next cohort is scheduled.

A useful additional view is the share of roles that were filled from the first interview slate. A low share may point to a sourcing problem or an interview process that is too narrow. Record the slate size and the outcome. That view helps the client decide whether to invest in sourcing or in the interview loop.

Data Sources and Methodology

The review uses public employment guidance to bound the definitions and to keep the recommended record fields within common legal and administrative practice. The sources below are used as context, not as a claim that any one employer follows them in the same way. Each measure in this protocol is defined from the employer's own records, then compared with these public references where the reference is relevant. The citations are listed with the specific topic they support so a reader can check the boundary without searching the whole site.

The method is deliberately descriptive. It does not pool employers or estimate a national rate. A reader who repeats the protocol should use the same definitions, the same observation window, and the same sampling rule, then report the counts beside the shares. Keep that report with the study record so a later reviewer can repeat the comparison.

Sources

Society for Human Resource Management, talent acquisition metrics - accessed November 8, 2026.
U.S. Bureau of Labor Statistics, job openings and labor turnover - accessed November 8, 2026.
U.S. Department of Labor, hiring guidance - accessed November 8, 2026.
U.S. Equal Employment Opportunity Commission, recordkeeping - accessed November 8, 2026.

Question and scope

Data sources and methodology

Why the stage split matters

Handling open and cancelled roles

Sampling and data quality

Analysis and reporting

Limitations and sources of error

Review cadence and next action

Data Sources and Methodology

Sources

Related Research