Context
Users (recruiters) create check packages consisting of the relevant checks they want to run on their candidates. They may have more than one package depending on the roles they're hiring for, or the seniority level of the candidate. Recruiters in different industries may also have different background check requirements, and subsequently may have to build different packages to meet their regulatory needs.
Problem
Building the right check packages is an important part in the hiring process, but it's not always clear which checks are right for which types of candidates. On top of that, regulations can also play a big role in which checks to run. Recruiters have a million tasks to do, so keeping up with regulatory changes isn't always top of mind.
Recruiters are often in the dark about what checks they're switching on. They lack any cues from similar companies or regulatory guidance on how to build the right check package. This can be particularly challenging as this is one of the first steps recruiters will have to do after signing up with Zinc — first impressions matter a lot.
Solution
To understand what information users cared about when creating a check package, we talked to a bunch of users and analysed data on existing check packages. Recruiters cared about several factors when creating a check package:
Following regulations
Knowing what companies similar to them do (size, location, industry)
Running relevant checks for candidates' seniority levels
To solve this, we introduced Templates which serve as a shortcut for recruiters to build the right package for them by looking at what companies similar to them do. The templates can be filtered by industry, seniority level, location, and regulations for ease of use.
Some users had already consented to publishing their check packages to help the package creation process easier for other companies, so in addition to Zinc-created templates we already had a database of templates created by our customers.
Recruiters are now able to create packages quickly without getting stuck on deciding which checks are right for them.
Using a template to create a package
First step of creating a package
Template preview
Naming a package
Publishing a template