Trainingload.ai

Trainingload.ai Documentation

Learn how to connect training data, create and execute endurance or strength plans, review activities, interpret load and performance, and use AI Coach with evidence.

Trainingload.ai Documentation

Trainingload.ai connects five parts of the training workflow:

  1. Profile context — thresholds, zones, units, sport settings, and current state.
  2. Planned work — endurance or strength workouts arranged in a training plan.
  3. Completed activities — recorded, synced, or uploaded evidence of what actually happened.
  4. Analysis — load, power, pace, heart rate, activity history, and plan-versus-actual review.
  5. Decisions — athlete-confirmed plan actions and AI Coach recommendations grounded in the available evidence.

The documentation is task-first. Use the guides to complete a workflow, the Planning section for workout and plan behavior, and Metrics when you need a definition or interpretation boundary.

Choose your route

Your goalStart hereFinished state
Set up a new accountGetting StartedA calibrated profile and one Ready activity
Continue between web and mobileWeb and MobileThe same plan, activity, and account state is visible on both devices
Record on mobileMobile RecordingA safely saved recording synchronizes as an activity
Build an endurance or strength planCreate a Training PlanA reviewed plan is saved and ready to activate
Execute a current planManage an Active PlanPlanned workouts have intentional statuses and completed activities are linked
Review one completed workoutActivity DetailThe source data, load, charts, and plan context have been checked
Answer a performance questionPerformance Analysis PagesThe page, sport, time range, and source activities support a traceable result
Turn evidence into a plan decisionTraining Analysis WorkflowOne conservative, reviewable action is defined
Configure account, permissions, or AI usageAccount, Permissions, and AI UsageIdentity, data-source status, automatic updates, membership, and usage are verified

If you are unsure, use Choose Your Path or take the Product Tour.

The core training loop

The loop is deliberately conservative. A chart or AI message does not silently rewrite a plan. Check the source activity, distinguish observed data from interpretation, and confirm any action that changes future training.

Set up trustworthy inputs

  • Profile, Thresholds, and Zones — configure time zone, units, benchmarks, load-source priority, and sport-specific zones.
  • Connect Data — understand providers, file upload, processing states, and sensor coverage.
  • Integrations — connect supported services and prevent duplicate import paths.
  • Upload Activity Files — import GPX, TCX, or FIT files and resolve batch errors.

Missing or unreliable input data should remain explicit. The product cannot recover a power stream, GPS route, or heart-rate signal that the source never provided.

Plan and execute training

Interpret metrics carefully

The Metrics section explains training load, PMC, power, pace, heart rate, and physiology concepts. Metric pages state what a value describes, which inputs it depends on, and where interpretation can fail.

In particular, CTL, ATL, and TSB describe modeled training-load history. They do not independently prove adaptation, fatigue, recovery, readiness, or medical status.

Use AI Coach with evidence

AI Coach can review activities, plan execution, trends, and proposed changes. A useful request includes the decision, time range, sport, constraints, and evidence to inspect. Keep high-impact actions confirmable and review the before/after state.

For a complete example, follow AI Marathon Plan Adjustments.

When something does not match

Use Troubleshooting for missing activities, processing delays, empty charts, connection problems, plan-link issues, and safe support diagnostics. Do not include passwords, OAuth tokens, API keys, private email addresses, or precise home locations in support material.

Start

Begin with Choose Your Path, or open Trainingload.ai if your account is already configured.