Results Service and Communication

The results service is the backbone of every successful regatta. While the Race Committee and PRO manage the race on the water, a professional results service ensures that participants, coaches, spectators and media always know who is where and when. Communication connects timing, scoring, protest procedures and public information into a reliable overall system. Without clear processes, uncertainty arises, protests due to information gaps, and loss of trust in the fairness of the event.

This guide explains how organizers build results service and communication from club regattas to championships, which channels are used when, and how technical tools can be integrated sensibly.

Why Results Service and Communication Are Inseparable

Sailing regattas thrive on transparency. Unlike sports with a central playing field, sailors often follow the action only from a distance – from the dock, the clubhouse or via app. The results service must therefore do more than a simple results list: it informs about start times, course changes, protest deadlines and both provisional and final scores.

The finish and scoring procedures define the sporting basis. The results service implements these rules understandably and promptly for all involved. Communication is not a by-product, but an integral part of regatta organization – comparable to courses and marks or the start procedure.

Results Service from Finish to Publication

1

Finish & Timing – Capture raw data and assign to boat

2

Data Entry – Plausibility check and document status codes

3

Provisional Results – Publish status "provisional"

4

Protest Window – Communicate deadlines, hearings and open protests

5

Final Scoring – Status "final" after jury decisions

6

Publication & Archive – Save lists and report to associations

Core Tasks of the Results Service

A modern results service takes on several closely interlinked tasks. The larger the event, the more important clear role distribution between race committee, secretariat and results team becomes.

Timing and Data Entry

The basis of every result is precise finish line and timing. Whether by hand stopwatch, electronic timing on the committee boat or GPS-based tracking – raw data must be captured immediately after the finish and assigned to the correct boat.

Boat identification: Correctly assign sail number, national letters and hull number if applicable
Status codes: Document DNF, DNS, DSQ, OCS and BFD cleanly
Backup: Redundant recording for large fleets (two independent timekeepers)
Immediate check: Cross-check with expected start list before publication

Scoring and Results Calculation

After raw data entry, the results team calculates the point scoring according to the sailing instructions – low-point system, high-point, handicap corrections or medal race rules. Provisional results are only published when all finishes have been recorded and plausibility-checked.

Protest and Information Communication

Protests change results. The results service must therefore work closely with the jury and inform participants about deadlines, hearing times and changes. What sailors expect after the race is also described in the article After the Race: Protest and Results.

Important: Provisional results are not final results. Every publication must clearly indicate the status "provisional" or "final" – in the list, on the website and in the app.

Communication Channels in Regatta Operations

Regattas use several parallel channels. The art lies in using each channel for the right purpose and avoiding contradictions.

Channel

Typical Content

Reach

Priority

VHF Radio

Start signals, course changes, safety, recall

All boats on the water

Highest – binding for RC

Notice Board

SI changes, protest lists, results

Participants on shore

Legally relevant at many events

Regatta Website / App

Live results, start lists, tracking

Worldwide, including spectators

High – public perception

Email / Push

Personalized info, weather updates

Registered participants

Medium – supplementary

Social Media

Highlights, winner photos, brief updates

Interested public

Low – not binding

Radio Communication on the Water

VHF radio remains the binding channel between committee boat and fleet. Results-relevant radio messages – such as "All races finished" or notices of postponed results publication – should be brief, clear and on the channel specified in the sailing instructions.

Notice Board and Digital Equivalents

Traditionally, provisional results are posted on the notice board in the regatta office. Digital events replace or supplement this with a fixed URL. Crucial: timestamp and version number of every publication, so it is traceable which results list applied at the time of a protest submission.

Schedule: When Which Information Arrives

A well-thought-out communication schedule prevents chaos after the race. The following guidance applies to typical inshore regattas with multiple races per day:

Immediately after finish: Radio message "Last finisher through the line"
Within 15–30 minutes: Provisional individual race results on the notice board
Within 60 minutes: Updated overall standings (provisional)
During protest window: List of open protests, hearing times
After jury decision: Updated results marked "amended"
Evening: Final daily results (final), if all protests are resolved

Communication After the Last Race of the Day

0 min

Last Finisher – Radio message, timing completed

15 min

Provisional Race Results – Individual race results published

