Run Snapshot
Raman completed a 5K tempo run with an average pace of 5:04/km at the fastest point, during a segment with a -6.1m elevation change. The context of this run is a series of tempo-paced kilometers, with Raman’s pace ranging from 4:53/km to 6:03/km across different segments. Unfortunately, there is no available data on the time of day, weather conditions, or heart rate.
Pace & Effort Breakdown
Comparing the average pace to the max pace reveals a pacing strategy where Raman maintained a relatively consistent speed, with the fastest kilometer being 4:53/km and the slowest at 6:03/km. Given the absence of heart rate data, we cannot compute an effort-to-pace ratio. However, the cadence data shows an average of 159 spm, indicating a good form efficiency. The lack of weather data, including temperature, dew point, and AQI, limits further analysis on environmental impacts.
Route Narrative
Breaking down the run kilometer by kilometer, Raman started with a 6:03/km pace, followed by a 5:44/km pace, then accelerated to 5:04/km, and continued with a 5:12/km and finally a 4:53/km pace. The pace responded well to elevation changes, with the fastest segment corresponding to a slight downhill. Cadence shifted from 158 spm to 161 spm, indicating a good adaptation to the terrain. The positive split in the early kilometers suggests a strategic approach, building up to a faster finish.
Run Analysis
Workload Intelligence
Unfortunately, without the ACWR value or acute and chronic load data, we cannot classify Raman's training zone or assess the risk of overreaching or undertraining. The absence of weekly run count and distance trends also limits the analysis of workload intelligence. Normally, we would compare the acute load to the chronic baseline to understand the training impact, but this data is not available.
Physiological Impact
Based on the pace and duration, this session likely targeted the lactate threshold energy system, driving adaptations such as improved mitochondrial density and capillarization. Without heart rate data, it's challenging to specify the exact energy system utilization. However, the consistent tempo pace suggests a focus on aerobic capacity and endurance.
Recovery & Next Session
Given the lack of data on today's load and current ACWR, prescribing a specific recovery duration or next workout is challenging. Typically, after a tempo run, a recovery period of 24-48 hours would be recommended, followed by a session that continues to build aerobic endurance, such as an easy run or a fartlek workout. The target pace range for the next workout would depend on the current training phase and goals.
Training Trajectory
Assessing the 28-day volume trend is not possible without the necessary data. However, a general recommendation for progressing safely would involve gradually increasing weekly volume by no more than 10% each week, ensuring at least one easier week every fourth week to allow for recovery. A concrete coaching directive would be to aim for an ACWR within the optimal training zone of 0.8-1.3 and to monitor weekly km goals and pace targets closely to avoid overreaching.
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.