<aside> đź’ˇ This guide aims to review what makes for a good set of archive reasons and how to set your team up for success. With archive reasons in place, a set of example analyses to explore results is given, wherein the common field names and report types are reviewed.

</aside>

Section overview:

Introduction

This article will give a quick overview of utilizing and analyzing archive reasons to understand your recruiting trends. Successfully doing so can yield useful insights for both your top of funnel and late-stage recruiting activities, such as understanding trends in offer decline reasons. Before effective analysis can begin, you’ll need to make sure your archive reasons are amenable to analysis, so we’ll start with a basic recommended taxonomy and some comments on special cases.

Once your archive reasons are in good shape, we’ll discuss how to create custom grouping of reasons to facilitate analysis, and we’ll conclude with some short example analyses:

Creating an Effective Taxonomy of Archive Reasons

The purpose of adding archive reasons is to facilitate a review of why candidates are being rejected or dropping out, and that why should drive insights that help improve your team’s process. You may find, for example, that the primary offer decline reason shifted from relocation to compensation in the quarter you implemented new policies. This raises the point that you’ll want to examine these reasons, generally speaking, via two broad methods: by trend over time and in aggregate.

The trend in reasons over time to reveal changes due to your team’s process and external market factors.

The trend in reasons over time to reveal changes due to your team’s process and external market factors.

A segmentation analysis, e.g. by department or interview stage group, helps identify dominant reasons.

A segmentation analysis, e.g. by department or interview stage group, helps identify dominant reasons.

<aside> đź’ˇ A pitfall to avoid: ambiguous reasons. You want your reasons taken in aggregate to be informative.

</aside>

Some recommendations to help identify the archive reasons that matter to your team the most