45 min

Overall Standings – Updated daily standings (provisional)

90 min

Protest Deadline – Deadline for protest submissions ends

120 min

Hearings – Jury hears submitted protests

180 min

Final Results – Final daily results (if possible)

Technical Solutions for Live Results

Modern regattas rely on scoring software that connects timing, scoring and publication. Common systems allow import of timing files, automatic calculation of handicap corrections and output as a website or API for apps.

Requirements for Scoring Software

Criterion

Club Regatta

Championship

Multi-class capability

2–5 classes

10+ classes in parallel

Handicap integration

Optional (ORC/PHRF)

Mandatory for rating classes

Live update

Desirable

Mandatory

Offline capability

Yes (unstable network)

Redundant systems

Export for DSV/World Sailing

No

Yes for ranking-relevant events

Participant expectations: Surveys among regatta sailors show: Over 80 percent expect provisional results within 30 minutes after race end. At events with medal race or decisive final race, pressure rises to under 15 minutes.

Live Tracking as a Supplement

GPS tracking does not replace official timing, but supplements the results service for spectators and coaches. Positions on the course help trace tactical decisions – scoring however always remains tied to the binding finish time.

Tip: Visually separate tracking display and official results list. Spectator apps must never give the impression that live positions are already scored results.

Team Structure and Roles

A functioning results service needs clear responsibilities. At small events roles may overlap; from about 50 boats a dedicated staffing is recommended.

Results service manager: Overall responsibility, coordination with PRO and jury, approval of publication
Timing coordinator: Recording and plausibility check of all finish times
Scorer: Calculation of standings, discard rules, handicap corrections
Communications officer: Notice board, website, social media, press
IT support: Software, network, backup systems

Coordination with Regatta Organization

The results service is not an isolated post, but part of overall organization as described in Planning and Running a Regatta. Already in the planning phase, number of race days, classes, expected protest rate and IT infrastructure should be defined.

Checklist: Results Service Before the First Race Day

Scoring software installed, tested and equipped with backup laptop
Start lists fully imported, sail numbers checked
Scoring rules (low point, discards, tie-break) entered in software
Notice board set up physically and digitally with fixed URL
Radio channels documented in SI, results messages formulated
Timing team trained, emergency protocol defined in case of failure
Jury contact and protest schedule coordinated with results service
Template for provisional/final labeling on all channels
Power supply and WiFi secured at results location
Archiving plan for results after event end defined

Common Mistakes and How to Avoid Them

Warning: Results without status labeling ("provisional" vs. "final") are a common source of protests and dissatisfaction. Always label explicitly.

Typical problem cases:

Confusion of similar sail numbers – Double plausibility check by two people
Delayed publication – Participants miss protest deadlines; solution: adhere to clear SI time requirements
Contradictory information – Radio says something different than website; solution: one communications officer approves
Software failure – Keep paper backup and manual emergency lists ready
Unclear handicap values – Validate ORC/IRC certificates before the event

FAQ: Frequently Asked Questions About the Results Service

When are results final?

When all protests are decided and published as "final".

Can I protest with "provisional" results?

Yes, within the SI deadline.

Who corrects incorrect timing?

Race Committee; results service implements the correction.

How long to archive results?

According to association requirements, permanent online archiving recommended.

Best Practices for Different Event Sizes

Small Club Regatta (up to 40 boats)

Volunteer team, simple software or Excel, results on notice board and by email. Radio for start and finish, results service usually in the clubhouse. Focus on accuracy over speed – but still within 45 minutes after race end.

Regional Championship (40–150 boats)

Dedicated results location, live website, close coordination with jury. Redundant timing for large classes. Press releases after each race day.

National and International Events (150+ boats)

Professional results team, multiple parallel scorers, API connection for media and tracking partners. Press conferences, multilingual communication, archiving for ranking systems.

Quality Assurance and Follow-up

After the event, a structured debriefing pays off. What went well? Where were there delays? Were protest deadlines met? The answers flow into planning the next regatta.

Results archive: Save all final lists with date and version
Participant feedback: Brief survey on information quality
Technology review: Document software logs, failures, improvement needs
Handover to association: Report ranking-relevant events to DSV or class association