Welcome back aboard. Issue #1 was about the 10pm commodore — the volunteer absorbing every gap your club's software leaves open. This issue takes the single heaviest item out of that inbox and goes deep on it: the duty roster.
The roster isn't a scheduling problem
Most boards treat the duty roster like a calendar problem: who's free on Saturday. It isn't. A calendar problem has one failure mode — a gap. A duty roster has a second, quieter failure mode — an uneven one, and it's the one that actually costs you volunteers.
Here's the pattern we hear from board after board: six reliable members get tapped for race committee every single season, because they're the ones who answer the email fastest. The other eighty members never hear their name. Nobody decided this on purpose. It's just what happens when the only record of "who served" lives in one person's memory, or a spreadsheet tab nobody else opens. Reliability gets punished with more work, and the people doing the most quietly stop volunteering for anything else.
That's the fairness ledger problem, and it's worth naming precisely because the fix isn't a nicer calendar app — it's making "who's served, how much, how recently" visible to the whole board, not just the roster owner.
What actually changes the conversation
The full template and the operating rules are in our duty roster guide, linked below, but one point is worth repeating here on its own: make the hours-served column public — visible to every member, not just the person running the roster. Most "why is it always me" conversations start because the load isn't visible, not because it isn't fair. Volunteers don't usually resent doing the work. They resent not being able to see that the work is shared.
The second point: swaps are where rosters actually die. A text-message swap that never makes it back into the roster is the single most common cause of a race-day no-show — not because anyone lied, just because the system of record and the actual plan diverged. One rule fixes most of it: no swap is real until the backup's name is in the roster and the original person's row says "swapped out." No exceptions, no group-chat swaps.
Where we are, honestly
The club I sail with has run its scheduling on Zeil since July 13 — that's where the product gets tested, and duty rosters are exactly the kind of thing that surfaces fast in daily use. To be clear: it's my own club, comped as a design partner in exchange for feedback, not a customer or a reference — we don't have paying customers yet, and we're not going to imply we do.
What's live in the product today for the roster problem specifically: eligibility and certification records per member, enforced server-side, so the system already knows who's qualified for race committee, safety boat, or a chaperone role before anyone gets assigned to it. Boat reservations with database-enforced overlap prevention. Crew assembly with invite/accept and minimum-crew enforcement. Announcements and a weekly digest instead of reply-all chaos.
What isn't live yet: an in-product duty roster with the fairness ledger built in — hours served, last assignment, automatic swap handling, all tied to the same certification data reservations already check. [ROADMAP — beta 2026-10-15 → GA 2026-12-01], shipping alongside race series scoring. If your board needs it before then, the honest path is the Founding Clubs program — locked founding pricing, committed dates, and direct input into how the roster and scoring beta work. We'd rather tell you the date than sell you something that isn't there yet.
This issue's tool
If you haven't grabbed it yet: the free six-column duty roster template — date, role, assigned to, confirmed, hours this season, backup contact — gets a season-length roster onto one page tonight, by hand, no software required. Get the free duty roster template →
Publish the whole season at once. Make the hours column visible to every member. Enforce the one swap rule. That alone fixes most of what a board fights about every fall.
The club story slot is still open
Still empty, and it stays empty rather than getting filled with something invented. If your club moved its roster off paper this season, send us two hundred words on what actually happened — including the parts that didn't work, which are the parts other boards need most. hello@zeilapp.com. We edit for length, never for sentiment, we will not name your club unless you say we can, and you approve the text before it runs.
Where to go next
If the roster is only one symptom, our guide to sailing club management software covers what to require from a system before you buy one, and boat scheduling software covers the booking half of the same problem. If your club's centre of gravity is racing, for racing clubs sets out what is live now and what lands with the October beta.