In the first article I described why we built EIKON-iQ as an integration layer, and in the second I talked about where AI fits in our workflows and where it does not. This article is about what happens when you put those two things together.
Let me describe what a workflow looks like when it runs through the evolved platform. Content arrives via API from a client’s orchestration system. The platform identifies the language, assesses the content type and complexity, and routes it through the right combination of AI-assisted analysis and human expertise based on that client’s specific requirements. Status flows back upstream in real time, deliverables return automatically, and the client sees progress rather than process.
From the outside it just works; from the inside, there is a lot going on.
From integration to orchestration
When we first built EIKON-iQ, it was essentially a connector. It linked client systems to our internal operations so that work could flow in and status could flow back without the emails and spreadsheets I described in Article 1. That was valuable in itself, and for some clients it remains exactly what they need.
But once we had that integration in place, we started to see what was possible with a platform that has visibility across all of our internal systems and workflows. The original iQ connected point A to point B; the evolved platform sits in between and makes intelligent decisions about how work flows through the entire pipeline.
Consider the stages involved in a typical content servicing workflow: ingest, language detection, transcription, translation, subtitle creation, QC, mastering, compliance checking, packaging, and delivery. Each of those stages is configurable per client, per content type, per territory. A Japanese localisation for a tentpole series has different requirements to a French subtitle pass on a catalogue title, and the platform needs to understand that and route accordingly.
The original iQ connected point A to point B; the evolved platform sits in between and makes intelligent decisions about how work flows through the entire pipeline.
This is where the agentic architecture I touched on in the last article starts to scale. We have been developing a video comparison workflow that illustrates the pattern well. A coordinating agent plans the analysis and delegates to specialised agents, each handling a distinct part of the process: ingest and alignment, scene boundary detection, scene comparison and differencing, reporting with NLE-compatible output. A further agent integrates the results for operator review. It is modular, each agent focused on what it does best, and the pattern is repeatable across QC, localisation, and compliance.
The video indexing and localisation workflow we have been building illustrates a different orchestration pattern. Here, a single piece of content triggers multiple AI processes running in parallel: audio isolation and speech-to-text for dialogue extraction, speaker detection for character identification, computer vision for cut detection, optical character recognition for on-screen text, and scene analysis for content descriptions. Each of those parallel streams produces output that an operator then verifies and confirms using our own purpose-built tools — Skribe for dialogue and character data, Krosscut for visual analysis and on-screen text — before the confirmed results converge into the Video Indexer database. It is a fan-out pattern rather than a sequential one; the orchestration layer manages the entire pipeline, triggering the right AI processes, routing outputs to the right verification tools, and assembling the confirmed data into a structured, searchable index. The advantage is not just speed, although the parallel processing is significantly faster than doing any of this manually; it is consistency, because every asset goes through the same rigorous extraction and verification pipeline regardless of scale.
These two workflows represent different orchestration patterns, but the principle underneath is the same: coordinated, specialised processes managed as a whole. That matters, because it means we can evolve individual components without rebuilding everything around them, and the pace at which AI capabilities are improving makes that flexibility essential.
The architecture underneath
I want to say a few things about the technical foundations, without getting into proprietary detail.
The platform migration we have been working through is not a lift-and-shift. AI workloads have fundamentally different compute profiles to traditional content processing; they need elastic scaling, they are GPU-intensive in bursts, and the economics only work if you can scale down as efficiently as you scale up. We have re-architected around that reality, with clear unit economics per title, per language, per service type. API-first design throughout, so that every capability is available programmatically, not just through a user interface.
The governance architecture sits at the core of this, not alongside it. Segregated client instances, on-premise model deployment, no client data through public AI endpoints. I covered our position on this in the last article, but it is worth repeating here because the architecture enforces it. These are not policies that rely on people following rules; they are engineering constraints built into the platform itself.
Quality management at scale
This is the problem I find most interesting, and in some ways the hardest to solve, because the challenge is not getting AI to produce output; it is knowing when that output is good enough and when it is not.
Every AI-assisted process in our workflows has confidence scoring built in. When the system is confident in an output, it flags it for efficient human review. When confidence drops below a threshold, it routes to more detailed human assessment. The thresholds are not static; they are calibrated per content type, per language pair, and they adjust as we learn more about where the models perform well and where they struggle.
The challenge is not getting AI to produce output; it is knowing when that output is good enough and when it is not.
Quality gates sit at every stage, and nothing moves to the next step without passing the gate for the current one. Human corrections feed back into measurable improvements; we can track, over time, how accuracy shifts for specific content types and language combinations. That feedback loop is what turns a collection of AI tools into a system that actually gets better at serving our clients’ specific needs.
We are also building operational intelligence capabilities on top of this. Predictive scheduling, where the platform learns from patterns to forecast turnaround times and flag potential bottlenecks before they become problems. Anomaly detection, flagging unusual QC failure rates, turnaround deviations, or spec mismatches that might indicate something upstream has changed. Automated packaging and delivery validation, so that compliance checks happen before anything ships rather than after.
None of this replaces human judgment; it gives our operations teams better visibility and earlier warning, so they can focus their attention where it is most needed.
What this means for clients
I am conscious that the last few sections have been technical, so let me bring it back to what this actually means in practice.
For a client integrating with EIKON-iQ, the experience is a single integration point: one API connection where work flows in, status flows back, and deliverables return. Behind that single connection, the platform is managing the full complexity of routing, processing, quality management, and delivery across whatever combination of services that client requires.
Turnaround becomes more predictable, because the platform is scheduling and managing capacity rather than relying on manual coordination. Visibility is real-time, because every stage reports status as it completes. The client can configure their requirements per content type; their most important content gets the most human-intensive workflow, while other content can take advantage of more AI-assisted processing where appropriate.
The 1.3 million asset registration project I described in Article 1 is built on exactly this kind of workflow. Each asset runs through the parallel extraction pipeline — dialogue, characters, scene boundaries, on-screen text, content descriptions — with operators confirming outputs at every stage using our own tools, and the confirmed data feeding into a structured index. The project coordinates across three separate entities, with assets that never leave the client’s own infrastructure, and the platform handles automated work order generation, automated billing, and intelligent orchestration across the entire pipeline. At that scale, the acceleration has come entirely from the orchestration, not from adding headcount.
1.3M assets indexed through the parallel extraction pipeline: AI-assisted dialogue, character, scene, and text extraction with human verification at every stage, coordinated across three entities without assets ever leaving the client’s infrastructure.
Technology serving the craft
I want to close with something I feel strongly about. EIKON is a service business, and we always have been. The technology we are building exists to make skilled people more effective and to ensure quality at scale; it does not exist to replace the craft that our clients value.
The orchestration layer is not about removing people from the process; it is about giving them better tools, better information, and better support so they can focus on the work that requires their expertise. The platform handles the coordination, the routing, the scheduling, the compliance checking, and the status reporting, while the people handle the judgment, the creativity, and the quality.
That distinction matters to us, and I think it matters to our clients.
In the final article, our COO, Richard Fish, will talk about how these technical developments influence the relationship between content owners and the companies that service their content. The platform is built, the workflows are proven; the question now is what comes next.
AI-powered servicing, human-perfected quality.
More In This Series
Article 1
The Integration Problem Nobody Talks About
The media supply chain has modernised dramatically, but there is a gap where automation meets human judgment. EIKON-iQ was built to close it.
Article 2
Where AI Belongs in Content Servicing: And Where It Doesn’t
The industry is flooded with AI hype. But which tasks genuinely benefit from automation, at which quality tier, and with what safeguards?
How do you distinguish between what AI handles well and where human judgment remains non-negotiable?
Article 4
The Future of Content Servicing Is a Partnership
What does trust actually look like when AI is touching studio content? How does the relationship between content owners and service providers fundamentally change, and what does the governance framework need to deliver?
