How should test fatigue be managed when collecting normative data?

How should test fatigue be managed when collecting normative data?

• A. Testing should occur when rested and fresh to avoid underestimating performance.
• B. Test immediately after a heavy workout.
• C. Fatigue is irrelevant.
• D. Test only in the evening.

Answer: (B)

Fatigue strongly alters performance, so when building normative data you want a standardized state of fatigue across all testers. Testing immediately after a heavy workout imposes a uniform high-fatigue condition, allowing you to compare athletes on a level footing and to quantify how fatigue reduces performance. This approach mirrors real training and competition where athletes often perform while fatigued, making the norms more applicable to typical conditions. Resting before testing would yield peak, unfatigued performance that isn’t representative of many real-world scenarios, and claiming fatigue is irrelevant or relying on evening timing don’t ensure the same fatigue level for everyone.

Fatigue strongly alters performance, so when building normative data you want a standardized state of fatigue across all testers. Testing immediately after a heavy workout imposes a uniform high-fatigue condition, allowing you to compare athletes on a level footing and to quantify how fatigue reduces performance. This approach mirrors real training and competition where athletes often perform while fatigued, making the norms more applicable to typical conditions. Resting before testing would yield peak, unfatigued performance that isn’t representative of many real-world scenarios, and claiming fatigue is irrelevant or relying on evening timing don’t ensure the same fatigue level for everyone.