A practice test tells you where you stand. It also produces maximum fatigue, requires extended recovery, and carries real injury risk if you’re not prepared. It’s the “boss fight” of PT test training — high reward, high cost.
Pacewright schedules practice tests strategically to maximize the data while minimizing the damage.
The Schedule
Baseline (Weeks 1-2). One full practice test at the start of training. This establishes where you are — not where you want to be — and gives the algorithm a starting point for all predictions and progression calculations.
For running: run the exact test distance at maximum effort. For strength: do a 2-minute push-up max, 2-minute sit-up max, and max plank hold.
Mid-cycle (Every 4-6 weeks). One practice test to measure progress and recalibrate predictions. This is where you see whether training is working and whether the algorithm’s estimates match reality.
Final (Pacewright picks the date and tells you). One last practice test to confirm readiness and practice pacing, placed close enough to test day that the data is still relevant but far enough out that you can fully recover.
The one firm rule: don’t max-test in the final stretch before the real thing. A full max-effort test leaves fatigue behind, and testing too close means showing up to the real one carrying it. Pacewright won’t schedule a practice test that late.
Between Practice Tests: Submax Predictors
Full practice tests are expensive. Between them, Pacewright uses submaximal predictors — shorter, less fatiguing sessions that still provide useful data.
For running: A 6-10 minute hard effort (not an all-out sprint) gives enough data to estimate current fitness without the full recovery cost of a max-distance test. Repeatable interval sessions (like 6 × 400m) where you track times across weeks also serve as progress indicators.
For strength: Instead of going to failure every session, report your RPE for each set. If your training set of 20 push-ups used to feel like RPE 8 and now feels like RPE 6, your capacity has increased — without the need to prove it by testing to failure.
These submax data points feed into the capacity estimation system between formal practice tests, keeping predictions accurate without the fatigue cost.
How the Data Is Used
Running
Your practice test time feeds into the race prediction models — Riegel, VDOT, and Critical Speed — which produce an estimated test-day time with a confidence range. The adrenaline buffer and taper effect are applied on top of your practice time.
Strength
Practice test results establish your observed capacity. When you go to true failure (RPE 10), the observed capacity equals your rep count. When you stop at RPE 8 or 9, the algorithm estimates what you could have done:
| Reported RPE | Estimated % of True Max |
|---|---|
| 10 (failure) | 100% — reps = max |
| 9 (1 left) | 90% — max ≈ reps ÷ 0.90 |
| 8 (2-3 left) | 85% — max ≈ reps ÷ 0.85 |
| 7 (3-4 left) | 80% — max ≈ reps ÷ 0.80 |
The running estimate is smoothed using an exponentially weighted moving average — 70% weight on your existing estimate, 30% on the new data point. This prevents a single bad test from catastrophically resetting your predicted capacity.
Reading the Results
After a practice test, Pacewright shows you:
- Your result vs. your previous test
- Your estimated test-day performance (with adrenaline buffer)
- Whether you’re ahead, on-track, behind, or at-risk relative to your target
- What the trajectory looks like for the remaining training time
The thresholds:
- Ahead: At or above 110% of your target
- On-track: 90-110% of target
- Behind: 70-90% of target
- At-risk: Below 70% of target
“Behind” doesn’t mean failure is inevitable. It means the current trajectory needs adjustment — more focused training, or an honest conversation about whether the target is realistic in the remaining time.
Common Mistakes
Testing too often. Weekly max-effort practice tests create accumulated fatigue that undermines actual training. You’re spending recovery resources on measurement instead of improvement.
Testing too rarely. Going 8-10 weeks between practice tests means you don’t know if training is working until it’s too late to adjust. Every 4-6 weeks is the right frequency.
Not treating practice tests as hard workouts. A practice test is a maximum effort. The algorithm needs to know it happened so it can adjust the following days. If you run a full-speed 1.5-mile practice test on Tuesday and then try to do intervals on Wednesday, you’re asking for trouble.