Age Verification confirms that a player's birth date is real. On its own, it does not confirm that the player belongs in the division they registered for. Date Range Validation adds that check: you set a birth date window on an Age Verification requirement, and members whose profile birth date falls outside the window are marked Rejected before they are asked for a document.
This guide covers how to set it up, what your members see, and what to do when a member shows as Rejected.
How It Works
When Date Range Validation is on, Ankored compares the birth date already on the member's profile against the range you set. This happens before any document upload or AI review.
Birth date inside the range — the member goes through the normal Age Verification flow (headshot, document, review). Nothing changes for them.
Birth date outside the range — the requirement is marked Rejected immediately. No document is collected, nothing is sent for review, and the member sees a View Reason button instead of a retry option.
Date Range Validation is off by default. Existing Age Verification requirements are not affected unless you turn it on.
Date Range Validation is not the same as Age Trigger. Age Trigger controls when a requirement applies to a member (for example, only once they turn a certain age). Date Range Validation controls whether they pass. You can use either or both.
Setting Up Date Range Validation
Date Range Validation is configured per requirement. If you need to enforce eligibility for several divisions, create one Age Verification requirement for each age group and assign each to the matching program.
1. Open the Age Verification requirement you want to scope, or create a new Age Verification requirement.
2. Give it a Requirement Name that includes the division (for example, Age Verification — 12U Spring 2026). Parents see the requirement name and the date range, but not the division name, so putting it in the title avoids confusion.
3. Confirm Age Verification Enabled is checked.
4. Scroll to the Date Range Validation section at the bottom of the requirement settings and turn on Require birth date to fall within a range?
5. Set one or both dates:
Born on or after — the earliest allowed birth date. Leave blank for no earliest limit.
Born on or before — the latest allowed birth date. Leave blank for no latest limit.
6. Check the blue summary panel below the dates. It restates your rule in plain language, for example: "Members must be born between March 1, 2012 and July 1, 2012 (both dates included) to pass this requirement." If you're building many of these, read this sentence rather than re-checking the two fields.
7. Save the requirement and assign it to the correct program as you would any other requirement.
Errors you may see on save
Inverted range — the "on or after" date is later than the "on or before" date. Both fields are highlighted; swap or correct the dates.
Toggle on with no dates — enter at least one date, or turn the toggle off.
What Members and Parents See
When a member's birth date is outside the range, the Age Verification row on their Requirements tab shows a red Rejected status and a View Reason button. Clicking it opens a window titled "[First name] isn't eligible for this division" that shows:
Birth date on file — the date on the member's profile
This requirement allows — the range you set
The window tells the parent to update the birth date on the profile if it's wrong, or to contact you if the division is wrong.
The range also appears inside the verification wizard. If a parent enters a corrected date of birth that falls outside the range, they'll see an inline error and won't be able to continue.
You can share Why Does My Child's Age Verification Say "Rejected"? with parents who ask about this status.
Resolving a Rejected Member
A Rejected result from Date Range Validation means one of two things is wrong. Retrying won't change it — the check is a simple date comparison.
The profile birth date is wrong
Compare the birth date on the member's profile to what the parent expects. If it's a typo or an outdated record, correct the birth date on the profile (or have the parent do so). For organizations using LeagueApps, the birth date comes from LeagueApps and must be corrected there.
The birth date is correct, but the member is in the wrong division
If the birth date is accurate and falls outside the range, the member is registered in a division they aren't eligible for. Move them to the program for the correct age group, where the matching Age Verification requirement will apply.
The range on the requirement is wrong
If several members in the same division are Rejected unexpectedly, check the requirement itself. A mis-keyed date (wrong year, or "before" where you meant "on or before") will reject an entire age group. Open the requirement and read the summary panel to confirm the range matches your division rules.
Good to Know
Both boundary dates count as passing. "Born on or before July 1, 2012" includes July 1. If your league's eligibility chart says "before" rather than "on or before," adjust the date by one day.
One requirement per division. A single Age Verification requirement can hold only one range. For 8U, 9U, 10U, and so on, create one requirement each.
Out-of-range rejections never reach the review queue. Only document-stage issues (unreadable files, ambiguous dates, identity mismatches) go to Ankored review, same as before.
Documents are still destroyed after the decision. Date Range Validation keeps the same privacy protections as standard Age Verification. Members who are rejected by the range check never upload a document at all.
Verification does not carry over year to year. A member verified for 10U this season will complete Age Verification again for 11U next season.
Replacing a document validator workaround? If you've been using a generic AI document validator requirement to enforce division eligibility, Date Range Validation on Age Verification is the intended replacement. Reach out to your Ankored contact for help transitioning existing requirements.