Race Replay: How It Helps Sailors and Sailing Clubs

Ask a sailor what happened on the second beat and you will usually get a story, not a fact. "I think I was in phase with the shifts," or "we just got rolled by the group on the right," or the classic, "I have no idea, it all happened so fast." None of that is a criticism. Racing a boat takes your full attention, and the part of your brain that would otherwise be building an accurate memory of the leg is busy calling the next shift and keeping the boat flat. The story you tell afterwards is reconstructed, not recorded, and reconstructed memories are notoriously kind to the person doing the reconstructing.

Race replay solves a simpler problem than analytics usually promises to solve. It does not try to tell you what to do differently. It shows you, accurately and without editorial comment, what actually happened, so the conversation about what to do differently can start from facts instead of vibes. This post walks through how replay works in SailingMetrics, why it matters for an individual sailor and for a club running a race night, and where it sits next to the other tracking tools sailors already know about.

What Replay Actually Shows You

At its simplest, a replay is a GPS track played back as a moving boat on a map instead of a static line. You upload a session, and once it has been processed you get a player with a timeline, a play button, and a speed control, sitting next to a map that shows your boat moving through the course exactly as it did on the water. Scrub the slider and the boat jumps to that point in the race. Hit play and it moves at whatever multiple of real time you choose, from a careful 1x to an 8x fast-forward that gets you through a forty minute beat and run in a few minutes.

The boat icon itself carries information, not just position. It rotates to match your actual heading at that instant, and the trail behind it is coloured by speed, so a glance at the map tells you where you were fast and where you were parked, without reading a single number off a chart. Underneath the map, a metrics panel keeps pace with the slider: speed over ground, heading, and VMG update in real time as playback runs, so if you pause on a moment that looks interesting you immediately have the numbers to go with the picture.

The other thing the player does automatically is mark where you tacked and gybed. Every manoeuvre detected in the track shows up on the timeline as a marker you can jump straight to, which matters more than it sounds. Nobody wants to scrub through forty minutes of straight-line sailing looking for the three seconds where something went wrong. The markers let you go directly to every tack in the session, watch the speed trace dip and recover around each one, and compare the shape of tack four against tack eleven without hunting for either.

From an Uploaded File to a Replay You Can Trust

None of that is useful if the underlying data is noisy or the manoeuvre markers are in the wrong place, so a fair amount of the work happens before you ever see the player. A raw GPS track, whether it comes from a phone, a watch, or a dedicated logger, arrives full of small imperfections: duplicate fixes a few milliseconds apart, positions that jump slightly due to satellite geometry, and gaps where the device lost signal under a bridge or behind a headland. The processing pipeline smooths the positions, removes near-duplicate fixes, and interpolates sensibly across small gaps, so the track that reaches the replay screen is a clean version of what actually happened rather than a literal, jittery transcript of the raw GPS feed.

Tack and gybe detection runs on top of that cleaned track, and it is worth being specific about how it is validated rather than just asserting that it works. Manoeuvres are checked against a hand-labelled evaluation dataset, sessions where a human has gone through and marked exactly where each tack and gybe happened, so that changes to the detection logic can be measured against real outcomes rather than judged by eye. That matters because a manoeuvre detector that is only ever eyeballed against a handful of familiar tracks tends to quietly get worse in conditions nobody happened to check, choppy water, light air, a very slow tack in a heavy keelboat. Testing against a fixed, labelled dataset catches that kind of regression before it reaches a real session.

Wind direction is the other piece that has to be solved before a replay means much. A beat leaves an unmistakable signature in a GPS track: two families of headings roughly ninety degrees apart, alternating at every tack. Splitting the difference between them gives a wind direction estimate accurate to within a few degrees, with no wind instrument required at all. If a session was sailed with logged wind data from an onboard sensor, that data is used instead and the estimate simply steps aside. Either way, by the time you open the replay, the wind direction, the manoeuvre markers, and the VMG figures are already sitting there waiting for you rather than something you have to derive yourself.

Watching More Than One Boat at Once

