Most school sports broadcasts don’t fail for lack of ambition. They fail because the whole crew is two volunteers and the tools assume a truck. So here’s a home game on MediaCore2, hour by hour, run by exactly two people: one parent with a phone, one with a laptop.
Monday: the season is already there
The athletic director did the hard part once, before the season started. They entered the organisation’s identifier, pressed one button, and every fixture on the schedule became a real, ready-to-broadcast event — title, home and away teams, kick-off, end time and venue.
Two games have moved since. Re-running the import updated the changed times and left alone every edit someone had made by hand. The programme guide caught up by itself, because every active event appears there automatically — it can’t disagree with the events list.
Nobody designed a poster, either. Each event’s artwork was generated from the two teams’ names, colours and crests, in portrait and banner shapes.
Thursday: sell it without a second tool
The game is set to hybrid. Families holding the season pass get in free; everyone else buys a pay-per-event ticket with a 24-hour access window. The pass has fixed dates, so it ends for every buyer on the same day — the end of the season, not a month after whenever someone happened to pay.
The announcer reads the event’s share code over the stadium speakers during the junior game. It’s ten characters from an alphabet with no 0, O, 1, I or l, so it survives a crackling PA.
Everyone who saved the event gets a reminder 15 minutes before kick-off and another the moment it goes live, in the app and by phone push.
17:30 — a camera nobody has to run
The camera is fixed to the press-box rail. It’s set as the event’s automated camera, so it starts recording exactly when the scheduled window opens and stops when it closes. Nobody stands behind it. Nobody has to remember to press record.
18:15 — two logins, two jobs
Volunteer one signs in to the scoring app on their phone with their own credentials. That account can touch the score and nothing else — not the stream, not the pricing, not billing.
Volunteer two opens the Studio on a laptop in the stand, under a role built for the night: run the broadcast, switch destinations, moderate comments. The settings that could take the stream off the air sit behind an extra password they don’t hold. They can run the show all night; nobody can quietly repoint a camera.
18:55 — one signal, several places
From the event’s control room, volunteer two switches on the simulcast: YouTube for the grandparents, the NFHS Network for the wider audience, Facebook for the booster club’s page. Each destination has its own switch, the stream keys stay masked on screen, and up to 5 can run on one event by default.
The same screen shows what matters when you’re the only technical person in the building: live status, how long you’ve been on air, viewers, bitrate, resolution and a performance chart, with the ingest address and every destination alongside.
19:00 — kick-off
At the scheduled start, every waiting countdown gives way to the player on its own. Nobody refreshes.
Volunteer one taps the score up after the opening drive, starts and stops the clock, and sets the period with whatever label the sport uses — Q1, Half 2, Set 4. Every viewer on the web, in the apps and on a TV sees the change within seconds — the watch page checks every 10 seconds, and the clock keeps ticking smoothly in between. The matchup card in the programme guide carries the same live score, and its live-now banner puts a Watch button one tap away.
At halftime an assistant coach opens the scoring app on a second phone to add a field goal they think was missed. It wasn’t — volunteer one already has it. The second phone is stopped and shown the current score instead of overwriting it. Two scorers can’t clobber each other.
21:38 — lock the final
Final whistle. Volunteer one marks the score final, and it freezes.
On Monday morning the visiting coach disputes the fourth-quarter score. There’s nothing to argue about. Every accepted change was recorded — who made it, when, from which device, and the score before and after — so the whole game can be reconstructed tap by tap.
And then nobody does anything
The window closes and the camera stops recording. The event page retires, the homepage banner comes down, and the simulcast destinations are torn down on their own. The replay publishes itself into the on-demand catalogue with the event’s artwork and access — here’s how that works.
Tag that replay with both teams and it appears on each team’s page, under On-Demand, next to the articles and reels already tagged with them.
What the two volunteers never did
- Type a fixture list
- Design a poster
- Copy a stream key out of an email
- Press record — or stop
- Sign in to three platforms to start a simulcast
- Download a recording and upload it again
That’s the job sports on MediaCore2 was built to do: make a two-person crew look like a broadcast. Start with running the scoreboard from a phone.