Quote:
Originally Posted by Jon Stratis
The "mandate" to do districts within some sort of regional border is logistical. When placing an event (whether it's a district or a regional), you need to ensure its properly located close to teams, that it serve the teams properly. Allowing teams to "opt in" or "opt out" makes doing that a whole lot harder, especially in the border areas. You end up with a chicken/egg scenario - you need to know which teams are in before you plan events, but teams want to know where events are going to be before they decide if they want in or not. So, you have to draw some border ahead of time. Having teams from relatively far away truck in creates even more problems, as you need to ensure two plays for everyone in your district, and you often don't have many extra plays to go around.
|
Regarding this assumption.
Could you follow this process for an opt-out:
1) Draw the District boarder
2) Teams within boarder default to opt-in
3) Teams can choose to opt-out by certain date in mid-late summer
4) All teams that remain opt-in have district events planned around their location
I think this could work marginally well.
I do see your point though. If a district region has 100 teams near each other, and then 20 teams in a single removed location, this method could definitely break down quick. Imagine 19 of those 20 teams opt-out, leaving 1 team a part of the district structure, but geographically removed from the other 100 district participants. That is a real bummer for that 1 team, since they will have to travel to attend both district events. If, on the other hand, no team could opt out, that 1 team would likely have at least one district event local to them, given the 20 teams in their region that all participate in their district.
Just some thoughts.
-Mike