One of the core features of BenchLocker is tracking required paperwork for players. Player requirements help administrators review, approve, or reject uploaded documents in real time—ensuring players remain eligible and compliant throughout the season.
✅ Creating a New Player Requirement #
- From the Administrator Dashboard or sidebar, click “Player Requirements”
- You’ll see a list of existing requirements already set up in your system
- Click “+ Add New Requirement” to begin creating a new one
🛠️ Required Fields Explained #
| Field | Description |
|---|---|
| Requirement Name | The title of the requirement (e.g., Birth Certificate, Medical Clearance, SafeSport Certification) |
| Frequency | How often this must be renewed: Once, Annually, or Seasonally |
| Description | A brief note explaining the requirement or where to complete it |
| Expiration (Months) | Enter the number of months before the requirement expires (leave blank for no expiration) |
| Active | Use the checkbox to make this requirement live and visible to users |
| Validation (Regex) | (Optional) Use a regular expression to validate document numbers or codes (see below) |
🔍 What Is Validation Using Regex? #
Some requirements—like USA Hockey Numbers—follow a specific format. BenchLocker lets you validate inputs using regular expressions (Regex).
Example: #
To ensure a 15-character alphanumeric USA Hockey number with a “6” as the 4th digit, use this Regex:
^[A-Z0-9]{3}6[A-Z0-9]{10}$
This pattern means:
- Exactly 15 characters
- Only uppercase letters and numbers
- The 4th character must be a 6
Examples that match:
XYZ6000111222A1236ABC456DE789AAA6BBBCCCCDDD
💡 If you’re unsure how to build a Regex, contact BenchLocker Support — we’re happy to help.
✏️ Managing Existing Requirements #
Once your requirements are created, use the action icons on the Player Requirements page:
- 🖉 Blue Pencil – Edit the requirement
- 🟡 Yellow Toggle – Activate or deactivate it (inactive requirements won’t show to players)
- 🗑️ Red Trash Can – Delete the requirement
⚠️ Important:
You cannot delete a requirement if it’s already assigned to a team.
Deleting a requirement will also delete all associated history.
🛑 It’s recommended to simply deactivate the requirement instead.
