A boundary appears on a scoring app almost as fast as it appears on television. The path between the two is a chain of systems with measurable delays at every link.
The chain starts with a keystroke
An official scorer enters the outcome of the delivery into scoring software at the ground. That entry is the origin of every downstream number.
A second operator often enters richer detail — line, length, shot, fielder — into a separate system. Two feeds leave the venue describing the same ball at different resolutions.
Both are transmitted over dedicated connectivity rather than public networks, because the venue's general internet is saturated by spectators and by the broadcast itself.
Distribution splits by customer
A central distributor receives the feed and fans it out to broadcasters, apps, statistical services and commercial clients, each with a contracted latency and level of detail.
Not all customers receive the same thing. Some contracts specify enriched data, others only the basic scoring events, and priority tiers determine who gets it first.
This tiering is why an official app and a third-party site can be seconds apart on the same event without either being broken.
Why television is behind the data
The video path adds encoding, satellite or fiber transmission, and decoding at the viewer's end. Streaming adds buffering on top of that.
The consequence is that a scoring feed can be ahead of the pictures. Viewers watching a stream while following a live score routinely see the number before the shot.
Broadcasters manage this by delaying graphics rather than by speeding up video, so on-screen scores stay synchronized with the pictures the viewer is actually watching.
Corrections travel the same pipe
When a scorer amends an entry — a leg bye reclassified, an over-count corrected — the amendment is distributed as a revision rather than as a new event.
Consuming systems must handle revisions, which is harder than handling appends. A display that only adds events will show a total that no longer matches the source.
Most visible scoring glitches are revision-handling failures rather than transmission failures. The data arrived; something downstream did not know what to do with it.
What the architecture implies
Because the feed is a commercial product, its accuracy and speed are contractual obligations with penalties attached. That is why the scoring operation is staffed and provisioned as heavily as it is.
It also means the official record and the commercial feed have diverged in purpose. One certifies the match; the other serves customers in real time.
They agree almost always. When they do not, the certified version wins, and the commercial feed issues a revision that most viewers never notice.

