- Why do you require this information?
This is not our requirement per se as a league, but a requirement of the City of Scottsdale that has competing requests from others for City resources.
- Why does the City require this and how does impact the league?
As a league with participants all over the map, to maintain our status as a high level partner for permitting, we need to hit a certain participant threshold. If we do not have the supporting information for an audit, we run the risk of:
-
- Losing access to fields we have historically have had access to
- Changes in pricing made available to us (which then gets passed to you)
- Do I need to live in Scottsdale to participate in Scottsdale Cal Ripken?
No. Our boundaries remain the same. Refer to this league FAQ (first question).
- I don't live in Scottsdale, do I need to still provide this information?
As a league, we are trying to maximize our participation count for Scottsdale. This does not include just residents of the City but also families that:
a) attend an SUSD school but may not live in the City of Scottsdale - for example, a large group of families live in the 85254 zip code, may be zoned for Sequoia (SUSD) and these families have Scottsdale postal addresses but really live in the City of Phoenix. The fact that some of these families go to a SUSD helps our counts although technically City of Phoenix residents (regardless of what the postal address says).
b) attend a school that has ballfields that are maintained by the City - Grayhawk is an example of a PVSD school -- again, the fact that participants attend Grayhawk regardless of home address is a positive to the league.
These are just a few examples, but hopefully help provide context.
Lastly, we don't want to overcomplicate the registration process and have applied the requirement to all registrants. While not a requirement as of now, we may have similar requirements in the future with the City of Phoenix so we applying the requirement of documentation globally. With the amount of scenarios, its not really feasible to require this information conditionally within TeamSnap.