Deutsch
English
Live Scoring and OCS Tracking
Modern sailing regattas thrive on transparency and speed. Whereas results used to appear on the notice board only hours after the finish, sailors, coaches, media and spectators today expect real-time information: Who is leading after round three? Who was identified as On Course Side (OCS)? Which boats must sail back? Live scoring and OCS tracking form the technical backbone of this expectation – they connect the race committee, scoring team and audience in a continuous data flow.
This guide explains how live scoring works, which systems capture OCS violations automatically or semi-automatically, and which organisational processes organisers must plan for. It complements the overview of scoring software and scoring tools as well as the article on Sailwave and regatta software with a focus on real-time scoring and start line discipline.
What is Live Scoring?
Live scoring refers to the continuous, visible updating of interim and overall results during race day. Instead of waiting for a manual export from desktop software at the end of each race, finish times, status codes and series standings are transmitted immediately after entry to websites, apps or large display boards.
Distinction from Classic Scoring
- Classic scoring: Results are entered manually in Sailwave or comparable software after each race, exported as HTML and uploaded to the website – latency typically 15 to 60 minutes.
- Live scoring: Finish data flows via API, cloud dashboard or dedicated scoring apps directly into a public frontend – latency often under two minutes.
- Hybrid operation: Many organisers use Sailwave as the master system and synchronise via export or plugin with a live platform.
Important: Live scoring does not replace the responsibility of the race committee. Status codes such as OCS, BFD or DSQ must still be set correctly from a technical standpoint – the software only speeds up publication.
OCS Tracking: Start Line Discipline in the Digital Age
OCS stands for On Course Side – a boat is on the wrong side of the start line at the starting minute or crosses the line before the starting signal. According to the RRS, OCS is penalised with a Scoring Penalty (SCP) or as disqualification for the race in question, depending on the scoring systems and retirements in the sailing instructions.
OCS tracking encompasses all technical and organisational measures used to detect violations, document them and transmit them to the scoring system. Details on status codes can be found in the article DNF, DNS, DSQ and OCS.
Manual vs. Automatic OCS Detection
Manual detection remains the standard at most club regattas: start umpires on the committee boat or at the pin-end mark identify OCS boats visually, report sail numbers by radio to the scoring team and hoist the appropriate flag for individual recall in accordance with individual recall and general recall.
Automated systems use GPS transponders, AIS data or optical cameras at the start line. They capture position and time of line crossing and mark boats that passed the line before the starting signal. For U-flag or black-flag starts, relevance increases – see black flag and U-flag.
OCS Detection to Live Results
Technical Solutions Compared
Organisers choose between purely manual workflows, semi-automatic GPS systems and fully integrated professional platforms. The decision depends on budget, fleet size and media requirements.
Latency vs. Reliability
Live Scoring Architecture: From Finish to Display
A robust live scoring system consists of several layers that can fail independently without jeopardising the entire race day.
Data Entry Layer
- Finish booth: Timekeepers record sail number and time via tablet, radio or paper list.
- Scoring operator: Enters finish data and status codes into the master software.
- OCS coordinator: Maintains the OCS list immediately after the start and communicates with the race committee and PRO.
Transmission Layer
- Cloud sync: Regatta platforms synchronise automatically with the central server.
- HTML auto-refresh: Sailwave export is updated at fixed intervals via script or CMS upload.
- API push: Finish events trigger webhooks that update frontend and app.
Output Layer
- Event website: Embedded iframe or native results page.
- Mobile apps: Regatta-specific or class apps with push notifications.
- On-site displays: Large monitors at the harbour, in the clubhouse or at the finish area.
The interface with live tracking and apps is close: tracking shows positions on the water, live scoring delivers the formal scoring. Both systems should use the same boat identification (sail number, transponder ID).
Live Scoring Data Flow
OCS Tracking in Practice
Preparation Before Race Day
- Measure start line precisely and document GPS coordinates (for geofence systems).
- Create OCS protocol template: sail number, time, recall type, return yes/no.
- Coordinate radio channels between start team, scoring and PRO.
- Check sailing instructions: OCS penalty (SCP vs. DSQ), recall rule, time limit for return.
- Conduct test run with two to three boats for automatic systems.
During the Start
- Start umpires focus exclusively on the line – no double duty with scoring.
- OCS reports are transmitted with sail number and position (pin/boat end).
- For individual recall: immediately mark affected boats as OCS provisionally in the scoring system.
- Boats that correctly sail back and restart receive no OCS status – delete entry.
After the Start
- Finalise OCS list and hand over to scoring operator.
- Set OCS status in software before the race is officially closed.
- For live scoring: trigger update and spot-check on the website.
- Communicate protest time limit and protest time limit and hearings – OCS can be subject to hearings if sailors dispute identification.
Warning: Automatic OCS systems are aids, not a replacement for umpire decisions. GPS drift, poor reception or incorrect transponder mounting can cause false alarms. The race committee retains final decision-making authority.
Checklist: Setting Up Live Scoring and OCS Tracking
- Master scoring software (e.g. Sailwave) configured with correct SI parameters
- Live frontend (website/app) populated with test data and checked for responsiveness
- OCS protocol and radio plan created for start team
- Scoring operator and OCS coordinator named and trained
- Backup plan for internet outage (offline export, notice board)
- GPS/transponder tested (if deployed)
- Uniform boat IDs reconciled in tracking and scoring
- Latency target defined (e.g. results visible within 5 minutes of last finish)
- Data protection: consent for GPS tracking with mandatory transponders clarified
- Media release: schedule for live results coordinated with press
Best Practices for Organisers
Plan for Redundancy
No live system is fail-safe. Professional events run a parallel manual workflow: paper finish list, local Sailwave file and HTML export as backup on the notice board.
Communication with Sailors
Sailors expect clarity. Brief notes in the sailing instructions and at the morning briefing help:
- Where do I find live results? (URL, app name)
- How quickly are OCS reports visible?
- Who do I contact for incorrect OCS assignment?
Tip: Use QR codes at the dock and in the clubhouse that lead directly to the live results page. This reduces enquiries to the scoring team and relieves the race office.
Media and Sponsoring
Live scoring makes regattas tangible for spectators and sponsors. Organisers should integrate live results into sponsor packages and social media strategy.
Sailor expectations: Typical values at national events: over 80 percent use mobile results apps; over 60 percent expect results within 10 minutes of race end.
Common Mistakes and How to Avoid Them
- OCS entered too late: Boat is already racing, scoring sets OCS only after finish – leads to protests and confusion. Solution: finalise OCS list immediately after start sequence.
- Duplicate boat IDs: Tracking and scoring use different numbers. Solution: synchronise master entry list in all systems before the event.
- Live update without validation: Automatic syncs transmit typos worldwide instantly. Solution: four-eyes principle before the first live push per race.
- Geofence too tight: GPS systems falsely mark boats as OCS. Solution: test and document tolerance zone.
- No offline fallback: Internet outage paralyses entire results communication. Solution: Sailwave HTML on USB stick and local web server as emergency solution.
FAQ: Frequently Asked Questions on Live Scoring and OCS Tracking
Can OCS be set automatically without an umpire?
No. Automatic systems provide indications; the final decision lies with the race committee.
Is Sailwave sufficient for live scoring?
HTML refresh yes; true real-time requires cloud integration or API connection.
What happens with timely return?
No OCS status – the provisional entry is deleted.
How do you connect GPS with scoring?
Uniform boat IDs in all systems; synchronise master entry list before the event.
Who bears transponder costs?
According to notice of race and sailing instructions – clarify and communicate before the event.
Future Trends
Development is moving towards closer integration of tracking, scoring and rule automation. World Sailing is testing optical start line systems; class associations are bundling finish confirmation and protests in apps. For clubs, the barrier is lowering through affordable tablets and standard APIs.
Live Scoring Development
Related Topics
- Scoring Software and Scoring Tools
- Sailwave and Regatta Software
- Live Tracking and Apps
- DNF, DNS, DSQ and OCS
- Individual Recall and General Recall
Last updated: 4 July 2026