You open Pacewright and today’s workout is different from what you expected. Your 6-mile tempo is now a 4-mile easy run. Or your long run got shortened by 2 miles. Or the pace target is slower than last week even though you’re feeling great.
Your first reaction: frustration. Your second reaction should be curiosity. Because Pacewright never changes a workout without a reason — and it always tells you what that reason is.
The Transparency Rule
Every modification in Pacewright includes three things:
- What changed — “Today’s run is now 4 miles instead of 6”
- Why it changed — “Your training load ratio is elevated at 1.4, in the caution zone”
- What data drove the decision — “Based on your last 7 days of training”
This isn’t a nicety. It’s the core design principle. Most training apps change your plan silently — you just see a different workout and have no idea why. Pacewright believes you should understand every decision the algorithm makes about your training, because understanding builds trust, and trust builds consistency.
The 10 Reasons Pacewright Modifies a Workout
1. ACWR Is Elevated
Your acute-to-chronic workload ratio — the relationship between your recent training load and your longer-term baseline — is above 1.3 (the caution threshold) or above 1.5 (the high-risk threshold). Pacewright reduced volume or intensity to bring you back into the safe zone.
What it means: You’ve been training hard recently — possibly harder than your body has adapted to. This isn’t a punishment. It’s the algorithm noticing a pattern that research consistently links to increased injury risk.
2. ACWR Is Low
Your ACWR is below 0.8, meaning your recent training is low relative to your baseline. This might trigger a slight volume increase or a note that you have capacity for more.
What it means: You’ve been training less than usual. If that’s intentional (recovery, life got busy), no problem. If it’s not, the algorithm is flagging that your fitness may be detraining.
3. Volume Cap
This week’s planned mileage would exceed the safe increase limit for your current training level. Pacewright capped it.
What it means: Your body can handle more volume — but not this much more, this fast. The volume caps are mileage-dependent: runners under 15 miles per week can safely increase 20%, while runners over 50 miles per week should increase no more than 5%. The traditional “10% rule” is too blunt — Pacewright’s caps are calibrated to where you actually are.
4. Spike Guardrail
Today’s run would have been significantly longer than anything you’ve done in the past 30 days. Pacewright capped it at 110% of your longest recent run.
What it means: Even if your weekly volume is fine, a single unusually long run creates disproportionate injury risk. This guardrail catches the “I haven’t run more than 6 miles in a month but the plan says 10” scenario.
5. Recovery Needed
Based on your recent training load and workout types, your body needs more recovery time before the next hard effort. Today’s workout was adjusted to be easier.
What it means: Hard efforts — intervals, tempo runs, long runs — create fatigue that requires 48-72 hours to recover from. If you did a hard session yesterday, today becomes easy regardless of what was originally planned.
6. Back-to-Back Hard Days
You had hard workouts on consecutive days. Today’s session was downgraded to prevent accumulated fatigue.
What it means: Two hard days in a row is a recipe for injury or overtraining for most recreational runners. Even if each individual workout is reasonable, the cumulative stress can exceed what your musculoskeletal system can handle.
7. Return From Break
You’re coming back after time off. Pacewright is starting conservatively to rebuild your base without injury.
What it means: When you take time off, your cardiovascular fitness holds up reasonably well, but your structural tissues — tendons, ligaments, bones — lose their adaptation to impact. The algorithm uses a comeback protocol that takes roughly half the time you were off to return to your previous level. Rush this and you’ll get hurt.
8. Weather Adjustment
Environmental conditions — heat, humidity, or altitude — are affecting expected performance. Pacewright adjusted your pace target accordingly.
What it means: Running in 85°F with high humidity is physiologically harder than running in 55°F. The same effort produces a slower pace. Pacewright adjusts your targets so you train at the right effort, not the right number on your watch.
9. Taper Phase
You’re approaching a race. Volume is being reduced while maintaining some intensity to keep you sharp.
What it means: Tapering is not detraining — it’s strategic fatigue reduction. Your fitness doesn’t disappear in 1-2 weeks, but accumulated fatigue does. The algorithm progressively reduces volume (80% → 60% → 40% → 20%) while keeping some intensity work to maintain sharpness.
10. User Override
You chose to override the algorithm’s recommendation. Pacewright logged it and adjusted accordingly.
What it means: You’re the boss. The algorithm tracks your override so it can factor the actual training load into future calculations. You won’t be penalized, but the system will note the deviation when making its next set of decisions.
What to Do When Your Workout Changes
Read the explanation. Every modification tells you what data drove the decision. If the ACWR is elevated, you can check your recent training load and see exactly why. If a volume cap triggered, you can see how close you were to the limit.
Trust the process — usually. The modifications exist because the research consistently shows that training load spikes, inadequate recovery, and volume jumps are the primary causes of running injuries. The algorithm is conservative by design.
Override when it makes sense. If you’re feeling great and the algorithm is being cautious because of stale data or unusual circumstances, override it. You know your body better than any algorithm. Just know that the system logged the override and adjusted its future calculations.
Don’t fight the pattern. If Pacewright keeps pulling you back — reducing volume, downgrading intensity, adding recovery — that’s not a bug. That’s the algorithm telling you something your body might not be communicating clearly yet. Consistent modifications in the same direction are a signal worth listening to.