Switching your NRCS? Join our free webinar · 18 June · 5PM CEST

Sign up

What Unified Production Actually Means and Why It Matters

At NAB 2026, Cuez CEO Jens De Maere joined EVS's Mike Shore on stage to talk about the future of live news production and what it means in practice. Here are some of the insights.

The problem with "story-centric"

Everyone on the show floor uses the phrase. Not everyone means the same thing. For Cuez and EVS, story-centricity only works if rundown, media, automation, and playout behave as an entire connected system.

The goal is simple: your experience should be consistent no matter your role or entry point. The journalist, the editor, or the gallery director should all see the same thing at any point in time.

MOS is legacy; API is the future

Here at the Cuez office, we used to have a poster that read: "We don't do MOS."

But that poster had to go. MOS is still the baseline for newsroom integration, and pretending otherwise is denying reality. However, things are changing.

MOS is over 25 years old. API-level integrations allow the free exchange of metadata, enable real-time synchronisation, and are what make two systems talk to each other easily and feel like one. That's exactly what the Cuez and EVS integration is built on. API is the future ahead.

One file in every system

One of the most practical points of the session is that in a unified system, you're not copying or uploading media. Instead, you're passing references.

Imagine a journalist films something in the field. That clip doesn't get copied, sent, or uploaded anywhere. It just sits where it was recorded. But a link to it (a reference) instantly appears in everyone's tools: the rundown, the media browser, everywhere. Anyone can grab it and use it as if it were right in front of them. And if the internet goes down? The file is still there, nothing is lost, and the system just keeps pointing to it.

Remote production, live synchronization

There is no denying it: remote production is no longer just an option for modern broadcasters. For large events like the Olympics, working in the same rundown from multiple locations, accessing the same media, and operating as one team is what makes production manageable. Cuez is built for exactly that: rundowns and scripts live in the cloud by default, while high-resolution media stays wherever it makes the most economic sense. When something changes in the rundown, it changes for everyone immediately. That means, the anchor sees it on the prompter, the news director in the gallery, a remote editor on their laptop or a phone. It works like a live Google Doc for the entire production team.

Cost transparency

The most unpleasant part of the cloud is getting an unexpected bill that you were not prepared for. This is why cost transparency is non-negotiable.

Jens and Mike agree: the total cost of ownership has to be visible, predictable, and controlled by the broadcaster (not the vendor).

Cuez doesn't lock you into its own AI tooling. Bring your own. Train it on your metadata, your media, your workflows. Control your own costs. The same logic applies to infrastructure: on-prem, cloud, or hybrid — that decision should be driven by economics, not by what the technology forces.

Lessons to be learned

When broadcasters look for unified workflows, just connecting the tools will not cut it. The goal is to make those connected tools actually work together. Especially in news productions, time is of the essence; the sync between tools should be smooth, stable, and frictionless.

Content Marketeer