Analysis: Remote production won, now the industry has to live with what it moved

The question of whether remote production works has been settled. Ask it in an industry roundtable today, and you get something close to a shrug.

The more useful question, and the one that actually surfaces in our four-part Industry Insights series on sports production, is where the complexity that remote production removes from a venue actually goes, and who is left holding it.

That question runs under nearly every topic in the series, from REMI deployment to IP infrastructure to the flood of alternate feeds broadcasters now generate from a single live event.

The pattern is consistent: technology has made it possible to relocate people, signals and production functions almost anywhere. It has not made the underlying work simpler. It has just moved it, often onto systems and teams that are not yet built to absorb it.

The binary is dead, the allocation problem is not

Every contributor asked about on-site versus remote production gave some version of the same answer: it depends on the event, and increasingly it depends on the role, not the production as a whole.

“Every sporting event benefits from remote production because it removes the physical limitations of the venue. Cloud-based production adds instant scalability, so broadcasters have the same toolset whether they’re producing the Super Bowl or a regional qualifier. The real decision becomes which specific roles need boots on the ground for a given production, not whether remote is viable,” said Steph Lone, global leader, solutions architecture, media and entertainment, Amazon Web Services.

“I think productions are finally getting more honest with themselves about who actually needs to be at the venue, rather than just doing it the way it’s always been done. What I’d push back on is the idea that this means stripping people out of the event altogether. It doesn’t. It means being much more deliberate about it, keeping the people who need to react in the moment close to the action, and letting everything else run from somewhere it can be done more efficiently,” said Alistair Horne, managing director, Hornets Tech.

Horne drew that line deliberately.

Advertisement

It separates two narratives that get flattened together in industry conversation. One is technological: IP, cloud and software-defined systems have removed the physical constraints that used to force a production trailer into a parking lot. The other is economic: rights fees have climbed to a point where broadcasters are hunting for savings in places they used to consider untouchable.

“The bar is changing quickly. Remote production used to be reserved mostly for tier-two and tier-three events, but with sports rights fees as high as they are, broadcasters are looking for savings everywhere, including tier-one productions. Keeping more production resources centralized and reusing infrastructure across events are practical ways to reduce overhead without compromising the final broadcast,” said Dave MacKinnon, vice president of product management, Clear-Com.

Both things are true at once, and the roundtable mostly treats them as one story. They are not. The technology answers whether a workflow is possible. The economics answer why a broadcaster does it anyway, even when the technology argument is marginal. Conflating them is how an industry ends up calling a cost decision an innovation.

Complexity does not disappear, it relocates

If there is a single passage that should be pinned above every engineering desk discussing this transition, it is this one.

“IP has genuinely opened things up, there’s a lot more freedom to move signals, people and resources around intelligently across remote and centralized workflows than there used to be. What I don’t buy is the idea that IP makes things simpler. It doesn’t remove the complexity, it just relocates it, and if you’re not careful that complexity ends up sitting somewhere nobody’s properly engineering, monitoring or taking responsibility for,” Horne said.

That is not a minority view dressed up as a hot take. It is the quiet consensus underneath a series of contributions that, on the surface, read as celebrations of flexibility.

“IP has given sports production much more freedom in how signals are routed and resources are shared, but it has also made timing less predictable. In SDI, teams generally understood the timing behaviour of the path; in ST 2110 environments, multiple buffers and network routes can introduce delays that are difficult to spot by eye. The next stage of IP maturity is not simply moving signals onto a network, but being able to verify what is happening inside that environment,” said Nicola Milburn, technical sales manager, Hitomi Broadcast.

Milburn’s conclusion was not that IP is worse. It is that the industry has not caught up on verification.

This is where the roundtable’s repeated emphasis on reliability over latency starts to make sense as more than a talking point.

“And I’d say people spend too much time worrying about latency when reliability is the thing that actually matters. A slightly delayed signal is still usable. A missing one is worth nothing,” Horne said.

“Broadcasters have learned that reliable remote production depends on consistency more than chasing the lowest possible latency. Stable timing and accurate synchronization give production teams the confidence to work across different locations without affecting the viewer experience,” said Andy Rayner, chief technology officer, Appear.

