Review a race after the finish
A useful post-race review needs three records: what the crew committed to, what the boat sailed, and what weather the plan expected. A project keeps those pieces connected.
Arm the plan
Before the start, open the project's race-plan page and choose the run the crew intends to sail. Arm freezes that run and the exact course version behind it. A later route does not silently replace the plan; arming a replacement creates a new snapshot and leaves the earlier choice in the record.
The Before the gun checklist reads five facts from the selected run. It is not another settings form. Use it to catch the wrong course, boat, limits, weather cycle, or coverage while those are still fixable.
Add what the boat sailed
After the finish, add a track in either of two ways:
- Upload a GPX file exported from the plotter or logger.
- Import your boat's history from the tracked race attached to the project.
Name the recording clearly when more than one device or tracker is available. The stored track is the evidence used by every later comparison.
Compare plan and track
Open Planned versus sailed and choose the armed snapshot and recording. The comparison is computed when you open it from the frozen course, frozen route, and stored track. It is not a stale image captured on race day.
Read geometry before speed: where the plan and boat separated, whether they later converged, and which course constraint or weather feature sat at the split. Tracker chords and missing fixes still limit what can be inferred about manoeuvres.
Check the forecast
Was the forecast any good samples the relevant forecast fields along the sailed track and compares the available models. This asks whether the plan's weather arrived, not whether the crew executed the route. Keep those questions separate.
Retained project weather makes the review richer, but the run, plan snapshot, and track remain after the ninety-day weather archive expires.
Build the race story
The story page collects material the crew wants to keep together: planned-versus-sailed analyses, forecast scorecards, tracks, crew notes, images, vendor files, and outside URLs.
Attachments start private to the project. Where link sharing is enabled, the permitted owner or author can expose one attachment without opening the whole project. Crew names are redacted from shared views unless each person opts in.
The result is not a polished public article by default. It is the project record from which a crew can explain what it planned, what happened, and which evidence supports that account.