Pilot plan.
Build to track one.

Actual usage

• Run a live race day on the current event flow
• Validate registration, class assignment, and check-in under real load
• Capture operator notes from first usage

Refinement

• Tighten admin screens based on floor feedback
• Clean up edge cases from real registrations
• Document repeatable race-day setup

Repeatable track flow

• Package setup for next pilot track
• Create migration checklist for events and classes
• Confirm full registration-to-grid handoff

Polish current dashboard

• Refine profile, garage, waivers, and registration history
• Close usability gaps from racer account testing
• Make race-day state clear to racers

Managed users

• Build guardian and managed-racer relationships
• Clarify account switching and permission boundaries
• Connect managed racers to waivers and entries

Pilot hardening

• Stress-test family and multi-racer accounts
• Add support workflows for account recovery
• Prepare racer onboarding for pilot track

Team model

• Define team, roster, guardian, and linked-racer structure
• Build team-level permissions
• Connect teams to race entries

Cost management

• Add team cost tracking for entries, passes, and shared spend
• Clarify billing responsibility across team users
• Expose cost summaries to operators

Race-day team ops

• Support team check-in and roster changes
• Validate team flows during a live event
• Prepare team admin guide for pilot

Bridge from manual

• Stabilize current manual import/export flow
• Map MYLAPS X2 entities to KOS events, sessions, racers, and classes
• Define scoring and penalty data model

MYLAPS X2 sync

• Implement live timing sync from MYLAPS X2 server
• Persist results and session timing into KOS
• Add penalty application and result correction tools

Championship layer

• Calculate championship points from synced results
• Publish results and standings to racer dashboard
• Run full registration-through-scoring pilot day

Discovery + model

• Define kart asset model and service history
• Map inspection records and incident linkage
• Identify renewal evidence requirements

Maintenance v1

• Build work orders, inspections, and kart service logs
• Track parts usage and maintenance status
• Connect incidents to follow-up work

Evidence layer

• Create renewal-ready maintenance exports
• Add operator dashboards for overdue work
• Validate CMMS against real fleet history

Retail storefront plan

• Define Shopify-style storefront structure
• Map product catalog, categories, variants, and inventory
• Separate retail commerce from service workflows

Storefront v1

• Build retail product pages and cart flow
• Support passes, memberships, gift cards, apparel, and parts
• Connect purchases to the customer record

Operator commerce

• Add order management and fulfillment views
• Tie inventory updates back to track operations
• Validate retail storefront with pilot catalog