Racing is its own broadcast category, and it always has been. Every race is a self-contained production — a field of runners, a few minutes of action, a result that has to be on screen the instant it’s official. Across a typical race day a venue might run twelve races, each with its own runners list, late scratchings, jockey or driver changes, pre-race odds, in-race positions, photo finishes, dividends, and post-race interviews. The graphics have to keep up with all of it, and they have to be right the first time.

Lightning Visuals delivers broadcast and venue graphics across the racing codes — thoroughbred, harness, and greyhound — for race clubs, broadcasters, and racing bodies across Australia, New Zealand, and internationally. Our cloud-based platform integrates with the major timing, scoring, and information systems racing relies on, and renders the output simultaneously to broadcast, streaming, trackside big screens, hospitality tickers, and internal venue displays. Same data pipeline, every screen.

Why racing is different from every other sport

Three things make racing a distinct broadcast challenge.

The data is structured but the data is also constantly changing.
A runners list looks like a stable data object up until twenty minutes before the race, when a scratching changes it, or a jockey allocation moves, or a late weight adjustment comes through. The graphics system has to absorb these changes silently across every output simultaneously — broadcast, big screen, ticker, hospitality, internal — without an operator manually updating each one. Our platform was built around this.

The commercial integration is the deepest in sport.
Naming-rights sponsors on races, sponsor logos on the runners list, presenting partners on the photo finish, branded post-race dividends panels, hospitality-area sponsor tickers — racing has more co-branded inventory per minute of broadcast than almost any other category. The graphics platform has to treat sponsor inventory as a first-class object, not an afterthought.

Wagering data needs to live alongside broadcast data.
Live odds, fluctuating prices, dividends — these flow through the same broadcast environment as the race telemetry itself, and viewers (and bettors) expect to see them updated in real time. Our system supports live wagering data integration alongside race data, with the visual treatment, latency, and accuracy that a regulated environment requires. (For race clubs and broadcasters interested in the deeper commercial play around sponsorship and wagering integration, our Racecourse Graphics article covers the full thinking.)

Where the graphics show up across a race day

On the broadcast feed. Pre-race runners and odds, in-race position graphics, GPS-driven telemetry overlays, photo finish reveals, post-race dividends, jockey and trainer interviews with lower thirds.

On the trackside big screen. The same data, rendered for the venue audience — runners panels, live odds, hype animations between races, replays, sponsor segments, post-race results.

On hospitality and internal screens. Rolling tickers with live odds and upcoming races. Sponsor messaging. Venue promotions. Dividends posted to the bar within seconds of the official result.

On the judge’s semaphore panel. Result outputs at the venue level, automated to the official timing call.

All of these run from the same data feed, on the same cloud-based platform, with no separate production effort per output.

What this means commercially for racing venues

A race club running a typical meeting owns more digital screen inventory than almost any other sports venue category — the main video board, the trackside ribbon LED, the semaphore panels, the hospitality screens, the bar tickers, the entry signage. Most clubs use a fraction of what they own.

The same Lightning Visuals platform that powers the broadcast graphics can power every screen in the venue, automated to the race schedule, with sponsor and promotional content built into the rotation. The economics work because you’re not running parallel systems — you’re running one system across every screen. The revenue case is straightforward, and it compounds across a season.

Operating a race club, broadcasting a racing code, or producing a meeting where the graphics need to work across every screen at once? Talk to our team.