Bulk-Import Tournament Data with a Ready-Made CSV Template
You exported a fixture list from your old tool. The column names are in your native language — Hazai, Vendég, Időpont. You upload to Score7. Every row comes back as "unknown column". The validator can't help — every field is a mystery to it.
That problem just disappeared. Score7's CSV import dialog now has a Download an example CSV link that gives you a working template — the exact column names Score7 expects, plus a couple of placeholder rows you can replace with your own data. No more guessing the column list; no more rebuilding the file three times.
Where to find it
The link sits at the top of the CSV import dialog. There are two places that dialog opens:
- Round-robin schedule import — on a round-robin stage, open the Import / Export CSV menu and click Import. The dialog shows "New here? Download an example CSV to see exactly what columns we expect" with the download link inline.
- Teams (with players) import — on the Participants page when "Teams with player lists" is enabled, click Import CSV. Same affordance.
Click the link, save the .csv file, open it in Excel, Google Sheets, or any text editor. The template doubles as a column-list reference and as a starting file.
Walkthrough — round-robin schedule
Open the round-robin stage, the import dialog, and click the link. You get score7-round-robin-league-template.csv (or score7-round-robin-groups-template.csv if your tournament uses multistage with groups). The header row is:
leg,day,datetime,location,referee,home_participant,away_participant,home_scores,away_scores,outcome
(For groups variants, the row starts with group.)
Below the header, the template has six example matches — a full round-robin between four placeholder teams (Team A, Team B, Team C, Team D) across three days. Datetimes use the ISO format Score7 understands (2026-05-01T18:00:00). Scores and outcomes are left blank — the importer accepts that as "match not played yet", so the template doubles as a schedule-only seed.
Steps from here:
- Open the template in Excel or Google Sheets.
- Replace
Team A/Team B/Team C/Team Dwith your registered participants. Spelling has to match the names you registered. Score7 validates participant names against the tournament's registered list. - Edit the datetimes to your real schedule. Keep the ISO format (
YYYY-MM-DDTHH:MM:SS). - Edit
locationandrefereeif you have them. Leave blank if not. - Save the file (keep it as a CSV) and upload it back through the import dialog.
If your tournament uses multistage round-robin, your template has a leading group column with numeric values (1, 2). Use numbers, not letters — Score7 validates the group column as an integer first.
Walkthrough — teams with players
For team imports, the template is score7-teams-with-players-template.csv. The header row is:
team,player,playerLabel
The template has two teams (Team A, Team B) with three players each. The first player per team has playerLabel: Captain; the rest have empty labels.
playerLabel is up to 4 characters — typical use is a jersey number (10, 7) or a short role tag (C for captain, GK for goalkeeper). Leave it blank if you don't track that.
Same workflow as above: replace the placeholders with your real teams and players, save, upload.
Why the example rows matter
The template isn't just a list of column names — the placeholder rows show you exactly:
- The datetime format Score7 accepts (
2026-05-01T18:00:00, not01/05/2026 18:00). - Which columns can be blank — the importer is happy with empty
home_scores/away_scores/outcome/referee. - Which group code style to use (numeric
1/2, not letters). - Where the captain label goes in the players file.
That's information you'd otherwise have to learn by failed-upload-and-error-message. Starting from a working file skips the round trip.
Pro tip: dry-run with the template unchanged
If you want to verify that the import pipeline works on your account before editing anything, register four participants named exactly Team A, Team B, Team C, Team D (or just Team A, Team B for the teams template), then upload the downloaded template unmodified. Validation should pass on the first try.
It's a five-minute sanity check that proves the round-trip works before you spend an hour preparing your real data.
Where we're going
We're slowly moving Score7's CSV import experience from "guess what we want" to "here's a working file, edit and re-upload". This template download is the first step. Earlier in 2026, we shipped semicolon and tab auto-detection for non-English Excel exports, plus much clearer per-row error messages when validation does fail. Coming next: a dedicated CSV format reference page with the full column glossary in nine languages.
Got a CSV import problem we haven't solved yet? Reach out — the export/import workflow is one of the areas we actively iterate on with organizer feedback.