The table below shows the fundamental differences between a recruiting and a reporting pipeline in terms of setup, usage, and editing.
Recruiting Pipeline |
Reporting Pipeline |
|
You can have a single pipeline that will be the default pipeline for all your jobs or create multiple custom pipelines that you can assign to jobs. |
Single pipeline: The default pipeline will also be used for reporting. Custom pipelines: When creating a new pipeline for the first time, a reporting pipeline is automatically generated as well. |
|
Used to progress candidates through pipeline stages for jobs. |
Used solely to capture data for the reports. |
| Can be fully customized to match specific hiring needs e.g. use for a specific job/level, department, or location. |
Each stage of a recruiting pipeline will be mapped to a stage of the reporting pipeline. It is advised to use generic recruiting stages and prevent frequent editing since changes to the reporting pipeline impact all pipelines in your account. |
| You can delete stages. |
Before you delete a stage in your reporting pipeline, please ensure that you have removed any other stages mapped to it in your recruiting pipelines. This includes stages in both active and disabled pipelines. |
|
Single pipeline: If you edit or delete a stage, this will affect reporting for all jobs. Custom pipelines: If you edit or delete a stage of a pipeline, this will affect the Current Pipeline, Hiring Velocity, and Historic Pipeline reports only if you are looking at job data that are using the specific pipeline. Learn more here. |
If you edit or delete a stage, this will affect reporting for all jobs. |
|
Single pipeline: Cannot be disabled Custom pipelines: You can disable pipelines you don't use anymore to prevent them from being available for new jobs. |
Cannot be disabled |