The drift is there before the cost report shows it.
telemetry detects the drift before it forces creative compression.
telemetry reads the documents your production already generates, tracks plan against actual every day, and surfaces the signals early enough to act on.
The problem standard tools can't see.
Film and television productions are complex physical operations coordinated through documents. Call sheets, daily production reports, cost reports, schedules, script supervisor notes. Experienced producers read those documents every day to form a judgment about whether the production is tracking.
By the time anything unusual shows up in the cost report, the compounding drift has already been absorbed. Good producers don't let budgets go over. What they do instead is quietly reduce the creative product. A three-day sequence compresses to two. A location option gets dropped. A design ambition gets scaled back. The shooting schedule tightens. The budget holds. The schedule holds. The production becomes a little less than what was financed.
This is the loss mechanism standard tools can't measure. They measure what was spent. They don't measure what was built, against what was financed. That gap is where filmIQ operates.
Not all compression is bad. Some is planned at greenlight, when a production is approved with a script larger than the schedule and budget can deliver and creative reduction is the agreed mechanism for bringing them into alignment. The compression telemetry detects is the unplanned kind, the absorption that compounds during production when operational drift exceeds what the team can recover through normal management.
What telemetry does.
telemetry reads the documents your production already generates. Call sheets, DPRs, cost reports, hot costs, schedules, scripts, time cards, contracts, cast availability windows. It compares what was planned against what is actually happening across three layers (operations, creative vision, and contractual constraints) and flags compounding variance before it shows up in any cost report. Most production tools see one layer. telemetry monitors all three at once.
It delivers the findings to producers and executives through a daily email, not a dashboard they have to remember to open.
01 Ingest
You add telemetry's ingestion address to your distribution list. Every document your team already sends arrives in our system the same way it arrives in your inbox. No new software. No upload step.
02 Compare
telemetry structures every document and compares what was planned against what is actually happening. Scene deficit. Page drift. Velocity changes. Overtime cadence. The signals are calculated daily, not weekly.
03 Deliver
The Production Pulse lands in your inbox every morning. Producers, executives, department heads. Two-minute read. The full picture lives in the dashboard when you want depth.
What we found in early pilot work.
Across the platform's first live deployment, the central finding was a measurable gap between when operational drift first registered in the schedule layer and when it became visible in financial reporting. Operational signal emerged within the first week of production. Financial reporting stayed clean across the run.
The middle number is the finding. The financial metrics looked clean because the production absorbed the drift through reduced creative scope. That absorption is the loss mechanism standard tools cannot see. The roughly 12-day lead time between the operational signal and the financial signal is the interval during which creative compression is still reversible. The figure itself is pending engineering verification, and broader corroboration across productions is part of what subsequent deployments contribute to.
Why this team.
filmIQ's founders have run production and production technology at scale, and built the data platforms that make intelligence systems work.
Fifteen-plus years as SVP of Production and Production Technology at NBCUniversal, overseeing fifteen-plus concurrent scripted series. Daytime Emmy winner for New Approaches.
Enterprise cloud leader with twenty-plus years across entertainment, technology, and media. Led enterprise engagements at Warner Bros., SONY, Discovery, and Apple. Started at HBO.
Two decades running technology-enabled transformation programs for global enterprises, most recently at Capgemini.
Data platforms, distributed systems, and applied ML at Amazon, Microsoft, and SAP.
The research panel.
telemetry runs on a pattern library defined and validated by working producers. Our panel represents more than a hundred combined production credits. They are the research instrument for pattern library construction, not an advisory board in the conventional sense. Their judgments at active production inflection points are the labeling mechanism the platform runs on. They define what drift looks like, validate the signals, and tell us when we're wrong.
Writing.
Essays on production intelligence, operational drift, and the future of physical operations. Written by John Corser.
What Happens When AI Comes for the Knowledge Work That Holds Physical Operations Together?
A response to Matt Shumer's essay, from someone building AI in an industry where the cognitive work can't be separated from the physical.
Read on Substack →What the AI Industry Learned About Drift, and Why Physical Operations Need Something Harder.
The enterprise world solved the easy version of a problem every complex physical operation faces. Here is what the hard version requires.
Read on Substack →See your production the way telemetry sees it.
telemetry is additive. You add our ingestion address to your distro. The Production Pulse starts landing in your inbox. Nothing in your workflow changes.
We're talking with studios, streamers, independent producers, and completion bond companies about production deployments and portfolio-level intelligence. If you want to see the product against your own data, we'll show you.