Currently Tracks has very limited functionality. A Track can put a Volunteer into a User Group, but that is where the benefit ends. Tracks is currently not very suitable for ensuring users have met and maintain qualifications. With my proposed changes, Tracks will become a more useful way of separating Users across regions/countries/or other categories. 

For example (how VMS currently works), 

• A Volunteer completes an "Australian" track, and automatically joins an Australian User Group.
• When completing the track, the volunteer completed Qualification (sign an Australian legal agreement).
• Now, in order to ensure volunteers have completed the legal agreement, a Program Manager has 2 options

1. 1. Put all new Opportunities into the Australian User Group and make the Opportunity "private"; or
2. 2. Put a qualification requirement on every single Opportunity created to ensure the volunteer has completed their legal agreement (very cumbersome)
3. 
   

• If the Program Manager follows option 1 above, we lose the benefits of Qualification management from VMS: if the User's qualification expires, they still belong to the User Group and would still be able to respond to Opportunities.
• If the Program Manager follows option 2 above, this opens us to risk of human error. A new Program Manager (we will have hundreds of them), could forget to include this qualification requirement. Also, Volunteers who are outside of Australia would simply be able to submit a qualification without completing the track; making Tracks completely pointless.
• Only workable solution is for Program Managers to do both Option 1 and Option 2, but there is still risk of non-compliance and this is cumbersome.