Pipeline History

this document gives a basic introduction to the topic of historical pipeline reporting and an overview of the pipeline history template report overview a pipeline history report for all active interview stages across an organization's entire recruiting process a pipeline history report for all active interview stages across an organization's entire recruiting process ashby’s pipeline history report allows you to address the question how many candidates were present in which stages over time? this is achieved by analyzing the full history of your application stage entries and exits and provides an easy way to visualize trends of candidate applications in your process over time tutorial pipeline history examples example pipeline history for a single job, where application review is optionally shown as the weeks progress, candidates progress through to the offer stage the pipeline history report can address a few different reporting needs at the most granular, you may want to report on the history for a specific, individual job more broadly, you may want to look at departmental, team, or organization wide pipeline history trends across many jobs and their associated applications in aggregate pipeline history for a given job pipeline history for a group (department, team, entire organization) pipeline history for a specific stage (e g number of candidates in the offer stage over time) pipeline history for specific hiring team members (recruiter, hm) the standard pipeline history report will group counts by the historical stage group an application was in, but with ashby, you can optionally group by any field that has historical pertinence you may want to see your pipeline by important dei metrics, departmental breakdown, or possibly source example pipeline history for the job analyzed above, this time focusing on the active stages only (excluding application review) and grouping by gender example pipeline history for the job analyzed above, this time focusing on the active stages only (excluding application review) and grouping by gender create a pipeline history report build the report from the template report library to analyze your pipeline history, we recommend using our pipeline history template report from our template report library from your home page, select reports > templates > pipeline history screen cast 2022 12 08 at 7 27 06 am gif from count over time report you can access the reporting subject historical applications when creating a count over time report from your home page, select reports > build > count over time then change the subject to historical applications screen cast 2022 12 08 at 7 28 06 am gif filter your pipeline history report the historical application fields for filtering the historical application fields for filtering historical interview stage group/name can be used to filter the pipeline history report to include or exclude specific stages or stage groups as needed for example, selecting a historical stage group of onsite would filter the pipeline history to show the the weekly count of all applications in the onsite stage historical interview stage type allows you to select all stages of a specific category easily (e g all lead stages, or only active interview stages) was in stage allows selection on the historical time period of interest (e g the last 12 weeks, current ytd or last week) current application follow this path to find easy reference to all of the current application, candidate and job data fields as of today an example of this may be filtering by all applications of a specific source type group your pipeline history report the pipeline history template report defaults to grouping by stage or stage group, depending on your ashby configuration the application stage history provides a means of reconstructing all historical counts other fields accessed when selecting current application are static (e g the candidate dei information or application source) these fields are good candidates for grouping active pipeline history grouped by source type to reveal the composition over time active pipeline history grouped by source type to reveal the composition over time take care when grouping your pipeline history by fields that may not have been preserved historically however, you are advised to take care when grouping by a current application field that it may be liable to change on the application, such as the job’s hiring manager or the application’s recruiter this may result in showing a historical count grouped by a value at the present time that was not the value at a historical point in time faq is this a snapshot at a specific time? no pipeline history is not a snapshot at a specific point in time a snapshot approach would capture your candidate pipeline at one point in time (e g every monday at midnight) and be liable to miss any stage presence between that time and the next snapshot for example, if a candidate’s application was in the screen stage on monday when a snapshot was taken, and then was moved through a technical screen, an assessment, and was moved to onsite, the second snapshot the following week would capture only the onsite stage, missing the stage transition events over the last week can an application count more than once in a given time period (e g week)? yes as a candidate’s application moves through stages, the pipeline history report will count their presence in each stage that they enter or are in during the time interval of interest (e g weekly) for example, a candidate with an application that starts in screen and moves to technical assessment within one week would be captured and reflected in the pipeline history report as a unique count in each respective stage when grouped by stage if there is no group by selection applied, an application will count once and only once in the given time interval what’s the difference between historical applications and current application ? application history refers to the reconstructed stage history of each application this is a unique set of data which ashby allows selection and filtering of based on the stage presence at any point in time the current application path references the candidate’s application at the present moment in time for example, an application will have been at a screen stage at some point two weeks ago, but at present, its current stage may be onsite w hat is a historical job consideration? a historical job consideration is the stage or stage group the job consideration was in on the given calendar date