Use the fields the roster import supports
The roster importer maps three fields. A name is required for every athlete. Roster division and training group are optional columns, with defaults selected in the import screen. Keep unrelated administrative information out of this file.
Scroll the table horizontally to read the field notes.
| Column | Example | What to check |
|---|---|---|
| Name | Alex Morgan | Required full display name, at most 120 characters |
| Roster | men, women, or unassigned | Use the intended roster division; unmapped values use the selected default |
| Training group | Distance | The group must already exist; use Unassigned to leave membership unset |
The screen recognizes several familiar headers, including “Athlete name,” “Full name,” “Division,” and “Group,” and lets you match columns manually. Inspect those mappings even when they are suggested automatically. A recognized header does not prove the values beneath it belong in that field.
Copy this CSV template
These are fictional names. Replace them with your roster before importing. Keep the first line as the header and give each athlete one row. The example uses Unassigned so it does not depend on a training group already existing.
Name,Roster,Training group
Alex Morgan,unassigned,Unassigned
Jordan Park,unassigned,Unassigned
You can paste the columns into a spreadsheet and export as CSV, or save the text as a .csv file. Use a comma-separated export with a header row. Spreadsheet formatting, colors, and formulas are not part of the roster data the importer needs.
A value containing a comma needs CSV quoting. For example, a display name written as last name, first name must stay in one quoted field. The common quoting conventions, including doubled quotation marks inside a quoted value, are described in RFC 4180, section 2. Exporting from your spreadsheet is less error-prone than adding punctuation by hand.
Prepare the roster and groups first
- Check the active roster. Remove people from the import file who already have an active record. This importer adds records; it is not a bulk update tool.
- Resolve duplicate names. Repeated names in the file or names already on the active roster block the import. Matching ignores letter case and extra spacing.
- Create the groups you intend to use. A typed group name does not create that group. Check spelling or select Unassigned.
- Check capacity. The complete file must fit within your team's available active-athlete capacity.
- Trim the file. Use no more than 250 athlete rows in a roster import and keep the file at or below 2 MB.
If two athletes genuinely share the same full name, resolve that case with the person responsible for your roster before importing. Do not invent a spelling just to bypass a duplicate warning. Consistent names also matter when matching later meet entries and results.
Keep email addresses, guardian details, birth dates, health notes, and PRs out of the roster template. They are not mapped by this import. Use the appropriate account, roster, or results workflow for information your program actually needs.
Review the full file, then the preview
Open Import CSV, choose Roster, and select the file. Match Athlete name, Roster, and Training group to the intended columns. Choose the default roster and group for blank or unmapped fields.
Compare the detected row count with your spreadsheet. A mismatch can reveal a forgotten athlete, an extra header, or a malformed row. Then inspect the preview for names, group spelling, and defaults. The preview shows only the first 20 rows; validation checks the complete imported set. Review the later rows in your source file too.
Resolve every warning before saving. If the current roster or meet lookup cannot load, reconnect and use Retry. Treat a failed lookup as unavailable data, not as evidence that the team is empty.
Check the result before assigning work
The roster import saves all rows together. A duplicate, nonexistent group, capacity problem, or invalid row prevents that file from being partially imported. Wait for the success message, then check the roster count and a few records from the beginning and end of your file.
Open the relevant groups and confirm membership. A row imported as Unassigned is a valid roster record, but it may still need placement before you select a training group for a workout.
Account access is a separate step. Importing a name does not establish that an athlete can sign in or see an assignment. Complete the team's account-linking process and verify access before using the workout sharing checklist.
Handle an uncertain save without creating confusion
If the connection drops after you press Import, check the roster after reconnecting before submitting again. The server may have saved the file even though the confirmation did not reach your screen. The import screen does not automatically repeat an uncertain write.
Compare names and counts with the original file. A repeat submission that matches active athletes should be rejected as duplicates, but that message does not tell you whether every earlier setup choice was correct. Inspect the records and resolve the uncertainty before moving on.
Choose the right import for the job
PaceCommand has separate CSV workflows for rosters, meet entries, and meet results. Results can include event, mark, timing method, wind, round, heat, lane, and notes. A track-meet column preset helps map downloaded Athletic.net-style files; it is not a connection to a meet account.
Finish and verify roster setup first so later files can match athletes correctly. If your decision is whether to leave an existing workbook, compare the full workflow in PaceCommand versus spreadsheets, including the work you will still do to keep names and records consistent.