The first warm block of the season has a way of exposing messy systems. Your long run uploads with a weird pace spike. Your bike computer still thinks you’re riding last year’s FTP. Your watch has three pairs of retired shoes in rotation. None of this ruins fitness, but it does make training harder to read.
Before race season gets busy, it is worth doing a simple data reset. Not a full overhaul. Not another app rabbit hole. Just a practical check of the numbers and habits you rely on every week.
Recent updates on StriveKit have covered platform housekeeping, including the note to update your StriveKit app and the arrival of Strava support. This post looks at the athlete side of the same idea: making sure the data going into your training log is clean enough to trust.
Why a data reset matters
Endurance training depends on patterns. You look at pace, power, heart rate, distance, elevation, sleep, fatigue, and consistency. The problem is that small errors stack up.
A run recorded with poor GPS can make an easy day look too fast. An old heart-rate zone can turn a steady ride into a “threshold” workout on paper. A shoe with 650 miles on it can hide in your log until your calf starts talking.
Good data does not have to be perfect. It only needs to be consistent, current, and easy to interpret. That is the goal of this reset.
1. Re-check your training zones
Training zones drift as fitness changes. If you set your heart-rate or power zones months ago, they may no longer match your current ability.
This is especially true after a winter base block, a break from training, or a move indoors. A cyclist who raised their FTP from 220 watts to 245 watts will have very different endurance and tempo targets. A runner returning after time off may need easier heart-rate caps than last season.
A simple approach:
- Running: Use a recent race, time trial, or controlled threshold session to update pace and heart-rate ranges.
- Cycling: Retest FTP or use recent hard efforts if you have reliable power data.
- Swimming: Update your CSS pace or threshold pace from a repeatable test set, such as 400m plus 200m time trials.
- Triathlon: Check zones by sport. Do not assume your bike heart rate and run heart rate line up neatly.
You do not need to test every week. But if you have not checked your zones in eight to twelve weeks, or your training feels mismatched on easy and hard days, it is time.
2. Clean up your gear list
Gear tracking is one of the most useful boring habits in endurance sport. Shoes, chains, tires, goggles, wetsuits, cleats, and heart-rate straps all have a lifespan. When your gear list is cluttered, the useful signal gets lost.
Start with running shoes. Many runners rotate shoes by feel, which is fine, but mileage still helps. A common replacement range is roughly 300 to 500 miles, depending on the shoe, surface, runner size, gait, and injury history. Some shoes feel dead earlier. Some last longer. The point is not to follow a rigid number. It is to notice the trend before a problem shows up.
For cycling, check chain wear and tire age before race volume ramps up. A worn chain can accelerate cassette wear. Old tires may look fine until they start cutting or flatting under load. For swimming, check goggles and paddles. A leaking pair of goggles is a small annoyance in training and a big distraction on race morning.
Archive anything you no longer use. Rename similar items clearly. “Endorphin Speed 4 – Blue” is more useful than “Shoes 2.”
3. Fix the common GPS and sensor mistakes
Bad data often starts before the session begins. A rushed start, a low battery, or a loose sensor can turn a normal workout into a confusing file.
Before key sessions, give your watch or head unit a few extra seconds to lock onto GPS. In dense cities, forests, and mountain valleys, GPS can drift more than you expect. If you train on tracks, use track mode when available. If you run tunnels or routes with heavy tree cover, judge the workout by effort and splits instead of obsessing over instant pace.
Heart-rate data needs the same attention. Optical wrist sensors can struggle in cold weather, with tattoos, loose fit, or rapid intensity changes. A chest strap is usually more reliable for intervals, racing, and cycling. If your heart rate jumps from 120 to 185 in the first minute of an easy run, that is probably not sudden superhuman suffering. It is likely a bad reading.
Power meters also deserve a quick check. Calibrate or zero-offset according to the manufacturer’s guidance, keep firmware current, and replace batteries before they fail mid-ride.
4. Standardise your workout names and notes
Workout titles and notes are easy to ignore, but they make your history searchable. Six months from now, “Morning Run” will not tell you much. “8 x 2 min hills, strong finish” will.
You do not need a complex system. Use simple patterns:
- Easy Run – 45 min
- Bike – 3 x 10 min Sweet Spot
- Swim – 10 x 100m CSS + 200m pull
- Brick – 90 min bike + 20 min run
- Strength – Lower body, moderate load
Then add one short note after important sessions. Include what the numbers cannot show: heat, wind, sleep, fueling, soreness, terrain, or mental effort. “Felt flat, slept 5 hours” is useful context. So is “First gel at 35 min, no stomach issues.”
5. Audit your weekly training picture
Once the inputs are cleaner, step back and look at the week. Most endurance athletes do not need more data. They need a clearer read on the basics.
Ask these questions:
- Are easy days actually easy?
- Are hard days separated enough to absorb them?
- Is strength training supporting endurance work, or competing with it?
- Is volume rising gradually enough to recover?
- Are long sessions getting specific to the event?
- Are rest days real rest days?
A clean log can reveal simple issues. Maybe your “easy” runs are all drifting into moderate effort. Maybe your swim volume is too low for a triathlon goal. Maybe you are stacking hard bike intervals, leg strength, and a long run in the same 48-hour window and wondering why you feel stale.
The fix is not always dramatic. Often it is moving one session, slowing one run, or adding one recovery day every second week.
A 20-minute reset checklist
If you want to do this quickly, set a timer for 20 minutes and work through the list:
- Update current training zones for run, bike, and swim.
- Archive old shoes, bikes, tires, straps, and other retired gear.
- Check sensor batteries and device firmware.
- Rename key gear so it is easy to identify.
- Review the past four weeks for intensity creep.
- Add notes to recent key workouts if they are missing context.
- Choose one data habit to improve this month.
That last point matters. Do not try to become a full-time analyst. Pick one habit. Maybe you will add fueling notes to long sessions. Maybe you will keep easy runs under a set heart rate. Maybe you will track shoe mileage more carefully.
The takeaway
A race-season data reset is not about chasing perfect numbers. It is about removing noise so your training story is easier to read.
Current zones, accurate gear tracking, reliable sensors, clear workout names, and short notes can make a big difference. They help you spot patterns earlier, adjust training with more confidence, and avoid making decisions based on bad information.
Before the next build block starts, give your training log the same attention you give your bike, shoes, and race kit. A cleaner system now can save you confusion later.
Leave a Reply