Operations & Season Planning

The Physics-Aware Command Center. Move away from static event management and step into true Operational Orchestration using Template-to-Instance architecture and automated conflict resolution.

While legacy platforms treat a club schedule as a static "Digital Calendar" (essentially a shared Google Calendar with a sports logo), MyAthlete treats the season as a Dynamic Model. The architectural core of this suite is the Template-to-Instance State Machine.

1. The Season Builder: Template-to-Instance Architecture

The Season Builder is your primary "Force Multiplier." Instead of manually creating 300+ individual sessions, an admin builds a single Model Week.

  • The Architectural Choice: In MyAthlete, a session doesn't exist as a "Standalone Event" until it is Projected. You define a "Golden Week" (The Template) that includes the Squad, Coach, Location, and Time.
  • High-Speed Projection: The system's projection logic allows the engine to generate an entire 40-week season in under 10 seconds.

2. The Bulk Action Tool: Surgical Database Manipulation

Maintenance is the "death by a thousand cuts" for club secretaries. If a pool closes for maintenance every Tuesday in November, legacy systems require tedious manual deletions. MyAthlete treats sessions as a queryable database.

Filter-Based Execution

Use Boolean logic to perform surgical edits across the entire season in seconds.

Logic: Filter (Day=Tuesday) AND (Month=November) AND (Squad=Gold) → ACTION (Cancel)

Historical Integrity & Session Realization

In MyAthlete, once a session passes in time, it becomes a "Realized Session." It is permanently detached from the template. This means editing future sessions (e.g., changing a start time from 06:00 to 06:15 for the rest of the year) will never accidentally wipe out past attendance data or coaching logs. This "locking" of history is a professional-grade ERP feature.

3. The "Physics" Engine: Hard vs. Soft Conflict Detection

This is where MyAthlete blows the competition out of the water. Competitors allow you to book a coach for 4 sessions at once because they lack an Identity-Aware Logic Layer. MyAthlete understands the physical constraints of a pool deck.

The system runs a validation check on every session creation (Individual or Bulk) against two constraint levels:

  • Hard Conflicts (The Impossibles): A coach cannot be at Pool A and Pool B simultaneously. A squad cannot be in two different sessions at once. The system strictly Hard Blocks these actions to prevent the "Double-Booking Nightmare."
  • Soft Conflicts (The Co-locations): Two squads can share a pool if lane counts allow. The system Flags these for admin review but permits the action.

4. POD (Parent On-Deck) & The Fairness Algorithm

Volunteer rostering is usually a major source of club politics and "burnout." MyAthlete removes human bias via a Mathematical Fairness Model.

  • The Algorithm: It assigns duties based on Weighted History, prioritizing parents who have done the least work, ensuring the "Duty Burden" is spread perfectly across the club.
  • Compliance Integration: The algorithm talks to the Compliance Hub, ensuring it only assigns parents who have a "Green Status" (fully vetted and qualified).

P2P Sovereignty

Parents can initiate Swaps or Offers directly in-app. The system handles the "Handshake," updates the roster, and sends the notification. The Admin doesn't have to be the middleman for a simple shift change.

5. The "Golden Thread" Integration

The true power of this section is its Downstream Impact. It is a closed-loop system where the Operation directly feeds the Financials and the Performance records.

  1. The Season Builder creates the sessions.
  2. The POD System staffs them with compliant volunteers.
  3. The Attendance Engine tracks swimmer participation.
  4. The Finance Hub uses the resulting SquadLog to calculate the pro-rated bill.

6. Legacy Systems vs. MyAthlete OS

Feature The Legacy Way (Excel / TeamUnify) The MyAthlete Way
Setup Days of manual entry / Copy-Paste. 10 Minutes via Template Projection.
Schedule Changes Manual "one-by-one" edits; high risk of error. Surgical Bulk Edits with Template Syncing.
Double Bookings Discovered on the pool deck at 6:00 AM. Prevented at Ingestion by the Physics Engine.
History Changing a recurring event often deletes past data. Session Realization locks history permanently.
Rostering Messy spreadsheets and angry emails. Automated Fairness with self-service P2P swaps.