Book a consultation

Insights · Data costs

How to audit data feed usage before a renewal

Almost every data cost review we have run has found feeds nobody could explain. Finding them is not complicated, it is just rarely done, because nobody owns the question between renewals.

Why this step gets skipped

It takes longer than the renewal deadline allows for.

A proper audit touches procurement, trading, risk and IT, and most companies only start looking once a renewal notice has already arrived, with a deadline attached. Oil price reporters are well aware that few buyers carry out this kind of review on a cycle independent of the renewal date.

Starting the audit well ahead of that date is the single biggest lever available. See when to start preparing for a renewal, or how our data cost reduction advisory runs this process, on a no-saving, no-fee basis.

Book a consultation to run this audit

Questions

Auditing data feed usage, in brief.

How long does a usage audit usually take?

It depends on how many entities and systems are involved, but a focused audit for a single business unit can often be completed in a few weeks. A group-wide review across trading and risk functions takes longer.

Who inside a company should own this?

Usually procurement, working with trading and risk teams who know how the data is actually used day to day. Without input from the actual users, an audit based on contracts alone misses most of the detail.

What is the most common finding?

Feeds that were set up for a project, a desk or a system that no longer exists, but were never cancelled because nobody was explicitly responsible for reviewing the subscription list.

Should the audit happen every renewal, or only occasionally?

Ideally every renewal, and lightly in between. Usage tends to accumulate steadily rather than all at once, so a periodic check catches drift before it becomes a large, awkward correction.

Related

Find out what your next renewal should cost.

Book a consultation