
Peak-power windows show best bursts; lap splits show sustained pacing. Learn which curve to trust after a hard ride and how to adjust the next seven days.
On this page

Photo by CLEMENT Ader on Unsplash.
Peak-power windows show best bursts; lap splits show sustained pacing. Read both before you change the week.
After a hard ride, one chart may say your top end is gone while another says the work looked steady. That mismatch is not noise by default. Peak-power windows and lap splits ask different questions, so they can point to different next moves.

Photo by Ismael Rodríguez Martín on Unsplash.
Peak-power windows find your best average power over a set time span anywhere in the ride. A brief surge, bridge, or sprint can set the mark even if the rest was flat.
Lap splits average the power inside a segment you choose, such as a climb, interval, or timed block. They are better for seeing pacing drift, especially when you compare the same route or work set.
Use windows when you want to see the ceiling of a given effort length. Use laps when you want to see how well you held the task you meant to ride.
This is why how quadrant patterns frame power can tell a different story than a lap file. The same ride can also look different when you check first-half and second-half pacing.
Use peak windows for best 5-second to 5-minute outputs.
Use lap splits for climbs, intervals, or steady course segments.
Compare the same window lengths after similar rides.
Compare lap splits only when the route or task matches.
Short, hard power can fall before steady power because it asks for fast force and clean recruitment. A hard ride can leave that snap muted while sub-threshold riding still feels sound.
Middle-length windows blend hard anaerobic work with aerobic support, so they often sit between sprint loss and steady-state hold. Longer laps smooth the spikes, which can hide a short burst that never came back.
Be careful with firm cause labels from one file. Power curves show output, not a lab-grade cause, so pair them with feel, cadence, and heart-rate context.
If your ride had many surges, variability index for surgey rides may help explain why windows stayed high. If the work was steady, normalized power versus average output can help frame the load.
Treat short windows as a top-end signal.
Treat longer laps as a pacing signal.
Do not name the cause from power alone.
Check cadence and heart rate before changing the block.
Read both curves so the next decision fits the system, not one noisy spike.
The top-end spike gauge may drop first; your steady gate can hold longer unless the whole system is stressed.
Peak-power (rolling) windows highlight maximal outputs over fixed durations and are best for spotting high-end efforts and neuromuscular …
In the first day after a hard ride, use peak windows to check whether your snap has returned. If short windows are flat, do not force sprints just to prove fitness.
Across the next few days, lap splits give a steadier read on sustained work. If laps hold while peaks lag, keep aerobic work and skip max efforts.
If both curves fade against your normal fresh baseline, treat the whole week as under-recovered. Your threshold did not disappear; your recovery inputs shifted, so the output dropped.
You can also cross-check with cadence trends during fatigue when power drops late. When heart rate and power drift apart, aerobic decoupling signals may add useful context.
First day: trust peak windows for top-end readiness.
Next few days: trust laps for sustained work.
Peaks down, laps steady: skip sprints and keep aerobic rides.
Both down: reduce the training load before testing again.
One tactical email with training ideas and product updates. No spam — unsubscribe anytime.
Keep reading
- Indoor vs Outdoor Training Data: Understanding the Indoor–Outdoor Power Difference — Explore the indoor outdoor power difference: why identical power can feel harder indoors, how smart trainer power, inertia, heat, and variability ind...
- W' Balance and Anaerobic Capacity: Interpreting the Mental Battery Mid-Ride — W' balance estimates remaining anaerobic work during a ride. Learn how to use it for pacing, post-ride review, and one clear training adjustment.
- Data engineering tips for cyclists — Data engineering tips for cyclists: practical steps to clean training data, prevent duplicates, and ensure time series consistency for better adaptiv...
Before you change training, make sure the file is worth reading. Dropouts, zeroes, bad starts, and mixed lap rules can all bend the curve.
Peak windows are highly sensitive to one odd point because they hunt for the best slice. Lap splits can look stable while hiding a sensor problem inside the segment.
Check the power trace beside cadence, speed, and heart rate. If cadence falls with power, the ride may show real fatigue, but if power alone jumps, suspect the device first.
A clean setup matters more when you compare small changes. Use power meter setup best practices before you trust a strange peak.
Scan for gaps, zeroes, and sharp spikes.
Use the same lap start and stop rules.
Check cadence beside power before judging fatigue.
Discard files with clear sensor faults.
If peak-power windows are down but lap splits are close to your usual level, keep easy-to-moderate aerobic rides. Do not add sprints or VO2 max repeats this week.
If both windows and laps are down, cut the load and give the system room to rebound. That means less total work and no high-intensity intervals until the curves stop sagging.
If windows stay high while laps fade, you likely kept snap but lost the ability to hold the task. Keep one short quality touch, then pull back the rest of the week.
Use the same test and the same data rules when you check again. For a wider view, find your rider power profile before you judge one hard ride too harshly.
Peaks down, laps OK: keep aerobic work and skip max efforts.
Both down: cut load and remove high-intensity intervals.
Laps down, peaks OK: protect one short quality touch.
Retest after seven days with the same format.
The goal is one clear next move, not another week of second-guessing.
Preserve intensity where your lap splits survive, but back off when the whole curve sags.
Day 0 — Read the curves: compare your best short and middle windows with a fresh baseline, then compare two steady lap splits from a matching task.
Decision rule: if peak windows drop while lap splits hold, keep aerobic work, remove max efforts, and cut total volume for seven days.
If both peaks and laps drop, cut volume and intensity for the week and avoid high-intensity intervals until the retest improves.
Days 1–6 — Recovery week: ride easy aerobic sessions, add one short tempo touch only if lap splits were stable, and skip sprints.
Day 7 — Reassessment: repeat a standard short maximal effort and a short all-out effort, then compare the same windows and laps.
Peak-power windows show your best bursts; lap splits show sustained pacing. If the curves disagree after a hard ride, trust the curve that matches the next workout demand, then make one measured change for seven days.
No. Normal lap splits mean sustained work may be intact, but low peak windows still warn against max efforts. Keep aerobic work and skip sprints until the short windows recover.
Yes. A rolling window can be set by one brief effort, so it may overstate readiness for repeated hard work. Check repeatability, lap quality, and how the rest of the file looks.
Do not base the week on a broken file. Check for zeroes, spikes, and missed recording, then repeat the key test with a clean setup when you can.
Match the metric to the race demand. A sprint-heavy event needs short-window snap, while a climb or time trial needs strong lap-style sustained output.