Rowing club safety software: incident logging, RAG flags & overdue-outing alerts

Safety shouldn't be an afterthought

Rowing is a safe sport when clubs treat safety as part of how they run outings, not as paperwork filed away after the fact. British Rowing's RowSafe guidance puts responsibility for this squarely with clubs and their Rowing Safety Advisers — deciding what conditions are safe to row in, making sure members know what to do if something goes wrong, and reporting incidents so the wider sport can learn from them.

BoatLog is built to support that responsibility with three things clubs consistently struggle to keep on top of: knowing whether conditions or a specific outing carry extra risk, knowing when a boat hasn't come back when it should have, and having an accurate record of what happened when an incident does occur.

RAG flags: risk at a glance

RAG — Red, Amber, Green — is a traffic-light convention used widely across safety-conscious sports and workplaces to communicate risk quickly, without everyone having to read a full risk assessment under pressure. In BoatLog, outings can be flagged Green for normal conditions, Amber where extra caution is needed (stream, wind, light, a novice crew), or Red where the safety adviser has called it — stand down. The flag travels with the outing record, so it's visible to whoever's signing boats out at the kiosk, not just in a document nobody reads before setting off.

Overdue-outing alerts

Every outing on BoatLog starts with a boat sign-out, and every sign-out carries an expected return time. If a boat hasn't been signed back in by then, that outing can be flagged as overdue — so someone on shore knows to start checking, rather than only noticing when the boathouse is being locked up for the night. It's a small thing that closes a real gap: the time between "we don't know" and "we're worried."

Incident logging that feeds British Rowing's process

When something does happen — a capsize, a collision, a near miss, an injury — the details matter, and they matter most in the first hour, not the next morning. BoatLog lets a club capture what happened against the outing it relates to: who was involved, which boat, roughly when and where, and what happened next. That record then supports your club's own report through British Rowing's incident reporting system, which asks for online reports within 24 hours of the incident. See our dedicated incident reporting page for exactly how that process works and how BoatLog fits into it.

Safety starts at the boathouse door

None of this works without an accurate sign-out in the first place — see how BoatLog's offline boat sign-out & boathouse kiosk captures every outing, even where signal at the water's edge is poor. And if an outing ends with a damaged boat rather than an incident, that's covered by damage reporting.