The Scoreboard Was Never Supposed to Be There
It started with one annoyed executive in 1992, who kept a graphic on screen against his own boss's direct orders. Now, with the World Cup's knockout rounds just days away, three new templates carry that same instinct into design problems football has spent thirty years solving in public.
In 1994, a handful of TV producers invented the scorebug by accident — and accidentally gave every broadcaster who came after them a problem worth solving. Thirty-two years later, the World Cup is back, and the graphic they invented is now something you can have running on your stream in under five minutes. Here's the story of how it got there, and the three free templates that bring it to your next match.
In August 1992, English football changed in a way nobody at Sky Sports had actually planned for. The network was launching coverage of a brand-new competition — the Premier League, in its first season — and its head, David Hill, had a problem that had nothing to do with strategy. He was tired of tuning into a match already in progress and having no idea what the score was. So he put a small graphic in the corner of the screen: the score, persistent, always there.
His boss hated it. Told him, in not so many words, that it was the stupidest thing he'd ever seen, and ordered it removed. Hill kept it on screen anyway. ITV added its own version the following season; the BBC followed by the end of 1993. Within a year, what had been one producer's personal irritation was becoming the default grammar of English football broadcasting.
The idea crossed the Atlantic in 1994, and it crossed for an entirely different reason. ABC and ESPN had just paid $23 million for World Cup rights and promised five sponsors continuous visibility for 45 uninterrupted minutes at a stretch — soccer has no natural breaks, no timeouts, no commercial windows, and there was no way to deliver that promise without putting something permanent on screen. So they did, borrowing the shape of what Hill had already built for an entirely different reason two years earlier. It worked, and it spread fast: when Hill became the first president of the newly formed Fox Sports later that year, he brought the same instinct to Fox's debut NFL season as the “Fox Box.” Variety reviewed it as an “annoying see-through clock and score graphic,” worried that fans who'd watched from kickoff would rather see a clean screen. One viewer was angrier than that — Hill received a death threat over it, pointedly noting that he was a foreigner telling American football how to look. Even Dick Ebersol at NBC waved it off at first, certain viewers would just change the channel from a blowout rather than sit and watch the gap on the scoreboard widen.
The graphic survived all of it. By the end of the decade it was everywhere — every network, every American sport, plus the football leagues that had started the whole thing. The thing we now call a scorebug — so ordinary today that its absence is what actually gets noticed — exists because one annoyed Sky Sports executive defied a direct order in 1992, and because a handful of people at ABC and ESPN had no choice but to reinvent his solution under deadline, for a World Cup, two years later.
Thirty-two years after that World Cup chapter, the tournament is back on American, Canadian, and Mexican soil — and two weeks into the group stage, with the Round of 32 about to begin, football is having a moment that goes well beyond the tournament itself. More people than ever are organizing their own football coverage right now — not just World Cup watch-alongs, but weekend five-a-side leagues, local club streams, school tournaments, fantasy league shows, and the match someone's cousin decided to put on YouTube this week. None of them have a broadcast engineer or a $23 million rights deal. What they have is the same problem Hill had in 1992, just shrunk down to one person and a laptop: how do you put a clean, accurate, professional-feeling scoreboard on screen without a graphics department behind you?
That's a genuinely interesting design problem, and football has spent thirty years quietly solving it in public — for every match, not just the big ones. We've just shipped three new templates that tackle it directly. Here's what each one solves, and the thinking behind it.
The Scoreboard: Solving for a Game With No Pauses
Soccer's central broadcast-design problem hasn't changed since 1994: the game doesn't stop, but the information on screen sometimes needs to. A scoreboard has to be permanently visible and almost permanently quiet — present for ninety-plus minutes, intrusive for none of them.
The hard part isn't displaying a score. It's displaying a clock. Football clocks pause for injuries, resume after the physio leaves the pitch, run past 90 when the fourth official's board goes up, and occasionally pause altogether at halftime for fifteen minutes that shouldn't count. A clock bound rigidly to a feed can't represent any of that cleanly — it just counts, regardless of what's actually happening on the pitch. The fix is to let a person run it: start it at kickoff, pause it when play stops, resume it when it restarts. The clock becomes an instrument the operator plays, not a countdown that runs itself.
Stoppage time is its own small design decision. It isn't scheduled — nobody knows it's coming until the fourth official raises the board — so it can't animate in on a timer. It has to be a switch: hidden until the moment it's needed, then toggled on the instant it's needed, joining whatever else is already on screen rather than running its own separate entrance.
And because the match period — first half, halftime, second half, extra time, penalties, full time — is one of the only fields on a scoreboard that absolutely cannot be wrong, the safest version of this field isn't a text box at all. It's a fixed list: H1, HT, H2, ET1, ET2, PEN, FT. Nothing else is a valid option, which means nothing else can accidentally go to air.
Team color is where most scoreboards get the contrast problem right or wrong. The instinct is to tint the whole graphic in a team's color — but with two teams whose colors might be nearly identical, or one team in something pale and unreadable against video, a tinted background breaks constantly. The more durable solution keeps color in accents only: a corner, a thin bar, a flourish at the edge — never the plate the score sits on. The chassis stays a predictable near-black no matter who's playing. The accent does the identity work, and the score stays legible regardless of which two kit colors show up that day.
The Lineup Reveal: Football's Pre-Match Ritual
If the scoreboard is about restraint, the lineup graphic is about choreography. Every football broadcast — from a Champions League final to a Sunday league stream — has a moment before kickoff where the eleven names go up, and it's one of the most-watched seconds of any pre-match show, because it's the first real information fans get about how a team is set up to play.
How the names appear matters as much as which names appear. A lineup announced all at once — all eleven names appearing together — reads as a list. A lineup that builds, goalkeeper first, anchoring the shape, then the back line, then midfield, then attack, reads as a reveal, because it mirrors how a commentator would actually call it out loud. The order itself is doing communicative work that a simultaneous reveal can't replicate.
The other quiet decision is what the graphic leaves out. No jersey numbers. No captain's armband icon. No printed position label next to each name. Position gets communicated by where a player's name sits on the pitch — a name positioned wide and high reads as a winger without a single word of explanation. That's not a World Cup broadcast's level of detail, and it's not meant to be. The goal was a graphic simple enough for anyone running a stream to actually use — no roster database, no jersey-number lookups, just eleven names and a formation. Keeping it that plain is also what keeps it legible in the four or five seconds a director typically holds it on screen.
And because even a small school tournament or a local league with a dozen teams means several different squads need this same treatment, the template stays completely neutral — built on a true-to-scale vector pitch rather than a background image, so it holds up sharp regardless of resolution.
Worth being upfront about the tradeoff this makes: it's built around one formation shape, a 4-3-3, with eleven fixed slots. It's not a tactics board — there's no way to reshape it into a back five or a diamond midfield, and no substitution state once the graphic's played. For the one job it's built for — announcing a starting XI before kickoff — that constraint is what keeps it simple enough to trigger and forget. If your team plays a different shape, that's a different template, or a few minutes in the canvas editor reworking this one.
The Penalty Shootout: The Graphic That Almost Never Gets Used
Most matches never need this graphic. League play, group stages, friendlies — draws are allowed, so the match just ends. But the moment a competition moves to straight knockout, this graphic is never far away: any match still level after extra time goes to penalties. The matches where it does get used are disproportionately the ones people remember, clip, and rewatch for years. A shootout graphic gap is one of the worst moments to discover you don't have a shootout graphic.
The design problem here is fundamentally different from a running scoreboard, because a shootout has no clock at all. The moment a match reaches penalties, time stops mattering — what matters is order. Kick one, kick two, kick three, read left to right exactly as the shootout unfolds.
The kick tracker itself is where the clearest design decision lives: five simple dot states per side — not taken, scored, missed. That's it. No animation flourish, no extra color, nothing competing for attention against a moment that's already almost unbearably tense.
A row of green and red dots tells the entire story of a shootout at a single glance, which matters enormously when a broadcast's chat or comments are moving faster than anyone can read.
Crucially, every kick outcome has to be set by a human, not a feed — there's no reliable real-time data source for “this penalty was saved” the instant it happens. The safest interface for that is a closed dropdown per kick rather than a free-text field, for the same reason the match-period field is a dropdown: a mis-typed result during the single highest-tension moment of a broadcast is the worst possible place for a typo to happen.
And when the score does change, it should tick upward quietly rather than flash or pop. The goal itself — the save, the miss, the roar — belongs entirely to the live shot and the replay. The graphic's only job is to register what just happened and then get out of the way.
What All Three Are Actually Teaching
Lay the scoreboard, the lineup, and the shootout tracker next to each other and a pattern shows up that has nothing to do with football specifically.
Identity goes in accents, never in the base layer.
Whatever varies — team colors, in this case — should live in the smallest element that can carry it, so the rest of the design never has to be rebuilt for the next matchup.
Control should sit exactly where judgment is required, and nowhere else.
A kickoff clock needs a human because pauses can't be predicted. A kick outcome needs a human because there's no feed for it. Everything that can run itself — the score tick, the reveal timing, the fade — should.
A closed set of options beats an open text field, anywhere a wrong answer is costly.
The match period, the kick outcomes — both are dropdowns, not text boxes, for the same underlying reason: live production has no time for a typo, and a fixed list makes one structurally impossible.
The narrowness is what makes each template fast to trigger and hard to get wrong, live.
— On design constraints as a featureThat's the actual throughline from one producer's stubbornness in a Sky Sports control room in 1992, through a $23 million broadcast contract in 1994, to a five-a-side league stream tonight: the constraints are different, but the design instincts that solve them are exactly the same — and they'll still be the same for whatever match gets streamed next year, or the year after that.
None of these three graphics is a flexible, build-anything tool. Each one is built tightly around the single moment it's for, and that's deliberate — the lineup reveal only ever shows a 4-3-3, the shootout tracker only ever runs five kicks a side. The narrowness is what makes each one fast to trigger and hard to get wrong live.
A Quick Reference for Anyone Covering a Match
Templates Purpose Built for the Moment
CloudMonet exists because the gap between “I want my football stream to look properly produced” and “I have a broadcast graphics department” shouldn't require the second thing — whether that's a World Cup watch-along this month, a weekend league fixture, or a match nobody's even scheduled yet.
What it offers for football right now is a small set of ready-made templates — a scoreboard, a lineup reveal, a shootout tracker — that you customize with your own team names, colors, and player names rather than build from scratch. They're deliberately specific rather than endlessly configurable: the lineup graphic is a 4-3-3, full stop, and the shootout tracker runs exactly five kicks a side. If that matches the moment you're covering, it'll look properly produced in minutes. If your team plays a back five or you need to show a sub coming on, that's a job for a different template, or for opening this one in the canvas editor and reshaping it yourself.
Whether it's the World Cup or your local five-a-side, now's a good time to get started.