Ankored supports age-triggered requirements, a way to automatically assign background checks and other requirements when a participant reaches a specified age. No spreadsheets, no manual tracking, no missed deadlines.

Age-triggered requirements allow your organization to configure a requirement once, and have Ankored automatically assign it when a user turns a specific age. This is especially useful for organizations that work with youth participants who will eventually need a background check once they turn 18.

When setting up an age trigger, admins can choose whether the requirement activates:

Previously, admins had to manually track birthdays, create workaround "minor" roles, and manually assign requirements when participants aged into eligibility. This was time-consuming and error-prone, and requirements would often sit as "Incomplete" for minors since background checks can't be run on anyone under 18.

Now, you configure the age trigger once per requirement, and Ankored handles the rest automatically. No role changes needed, no manual tracking, and no stuck requirements for minors.

Age-triggered requirements are configured in the requirement setup flow within your Ankored admin portal. When creating or editing a requirement, you'll see an option to set an age trigger. Simply enter the target age and choose your timing preference.

Note: Existing requirements are not affected unless you explicitly enable an age trigger on them.

Until a member reaches the trigger age, the age-triggered requirement appears greyed out on their profile. They can see that it is coming, but there is nothing for them to do yet. Once the trigger date arrives, the requirement becomes active and the member is asked to complete it.

Yes. Age triggers can be applied to any requirement type, including background checks, abuse prevention training, certifications, and more.

Our recommendation is to assign the background check immediately when a participant turns 18. There's no benefit to waiting.

Here's why: any unsealed records will appear on a background check as soon as someone is 18, so running it sooner rather than later gives you the same result you'd get at any point down the road. Sealed records won't appear regardless of when you run it, so timing doesn't change that outcome either.

The bottom line: assign it on (or as close as possible to) their 18th birthday to keep your screening process consistent and your organization protected.

Once you enable an age trigger on a requirement, Ankored will apply it going forward based on each participant's date of birth on file. We recommend reviewing your participant data to ensure birthdates are accurate before enabling this feature.

If Ankored can't use a member's date of birth, for example because it is missing or invalid, the age-triggered requirement is assigned to them right away instead of being skipped. This makes sure no one misses a required step because of a data issue. To prevent this, make sure your members' birthdates are accurate.

Reach out to our support team at [email protected]. We're happy to help you configure this for your organization.