The Time to Schedule report helps teams follow each step in the request lifecycle. Teams rely on these metrics to grade their performance against their SLAs and understand what’s working well and what needs improvement.
The Time to Schedule report can be found by clicking on the Reports tab, then selecting Scheduling > Time to Schedule:
Items to Note
We began tracking Loops data on 11/9/22 and Requests data on 11/14/2022. Previous data is not available in the Time to Schedule report.
However, there is an exception where the “Loops scheduled” column in the Loops report does count Loops scheduled before 11/9/22.
This report only tracks information from our own database, which means that availability collected via Greenhouse cannot be tracked in this report.
All of the quantities measured in hours/days are averages within the specified date range for the report.
Canceled interviews are automatically omitted from this report.
All days, including weekends and holidays, are counted in this report. There is no exclusion of non-business days.
Loops vs. Requests Reports
When expanding "More Options", users can choose to view either Requests or Loops data in the Time to Schedule Report:
The Requests report data is attributed exclusively to the current assignee of the request, whereas the Loops report data is attributed to the Loop creator.
In the Requests report, Loops data is counted in the “Requests Scheduled,” “Time to schedule,” “Time to interview,” “Availability to scheduled,” and “First action to scheduled” columns, but only as it pertains to the current assignee of the original request.
Report Metrics: Requests
Requests Assigned: Total number of requests assigned to the currently assigned user in the time range selected for the report.
For example, say a request was created in August, assigned to Atul in September, and scheduled in October. If we set the time range for the report to be September, that request would be counted towards the “Requests assigned” column for Atul, but not the “Requests scheduled” column. If we set the time range for the report to be October, that request would not be counted towards the “Requests assigned” column for Atul, but would be counted towards the “Requests scheduled” column.
Requests Scheduled: Total number of requests (created in the specified date range) that became scheduled interviews. This includes candidate self-scheduled interviews (booking requests) and loops created via availability requests.
Time to schedule: Average amount of time between when the request was created and when the event (booking or loop) was scheduled.
Time to interview: Average amount of time between when the request was created and the date/time of the interview. For loops, the date/time of the interview refers to the earliest interview in the loop.
Created to assigned: Average time between when the request was created to when it was first assigned.
Assigned to first action: Average time between when the request was first assigned to the first user action. “First user action” does not include candidate actions, such as submitting availability. It does include:
Making changes to the request configuration
Sending the candidate link
Creating an interview from the candidate’s submitted availability.
Availability to scheduled: Average time between when the candidate availability was received and when the corresponding loop interview was created.
First action to scheduled: Average time between the first action on the request and the creation of the corresponding interview (either booking or loop). The “first action” on the request includes:
Making changes to the request configuration
Sending the candidate link
Creating an interview from the candidate’s submitted availability.
Report Metrics: Loops
Loops Scheduled: How many loops were created by a user in the selected time frame.
Time to Schedule: Average time from when the user starts and finishes loop creation.
Start = User begins entering information on the Loops Interviews tab.
Finish = User clicks “Schedule” button on the Schedule tab.
Time to Interview: Average time from when the user starts loop creation and when the loop begins.
Start = User begins entering information on the Loops Interviews tab.
Loop Begins = Date/Time of first interview in Loop.
If you don't have access to the Reports tab in Prelude, please reach out to your CSM.