Skip to main content

Understanding application rejection

Understand how Reflect classifies a rejected or hired application.

Written by Reflect Team

Reflect considers an application rejected when it has a rejection date and does not ultimately result in a hire. This rule affects recruitment indicators that count rejected or hired applications.

The rejection date can come from a date recorded in your recruitment tool or from a stage normalized as a rejection in Reflect.

What happens if the outcome changes?

If a rejected application is later resumed and results in a hire, it is counted as hired and its rejection date is cleared in Reflect. Conversely, if an application marked as hired is later rejected, it is counted as rejected rather than hired. A withdrawal is counted as a rejection if it is recognized through a rejection date or a stage normalized as a rejection.

For example, an application rejected on March 5 and then hired on March 20 is ultimately counted among hires, not rejections.

What should I check if a figure looks wrong?

Check the application’s events and dates in your recruitment tool, then check stage normalization in Reflect, especially the Is rejected? column in the Recruitment stage category. A normalization change is reflected after the next data update. If the discrepancy remains, contact your Reflect representative with the application, source and date range concerned.

To change these settings, see the data normalization guide.

Did this answer your question?