Academy · Integration

The scoreboard is the last to know — on purpose.

The journey of a result from the finish camera to the big public screen, and why the final step is deliberately the slowest.

For most people at a race, the scoreboard is the timing system — nobody in the crowd sees the camera, the judge’s screen, or the approval click. Which makes it the most dangerous display at the venue. A wrong number on the judge’s monitor is a working step. A wrong number on the scoreboard is an event.

Two problems, one small journey

The first is language. Scoreboards are a zoo of manufacturers, generations, and protocols. The timing system prepares each result in exactly the form the connected screen understands; in Lion Timing, most scoreboards can be driven directly over Ethernet from the camera, with an output box for the rest. The second is publication timing. The tempting answer is “instantly,” and it’s wrong — the moment a close finish gets its first provisional reading is exactly the moment it must not appear four metres tall in front of the grandstand. If review changes it, the crowd experiences a timing failure.

The pause nobody notices

So the scoreboard sits deliberately behind the : the result appears when it’s official, not one second before. Done properly, this carefulness is invisible — spectators never notice a result took a few extra seconds; they only notice when a result appears and then changes. The screen the most people trust should be the screen the fewest mistakes can reach.

The explanation worth remembering

A scoreboard is the public face of the timing system: it speaks whatever language the screen requires, and it’s deliberately the last device to learn the result — because it’s the first place everyone else will.

Next in the Academy: 10.42 appears on the livestream — who typed it? →