Run Snapshot
Raman completed a 5.04K easy run at an average pace of 5:48/km in 29.2 minutes, with the temperature at 22.5°C and humidity at 83%. The run took place at 07:17 AM IST, with an Air Quality Index (AQI) of 34, indicating good air quality. Unfortunately, heart rate data was not available for this session.
In Raman’s Own Words
Raman noted that he “Ran after a long time”, which may have contributed to his average pace being slightly slower than his usual tempo. Given the relatively slow pace, his cadence of 80.0 spm was within a reasonable range, although it could be improved with more consistent training. The weather conditions, with a temperature of 22.5°C and humidity of 83%, would have had a minimal impact on his performance.
Pace & Effort Breakdown
The gap between Raman’s average pace of 5:48/km and max pace of 3:39/km suggests that he may have started conservatively and picked up the pace as the run progressed. Without heart rate data, it’s difficult to assess his effort level directly. However, his average cadence of 80.0 spm indicates that he may have been working at a moderate intensity. The temperature and humidity conditions would have resulted in a negligible pace slowdown, given that the temperature was only slightly above 20°C.
Route Narrative
Raman’s run can be broken down into five segments, each with its unique characteristics. The first kilometer was completed at an average pace of 6:55/km, with a slight elevation gain of 1.1m. The pace slowed down to 7:58/km in the second kilometer, despite a minimal elevation loss. The third kilometer saw a significant improvement in pace to 5:46/km, with no elevation change. The fourth kilometer was completed at a pace of 5:40/km, with a slight elevation loss of 2.1m. The final kilometer was the fastest, with a pace of 5:10/km and a minimal elevation gain. The positive split in the last kilometer suggests that Raman had a strong finish, possibly due to his strategy of conserving energy early on.
Run Analysis
Workload Intelligence
Raman's Acute-to-Chronic Workload Ratio (ACWR) is 1.79, which puts him in the danger zone, indicating a high injury risk. His acute load of 89.5 is significantly higher than his chronic load of 50.1. With three runs in the past seven days and a total distance of 16.1 km, Raman's training load is relatively high. At an ACWR of 1.79, his acute load of 89.5 sits above the chronic baseline of 50.1, suggesting that he may be overreaching.
Physiological Impact
Given the pace and duration of the run, it's likely that Raman's aerobic system was the primary energy source. This session would have driven adaptations such as increased mitochondrial density and capillarization. The good air quality, with an AQI of 34, would have minimized any added respiratory stress. However, the relatively high humidity may have still presented some challenges for evaporative cooling and breathing.
Recovery & Next Session
Based on the high ACWR and acute load, Raman should prioritize recovery for the next 48 hours. A 30-40 minute easy run at a pace of 6:00-6:30/km would be a suitable next workout, allowing him to active recover while minimizing the risk of injury. This will help him to gradually reduce his ACWR and bring his training load back to a safer range.
Training Trajectory
Raman's 28-day volume trend shows a moderate increase in distance, but the high ACWR suggests that he may be progressing too quickly. To reduce the injury risk, it's recommended that he reduces his weekly mileage by 10-20% for the next two weeks and focuses on active recovery and injury prevention strategies. A concrete coaching directive would be to aim for an ACWR of 1.2-1.3 by reducing his acute load to 70-80 while maintaining a chronic load of 50-60.
View the original activity on Strava
Gear Used: Asics Novoblast 5 (Shoes)
Transparency: The links above are affiliate links — if you purchase through them, I earn a small commission at no extra cost to you. It helps support my training and this data analysis hobby project.