Built by people who've been in the middle
RefWhistle wasn't built in a boardroom. It came out of years on the touchline: logging matches in wet notebooks, rewriting them into reports on Sunday night, and retyping them into portals that never talked to each other.
As referee coaches and officials, we were spending more time fighting software than developing people. The systems we had were built to collect data for administrators, not to get useful feedback to the official while the match was still fresh.
So we built one record for the whole job: appointments, live logging on a phone, reports drafted at full time, synced video and streaming, and a development history that follows every official through the season. It started in football, and the same record now adapts to other codes.
- Wed 15 OctAppointedReferee, Northside FC v RangersAccepted
- Sat 19:30Logged live18 entries from the touchlineLive
- Full timeReport draftedRatings suggested from the logDraft
- Sat 21:40Clips on the footage7 moments marked on the match clockSynced
- Mon 20 OctSeason trendPositioning up across 6 matchesImproving
What we build by
- Enter it once
- A log entry from the touchline becomes the report, the marker on the footage and a point in the official's season. Nobody types the same thing twice.
- Eyes on the match
- Anything a coach touches during play is built for one thumb and a glance, in the rain, with patchy signal.
- Evidence over recollection
- Decisions and disputes are settled with synced footage and timestamped logs, not memory or paperwork.
- Feedback in the same week
- The gap between a decision and the coaching conversation about it should be hours, not weeks.
Bring your association onto one record
Book a walkthrough