![SwimSquad. Behind every swim, a whole squad.](https://swimsquad.pplx.app/assets/swimsquad-logo-tm.jpg)

# SwimSquad School Meet Template

Version 1.1 | 7 October 2026 | School administration and meet preparation

This package provides a macro-free Excel workbook, matching CSV tables, a fictional worked example and an offline import/export validator. The School Gala's application area supports template uploads, direct meet entry, printable meet sheets/results, school performance and squad management. Sign in to SwimSquad and choose School Gala's from the main menu.

## What is included

- **Blank Excel workbook:** Meet setup, Schools, Age Groups, Swimmers, Events, Entries, Relay Legs and Results, plus a calculated Age Sheet, HY-TEK roster view, event catalogue, field dictionary and interoperability references.
- **CSV templates:** One file for each of the eight input tables, with matching field names and a single header row. Use the whole folder for a full meet exchange.
- **Fictional example:** Demonstrates all four strokes, individual medley, a medley relay, an age-based group, a school-year group, a no-time entry and a pupil without a membership number or DOB. No actual pupil data is included.
- **Offline exchange tools:** `exchange.py` and `schema.py` support validation, Excel/CSV/JSON conversion, documented HY-TEK roster CSV export and HY-TEK roster CSV staging import.

## School workflow

1. Make a new copy of the blank workbook for each meet. Assign a stable `meet_id`, meet date, age-as-at date and pool length.
2. Add participating schools and their organiser-approved team codes. School staff must confirm each pupil's affiliation.
3. Define age groups on **Age Groups**. Use inclusive minimum and maximum values, with `Age`, `School year` or `Open` as the basis. These are meet-defined categories, not assumed ESSA or Swim England rules.
4. Add pupils on **Swimmers**. Every pupil needs a `swimmer_id`; use a school-specific identifier, not a national pupil number. A genuine Swim England number is optional. Keep it as text to preserve leading zeros.
5. Use **Events** to choose stroke, total distance, individual or relay, age group, competition category, session and round. The dropdown offers common distances, but custom positive metre distances can be entered. The validator checks whole pool lengths and four-stroke individual-medley geometry.
6. Add **Entries**, using stable event and pupil IDs. Keep selected, reserve and withdrawn records distinct. For a relay, leave `swimmer_id` blank and enter the relay team label; assign swimmers and order on **Relay Legs**.
7. Record **Results** separately from seed times. Use `OK`, `DQ`, `DNS` or `DNF`; non-finish statuses have no numeric time. Keep provisional and approved results distinct.
8. Validate before transfer. Resolve every error and review warnings. The tool performs checks beyond Excel dropdown validation; pasted cells can bypass Excel's data-entry controls.

### Timing and eligibility conventions

- **Times:** Decimal seconds throughout: `83.45` means 1 minute 23.45 seconds. Do not type `1:23.45` into numeric seconds columns. `NT` is a separate seed status, not zero.
- **Course:** Record the actual pool length in metres; the package does not convert short-course, long-course or local school-pool times.
- **Age:** The Age Sheet uses the explicit meet age-as-at date. DOB takes priority. An organiser-confirmed age may be supplied instead when DOB is not collected; the organiser must reconfirm it if the cutoff changes.
- **School years:** Use the school's confirmed year group. Never infer it from DOB alone.
- **Categories:** The template labels are operational fields, not an eligibility policy. A category mismatch is blocked for organiser review. A mixed relay's required composition must be checked manually; no gender ratio is assumed.
- **Scope:** Pool swimming only. The event catalogue covers freestyle through 1,500 m; backstroke, breaststroke and butterfly through 200 m; 100/200/400 m IM; and freestyle/medley relays. Local 25 m races are included. Para-specific 150 m medley and classification rules are not implemented by the standard four-stroke IM validator; do not re-label them as ordinary IM. Open water, diving and artistic swimming are outside this template.

## HY-TEK and Meet Manager compatibility

### Supported now: documented roster CSV

Meet Manager publishes a roster CSV layout containing the eight headings below; the roster import does not contain meet-entry times. The `Swimming ID` column must be first and represents the Meet Manager registration ID. ([HY-TEK MM8 roster documentation](https://hytek.active.com/user_guides_html/swmm8/importrosters.htm))

```text
Swimming ID,Athlete First Name,Athlete Middle Name,Athlete Last Name,Athlete Gender,Athlete date of birth,Team name,Pref name
```

The workbook's **HYTEK Roster** sheet maps into that layout. The offline exporter writes populated pupil rows only, checks DOB and category mapping, and requires an explicit date-format choice. Use the `registration_id` field agreed with the meet organiser; the template never manufactures a membership number or silently substitutes a local pupil ID.

Manual athlete entry in Meet Manager describes registration ID as optional, but this is not proof that every version/configuration accepts blank IDs in CSV import. The exporter blocks blank IDs by default; `--allow-blank-id` is available only after the organiser has tested and approved that case. ([HY-TEK athlete setup](https://hytek.active.com/user_guides_html/swmm8/addathlete.htm))

The CSV importer stages source rows, retaining team name, registration ID, middle name and DOB. It deliberately leaves school ID, swimmer ID and Swim England number unmapped: a source team may be a club, a registration ID may not be a Swim England number, and a name is not a safe identity key. Human review is required before moving rows into the main workbook. The canonical roster has no middle-name column; retain the staging record if needed rather than silently discarding source data.

### Native event, entry and result files: not yet implemented

The documented vendor workflow is: the host exports **Events for TM**, the school imports those events into Team Manager/TM Lite, the school exports its meet entries, and the host imports those entries into Meet Manager. The organiser's event numbering should remain authoritative. ([Public Team Manager instructions](https://www.lhsaa.org/siteuploads/editorimg/file/Swimming/Hytek_Instructions_revised2.pdf))

Meet Manager's results export can produce a ZIP containing CL2 and HY3 files, with differences in the information those formats retain. A results export is not interchangeable with a roster or an entry export. ([HY-TEK results-export documentation](https://hytek.active.com/user_guides_html/swmm7/exportresultstotm.htm))

SD3 is not used as a universal substitute here: HY-TEK describes it as USA Swimming-oriented and states it omits fields/functions present in CL2/HY3. ([HY-TEK conversion documentation](https://hytek.active.com/User_Guides_HTML/SwTM8/HTML/converthy_tekexportfileto.htm))

**This package does not parse or generate native HY3, CL2, EV3, SD3 or Meet Manager database backups.** It rejects these inputs rather than silently claiming a successful import. No compatibility certification or successful round-trip through the proprietary software is claimed. Do not rename a CSV or Excel file to a native extension.

Before implementing native support, obtain an anonymised event export, entries export and results export from the target Meet Manager/Team Manager versions, together with the organiser's ID and category conventions. Test individual races, relay order, no-time entries, DQ/DNS/DNF, rounds, course, duplicates, missing IDs and corrections; compare counts and values after import back into Meet Manager.

## Using the offline tools

Requirements: Python 3.10+ and `openpyxl` for Excel conversion. The scripts use local files only; they do not contact Swim England, HY-TEK or SwimSquad servers. Run from the extracted package folder.

```bash
python -m pip install openpyxl

# Validate a completed workbook. Exit code 2 means errors; nothing is exported.
python exchange.py validate "Completed_Meet.xlsx"

# Export all eight canonical CSV tables.
python exchange.py to-csv "Completed_Meet.xlsx" --output "completed_csv"

# Prepare a versioned JSON record for app ingestion.
python exchange.py to-json "Completed_Meet.xlsx" --output "completed_meet.json"

# Load a completed CSV folder into the formatted workbook.
python exchange.py to-xlsx "completed_csv" \
  --template "SwimSquad_School_Meet_Template.xlsx" \
  --output "Imported_Meet.xlsx"

# Export a roster for a host who has confirmed this date format.
python exchange.py to-hytek-roster "Completed_Meet.xlsx" \
  --date-format "%d/%m/%Y" --output "Meet_Manager_Roster.csv"

# Import a documented eight-column HY-TEK roster into a review staging file.
python exchange.py from-hytek-roster "Meet_Manager_Roster.csv" \
  --date-format "%d/%m/%Y" --output "Roster_Review.json"
```

Use the host-confirmed date format (`%Y-%m-%d`, `%d/%m/%Y` or `%m/%d/%Y`) rather than guessing. The CSV staging importer expects all eight column headings, including the two optional columns with blank values if unused. Reopen a newly generated workbook in Excel to recalculate its calculated views. Input tables have 300 prepared rows each; the import tool rejects larger datasets rather than leaving validation or formulas incomplete. It does not overwrite live application records.

## School Gala's application workflow

1. Sign in and choose **School Gala's**, then create a named school workspace. Workspaces are private to the signed-in account, not to the club selected elsewhere in SwimSquad. Anyone sharing that account can access its school workspaces; use a separate coach account for each school.
2. In **School Meets**, create a meet directly or upload the completed `.xlsx` template or version 1.0 canonical meet JSON. Review table counts and added/changed rows before importing. Changes match stable IDs; missing rows do not delete saved records. Keep the eight worksheet headers in row 6, starting in column B.
3. Edit the Meet, Schools, Age Groups, Swimmers, Events, Entries, Relay Legs and Results tables using **Add row** and **Edit**. Save the workspace to retain changes. Server validation is all-or-nothing, with revision checks to prevent stale updates.
4. Print **Meet sheet**, **Results**, or **Both**. Meet sheets include draft heats/lanes and blank timing fields. Coaches must verify allocations and relay eligibility. Results retain provisional/approved and timing-method labels. Printouts omit dates of birth and membership numbers.
5. In **School Squad**, add pupils with a school-specific ID, with or without a Swim England number. Track active/inactive status and training group. DOB is optional; use an organiser-confirmed age and explicit cutoff where needed. Add the active squad to a meet and reconfirm ages if its cutoff differs.
6. In school **Swimmer Performance**, choose the pupil, event and actual pool length. Approved and provisional school results are distinguished. Optional Swim England numbers link only to records already held in the two club datasets, after name/category/birth-year checks. This is not a nationwide membership search; no name-only matching or school affiliation inference occurs.
7. Download completed Excel, the selected table as CSV, or canonical meet JSON. The offline tools remain necessary for complete CSV-folder import and HY-TEK roster CSV staging/export. Native HY3, CL2, EV3, SD3 and database backups remain unsupported.

### Storage and safeguards

Uploads are limited to 5 MB, 300 rows per input table, 300 squad members and 30 meets per workspace. Input formulas, macro-enabled/unsafe archives and invalid records are rejected. Original uploaded files are not retained. Workspace save audits record account, timestamp and revision, not complete per-cell edit history.

School storage is local to the application server and can be lost during redeployment. Download completed meet files and a workspace JSON backup regularly. A workspace backup is an archival export, not an automatic restore facility in this version; canonical meet JSON and Excel can be reimported. A coach can permanently delete a whole workspace by typing its name.

The feature does not change club membership registers, publish pupil records publicly, or turn school swims into official rankings or qualifying evidence. Obtain the school's appropriate permission and agree retention before storing real pupil records. Review and approve any printed or externally shared results separately.
