Skip to main content
All CollectionsReports
Why is the Count of Stage Movements Different than the Count of Candidates in Reports?
Why is the Count of Stage Movements Different than the Count of Candidates in Reports?

This article explains the discrepancy found in the stage movements of a candidate and the number of candidates

Amogh Balikai avatar
Written by Amogh Balikai
Updated over 2 months ago

Reports are a powerful tool in Recruiterflow designed to give you detailed insights into the progression of your business.

However, you might find the number of stage movements in a job pipeline usually higher than the number of candidates. Here's why this is happening:

Understanding Stage Movements and Candidates

In the Report, you will notice two key metrics:

  1. Movements: This refers to the total number of times candidates have been moved from one stage to another in the job pipeline within the selected time frame.

  2. Candidates: This is the count of unique candidates who have been moved through any stages in the selected time frame.

Why the Numbers Differ

It’s common to see the number of stage movements being higher than the number of candidates. This is because a single candidate can move through multiple stages.

Example Scenario

To illustrate, let’s consider an example:

  • Candidate A: Applied -> Screening -> Interview -> Offered

  • Candidate B: Applied -> Screening -> Rejected

  • Candidate C: Applied -> Screening -> Interview

In this scenario:

  • Number of Stage Movements: 9 (Candidate A moved through 4 stages, Candidate B through 3, and Candidate C through 2)

  • Number of Candidates: 3 (Candidate A, B, and C)

Hope this explains why the numbers differ for stage movement and candidates.


Did this answer your question?