Your Summer Pace Is a Lie: The Dew-Point Adjustment
Your Summer Pace Is a Lie: The Dew-Point Adjustment¶
You are three weeks into your Chicago or NYC training block. Last Tuesday's tempo run came in 75 seconds per mile slower than your spring benchmark. Your Garmin VO2max has slipped from 52 to 49. Your easy runs feel like tempo runs, and your tempo runs feel like a sustained negotiation with your own legs. Every metric in your training log is trending the wrong direction.
The algorithm doesn't know it's 78°F with a 68°F dew point.
That is the entire problem. Your watch, your Strava dashboard, your NavRun weekly report — none of them have access to the ambient conditions when your HR spiked to 168 and your pace fell off a cliff. They read elevated heart rate plus slow pace and output the same conclusion every time: you are getting slower.
You are not getting slower.
The algorithm has no idea it's hot outside¶
Garmin's VO2max estimates and training load scores are calculated using the FirstBeat algorithm, which derives fitness estimates from the relationship between your heart rate and your pace. It's well-calibrated for normal running conditions — approximately 55°F, moderate humidity, the conditions under which most race performances that trained the model occurred.
In summer heat, that calibration breaks in a specific and predictable direction.
On a 78°F day with a 68°F dew point, your heart rate at any given effort runs 10 to 20 bpm higher than it would in cool conditions. The algorithm sees elevated HR and slow pace and concludes the most statistically likely explanation: your fitness has declined. It outputs a lower VO2max estimate. Your training load score rises because HR-based load is genuinely higher. Your spring pace targets look further away every week.
Three metrics break simultaneously and reinforce each other: pace looks slow, HR looks broken, VO2max estimate drops. The watch is reading a logical pattern — it's just reading it without the one input that would explain everything. That input is dew point, and your watch doesn't measure it.
Dew point is the number your watch ignores¶
Not temperature. Dew point.
Air temperature tells you how hot it is. Dew point tells you whether your sweat can actually do anything. Sweat cools you through evaporation — and evaporation stops when the air is already saturated with moisture. Dew point is the temperature at which that saturation occurs. When it rises above 60°F, your primary cooling mechanism starts failing, your core temperature climbs, and your cardiovascular system diverts more blood to your skin to compensate. That's the mechanism stealing beats from your running.
The standard scale runners use, drawn from Running Writings' heat calculator and confirmed by coaching resources at McMillan and Runners Connect:
| Dew Point (°F) | Running Feel |
|---|---|
| Below 50 | Comfortable — close to race conditions |
| 50–54 | Slightly humid — minimal performance impact |
| 55–59 | Noticeably uncomfortable — effort increase begins |
| 60–64 | Significant performance impact — pace adjustments required |
| 65–69 | Hard work feels brutal — heat stress is dominant |
| 70+ | Dangerous — serious pace adjustment required; reduce intensity |
Chicago in July and August typically runs 65–72°F dew point on humid days. New York City is comparable, trending toward the 68–74°F range during peak summer heat waves. If you are training for Chicago (October 11) or NYC (November 1) right now, the majority of your summer runs are landing in the "significant performance impact" to "brutal" range on this scale. Every pace you have logged since late June is carrying a correction factor your watch doesn't know to apply.
The math: dew-point pace adjustment¶
The adjustment is straightforward once you have the dew point for each run. Pull it from Weather Underground's history or any hourly weather archive for your city — search for the station closest to where you ran, look up the dew point for your start time. Then apply this correction table, which represents the percentage to add to a raw pace to get the cool-condition equivalent:
| Dew Point (°F) | Add to Raw Pace |
|---|---|
| Below 50 | 0% — no correction needed |
| 50–54 | +1–2% |
| 55–59 | +2–3% |
| 60–64 | +3–5% |
| 65–69 | +5–7% |
| 70–74 | +7–10% |
| 75+ | +10–15%+ |
Running Writings' heat-adjusted pace calculator, which these ranges draw from, has been calibrated against large samples of road race results and represents the most field-validated correction method publicly available.
The formula runs backward from how it might first appear. You are not asking "how much slower should I run today?" You are asking: given what I actually ran in these conditions, what does that represent as a cool-condition equivalent? The calculation is:
Adjusted pace = Raw pace ÷ (1 + adjustment %)
Worked example. Your spring easy pace was 9:10/mi, established during a March training block at 46°F. Last Thursday you ran an easy six-miler at 9:48/mi. Temperature was 78°F, dew point 68°F. The 65–69°F dew-point band calls for a 5–7% adjustment; use 6% at the midpoint.
Adjusted pace = 9:48 ÷ 1.06 = 9:14/mi.
Your "terrible" 9:48 run is a 9:14/mi equivalent in cool conditions — four seconds off your spring easy baseline. Your aerobic base is intact.
That is the number your weekly report is not showing you, and the only number worth comparing against your spring training data. If you want to revisit your baseline training paces and VDOT context before running the math, training-paces-explained covers the full zone framework.
What this means for your NavRun weekly report¶
Your NavRun weekly report surfaces pace, HR averages, training load, and run consistency across the week. In July and August, three of those signals are corrupted by heat and two are honest. Reading them correctly is the difference between a functional training assessment and a weekly exercise in unnecessary self-doubt.
Corrupted by heat — don't use these as fitness signals right now:
- Pace — raw pace is meaningless without the dew-point correction. A week of easy runs showing 9:45–10:00/mi in 70°F dew-point conditions may represent 9:05–9:20/mi equivalent fitness. Never compare raw summer pace to spring targets.
- Watch VO2max estimate — actively misleading during summer heat blocks. The FirstBeat model will show 2–5 point drops that reverse completely in October. Ignore the absolute number for now; track directional trend only once fall temperatures arrive.
- Training load score (if HR-based) — elevated HR in heat inflates the perceived load score. The cardiovascular stress is real, but the fitness interpretation the score implies is not.
Honest signals even in heat:
- Perceived effort — if your easy runs feel controlled and sustainable — not comfortable, but not gasping — your aerobic base is working correctly. Effort perception is your most heat-honest metric.
- Distance and time-on-feet — you ran 48 miles this week. That happened. The pace was weather-affected; the mileage was not.
- Run consistency — five days versus three days this week reflects training adherence accurately regardless of ambient conditions.
Conditional — real but easily misread:
- Heart rate — corrupted as a performance metric (don't compare summer HR at a given pace to spring HR at that same pace), but honest as a cardiovascular load metric. Sustained elevated HR in heat represents real training stress. The adaptation it triggers is real. The number is just serving two purposes simultaneously, and the watch reports only one.
When reviewing your weekly report in July and August, ask one question: did I run the miles at controlled effort and stay consistent? If yes, the block is on track — regardless of what the pace column shows.
Why October will feel shockingly fast¶
The runner who logs 9:48/mi in July heat is not the same runner who will run 9:48/mi in 52°F Chicago race conditions on October 11.
Summer training logged at controlled effort triggers a specific cascade of cardiovascular adaptations: plasma volume expansion, earlier sweat onset, reduced heart rate at equivalent efforts. When race-day temperatures drop to 48°F, those adaptations are still fully active. The cardiovascular system that learned to handle dual-demand thermoregulation in heat is now running on cool air, and the efficiency gains become visible in ways the summer data never could show.
Runners Connect documents that heat-adapted runners tested in cool conditions demonstrate 5–8% VO2max improvements versus their own pre-heat-training baselines — gains that emerge in October even when the summer training data looked objectively worse than spring. The watch showed deconditioning. The physiology was doing the opposite. The race will confirm it.
The detailed mechanism — plasma volume expansion, cardiac output improvements, the retention timeline for each adaptation — is covered in Heat Acclimation for Runners: Two Paths, One Block. The short version: if you have been running consistently in summer heat, the adaptation is happening. The dew-point correction math is how you read the signal while it is building.
The confidence check: is your fall goal still achievable?¶
Two questions. Run them now, using data from your last three weeks.
1. The effort check. Have your easy runs felt genuinely controlled — not perfect, not cool-weather comfortable, but sustainable at a pace you could hold for another hour? Have you finished most easy runs feeling like you had more in reserve? If yes, your aerobic base is intact. Heat stress makes the same effort feel harder. "Harder" and "unsustainable" are not the same condition.
2. The adjusted pace check. Pull your last three easy runs. Look up the dew point for each from a weather archive. Apply the correction table above. Do your adjusted paces land within 10–15 seconds per mile of your spring easy baseline?
If yes to both: your fall goal is on track. Stop second-guessing. Run the miles.
If your dew-point-adjusted paces have drifted more than 15–20 seconds per mile from spring baseline consistently across multiple weeks — not one hot outlier, but a sustained multi-week trend — that warrants investigation. Normal summer heat variance does not cause a sustained 20-second adjusted drift. Genuine overtraining, incomplete recovery, or under-fueling will.
One more number: Chicago's race-day dew point on October 11 historically lands between 43–55°F. NYC in early November runs 40–50°F. Both races will cooperate with the adaptation you are building right now. The July weather is creating the same conditions that drove the 5–8% cool-condition VO2max gains documented in the research. The dew point on race day will let you run them.
Stop chasing spring paces in July¶
Every mile logged at controlled effort in summer heat is building the fall racing body — whether the watch registers it or not. The FirstBeat algorithm is reading the same data you are, without the weather context that would change every interpretation it outputs. Your Garmin VO2max will recover in September. Your fall performance will confirm what your summer numbers could not.
Here is what to do right now. Find the dew point for your last week of easy runs — three minutes in a weather archive. Apply the correction table. Compare the adjusted paces to your spring baseline. Then stop using raw July and August pace as a fitness signal.
Going forward: check the dew point at the start of each week's training review and apply the adjustment before reading your NavRun weekly report. The weekly view is where the signal becomes coherent — dew-point-adjusted effort patterns across four or five consecutive runs read very differently than the single-run panic that comes from a Tuesday tempo that came in 70 seconds slow.
Your summer block is not a problem to survive. The pace data just needs the key that makes it readable — and now you have it.
See your summer training block as a whole in NavRun. Connect your Strava account and review four weeks of activity data together — the consistency and effort-pattern signals that raw pace alone obscures. Start for free at navrun.app.