Officer of the Day Checklist for UK Sailing Clubs
What an OOD does on race day, broken into pre-race, day-of, and post-race tasks. Print this and keep a copy in the race box.
In brief
The race-day job in four checks
-
Confirm the forecast, tide, safety cover and qualified duty crew before anyone launches.
-
Inspect radios, fuel, first-aid kit, flags, keys and the sign-on process.
-
Brief the race team, record decisions and stop racing when the safe limit is reached.
-
Close the day with results, incident notes, equipment faults and the next committee action.
Visual guide
A race day has one clear line of command
Prepare the people and equipment, run the course, then record what happened.
Follow the marked routeWhat the Officer of the Day does
The Officer of the Day, OOD for short, is the person responsible for safe, fair racing on their nominated day. The job sits between the club committee and the racers on the water. If something happens on the start line, in the dinghy park, or to a member of the duty crew, the OOD is the one making the call.
Strictly speaking, the OOD and the Race Officer are different jobs. The Race Officer (RO) runs the race itself: the sequence, the line, the course, the recalls, the finishes. The OOD oversees the whole race day, the club duty rota, safety cover, the bar and galley, and the welfare of everyone on site. At RYA-aligned open meetings the two roles are usually held by different people. At club level, in most UK sailing clubs, one competent person does both, and the title flips depending on whose Sailing Instructions you are reading.
For the rest of this checklist, treat OOD as the catch-all role: the person in charge on race day, whatever the badge says. The work breaks into three parts. Pre-race is everything before you reach the club. Day-of is everything from arrival until the last boat is back on the water. Post-race is the wrap-up that stops problems compounding into next week.
Pre-race checklist
Most race-day problems are made the week before. A confirmed duty crew, a sensible course plan and a weather scan in the days running up to the event remove most of what would otherwise be Saturday morning chaos.
Start with the duty crew. Three or four days before the race, confirm every slot on the rota: Race Officer, Assistant Race Officer (ARO), Safety Boat helm, Safety Boat Crew, Galley, Results. Do not assume the rota is correct because it was correct in February. Phone or message every named member and get a yes back. If anyone is unavailable, sort the swap before Friday night, not Saturday morning.
Pull up the forecast forty-eight hours out and again the night before. Check wind speed and direction, gusts, tide times, and any front coming through the race window. Note the high water and low water for the day if your club is tidal. Decide your likely course shape (beat-reach-run, windward-leeward, or triangle) and write down a fallback for if the wind clocks round. Brief the RO and ARO on the plan.
Check the equipment the day before if you can. Work through four groups:
- Safety boat: fuel, spare fuel, kill cord, anchor and warp, throw line, first aid kit, knife, paddle, tow line and bailer.
- Signals: clean flags facing the right way, plus a working gun, hooter or horn with spare gas.
- Race box: keys, sign-on sheet or open digital form, charged radios and spare batteries.
- Comms: a radio check between the race box, committee boat and safety boat on the agreed channel.
Check each control against the club's current risk assessment.
- Confirm RO, ARO, Safety Boat helm and crew
- Confirm Galley and Results duty
- Check 48-hour and morning-of forecast
- Note tide times if applicable
- Agree primary and fallback course
- Brief RO, ARO and Safety Boat on plan
- Safety boat fuel, kill cord, anchor, throw line
- First aid kit checked and in date
- Flags: AP, N, X, First Sub, P/I/U/Black, class flags
- Sound signals tested with spare canisters
- Radios charged, channel agreed, comms tested
- Sign-on sheet ready (paper or digital)
Day-of checklist
Arrive earlier than you think you need to. Two hours before the warning signal is normal. Half of that goes on briefing the duty crew and laying the course. The rest is buffer for the things you cannot predict.
Briefing first. Get the RO, ARO, Safety Boat helm and crew in one room or huddle on the slipway. Walk through the day: number of races, target start time, the planned course, wind and tide, any boats with juniors or new sailors who might need a closer eye, the comms plan, and the criteria for postponement or abandonment. Make the criteria explicit. "We postpone if the average wind drops below five knots before the warning signal" is a usable rule. "We'll see how it looks" isn't.
Course laying is the next block. Take the safety boat with marks loaded and lay the windward mark first, then the leeward, then any wing or gybe marks. Set the line between a committee boat or pin-end mark and the start mark, square to the wind. Check sight lines from the line to the windward mark and adjust before you commit. A line square to the wind and a beat that is genuinely upwind are the two things that decide whether the racing is fair.
Run the start sequence cleanly. Standard RYA-aligned five-minute sequence: warning signal at five minutes (class flag up, one sound), preparatory at four minutes (P, I, U, Z or Black flag up, one sound), one-minute signal (preparatory flag down, one long sound), and start at zero (class flag down, one sound). Whatever procedure you use, write the times of every signal on the race log immediately. Trust nobody's memory of when the gun went, including your own.
Watch the line at the start. If one or more boats are over and identifiable, individual recall (X flag, one sound) until they return. If several are over and you cannot identify them, general recall (First Substitute, two sounds) and restart the sequence. If you are using a Black flag or U flag, know the rules around what that means for boats over the line in the last minute, those rules sit in the Racing Rules of Sailing and your Sailing Instructions, and they have real consequences for competitors.
Once the fleet is racing, watch the wind. A shift of fifteen or twenty degrees on a beat may need a new windward mark for the next race. A dying breeze may call for a shortened course. Use the S flag with two sounds at the finishing mark. If a squall or storm is coming, abandon early rather than late.
Put the safety boat where it can see the most exposed leg, often the run where capsizes cluster. Record each finish time against the sail number. Log every retirement.
Welfare runs alongside everything else. Juniors fed and watered between races. Members coming in cold get warm. A sailor who has had a bad capsize gets checked over even if they say they're fine. The OOD owns this on race day, regardless of who is technically afloat.
Post-race checklist
The race is over but the OOD's day is not. Twenty minutes spent now saves an hour next week.
Get the results in. Hand the finish sheet to the Results duty (or sit down and key it in yourself) before anyone leaves. Apply handicaps, run the calculation, and post provisional results to the noticeboard or the club portal. Note the protest time limit clearly so any aggrieved competitor knows the window.
Recover the safety boat. Wash it down, refuel ready for next week, secure the kill cord, lock the kit store. If anything broke or ran low, write it on the equipment log so the next OOD doesn't inherit the problem. Same for flags, radios and the first aid kit. Anything used or expired gets noted.
Hold a short debrief with the duty crew. What worked, what didn't, anything to flag for the committee. Ten minutes is plenty. If there was an incident on the water, log it in the club's incident book with date, time, conditions, sailors involved, what happened, what action was taken and follow-up needed. Some incidents are reportable to the RYA under their reportable incidents framework: capsize requiring assistance is generally not, anything involving serious injury, hospitalisation, or fatality is, and the boundary in between gets reviewed by the committee. If in any doubt, log it and let the committee decide.
Hand over to the next OOD. A quick message or note about anything they should know: a low fuel can, a flag that needs replacing, a member who had a hard day and might want a check-in.
Common scenarios and the right call
Four decisions every OOD eventually has to make. Make them quickly and clearly.
When to postpone (AP)
Wind has died below sailable. Fog or visibility under safe limits. You need more time to lay the course. A safety boat is delayed. Conditions should improve and the race is still on. Flag AP, two sounds going up, one sound coming down.
When to shorten course (S)
Wind dropping mid-race and the leaders will not make the next mark. Tide turning against the fleet and back markers will be stuck. Time pressure on the day means a long second race is unsafe. Flag S at the finishing mark, two sounds. Finish them at the next mark.
When to abandon (N)
Conditions have become unsafe. Squall, lightning, lost safety cover. Serious incident on the water. Course is no longer fair and cannot be re-set. Flag November, three sounds. Recover everyone before anything else.
Recall procedures
One or two boats over and identifiable: individual recall, X flag, one sound, leave the flag up until they return. Several over or unidentifiable: general recall, First Substitute, two sounds, restart the sequence. Black or U flag procedure changes the consequences, check your SIs.
OOD qualifications and expectations
There is no single national qualification that says "you are now an OOD". UK clubs set their own bar, written into the club's Sailing Instructions, the duty rota rules, and the club's risk assessment. Most clubs converge on a small set of expectations.
First Aid is near-universal. A current first aid certificate, refreshed every three years, is the baseline. RYA Powerboat Level 2 is the standard if the OOD is also driving the safety boat. Familiarity with the Racing Rules of Sailing, particularly Part 3 (the conduct of a race) and the relevant signals, is expected. Most clubs ask new OODs to at least one or two race days before running their own, and to stay in radio reach of a more experienced member on their first solo turn.
RYA Race Officer training (Club Race Officer or Regional Race Officer) is preferred and increasingly common. It is mandatory at open meeting level and at championship level, but not generally mandatory for ordinary club racing. If your club is RYA-affiliated, the local RYA training centre will run Club Race Officer courses several times a year and they're well worth doing. Track qualifications and expiry dates somewhere central (the duty rota tool, the membership system, or a spreadsheet) so admin can chase renewals before they lapse.
The OOD job, with the admin handled
SailHQ is sailing club management software built around the duty rota. For OODs that means duty types with qualification gating, so a member without Powerboat L2 can't accidentally end up in the safety boat slot. Members can request swaps from the portal and an admin approves with one click. No WhatsApp threads, no double-bookings. Email reminders go out before every duty so nobody arrives surprised. The admin dashboard shows a live weather widget for the club's location, pulled from Open-Meteo, so you can see what's coming before the duty crew does.
None of that replaces the OOD's judgement on race day. It just removes the admin around the role.
OOD questions
No national rule sets a minimum. Each club should state its requirements in its Sailing Instructions and risk assessment. Most clubs expect an OOD to know the Racing Rules of Sailing, read the club's race documents, hold current first aid training and shadow an experienced team. If the OOD also helms the safety boat, RYA Powerboat Level 2 is the usual standard. RYA Race Officer training is often needed for open meetings, but club racing rules vary.
Assess cover first. If a second safety boat is on the water and can take over the affected area, redirect it and continue racing. If you only have one safety boat and it is no longer operational, abandon the race using flag November with three sounds, recover all competitors, and tow or escort the disabled safety boat back. Do not let racing continue with no safety cover. Log the failure, the time, and the decision in the race log so the club can review it later.
Postponement, signalled by flag AP (Answering Pennant), means the start is delayed but the race is still going to happen. Use AP when conditions will likely improve, the wind has died, fog is lifting, or you need more time to set the course. Abandonment, signalled by flag November, means the race is cancelled and will not be re-sailed unless the Sailing Instructions say otherwise. Use November when conditions are unsafe, a serious incident has occurred, or the race cannot fairly continue. AP buys time. November ends it.
Use flag X with one sound when you can identify the boats over the line. Those boats must return and start correctly while the race continues. Use the First Substitute with two sounds when too many boats are over to identify, or when the start was unfair. The whole fleet returns and the start sequence begins again. Black flag and U flag starts change the recall and penalty rules, so check the Sailing Instructions before signalling.
At most UK club race days, yes. The Race Officer runs the race itself, the start sequence, course management, finishes, and recalls. The Officer of the Day is responsible for the wider race day, briefing the duty crew, overseeing safety boats, welfare, and the post-race wrap-up. In smaller clubs the same competent person handles both roles. At larger events or open meetings the roles are usually split, with the Race Officer afloat on the committee boat and the OOD ashore coordinating logistics. The split makes sense whenever the workload is too much for one person to do safely.
Next on SailHQ
Prepare the whole race day
Move from the checklist into fair duties, clear race documents and a rota members can use.