A broadcast run sheet for live combat sports commentary on ANT1+ — events, fighters, prepared Greek copy and result marking, on the single screen the commentators read from while the show is on air.
Client
Combat Edge
Type
Internal Platform
Sector
Live Broadcast
Status
Live
Combat Edge runs combat sports events broadcast on ANT1+, and its commentary used to operate out of a folder per event — a standalone page, a small server script and a results file, copied and hand-edited for every show. It worked, but it did not survive a card changing at short notice, and nothing was shared between the two commentators.
Speakage replaced all of it with one private application. Promotions, events, fighters and fees live in a single database, and the run sheet for a given event is one page: if a feature does not end up on that page, it does not exist. Both commentators work from the same data, updating live, while the broadcast is running.




One application, designed around the page the commentators actually read from.
The single screen commentary is delivered from — fight order, fighter detail, prepared notes and result marking, laid out to be read at a glance under time pressure.
Structured records for promotions, events and cards, so a show is assembled once and reused rather than rebuilt from scratch each time.
Names, nicknames, records and background gathered per fighter, including automated import from public event listings.
Draft commentary, fighter notes and result announcements generated in Greek and then refined in place, so the commentator edits rather than writes from a blank page.
Results marked as the card progresses and pushed to every connected screen immediately, so the second commentator is never reading stale data.
Per-event commentator fees recorded against the show they belong to, keeping the commercial side in the same place as the work.
The application is judged on one thing: whether it holds up while a card is running. That constraint drove the architecture — realtime sync between operators, editing that tolerates a dropped connection, and nothing in the stack that could not be self-hosted.
Platform Components
Operating Principles
Platform status as of August 2026.
1
Run sheet per event — the whole show on one page
2
Commentators working from identical live data
Real-time
Result marking pushed to every screen
Greek
Drafting in the language of the broadcast
We build for the moment the thing is actually used, not for the demo. Tell us where your operation is losing time.