Legwork keeps your team on course for a smooth relay race.
iOS and Android. Every projection updates as the race moves.
Each leg priced at the temperature forecast for the hour it runs. A tinted time is still a projection.
One recent race result per runner is the whole setup
The hard part was never the running. It's the twenty minutes before a handoff, in a gravel lot with one bar of signal, when the van has to leave now and nobody agrees on what now means. Someone is holding a pace chart printed on Thursday. Someone else has a spreadsheet that stopped updating four exchanges ago. The afternoon came in hotter than the forecast, the last leg climbed more than it looked like it would, and the runner out there right now is quicker than the number anyone typed in back in July.
We have been that van. Twelve runners, more than a hundred years of relay racing between us, most of it spent learning one lesson from different directions: the arithmetic is simple, and getting it right when nobody has slept is not.
Legwork does the arithmetic while the temperature moves and the legs come in fast or slow. The van gets one time to be somewhere.
It started as the fix for our own team. It's ready for yours.
Every leg time in Legwork is recomputed from the same four inputs, for every runner, every time something changes.
Legwork pulls an hourly forecast for the course and keeps refreshing it through race weekend, so a leg that runs at two in the afternoon is priced at two in the afternoon's heat, not at whatever the forecast said when your captain set the team up.
Heat cost fitted to real race data: roughly 0.5% slower per degree above 60°F.
One recent race result per runner is the whole setup. From it, Legwork works out how much that runner's own pace drops as the distance grows, and applies it to the length of the leg they are actually assigned. Miles already run today count too, with credit back for the hours spent resting in the van.
Riegel extrapolation, banded by fitness and target distance.
Climb and descent are costed separately across the leg, so a leg that gains 320 feet and loses 381 feet is never treated as flat ground. The curve comes from real GPS pace data: past about eight percent downhill, runners stop getting faster.
Empirical pace against grade, on elevation gain and loss.
Relay courses run through long stretches with no bars. Phones in the same van sync directly to each other over Bluetooth, so the roster, the assignments, and every recorded handoff stay current in the dead zones. The two vans are never in range of each other, and both stay correct while they are apart: when they meet, the logs merge, with or without a server.
Unattended sync retries from one minute out to fifteen, and never stops.
Most relay spreadsheets give you a single time and ask you to guess how much slack to add. Legwork separates the question of when to drive from the question of when you finish, because they are not the same number and they are not used by the same person.
A conservative time with the buffer already built in, so your van is never the reason a runner is standing alone at a handoff. It feeds the countdown on the race screen and the directions button next to it.
Arrive by 2:47 PM · Exchange 16
The unbiased projection, no padding, recomputed every time a real handoff is recorded. This is the number you send to the people meeting you at the beach.
Finish line · 11:38 AM
Relay handoffs happen at a chute in the dark with several teammates standing there. More than one taps, so Legwork keeps all of them and takes the earliest. The captain gets the final say if runners don't agree. You can see every claim and who made it.
Nothing is silently overwritten, and nobody has to agree on who is the official timekeeper.
Recorded by 3 people
Ranked by who said it and how deliberately, not by who said it last. The top row is the time every later projection is built on. The others stay.
Record Handoff sits between the arriving runner and the departing one, on the screen the whole time that exchange is live. One tap in a headlamp lit parking lot at 3 a.m., and several people can record the same handoff — the earliest of them is the one the race keeps.
Every leg in one list, with its distance and forecast temperature. Times sit half a row lower than the runners, interlocked on a seam, so a handoff time can never be read as the wrong runner's. A leg already run keeps the temperature it was run in, not today's forecast.
Captain a race or join a team, then assign legs and vans before race day. Every phone already knows the plan when the wave goes off.
Night is the primary mode, not an afterthought, with a manual day and night switch. A van interior at 3 a.m. and the same van at 2 p.m. need different screens.
Every course is entered from the race's own published leg data and checked before it goes live.
196.7 mi · 36 legs · 12 runners
201.4 mi · 36 legs · 12 runners
197.8 mi · 36 legs · 13,200 ft of climb
155.6 mi · 29 legs · 10 runners
73.6 mi · 19 legs · one van of 6
48.8 mi · 12 legs · one van of 6
67.2 mi · 12 legs · one van of 6
More relays are being added. Tell us which one your team runs and it can be next.
On the App Store now for iPhone. Android is in closed testing, which runs by invitation.
Legwork Relay Racing, free, iPhone on iOS 16 or later. Install it and you can create a team or join one from an invitation.
The same app and the same sync, with a tester list in front of it. Google Play shows the app only to accounts on that list, so getting your van on it takes three steps.