← Back to 2Timer

2Timer Help

Practical guides for humans, with structure that is easy for AI systems to parse.

Creating a Meet from a Hy-Tek Meet File

Build a new 2Timer meet from a Hy-Tek Meet Manager export: the meet’s details, divisions, events, teams, athletes, and entries in one reviewed step. On the home screen, drop the file on Import a meet or press Choose file: 2Timer recognises a Hy-Tek meet file and opens New meet from a Hy-Tek meet file with it read.

Which Hy-Tek file to use

Export the meet records from Meet Manager (File → Export): the semicolon-delimited .txt or .hy3 file, or the recognised record .csv. Other meet software that writes the same semicolon format works too. Export the file itself, not a .zip.

A Hy-Tek backup (the Meet Manager or Team Manager database, or a .zip holding it) isn’t a meet file: 2Timer says so and asks you to export the meet from Meet Manager (File → Export) instead.

A fixed-width team/athlete list (.tcl) is a roster only. Create the meet first, then use the Hy-Tek team/athlete list import in the meet. See Importing Data.

Create a meet from a Hy-Tek file, step by step

The steps are File, Details, Divisions, Events, Systems, Review, and Done.

  1. File: choose the export. If it isn’t a Hy-Tek meet file, 2Timer says so: export the semicolon-delimited file from Meet Manager and try again. When a meet on this device has the same name and date, the step says it is probably for that meet, with Add to that meet preselected (see Add a Hy-Tek file to a meet you already have).
  2. Details: the meet’s Name, Sport, Genre, Start Date, End Date, and venue. The name and dates come from the file, and the sport is guessed from it: check it, because it decides how the meet works. If a meet with that name already exists, choose Use the suggested new name, or Open the existing meet instead.
  3. Divisions: in a track meet, match each Hy-Tek division to a division; in other sports, name the new divisions.
  4. Events: check the names, types, and rounds of the events the file creates.
  5. Systems: how you’ll time the meet, and its registration, results, and scoreboard, the same step as a meet started from scratch (see Saved Systems and New Meets).
  6. Review: tick Athletes, Teams, Events, and Entries, answer any questions (below), and check the systems. Nothing is created until you press Create meet and import ….
  7. Done: Go to the meet, or Import another meet file.

Cancel at any step goes back to the home screen and leaves no meet behind.

Questions the Hy-Tek review asks

  • Where did this file come from? When the athletes carry registration numbers, pick the system they’re from, such as Athletic.net or MileSplit, or Other. It starts at Other.
  • How should the conflicts be handled? Only when rows in the file conflict with each other, for example two athletes on one bib. Skip the rows that conflict is recommended.

Both are explained in Importing Data.

What a Hy-Tek file creates

The new meet gets its divisions, events, teams, athletes, and entries from the file, and relay entries in a track meet. Any sport works: road race (Running), Cross Country, and Indoor or Outdoor Track & Field.

After it is created, finish the meet as usual: check Setup, number bibs, seed track events, and set up timing. See Getting Started.

Add a Hy-Tek file to a meet you already have

To bring a Hy-Tek file into an existing meet, use Import… on the meet’s dashboard and choose Hy-Tek meet file. A file you bring to Import a meet on the home screen gets there too: on the File step choose Add to the meet 2Timer suggests, or Add to a meet I already have and pick it, and the meet’s Hy-Tek import opens with the file already read. Start a new meet is still there if you want a second meet. Importing the same file again updates the matching records instead of adding duplicates. Teams only on the same card brings just the teams. See Importing Data.

If the meet already lives in 2Timer on another device, use its .2t backup instead: see Importing a 2Timer Backup.

Metadata

  • Last Updated: 2026-10-24
  • Document Version: 0.5
  • Status: Active