To ensure that training data and metrics are interpreted consistently, we have summarized the most important terms and framework conditions. These explanations apply to all evaluations and reports on this platform.
A load profile summarizes the physical strain of an athlete over a defined period. It records running performance, sprint shares, heart rate zones, and subjective recovery information. The values are always considered in relation to the individual baseline, not as an absolute norm.
A training cycle begins with the first documented session after a competition phase and ends with the next planned load test. The length can vary depending on the sport and season phase. By default, cycles of four to six weeks are evaluated, unless a different configuration is stored.
The analysis is based on GPS tracking, heart rate measurements, manual coach entries, and questionnaires on perceived exertion. Data from external devices without interface authorization are not considered. The origin of each metric is transparently disclosed in the report.
If more than twenty percent of the planned measured values of a cycle are missing, the evaluation is marked as preliminary. Coaches then see a notice before using the results for training control. No automated extrapolation takes place.
The availability of facilities, equipment, and support staff is included in the planning of training sessions, but not in the individual performance assessment. Resource conflicts are reported separately so that they are not confused with athletic metrics.
The underlying calculation models are reviewed at least once per season. Changes to thresholds or formulas are documented in the change log. Historical reports remain available in their original version so that comparisons over time remain traceable.
Our platform consolidates training data, load profiles, and organizational resources into a single interface. You can see at a glance where your team stands and where you need to make adjustments.