Central finding: A scheduling lag measure is useful when it separates recruiter approval, panel availability, candidate response, and final confirmation rather than reporting one elapsed time [Source: SHRM recruiting guidance].
Define the four timestamps
Record the approved request time, the first panel availability request, the candidate availability request, and the confirmed event time. Use one time zone and state the business-hours rule [Source: SHRM recruiting guidance].
A single request-to-confirmation number hides the step that caused the delay. The four timestamps show whether the lag sits with the recruiter, the panel, the candidate, or the coordinator.
Classify the interview and the exception
Record the interview stage, the panel size, the time zone spread, and any accommodation. A complex panel should not be compared directly with a single interviewer [Source: BLS administrative support outlook].
Separate a reschedule from a first booking. A reschedule has a different cause and should be reported separately.
Sample and report
Select a fixed period and include every approved request in scope. Report the count, median, range, and the number of reschedules. State the sample and the stage mix [Source: U.S. Department of Labor workplace guidance].
The measure describes the reviewed scheduling queue and does not establish an industry standard.
Use the result to test one control
If the delay is at panel availability, test a request that includes the role and preparation time. If the delay is at candidate response, test a clearer message and a single scheduling link.
Keep the measure in place long enough to compare. One fast week is a case, not proof of improvement.
Method note
We reviewed the public sources listed below and translated recurring operational ideas into questions for workflow ownership, source evidence, review, and escalation. This is operational guidance, not legal advice.