Deutsch
English
Results Software and Scoring Tools
Results software and scoring tools are the digital backbone of modern regatta organization. While the finish line and timekeeping provide the raw data, the software handles scoring, status codes, discards and publication. A professional results service and communication is hardly scalable without reliable scoring tools – from a club regatta with 20 boats to a championship with multiple fleets and handicap classes.
This guide explains which software solutions are common in sailing, how scoring systems are implemented technically, and what organizers should consider when selecting, setting up and operating live scoring.
What Results Software Must Deliver
Results software in sailing goes far beyond a spreadsheet. It must reflect the rules from the sailing instructions, be compatible with protest and jury processes, and output results in various formats.
Core Functions at a Glance
- Participant management: Start lists, sail numbers, national letters, crew data
- Series scoring: Low-Point, High-Point, bonus points, medal race
- Status codes: DNF, DNS, DSQ, OCS, BFD, ZFP and others per RRS
- Discards: Discard Rule rules and tie-break rules
- Handicap integration: ORC International, IRC, Club Handicap and club ratings
- Export: PDF, HTML, CSV, print for notice board and website
- Live scoring: Real-time updates for spectators and participants
Important: The software must never invent its own scoring rules. All parameters must exactly match the scoring systems and retirements from the notice of race and sailing instructions.
Common Scoring Tools in Sailing
In international and national regatta operations, several solutions have become established. The choice depends on event size, budget, handicap requirements and desired live integration.
Desktop vs. Cloud Scoring Compared
Sailwave as the Practical Standard
Sailwave is considered the de facto standard for most regatta organizers. The free software supports low-point systems, high-point, Appendix A and Q, team racing, match racing and numerous handicap formulas. Results can be exported as HTML and embedded on the regatta website.
For organizers, this means: an experienced Sailwave operator is often more valuable than the most expensive cloud solution. Pre-season training, test runs with historical data and a backup operator significantly reduce risk on race day.
Cloud Solutions and Live Scoring
For large events with public interest, cloud-based platforms are gaining ground. They combine registration, start lists, live results and often live tracking and apps in one system. Participants see their position in real time, media access current standings, and organizers save manual upload steps.
The downside: dependence on internet, server availability and platform know-how. Every cloud event needs an offline backup plan – typically Sailwave or Excel on a laptop with start lists already imported.
Implementing Scoring Systems Technically
The scoring systems and retirements from the sailing instructions must be configured in the software before the first race day. Errors here lead to protests, reputational damage and, in the worst case, invalid results.
Low-Point System (Appendix A)
The most common system in fleet racing: each placing corresponds to the point value of the position. DNF and DSQ typically receive "number of competitors plus 1" points. Discards are calculated according to the rules defined in the SIs.
- Set series length: Number of scoring races and discards
- Medal race: Activate separate race with double scoring
- Tie-break: Configure RRS A8 and A9 correctly in the software
- Provisional vs. final: Distinguish status before and after protest deadline
Handicap Scoring
For ORC, IRC or PHRF regattas, the software calculates corrected times. Integration with ORC and IRC in detail is crucial here: time-on-time factors, wind band corrections and current certificates must be correct.
Handicap Scoring: Workflow
OCS Tracking and Start Status
On Course Side (OCS) and black-flag starts require precise recording. Modern scoring tools integrate start lists with recall information: boats that were recalled receive OCS or BFD status without the operator having to search manually.
Integration with Timekeeping and RC
- Pre-start list: Record all boats that started before the signal
- Recall protocol: Document individual recall and general recall
- Status assignment: Enter OCS, ZFP, BFD immediately after RC decision
- Reconciliation: Score finish times only for validly started boats
OCS rate at club regattas: Typical OCS rate is 3–8 percent of starters per race. With U-flag starts and clear RC communication, the rate tends to decrease.
Setup Before the Regatta
Clean software setup saves hours on race day and avoids errors. The ideal timeline begins weeks before the event.
Checklist: Software Setup
- Notice of race and sailing instructions translated into scoring parameters
- All fleets and classes created (one-design, handicap, age classes)
- Start lists imported and sail numbers checked against entry list
- Handicap certificates (ORC/IRC) imported and validity verified
- Discard rules and tie-break configured
- Test run with dummy race results completed
- Export templates (HTML, PDF) created and tested on website
- Backup laptop with identical configuration provided
- Operator and deputy trained
- Offline plan documented (internet outage, server failure)
Ensuring Data Quality
Errors in start lists multiply in scoring. Before each race day:
- Reconcile entry list with physical boat inspection
- Check sail numbers and national letters
- Validate handicap data against measurement records
- Test export of provisional results list to the jury
Tip: Use the same boat IDs in timekeeping, tracking and scoring software. A unified numbering system prevents assignment errors in large fleets.
Live Operations on Race Day
On race day, speed and accuracy count. The scoring operator works closely with timekeepers, the race committee and the results service.
Live Scoring: Workflow on Race Day
Role Distribution in the Scoring Team
- Lead operator: Data entry, scoring, export
- Plausibility check: Second person verifies each race before publication
- IT support: Website, app, live feed, backup systems
- Jury liaison: Status changes after protest decisions
Provisional and Final Results
Provisional results must be published as quickly as possible after the finish – typically within 15 to 30 minutes for medium-sized fleets. Final results follow after the protest period expires and all hearings are completed.
Warning: Never label provisional results as final. Sailors plan tactical decisions for upcoming races based on the standings – incorrect status information leads to loss of trust and formal protests.
Integration with Results Service and Media
Scoring software is only one building block. Publication via website, app, notice board and social media makes results public. Cloud platforms automate this step; with Sailwave, the operator exports HTML files manually or via FTP.
For live events, connecting to tracking systems is worthwhile: spectators see position and standings in parallel. Details in the article Live Tracking and Apps.
Results Publication: Timeline After Finish
Choosing the Right Solution
Software choice depends on event type, budget and technical infrastructure.
Decision Criteria
- Event size: Under 50 boats, Sailwave is often sufficient; above that, consider cloud solutions
- Handicap share: ORC/IRC events need specialized modules
- Live requirements: Media, sponsors and spectators expect real-time results
- Budget: Plan costs for licenses, support and training
- Know-how: Existing operator competence more important than feature overload
- Backup: Always have a second solution for failure scenarios
Common Mistakes and How to Avoid Them
- Wrong discard configuration: Series scoring does not match SIs
- Outdated handicap certificate: Corrected times wrong, protests unavoidable
- Boat assigned incorrectly: Similar sail numbers, insufficient check
- Provisional marked as final: Loss of trust, formal objections
- No backup: Laptop failure stops entire results service
- Operator overload: One person for entry, check and export
FAQ: Common Questions About Results Software
Can I use Sailwave and cloud in parallel?
Yes, as backup or for different fleets.
Who is responsible for software errors?
The organizer, not the software.
Must results be posted on the notice board?
For many events yes, legally relevant.
How long to archive results?
At least for protest and appeal periods, ideally permanently.
Is Excel enough for championships?
Only with an experienced operator and double checking.
Future: API, Automation and AI Support
Development is moving toward full automation: timekeeping systems send finish times directly to scoring software, OCS detection via video or tracking reduces manual entries, and APIs connect registration, scoring and rankings of national associations.
For most organizers, the pragmatic approach remains: proven software, trained operators, clear processes and a solid backup plan. Technology supports – it does not replace the care of the results team.
Related Topics
- Results Service and Communication
- Scoring Systems and Retirements
- Tie-Break and Discard Rules
- ORC and IRC in Detail
- Live Tracking and Apps
Last updated: July 4, 2026