A single track answers "what did I do." The more interesting question, most of the time, is "what did everyone else do at the same moment, and how did that compare." That is what the multi-track view is for. Load several sailors' tracks into the same replay and the map plays them all together, each one in its own colour, moving in sync on the same clock. You can watch where the fleet split after the start, which side of the beat paid off, and how far apart two boats actually were at a mark rounding that felt close from the cockpit but might not have been.

A few controls make that comparison easier to hold onto as the replay runs. The track colouring can switch to a shared speed scale across every boat, so a quick glance shows which sailor was carrying more pace through a given patch of water rather than requiring you to read four separate numbers. The camera can lock onto one boat and follow it as the fleet spreads out, which is useful when you want to keep an eye on a specific training partner without losing them off the edge of the screen at 8x speed. You can choose which boats stay visible rather than always looking at the full group, and reset the view back to the whole course with one click once you have finished zooming in on a moment.

The deeper analytical layer on top of the multi-track replay, cutting every track into legs using the same start, mark, and finish gates and comparing distance, duration, and VMC leg by leg, is its own substantial feature and we have written about it in detail separately in our course analysis walkthrough. The short version that matters here is that the replay and the leg statistics are the same workspace: you draw the course once, and the system both plays the fleet back visually and produces a table underneath ranking everyone leg by leg. Watching the replay tells you where to look. The table tells you by how much.

What Replay Gives an Individual Sailor

For most sailors, the first thing replay does is turn a vague impression into a specific moment. "I think I was slow on the second beat" becomes "at 14:32 my speed dropped from 4.8 to 3.1 knots and took eleven seconds to recover, right after I tacked into a header I did not need to tack into." That level of specificity is hard to reconstruct from memory and routine to read off a replay.

Watching your own tacks back, rather than just seeing a count of how many you did, is often the fastest way to notice a habit you did not know you had. A tack that felt identical every time from inside the boat often turns out to be two different tacks depending on which side you started on, an asymmetry that is invisible until you see it laid out on a timeline rather than felt one at a time in the moment.

Training with a partner benefits from the same view. Two boats comparing distance ahead at the end of a speed test is a noisy way to judge a rig change, because the boat that came out ahead may simply have had the better side of a shift. Loading both tracks into the same replay, cut into the same legs, removes that ambiguity: you are comparing performance on the same patch of water in the same pressure, not just who finished the drill in front.

Replays are also shareable by a simple link, so a training partner, a coach, or a teammate who was not even on the water that day can be invited to look at the same session and comment on it, without needing to create an account first. A companion invite means the person reviewing the session with you sees exactly the same map, the same timeline, and the same numbers you do, which keeps the conversation grounded in the same evidence rather than one person describing a chart to someone who cannot see it.

What Replay Gives a Sailing Club

The same tools scale differently once you are running a fleet rather than a single boat. A bulk upload after a Wednesday night series turns a stack of individual GPX or FIT files into one shared replay for the whole group, ready for a debrief where the coach or race officer walks through the first cross, the pin end scramble, or the moment the fleet split on the second beat, on the same screen everyone actually raced on. Nobody has to reconstruct the moment from six different memories of it.

Handicap scoring sits in the same pipeline as the replay rather than off to the side of it, which matters for a mixed fleet. A club running a Wednesday series with a Laser, a couple of RS200s, and an old Wayfarer can look at the corrected results table and the multi-boat replay in the same sitting, rather than treating scoring and analysis as two separate systems that happen not to agree with each other.

None of this requires a club to run tracking hardware on the water or hire anyone to operate it. It works from whatever GPS-capable device sailors already carry, which matters for a club running weekly racing on a volunteer committee and a modest budget rather than a national championship with a professional race management contract. A junior squad coach can get a whole training group uploaded, processed, and ready for review before the sailors have finished putting their boats away.

A shareable replay link also gives a club a low-effort way to make a race feel like more than something that happened out of sight and is over now. Posting a link to Sunday's replay in the club group chat, where anyone can watch the fleet round the top mark again without an account, turns something that was invisible to nearly everyone into something anyone can look at afterwards.

Replay Is Not the Same Thing as Live Tracking

