Projects
A project is a race. It holds the course you drew, the boats you may run it with, and every route anyone has asked for — for as long as your account lasts, rather than for the weeks a share link survives.
Without one, the workspace has no memory. A course built and never solved is gone on reload, and a finished route lives only behind its link. That is the right shape for a quick answer and the wrong shape for a race you plan over a month, with people.
Projects are part of Pro. Being invited onto somebody else's project is free.
Who is on a project
An owner, editors, and viewers. The owner invites people by email, changes roles, removes members, and deletes the project. Editors can draw courses, add boats, run routes, arm a plan, and import tracks. Viewers can read the project but cannot change it or spend the owner's Pro entitlements in the workspace.
An editor invited onto a project routes at the project owner's limits. A viewer does not.
Runs inherit the project's plan, not yours
A route started inside a project runs at the project owner's entitlements. A navigator on the free tier, invited to help plan an offshore race, gets the offshore limits while working there — they were asked to help plan this race, and which models they can reach should not depend on whether they also subscribe.
Your own plan still applies to everything you do outside that project.
Courses
A project keeps as many courses as you like: the official one, and the variations worth arguing about. Loading one puts it in the editor; saving writes it back.
Courses can be drawn by hand, imported from a GPX or KML file, copied from the preset library, or pulled from an attached tracked race — which brings the organiser's own geometry with it.
Two people editing one course is a case the app expects and refuses to guess at. A save carries the version it started from, and a save that arrives second is refused rather than merged: half of one course and half of another is a course nobody drew. You are shown what changed and choose whether to take it or keep yours.
Boats
A boat belongs to you, not to a project — navigators sail more than one boat, and sail in other people's races. A boat carries a name, its performance (an ORC certificate or a saved polar), and the settings you would otherwise retype every time: draft, safety margin, performance percentage, manoeuvre penalties, wave comfort.
Adding a boat to a project is what permits that project's other editors to run with it. There is no second switch. Removing it takes the permission back.
They still never see the polar. As everywhere else in WX Navigator, the numbers travel as a digest and are read only to compute — see performance models.
Runs are a record, not a workspace
Every route started inside a project is appended to its history: who asked, which boat, which version of which course, what was requested, and what came back. A run can be labelled a what-if with a note, so an exploration reads as one.
Nothing in that history can be edited afterwards, including by us. A run is not corrected by a later run — the later run is another entry, and the record of what a crew considered is only worth keeping if the ideas they rejected are still in it.
The full result of a project run is held far past the usual retention, so a route from last season still opens.
From plan to race record
A project can mark one run as the plan the crew intends to sail. Arming it freezes the run and the course version behind it. Before the gun, the readiness check reads back the course, weather, performance model, limits, and forecast coverage as five explicit checks.
After the finish, upload the boat's GPX track or import it from the attached tracker. The project then compares planned and sailed geometry and scores the forecast along the recorded track. The race story collects those analyses with crew notes, images, and outside reports. See Review a race after the finish.