Metadata is the part of a streaming product that nobody talks about until it breaks. When it works, viewers find the right content at the right time and the experience feels seamless. When it breaks, the problems are visible to every viewer — wrong game titles, incorrect start times, missing artwork, events that appear to have already ended when they are still in progress.
In VIP's experience, metadata problems fall into five recurring categories. None of them are exotic. All of them are preventable. Here is what they look like and what to do about them.
Time Zone Errors
This is the most common metadata problem in live sports streaming, and it is almost always caused by the same thing: the content management system stores event times in UTC, and something in the display chain fails to convert correctly to the viewer's local time.
The result is that events appear at the wrong time. A game scheduled for 7:00 PM Eastern appears at 7:00 PM Pacific — three hours late — because the time zone conversion was not applied. Or the conversion is applied twice, and the game appears six hours early.
The fix is to establish a clear, documented convention for how times are stored and displayed throughout the system, and to test it explicitly across multiple time zones before launch. A test that checks event times in Eastern, Central, Mountain, and Pacific time zones takes less than an hour and catches this problem reliably.
Inconsistent Team and Event Naming
A sports streaming product typically has multiple places where team names appear: the schedule, the event detail page, the search index, the navigation, and potentially the artwork. If these names are not consistent — if the same team appears as 'LA Lakers' in one place and 'Los Angeles Lakers' in another — the product feels unpolished and search within the app may not work correctly.
This problem is usually caused by metadata coming from multiple sources — a schedule feed, a content management system, and a rights management system — that use different naming conventions. The solution is to establish a canonical name for each team and enforce it across all data sources before the data reaches the product.
Missing or Placeholder Artwork
Artwork problems are often caught late because they require visual inspection. A developer testing the app may not notice that a team logo is missing or that a placeholder image is still in place, because they are focused on functionality rather than visual quality.
For a sports streaming product, the minimum artwork requirements are: a team logo for every team in the catalog, an event thumbnail for every event, and a hero image for the home screen. Missing any of these creates a visually broken experience.
The most reliable way to catch artwork problems before launch is to do a visual review of the entire content catalog — every event, every team, every category — on the actual app UI, not in the content management system. Problems that are invisible in a spreadsheet are obvious in the app.
Replay Availability and Duration Errors
Replays are a critical feature for sports streaming products, but they are often the last thing to be tested before launch. The replay workflow — recording the live stream, processing it into a VOD asset, updating the metadata to reflect the replay's availability, and making it accessible in the app — involves multiple systems and multiple handoffs.
Common replay problems include: replays that are not available until hours after the event ends (when viewers expect them immediately); replays that start at the wrong point (the beginning of the broadcast rather than the beginning of the game); and replays that show the wrong duration in the metadata.
Testing the replay workflow requires actually running a live event through the full production pipeline and verifying the replay at each stage. This cannot be done with synthetic test data — it requires a real or simulated live event.
Event Status Not Updating
A live event that has ended should not continue to appear as 'LIVE' in the app. An upcoming event that has started should not continue to appear as 'UPCOMING.' The event status — upcoming, live, ended — must update in real time as the event progresses.
This sounds obvious, but it is a common failure mode. The status update may depend on a signal from the production team, a scheduled job that runs on a fixed interval, or a manual update in the content management system. Any of these can fail or be delayed.
The practical consequence is that viewers see incorrect status information — a game that ended an hour ago still shows as 'LIVE,' or a game that started 20 minutes ago still shows as 'UPCOMING.' This erodes trust in the product and creates confusion about what is actually available to watch.
The Common Thread
All five of these problems share a common characteristic: they are invisible in development and visible to every viewer in production. The content management system looks fine. The data feeds look correct. The app passes functional testing. And then a viewer opens the app and sees a game that ended three hours ago still listed as live.
The only reliable way to catch metadata problems before launch is to test the full system end-to-end with realistic data — real team names, real event times, real artwork — and to do that testing on the actual app UI, not in the back-end systems. The problems are in the display layer, and that is where they need to be found.
About the Author
Danny Ohman
Co-Founder & Chief Product Officer
Danny Ohman is Co-Founder and Chief Product Officer of VideoStream Interactive Partners. He brings more than 25 years of television production experience, including 2,500+ hours of live production at SiTV (now Fuse), and deep expertise in content operations, metadata, and the practical realities of live sports streaming.
Areas of Expertise
More from Danny