Readiness and load intelligence for runners · now in private beta
Plover reads the runs you already record and tells you the few things that changed this week. Each one comes with its evidence and how much to trust it.
Works with Strava, intervals.icu, and .fit, .tcx or .gpx files.Have an invite? Sign in →
A week in Plover
What changed, and every check behind it. See the full week →
Worth watchingStep lengthlast 6 weeks
Performance signalThis can come with fatigue. It is a reason to take an easy day, not a diagnosis.
4% shorter over 6 weeks than your usual
Stride length at the same easy pace
10 km easy · usual route
No notable change. Step length and heart rate matched your similar runs.
6 × 400 m intervals
Pace held across the reps, and heart rate came back down between them as usual.
8 km easy · same pace
Steps a little shorter again, the third easy run in a row. The week’s finding comes from here.
Every run gets checked · quiet when nothing changed
Run. Stop. Scan.
Plover only brings up the changes that earn your attention.
After every run, Plover works out what kind of run it was and checks it against your own recent runs. It recomputes your load, mechanics and recovery. If nothing changed enough to matter, it stays quiet.
Each change is labelled a load, performance or recovery signal and graded by how strong the research behind it is. A recovery signal alone can only ever be worth watching.
Every finding shows the window it compared, the runs it drew on and its sources. When a check couldn’t run, Plover says why. It never tries to predict injuries.
Evidence, graded
Some signals rest on strong research and some on very little. Plover grades each one and shows the grade next to the finding.
Strong evidence
Over a set limitWeekly mileage
Load signalYour weekly mileage went up faster than your body is used to.
34% more than your 4-week average
Good evidence
Worth watchingGround contact
Performance signalEach step spends longer on the ground at the same easy pace.
6% longer over 3 weeks than your usual
Supporting evidence only
Worth watchingOvernight HRV
Recovery signalYour overnight heart-rate variability dropped below its usual range.
Stays at worth watching until a performance signal agrees
A recovery signal on its own never goes past worth watching. How each signal is graded →
Inside the app
The app has three places to read: Runs, Metrics and Planner. Each run also gets a page of its own. The examples below use made-up data.
Runs
Your runs sit in one feed under a week tape. Beside them, Plover keeps the few findings that need attention now. When nothing does, it says so.
A run
Plover reads what kind of run it was. Intervals are checked rep by rep for pace, step length and heart-rate recovery. Steady runs are checked for heart rate and ground contact at the same pace, and every run is compared with your similar runs. The run page lists every check and its verdict, including the ones that found nothing.
Metrics
Plover turns each run's heart rate into load points. An easy hour at 70% of your max heart rate earns about 75. Fitness is that load averaged over about six weeks, and the card says how it compares with a month ago and with your high. Training load, weekly mileage, ramp, monotony, decoupling and efficiency follow.
Fitness
62 load/day
Up 6% in 4 weeks · Just under your high from Sep 19
Planner
Sketch the coming days and Plover projects where your load and weekly ramp would land. Turn on suggestions and it drafts a week of sub-threshold sessions, every rep slower than your estimated lactate threshold, then checks the week against your own limits.
Projected load
Bring your runs
Sync runs when you press Sync. If Strava and intervals.icu both have a run, Plover keeps the intervals.icu copy, because it has the original file.
Connect in Settings
Sync brings in your recent runs with heart rate, pace, cadence, altitude and GPS. Strava doesn’t share a watch’s running dynamics, so those checks say there is no data.
Paste your API key
Plover gets the original file from your watch, plus the overnight HRV that the recovery signals read.
Upload Strava’s bulk export
Bring in years of runs at once, so your baselines start from your real history. The import report counts every file, including the ones it skipped.
Drag and drop
Upload .fit, .tcx or .gpx files. The same file uploaded twice is only counted once.
What we won’t tell you
We show what changed. Whether to act on it is up to you.
Missing data stays missing. A treadmill run has no ground-contact data, so that check says so instead of guessing. Every detector is replayed over real training histories, using only what it could have seen on the day.
An observant record
Read the signal, its evidence and its limits.