Best Practices: Managing & Analyzing Archive Reasons

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 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 a custom grouping of reasons to facilitate analysis, and we’ll conclude with some short /#hands on with ashby analytics analysis examples looking at archive reasons by stage group taking a closer look filtering and exploring archive reasons examining archive reason trends over time utilizing archive reasons to re engage candidates how to set up archive reasons in ashby you can add and/or edit archive reasons by heading to admin > jobs & applications > https //app ashbyhq com/admin/organizational settings/candidate archive reasons click + new to add a new archive reason, or click on an existing archive reason to make any edits 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 pitfall to avoid ambiguous reasons you want your reasons taken in aggregate to be informative some recommendations to help identify the archive reasons that matter to your team the most what stage of the recruiting process are we most invested in improving? do the archive reasons we have facilitate that process? do you have any unique factors at your company or team that need to be accounted for? this can show up in archive reasons unique to evaluating certain company values or evaluating a very specific industry experience or skills that go beyond “lacks skills” type reasons pay close attention to whether the given reason is informative one of the most common archive reasons we see is “offer declined ” this reason makes sense when doing a very basic analysis of comparing all archives and seeing how many are offer declines however, given you can group and filter by stage (and other conditions of interest) with ashby, such a general offer reason does not provide much insight six months from now when you analyze offer declines, you’ll want to identify actionable signals about this critical stage in your recruiting process another common archive reason is “other”, which in aggregate can be taken to represent what fraction of your candidate archives lack informative categorization in our experience, the “other” option is a well intentioned but easy default for recruiting teams that need to move quickly we recommend checking if “other” is a significant portion of your archive reasons and reviewing your available reasons if so consider what stage in your process you might use a particular reason “not a fit for role” might be acceptable at the application review or screen stage, but for later stages, more specific reasons may match hiring criteria, such as values or skill and level based reasons can help optimize your process another common archive reason is “withdrew ” this, in our opinion, is more of a category than a reason there are many reasons a candidate may withdraw from the interview process and your analysis should reveal them remember to ask yourself whether your archive reason informs a potential insight or action for your team archive reasons can also help other teams in your organization for example, using the "fraudulent candidate" reason can enable your security teams to identify and track suspicious activity more easily through a centralized marker if you’re just getting started, or looking to improve your current setup, the next section presents a standard set of archive reasons by category recommendation an example of a set of archive reasons ashby supports archive reason categories and our greenhouse customers inherit the greenhouse categories rejected by org or rejected by candidate lever does not support archive reason categories, but ashby’s docid\ wjbhw3mnd 381wu1n8f x can help resolve that challenge by creating custom groupings depending on the size of your organization the level of detail in your archive reasons may vary typically, larger organizations can support more reasons as the larger volume of applicants permits more specificity for this reason, there is a judgment call here if you’re a small team just getting started, you may not want to get too detailed on all the reasons a candidate can exit consideration for starters, an example set of archive reasons by archive reason groupings is given below category rejection by organization the reasons your organization will utilize may vary depending on your interview process, industry details, or certain policies the reasons below are given as a standard starting set, but you may need to add more, e g specific values related reasons rejection by organization reason lacks work authorization role fit general skills/qualifications role fit experience level too senior role fit experience level too junior reference/background check location unwilling to relocate / remote policy values fit reason(s), e g "value fit team player" follow up role filled fraudulent/fake candidate category rejection by candidate reasons the offer specific reasons below are given as a more detailed example you may not find all of them necessary at your current company size rejection by candidate reason offer specific reasons remain with current company offer declined leveling not interested general offer declined compensation salary not interested industry offer declined compensation equity not interested role / project offer declined career growth not interested career growth offer declined accepted competing offer accepted other offer offer declined remain at current company unresponsive offer declined other bad timing offer reneged category rejection due to process or data clean up (aka, “other”) the reasons that fall in this category should be thought of as those you most likely do not want to include in your archive reason analysis, barring analysis that is looking at, e g , data quality or re engagement for example, when analyzing offer rejection reasons you will want to exclude cases of archiving candidates that were moved to a different role other reasons did not respond to outreach position closed / on hold transferred to another role position filled cleanup inactivity non compete custom groupings with calculated fields if you do specify many reasons you can minimize the fragmentation of reasons by creating custom groupings with ashby’s docid\ wjbhw3mnd 381wu1n8f x feature apart from the standard grouping above, you may want to consider special use cases like grouping all archive reasons that permit following up with the candidate at a later date a custom grouping of the above reasons to select candidates for re engagement may look like the following custom grouping reasons position filled position closed / on hold location unwilling to relocate / remote policy follow up / future consideration hands on with ashby analytics analysis examples below we present a few pragmatic examples types related to archive reasons a short description and recorded example is provided per analysis, but for reference we find the below fields to be some of the most useful when navigating and analyzing archive reasons ashby fieldname why it's helpful archived at allows you to select the timeframe in which the applications you want to analyze were archived furthest stage group reached allows you to group by or filter to the furthest stage group the application made it to archive reason gives the specific archive reason used archive reason type gives the broad archive category, rejected by org, rejected by candidate or other the above is just one of many useful fields for analysis, others being department or team, source type (origin for lever users), or potentially hiring team member fields such as recruiter and hiring manager if you’ve created docid\ wjbhw3mnd 381wu1n8f x for custom grouping, you’ll be able to use those for your analysis, too! archive reason by stage group with ashby, you can examine archive reasons by the stage group in which the candidate was archived the composition of reasons should change as candidates progress through your interview process, so this analysis permits you to keep an eye out for things like on site reasons being appropriately matched to the on site stage if you find that candidates are being archived for reasons such as lack of fit, or not interested in relocating, that’s a sign that prior stages which should be screening for such factors are not functioning, resulting in precious time and resources being expended at the on site candidate rejections by stage group png narrow the scope of analysis & explore onsite stage group we can focus on the previous analysis by examining the onsite stage group specifically with this narrowed scope we can examine other variables that may be significant factors in the example below we take a closer look at the onsite rejections by candidate by source type, revealing that agencies result in a higher rate of candidates that weren’t interested in the opportunity in general, as you proceed with an exploratory analysis consider filtering and grouping your analysis to a specific department, region, or interview stage candidate rejections by source type at onsite png look at the trend over time plotting archive reasons over time can be challenging if your recruiting efforts are not at a sufficient volume two approaches to help with that are to look for trends in the broader archive reason categories (e g rejected by candidate) or custom groupings or to use longer time periods, such as a quarterly time series as opposed to a weekly time series this type of analysis is especially important in evaluating policy changes or external market factors in the example below we see some reasons change quarter to quarter, while others (accepting another offer) remain present, suggesting that time to offer may be a strategic initiative to improve engineering candidate rejections over time png utilize archive reasons for re engagement candidate re engagement is a cost effective manner of sourcing talent with targeted archive reasons you can filter by previously interviewed candidates to drive contextualized outreach at a later date for example, if your remote work policy changes, you can follow up with all candidates archived under the “relocation / remote policy” reason and let them know of new opportunities screen shot 2021 11 03 at 9 27 55 pm png conclusions we hope the above summary is useful as a refresher and recommendation on how to manage and analyze your archive reasons we covered the rationale for setting up helpful archive reasons, some prompts to evaluate what makes a good archive reason, and how to set your team up for success in the long run with some example analyses if you have any feedback, thoughts, or recommendations on this topic we’d love to hear from you! feel free to reach out to mailto\ support\@ashbyhq com we love hearing from you! faq who has access to add or edit archive reasons? see the table below for information on the roles that have access to configure archive reasons access role has access? limited access ❌ agency users ❌ elevated access external recruiter (not linked to an agency) ❌ elevated access analyst ❌ elevated access hiring team member ❌ elevated access hiring manager ❌ elevated access admin ❌ elevated access admin private ❌ organization admin ✅ only organization admins can set up archive reasons by default elevated access users can be given access to archive reasons if needed more on this at additional user permissions