When a user loads results into Commit, there is an additional step called “Confirm Swimmers”. In this step, the user can now confirm which swimmers in the file represent their team.
Previously the user could control this with less granularity by selecting a team code from the file. This caused problems in a few use cases:
1. Multi-site clubs often have the same team code but operate independently for the majority of their meets. These clubs using Commit would get top time reports flooded with the other sites’ rosters.
2. When a swimmer on Team A swims in a meet for a different team (zone team, high school team, unattached) but Team A wants to get this swimmer’s time into Commit, they would have to upload the file and select no team in the file. This would attach the meet result to that swimmer, but would fail to attribute the results to the team itself in Commit.
The additional “confirm swimmers” step solves both problem #1 and problem #2. In this step, we show to the user all the swimmers in the file(s) and which ones we “think” are theirs. The user can override our guess in any way they see fit. In addition, related to problem #1, we give the user the flexibility to select a team in the file based not only on team code, but on location of the team as well.
You work too hard to be stuck with outdated, clunky swim team management software. Switching does take time and effort but we do the heavy lifting for you. Our onboarding team helps you bring over your roster, family contact information, results history, and website content to Commit.