Why Plover
Built for the runner who lost a season to week six.
Between 37% and 56% of recreational runners get hurt in a given year — roughly 7.7 injuries per 1,000 hours on the road. Nearly all of them are wearing a watch that already recorded the warning signs. The data was never what’s missing.
The data isn’t missing. Triage is.
Your watch logs pace, heart rate, cadence, ground-contact time, stride length, overnight recovery — all of it. The tools that read it split into two camps. Analytics platforms compute every metric sports science has ever named and hand you forty charts. Wearable scores do the opposite: they collapse everything into one confident number each morning that never explains itself and never admits when it’s guessing. One drowns you; the other flatters you. Neither tells you the two or three things that actually changed this week.
A signal, not a verdict.
Plover was built the other way around. It reads the record you already have, ranks what moved, and writes a short, plain-English feed: here is what changed, here is the number, here is the window it’s measured against. It stays quiet when nothing moved — silence is its own signal. The name is the idea. A plover is a ground bird that runs, stops, and scans, and sounds a far-carrying alarm only when something is genuinely worth it.
Confidence is part of the finding.
Not every signal deserves the same weight, so Plover never pretends otherwise. A weekly-mileage ramp rests on strong prospective evidence and is allowed to raise its voice. A dip in overnight heart-rate variability is supporting evidence only, and never turns red on its own. The grade travels with the finding: you always see how much to trust it, not just what it says.
“My watch gave me a green readiness score the morning before my last calf tear. Plover is the first thing that talks to me like an adult — it keeps telling me what it doesn’t know.”Marta Keller, masters runner — illustrative composite
We’d rather tell you when we don’t know.
When a treadmill run didn’t record the data a finding needs, the tile says unavailable — it is never filled with a population guess. When there aren’t enough comparable runs yet, Plover says so instead of inventing a baseline. And every detector is tested the honest way: the same code that writes this week’s feed is replayed across real training histories, with no peeking at the future. Plover makes no injury prediction. No data reliably forecasts an individual runner’s injury, and anything that claims to is selling you a number it can’t back. What Plover does is smaller and more useful: it shows when your training has entered a pattern with documented, elevated risk, says how strong that documentation is, and leaves the decision to you — and your coach or physio.
Attention where it’s earned. Silence where it isn’t.