SwimMeetOS · compatibility and rehearsal

Check the files and the pool before the first race.

A successful switch depends on your programme rules, the files clubs send and the venue’s timing setup. Bring representative examples and rehearse the whole route with Lewis.

Active testing · rehearse your meet before switching

What each route covers.

Existing meet setup → SwimMeetOS

Import a Meet Events ZIP or EV3 file into an editable draft. Check days, sessions, age groups, event order, prices and standards. This is setup transfer; swimmers, entries and results are separate.

Club entries → SwimMeetOS

Entry import supports HY3, SD3 and CSV, including ZIP files containing a supported entry file. HY3 and SD3 include relay routes; CSV is an individual-entry route. Check actual exports, identifiers and relay details in rehearsal.

SwimClubOS → meet host

Clubs can import EV3 meet templates and export HY3 entries. Check the host’s event numbers, course, eligibility and entry requirements before submitting the club file.

SwimMeetOS → result recipients

Export routes include HY3, SD3, CL2 and team results ZIPs, alongside CSV and PDF reports. Rankings exports include neutral and Lenex routes. Agree the receiving system’s required format and validate a sample before relying on acceptance.

SwimMeetOS → Quantum-AQ

The generated timing pack includes a schedule and seeded start list. Individual layouts have been checked against a supplied Meet Manager 8 sample. Relay rows, suffixed events and the venue’s software version require validation.

Timing feed → scoreboard bridge

Meet Run includes a token-controlled scoreboard bridge route. A bridge endpoint is not a promise that every timing device connects directly. Rehearse the exact adapter, equipment, network and result-confirmation workflow with the venue.

Prepared offline operation.

  1. Load the meet online on the operator’s device.
  2. Use Prepare offline and confirm the snapshot is ready.
  3. Rehearse result changes and a lost connection.
  4. Reconnect, synchronise and resolve any conflicts.
  5. Check that public results reflect confirmed, synchronised work.

Meet Run uses a local snapshot and queued changes. It is not a cold-start offline application. Public pages update after online synchronisation; an emergency export gives the operator a recovery route.

A race-day readiness review

  • Sessions, event order and entry eligibility
  • Relay structure, finals and scoring
  • Representative club entry imports
  • Seeding, heat sheets and reports
  • Timing hardware, files and bridge route
  • Result status, official and publish steps
  • Offline recovery and a fallback system
  • Result and rankings export acceptance

Comparing with your current system.

Use the tasks above to compare the exact workflow you use, rather than assuming another product lacks a feature. HY-TEK offers web and Meet Mobile result routes; Swim Club Manager supports competitive-club operations; TeamUnify is now SportsEngine Motion.

What matters is how programme setup, entry handling, finance, family access and race-day work fit together for your club. Ask Lewis to demonstrate those tasks with your representative files.

Product references: HY-TEK, Swim Club Manager, SportsEngine Motion.

Start with a conversation

Make your rehearsal specific.

Send Lewis the programme format, entry file types, timing equipment and required result exports. We can agree what needs checking and demonstrate the relevant workflow.