5
5-6-7-8
Ok, I have been trying to think through this “trending” idea a bit more, to be able to summarize it for discussion. (Although now that I typed it up, it isn’t very “summarized.”)
Here is a brief summary of the key steps (and as I have been thinking this through, I have identified other benefits which can be discussed later.)
1. Before competition season, each gym creates and maintains a list of athletes, to include a benchmark “level” and date of birth. At this point, the level is just used as a guideline, it is not a set in stone credential.
2. Athlete list is submitted to the USASF (or ??) who then assigns a registration ID number and a ID / shoe tag per athlete. (Perhaps age verification can occur here as well.)
3. Event Producers register their events with USASF to receive event ID numbers.
4. Gym registers athletes for events, assigning them to a team # / division #. (It can be built in at this point that a gym cannot register an athlete who is age ineligible for said team.)
5. At some interval to be determined, system reviews by athlete the divisions registered for to that point. Depending on “athlete exception” criteria set, if an athlete has no exceptions, nothing happens. If “athlete exception” criteria are met, the next step is to look at that particular team. If “team exception” criteria are met (athlete appears to be a fill in) nothing happens. If the team appears to meet some sandbag criteria, the exception is sent for “human review.”
6. On the event day, to enter warm ups (or at some other defined point), athletes ID card / shoe tags are scanned and compared against team registration list. (Somehow, a photo must either be reviewed, or at the least randomly checked to prevent / deter athletes from borrowing cards. Unless photos are put on the cards (with no identifying information)
At this point, the basics of sandbagging are addressed, and the following could be additional benefits to the system.
7. EP records scores (one score, or detailed), placement, and if applicable, bid assignment for each team / division. This would enable the following:
a. Track team record in order to enable a team that is not performing well at level x to drop to level x-1 without issue.
b. Track bids assigned (and accepted / declined.)
Next Steps:
A. Develop “athlete exception criteria” – need to define what would trigger an exception. For example, if athlete A is competing level 4 most of the year, but then registers for a level 2 team. This step just to send athletes to the next level of review, not necessarily an outright exception.
B. Develop “team exception” criteria – would need to define what creates a team exception. For example, continuing from above, review the level 2 team to see it’s makeup. If Athlete A is the only “out of level” athlete, or the team is within a defined percentage of level athletes, than no exception is noted. If the remainder of the team is largely out of level than it is noted for human review.
C. Determine consequence if team is decided to be largely out of level (can gym fix before being penalized, an immediate penalty, or team/gym is not eligible to register for the event.)
D. Determine if EPs will also be held accountable, should an out of level team still be allowed to compete.
OK, I think that is it in a nutshell! Fire away with questions, comments, concerns!
Here is a brief summary of the key steps (and as I have been thinking this through, I have identified other benefits which can be discussed later.)
1. Before competition season, each gym creates and maintains a list of athletes, to include a benchmark “level” and date of birth. At this point, the level is just used as a guideline, it is not a set in stone credential.
2. Athlete list is submitted to the USASF (or ??) who then assigns a registration ID number and a ID / shoe tag per athlete. (Perhaps age verification can occur here as well.)
3. Event Producers register their events with USASF to receive event ID numbers.
4. Gym registers athletes for events, assigning them to a team # / division #. (It can be built in at this point that a gym cannot register an athlete who is age ineligible for said team.)
5. At some interval to be determined, system reviews by athlete the divisions registered for to that point. Depending on “athlete exception” criteria set, if an athlete has no exceptions, nothing happens. If “athlete exception” criteria are met, the next step is to look at that particular team. If “team exception” criteria are met (athlete appears to be a fill in) nothing happens. If the team appears to meet some sandbag criteria, the exception is sent for “human review.”
6. On the event day, to enter warm ups (or at some other defined point), athletes ID card / shoe tags are scanned and compared against team registration list. (Somehow, a photo must either be reviewed, or at the least randomly checked to prevent / deter athletes from borrowing cards. Unless photos are put on the cards (with no identifying information)
At this point, the basics of sandbagging are addressed, and the following could be additional benefits to the system.
7. EP records scores (one score, or detailed), placement, and if applicable, bid assignment for each team / division. This would enable the following:
a. Track team record in order to enable a team that is not performing well at level x to drop to level x-1 without issue.
b. Track bids assigned (and accepted / declined.)
Next Steps:
A. Develop “athlete exception criteria” – need to define what would trigger an exception. For example, if athlete A is competing level 4 most of the year, but then registers for a level 2 team. This step just to send athletes to the next level of review, not necessarily an outright exception.
B. Develop “team exception” criteria – would need to define what creates a team exception. For example, continuing from above, review the level 2 team to see it’s makeup. If Athlete A is the only “out of level” athlete, or the team is within a defined percentage of level athletes, than no exception is noted. If the remainder of the team is largely out of level than it is noted for human review.
C. Determine consequence if team is decided to be largely out of level (can gym fix before being penalized, an immediate penalty, or team/gym is not eligible to register for the event.)
D. Determine if EPs will also be held accountable, should an out of level team still be allowed to compete.
OK, I think that is it in a nutshell! Fire away with questions, comments, concerns!