When two competitors converge on the same priority without prompting each other, it is worth taking seriously as an actual industry lesson rather than a coincidence of phrasing.

Advertisement

REMI rewards discipline and punishes shortcuts

The clearest articulation of what relocated complexity costs a broadcaster who is not prepared for it came, again, from Horne.

“Mostly that REMI punishes sloppiness. If the timing’s off, the links are fragile, the comms is messy or nobody’s thought about what happens when something fails, remote production will find that weakness and expose it live, in front of everyone. When people treat it properly, as a live production that happens to be split across two locations rather than a video call with nicer cameras, it works brilliantly. The problem is when it gets treated as the cheap option rather than the engineered one,” Horne said.

That last line is a useful corrective to any framing of remote production as simply cheaper.

“The biggest lesson is that the public internet is a fully viable option for primary sports contribution if you manage the traffic right. Relying on a single network provider is simply a single point of failure during a live broadcast. Real operational security comes from using transport protocols with network bonding to tie multiple cellular and fixed networks together, ensuring that the video stream remains stable even if an individual connection fails,” said Peder Boberg, product owner, Intinor.

“The biggest lesson learned from deploying REMI workflows is that success depends less on saving travel costs and more on reliable signal transport, low latency, and maintaining operational confidence across distributed workflows. REMI workflows must work across various locations, so they are only as good as the connectivity behind them,” said Suzana Brady, vice president, worldwide sales and marketing, Cobalt Digital.

Put these together and the takeaway is unglamorous but important: the broadcasters getting value out of REMI are the ones who spent the savings from travel and venue costs back into redundancy, monitoring and testing. The ones treating it purely as a cost cut are the ones building the failures Horne describes.

One event, many outputs, and the same warning

Part three of the series shifts to alternate feeds, personalization and AI, and the throughline holds. Broadcasters are not just distributing production geographically, they are multiplying what a single event produces, generating broadcast, streaming, social and direct-to-consumer versions from one source.

“Many organizations are responding by building a strong, consistent primary production and then creating additional versions from that source. The challenge is how to support a near-infinite amount of event feeds while keeping operations manageable. Template-based automation and live event versioning technologies are playing a critical role here, helping pressured teams spin up multiple versions of the same event without significant headcount increases,” said Colin Moran, vice president, production products, LTN.

The AI conversation in the same section is notably uniform.

“The most effective approach keeps humans on the decisions and lets machines handle the volume. AI is proving its worth in tasks like automated logging, highlight detection and camera tracking, where it surfaces options quickly for a producer to approve. Editorial control stays intact when automation is framed as an accelerator for skilled operators, not a replacement for their judgment,” said Bea Alonso, marketing lead, Projective.

Advertisement

Contributor after contributor echoed that framing almost word for word. Nobody in the roundtable argued the opposite, which either means the industry has genuinely converged on this boundary or means nobody wanted to be the person on record saying otherwise. Given how carefully hedged the AI answers are compared with the bluntness elsewhere in the series, particularly from Horne, it reads more like the latter.

The part nobody wants to lead with

The final section’s “what are we not discussing” question produced the most candid material in the entire series, and it undercuts some of the optimism found earlier.

“I do not think we are talking enough about the skills gap that comes with the move to IP and software-based production. There are excellent broadcast specialists who have spent their careers working with SDI, and excellent IT specialists who understand networks, but those two areas of knowledge do not automatically overlap. As sports production becomes more software and IP-based, bringing those skills together is going to be just as important as the technology itself,” said Milburn.

“Traditional SDI engineers are retiring rapidly, and the industry isn’t replacing them fast enough with engineers who can support ST 2110 and IP workflows. On top of that, the newer talent entering the space has a very different background — they’re IT and software natives, so they don’t have that deep, legacy broadcast intuition yet. It’s going to create a pretty bumpy transition period, but it also forces the industry to finally adopt modern, software-defined architectures,” said Doug Price, global head, commercial and operations, broadcast solutions, Hawk-Eye Innovations.

That is the honest end to a series that spends three parts describing what remote and IP-based production makes possible. The fourth part quietly admits that the industry has not finished building the workforce and operational discipline needed to run what it has already deployed. The technology argument is over. The harder argument, about who monitors the relocated complexity and whether they are trained to do it, is just getting started.