A beginner runner asked a simple question on Reddit the other day:
“When a guided run says recovery pace, do you walk or run? I do running programs and they leave it up to the runner. What’s best for encouraging improvement?”
It sounds like a basic question. But beneath it lies the single most common trap in endurance training: the black hole of intensity.
Most runners spend their “recovery” runs in Zone 3 because running in Zone 1 feels embarrassingly slow or impossible without walking. Then, when it’s time for hard intervals, their legs are still carrying residual fatigue, making the fast runs mediocre. They work hard every day, but their body adapts slowly because every workout blends into the same middle effort.
A recovery run has one singular job: get blood flowing to repair micro-tears in muscle tissue without adding systemic fatigue. If your heart rate spikes or your legs feel heavy, walking isn’t failing the workout — walking is nailing the workout.
This got me thinking: why should runners have to guess what kind of stimulus their body just experienced?
The two signals that don’t lie#
When you finish a run, looking at your average pace tells you almost nothing about the workout’s true physiological demand:
- A 6:00/km pace on rolling hills might push your heart rate straight into threshold (Zone 4).
- A 6:00/km average on a track could be an intense 400m interval session where recovery jogs pulled the overall average down.
To classify a run objectively, you need two independent signals:
- Heart Rate Zone Distribution (Metabolic Demand) — How much time did your cardiovascular system spend clearing lactate versus accumulating it?
- Speed Coefficient of Variation (
Speed CV— Pace Dynamics) — Was your pace steady like a metronome, or did it oscillate between explosive sprints and walking breaks?
Speed CV = (Standard Deviation of Speed / Average Speed) × 100If your Speed CV is low (under 10%), you were cruising steadily. If it spikes above 15% with bursts into Zone 4 and Zone 5, you ran intervals, regardless of what the overall average pace says.
Five distinct stimuli, classified automatically#
Instead of requiring manual tags after every session, Apex Run evaluates incoming Apple Watch workouts through a deterministic hierarchy based on your personalized heart rate zones, pace dynamics, and workout structure:
| Run Type | What the Data Looks For | Primary Purpose & Effort |
|---|---|---|
| ⚡ Interval | Watch intervals OR Speed CV > 15% + Z4/Z5 > 15% | VO₂ Max & speed turnover. Fast reps alternating with recovery valleys. |
| 🔥 Tempo | Zone 3 + Zone 4 + Zone 5 > 70% (Steady pace) | Lactate threshold clearance. “Comfortably hard” sustained cruising. |
| 🏔️ Long Run | Duration > 90 min OR Distance > 15 km | Muscular stamina & glycogen efficiency. Completing distance over speed. |
| 🍃 Recovery | Zone 1 > 65% of total workout time | Active flush with zero fatigue. Effortless (walking steep hills welcome). |
| 🔵 Easy | Default baseline (Lives in Zone 1–2) | Aerobic engine & capillary growth. Comfortable conversation pace. |
Keeping your training honest#
No algorithm replaces how your legs feel when your alarm goes off at 6 AM. You can always tap and manually adjust any run’s type in Apex Run if you had a specific training intent.
But having an objective classifier running silently in the background does something subtle: it keeps you honest.
When you set out for a “recovery jog” and return to see the card labeled Tempo, it’s a gentle reminder from your heart rate data that your body worked much harder than your ego wanted to admit.
Next time you head out for a recovery run, leave the pace expectations at home. Keep the heart rate down, walk the steep hills, and let the run do exactly what it was designed to do: get you fresh for the next hard day.
To see how your weekly runs balance between easy base mileage and high-intensity work, explore the 80/20 Training Structure guide or dive into Heart Rate Zones.