Choose the process to move from Excel
Name the task first: current squad, parent contact, calendar or attendance. Moving every file at once makes the workflow harder to verify. Choose a team whose coach can complete a full week in the app.
Keep spreadsheets for custom calculations and older reports, but agree one place for current squad updates. Adding players in both the old file and the app creates different lists. Compare uses in Excel or a club app.
- Choose a team, a coach responsible for the rollout and someone to verify contacts.
- Agree when current attendance recording starts in the app.
- Label older reports as archives and define who can access them.
- Use the next session to test the full process from family information to actual attendance.
Prepare squad data rather than the whole workbook
TrainTeam accepts CSV or XLSX squad files. Use a header row and one row per player. Remove summaries, instructions and extra lists. Prepare age groups separately because each import is confirmed in a particular team.
Check names and contact details. Use supported dates such as 2014-05-12 or 12.05.2014. A valid email format does not prove that a parent's address belongs to the correct child.
The preview shows recognised columns and row errors before confirmation. Correct data or deselect rows needing clarification. The Excel import instructions explain the format and preview.
Import scope
Squad import does not recreate old attendance, payment history or formulas. Keep previous files as an archive and agree the start of a new recording period.
Check staff and family access before the first event
After import, compare the list with the real squad. Resolve missing people and duplicates before invitations. Check coach assignments, permissions and family links.
Team contact settings determine whether the parent or player responds. Check access with an active account rather than relying only on an email in a table. People handled outside the app need an agreed staff contact process.
Complete a first week before adding other teams
Test the whole information flow, not just the import. The coach creates an event, the family or player responds, and staff record actual attendance afterwards. A pre-session confirmation does not complete the register.
Review the checklist with the coach before expanding. If someone cannot see an event, fix their assignment or contact. Repeating the import without identifying the cause can add further people and make checking harder.
- The list matches the current squad and problematic rows have been resolved.
- The coach can access the team and knows how to change dates and attendance.
- Families see the correct events; people without active accounts have a contact process.
- Actual attendance is recorded after training and the old spreadsheet is an archive.
Next stage
Add more groups using the same checklist. For a larger club, read the multi-team management guide.
TrainTeam
Real-time player availability
Players and parents confirm from their phones. After the event, TrainTeam pre-fills the list from their answers; the coach confirms actual attendance and corrects any differences.
Training Wed, May 6
17:00 – 18:30 · SP 33 pitch
Example app view · demo data
Summary
- Start with one team and agree a changeover date.
- Import verified CSV/XLSX squad data and archive older reports.
- Check family access and complete one full training workflow before expanding.
