The MyAthlete Competition & Entry Management System treats competition data as a Linked Reality rather than a series of typed-in numbers. By doing so, it protects the club’s integrity, guarantees clean SD3 exports, and saves coaches hours of manual verification.
1. The Architectural Choice: "Linked Reality"
Most platforms treat a meet entry as a static text field. A parent types in "1:05.20," and the system accepts it blindly, leading to disputed "phantom times."
MyAthlete uses Seed-Swim Linking. Every entry is a foreign key pointing to a specific, verified result in the Self-Healing Database.
- The Forensic Audit Trail: When a coach or meet host views an entry, it is a "Living Link." One click reveals the exact meet, date, and split breakdown of the performance that earned the entry.
- Unimpeachable Reputation: Fraudulent entries and typos are mathematically impossible, ensuring your club's submissions are always trusted by meet stewards.
2. The Validation Engine: Hard-Gate API Integrity
While competitors rely on users to manually check qualifying PDFs, MyAthlete enforces the rules at the Serializer/API level.
- Eligibility Logic: The system cross-references the meet’s "Times Since/Till" and "Qualifying Standards" against the athlete's PB history in milliseconds.
- The Hard Gate: If an athlete is too young, too old, or too slow, the entry is blocked at the request level. The system physically refuses to create an invalid record.
- Equivalent Time Algorithm: MyAthlete features an industry-standard, physics-based conversion engine. If a meet is Long Course (50m) but the athlete only has Short Course (25m) times, the system calculates the mathematically precise converted seed time automatically.
3. The Workflow Pipeline
MyAthlete digitizes the natural hierarchy of a swimming club to ensure no data is sent to a host without professional oversight.
Stage 1: The Parent/Athlete Portal
Users see a clean matrix of the events they are eligible to swim. The standout feature here is Transparent Rejection (the "Why Not" feature). It explicitly explains rejections (e.g., "You are 0.2s outside the 1:04.00 standard"), drastically reducing the "Why wasn't my child entered?" emails to admins.
Stage 2: The Coach Review Dashboard
This is the "Safety Valve." Coaches can approve or reject entries in bulk or individually. Manual Overrides (like "No Time" entries or coach-estimated times) are strictly reserved for coaches and are visually flagged to separate them from verified database swims.
Stage 3: The "Lock" Mechanism
Once approved, an entry is frozen. A parent cannot retract or change an entry five minutes before the export file is generated, preventing the corruption of the final SD3 file.
4. The "Relay Architect": Solving the Hardest Math
Relays are traditionally a nightmare of manual calculation and age-group checking. The Relay Architect automates this entirely.
- Auto-Optimization: The system automatically calculates the best realistic team time based on individual PBs.
- Rule Enforcement: It strictly enforces gender and age-group combinations—even in complex "Mixed" or "Combined Age" events—preventing devastating "DQ-on-entry" scenarios.
5. The "Hidden" Advantage: Financial Handshaking
Because the Entry System is part of the integrated MyAthlete OS, it talks directly to the Financial Engine.
The moment a Coach clicks "Approve" on an entry, a financial trigger is pulled. The Finance Hub sees the approved swim, applies the club's defined Surcharges (handling fees), and places a pending liability on the family’s Temporal Ledger.
Ending the "Chasing Money" Phase
This integration eliminates manual gala invoicing. You don't swim if you haven't been billed, and you aren't billed unless the Coach says you're ready to race. When the monthly billing cycle runs, the batching engine sweeps up these entry fees automatically.
6. Legacy Systems vs. MyAthlete OS
| Feature | Legacy Standard (e.g., Hy-Tek, TeamUnify) | The MyAthlete Way |
|---|---|---|
| Integrity | "Trust the user." High risk of typos or faked times. | Verified. Entries are cryptographically linked to the Healed DB. |
| Effort | Admins manually check PDFs vs. athlete lists. | Automated. Eligibility is checked in milliseconds at selection. |
| Reporting | Basic text lists that often lack detail. | Rich PDFs. Professional Eligibility and Entry reports ready for the deck. |
| Interoperability | Files often "break" upon import for the host. | Pre-Validated SD3. Guaranteed 100% import success. |