Lever Tags: How to Use Tags to Trigger Background Check Packages

## How the tagging system works in Lever Background checks can be triggered at any stage in the hiring process. You decide when during the hiring process (e.g., after the interview stage, before an offer is made) you want the background check to be triggered . Once a candidate reaches the specified **trigger stage**, the background check will automatically be triggered. Tags determine which background check package is sent to the candidate. Each package has a unique tag starting with **zinc_**. These tags link directly to specific check packages and determine which one will be sent when triggered.. If no tag is assigned to the candidate or job, the default package (the first one in your list) will be sent. ### Important note about job tags and candidate inheritance Candidates inherit tags that were already on the job at the time they were added to it. If you add a tag to the job after candidates are already assigned, those existing candidates will not inherit the new tag retroactively. ## Ways to tag There are two main ways to apply tags to control which background check package is triggered: ### 1. Tagging the job This is the simplest method. If all candidates for a job need the same background check package, apply that tag to the job itself. Then, when any candidate for that job moves to the trigger stage, they'll receive the corresponding background check automatically. ### 2. Tagging individual candidates This method offers more flexibility. If you have candidates for the same job who require different background checks (for example, because they work in different locations), you can tag each candidate individually. Note that you must assign the tag before the candidate reaches the trigger stage; otherwise, they will receive the default package. Tagging candidates is especially helpful for managing **global job postings** with location-specific background check requirements. By tagging candidates individually, you ensure each candidate receives the appropriate check package based on their location or other criteria. ## How to create a new tag If you need a new tag for a new background check package: 1. **Notify us of the new check package:** Contact your Account Manager or the Customer Success Team and provide the name of the new package and the desired tag name. 2. **Tag creation:** The team will create the corresponding tag with the **zinc_** prefix. 3. **Tag assignment:** You can then assign this tag either to the **job** or directly to individual **candidates** to specify which checks should be triggered at the correct stage. ## Good to Know **I added a tag to the job, but the candidate doesn't have it — why?** Candidates only inherit tags that were present on the job at the time they were added. Adding a tag to a job after candidates are assigned does not retroactively add that tag to existing candidates.