The Rights Data Exists. The Answer Rarely Does.

A Question That Should Be Simple 

Ask most media organisations a straightforward rights question. Is this territory clear. Does this window still hold. What happens if the deal is extended by six months. The honest answer usually takes longer to assemble than it should. Not because the information doesn’t exist, but because it exists in five different places, held by three different people, in formats that were never designed to be queried quickly. 

This is not a niche operational inconvenience. For a media organisation of any real size, rights questions surface constantly, in sales conversations, in scheduling meetings, in legal reviews, in casual hallway check-ins before a deal moves forward. Each one is small on its own. Together, they are one of the more persistent sources of drag in the business. 

The Data Was Never the Real Problem 

Rights databases have improved steadily over the years. Contracts are better structured than they once were. Systems of record, the platforms that store what has been agreed, licensed, and cleared, are, in most organisations, reasonably mature. Two decades ago, a rights team was working from filing cabinets and fax confirmations. Today, that same team is working from structured databases, digital contract repositories, and dedicated rights management software. 

What has not kept pace is the layer above all of that: the ability to actually reason across the data at the speed a real decision requires. Having the information stored correctly and being able to retrieve a precise, trustworthy answer from it in the moment someone needs it are two different capabilities, and the industry has largely solved for the first while leaving the second mostly untouched. 

Where the Friction Actually Lives 

A rights question is rarely only a rights question. It touches availability, commercial terms, historical performance, and the status of adjacent agreements. Answering it properly often means moving between a contract system, a spreadsheet someone maintains privately, and the memory of whoever has been at the company longest. 

Picture a mid-sized broadcaster fielding an inbound licensing enquiry on a Friday afternoon. The commercial lead needs to know whether a title is available in a specific territory, whether an existing holdback affects the window being proposed, and what similar deals have gone for in the past. None of that information is missing. All of it exists somewhere in the organisation. But assembling it into a single, reliable answer means pulling in legal, checking two systems, and waiting for someone who is not at their desk that day. The enquiry that could have been answered in minutes takes until Monday, if it gets answered at all before the buyer moves on. 

That reconstruction work, not the underlying complexity of rights itself, is what actually slows most organisations down. 

The Cost of Reconstruction 

This rarely shows up as a single dramatic failure. It shows up as a deal that takes three extra days to close because nobody could confirm availability quickly enough. A title that continues to air past its window because the one person who would have flagged it was out that week. A sales conversation that loses momentum, not because the opportunity wasn’t real, but because nobody could answer a rights question fast enough to keep the buyer’s attention. 

There is a quieter cost too. Teams that spend their time reconstructing answers rather than acting on them start to lose confidence in the answers they do produce. A number pulled together under time pressure, from three sources that may or may not agree with each other, is not the same as a number a team can act on without hesitation. Over time, that uncertainty becomes its own tax on decision-making, independent of whether any particular answer turns out to be right. 

None of this looks urgent from the outside. It adds up regardless. 

What “Intelligence” Should Actually Mean Here 

The industry has talked about AI in rights and media operations for a few years now, mostly in the register of automation: processing documents faster, flagging obvious errors sooner. That is useful, but it only addresses part of the problem. Automating the extraction of a clause from a contract still leaves the harder question unanswered, which is whether that clause, combined with everything else true about the deal, actually means the title can be sold into the territory being asked about right now. 

The harder, more valuable shift is turning static rights data into something that can actually be interrogated. Asked a plain question, in context, and trusted to give a grounded answer rather than a best guess. That requires more than a conversational interface sitting on top of the same fragmented systems. It requires the underlying data to be connected in the first place, so that the answer a system gives is actually built on the full picture, not just the slice of it that happened to be easiest to reach. 

From Reconstruction to Decision 

The organisations that move fastest over the next several years will not necessarily be the ones holding the most rights data. They will be the ones that have closed the gap between having that data and being able to act on it at the moment a decision is actually being made. Where a rights question stops requiring a reconstruction exercise and simply becomes something a team can ask, and trust the answer to. 

This is the problem worth spending the next several years solving. Not another place to store rights data, but a way to make the data that already exists answer the questions the business is actually asking, at the moment it is asking them. The organisations that get there first will not necessarily look different from the outside. They will simply stop losing deals, hours, and confidence to a problem that was never really about the data at all.