Same-event delivery sounds like a speed claim. It’s a sequencing one.
A five-minute match highlight package takes about two hours to build. Start building it when the match ends and you publish two hours after the final whistle, by which time the result has been public all afternoon and the moment has gone. So the package can’t start at the whistle. It gets built while the match is being played, with the editor pulling as the game happens and the last goal dropping into a timeline that’s already cut.
That’s the whole method, and it has as many consequences for the communications team as it does for the crew. Four things have to be settled before kickoff, and none of them are technical.
**One named approver, available during the match.** Not a group chat. If approval has to travel through three people on a Saturday afternoon, the window closes while it’s in transit. This is the most common reason same-event delivery fails and it sits on the client side.
**Graphics built in advance.** Lower thirds, score cards, competition branding, player name templates. Built once before the season, not per match.
**A decision about what gets cut, made early.** A five-minute package plus a one-minute cut is a different edit from four social verticals. Settle it before the season, not in the 70th minute.
**Somewhere ready to receive it.** A destination with upload rights and somebody awake in the right time zone.
One more thing if you’re costing this out. An editor cutting a live match is a position, not a pool of hours. They can’t cover two matches at once, however many hours the month contains. Three simultaneous matches on a Saturday needs three editors that Saturday, and the monthly hours total tells you nothing useful about whether you’re covered.
That’s the arithmetic most quotes get wrong, in both directions.