It is worth being precise here, because the two features solve different problems and get confused easily. SailingMetrics also offers live tracking, where a spectator link lets anyone ashore follow every boat on the course in close to real time while the race is happening, using nothing more than a browser and a link with no app or login required. We have written about that separately in how to follow a race live from the shore. It is a different use case: the parent on the clubhouse balcony who wants to know where their sailor is right now, during the race.

Replay is the other half of that picture, what you look at after the racing is done, when the question shifts from "where is she now" to "what actually happened on that second beat." A club that runs both gets the full loop: supporters watch the race live as it happens, and the same sailors sit down afterwards and pull the tracks apart leg by leg once everyone is back on the dock.

How This Compares to Other Tracking and Replay Tools

Sailing already has a reasonably crowded field of tracking software, and it is worth placing replay in that context rather than pretending the space is empty. We covered the full landscape in more depth in our platform by platform comparison, so this is the short version focused specifically on replay. The descriptions below reflect our understanding of each platform based on its own public marketing and documentation at the time of writing. Feature sets change, so check each provider's own site for current details before drawing any conclusions.

RaceQs is a well known name for free, animated race replay. Sailors record independently on their phones, upload afterwards, and RaceQs stitches the tracks into a 3D replay that can be rotated and scrubbed through. It is a genuinely popular option at club level, and based on its own public description its focus is squarely on replay rather than on leg statistics or a structured training workflow.

TackTracker is positioned, by its own description, around manoeuvre timing: automatic tack and gybe detection with leg timing alongside its replay. It sits between a pure replay tool and a broader platform, with its stated focus on manoeuvre timing specifically.

Kwindoo and eStela both describe themselves as built primarily around live event tracking for spectators and race organisers, with replay as a secondary part of that offering. That is a different problem from post-race training analysis, closer to what we describe in the live tracking post above, and both are worth evaluating directly if live event coverage for a bigger regatta is what a club needs.

At the professional end, systems like SAP Sailing Analytics and TracTrac are publicly known for powering the broadcast graphics and real-time spectator experience behind events like the America's Cup, built for a scale and a budget aimed at professional event organisers rather than clubs. They are mentioned here for completeness rather than as something a typical club would evaluate directly.

Where SailingMetrics aims to differ is in how the replay connects to everything else. Manoeuvre markers come from detection tested against a labelled evaluation dataset, wind direction is estimated from the track itself rather than requiring a separate sensor, and the replay sits directly next to leg statistics, handicap scoring, and a coaching layer of companion invites, shareable analyses, and an AI chat that can talk through a session. The honest trade-off is scope: this is built for dinghy and club-level keelboat racing, not offshore passage routing or professional broadcast infrastructure, and it does not try to be either of those things. As with the platforms above, this description reflects what the product does today and may change as the platform develops.

Common Questions

Do I need a special GPS device to use replay? No. A phone recording at a reasonable rate produces a perfectly good replay, and the wind direction and manoeuvre detection both work from that same track without any extra hardware. A dedicated logger sampling at a higher rate gives you more detail around the exact shape of a tack, but it is not a requirement to get started.

Does the replay work if a sailor's track has a gap in it? Small gaps, from a lost GPS signal under a bridge or a brief dropout, get interpolated across sensibly. If a track ends early because a device stopped recording or a sailor retired, that sailor's replay simply stops at that point without affecting anyone else's track in the same view.

Can a club use replay without running live tracking as well? Yes. The two features share a data pipeline but are entirely independent to use. A club can run purely post-race replay and analysis without ever setting up a spectator link, or run live tracking for race day and skip the replay afterwards.

Getting Started

Everything above starts the same way it always has: record a session and upload the track. Whether that is a single dinghy race, a training session with a partner, or a whole fleet's worth of Wednesday night results uploaded in one batch, replay is what turns the file sitting in your account into something worth looking at twice, and worth looking at together.

Create a free account and upload your next session, or if you already have tracks recorded, open one from your activities and press play. If you run a club or coach a squad, the bulk upload tool is the fastest way to get a whole race night or training group ready for a shared debrief.