Screen a dataset for competition-sensitive information

Inspect the information exchange the license creates

A license for maintenance events might include future capacity, customer allocations or price changes that help competing businesses predict one another's conduct. An intermediary can distribute the same signals through a benchmark, dashboard or recommendation rather than handing over the original file. Review the information available to recipients and contributors, including what the combined product reveals.

The Commission's April 2026 TTBER explanatory note describes new data-licensing guidance. It says exchanges not objectively necessary and proportionate to implementing a data license are assessed using Chapter 6 of the Horizontal Guidelines. The Chapter 6 text actually reviewed here is the Commission's approved-content 2023 annex; it addresses commercial sensitivity, age, aggregation and indirect exchange.

This is an EU competition screening method for specialist review, not an exemption finding. Keep rights, privacy and trade-secret checks separate. A company may have permission to disclose a field while the proposed exchange still needs competition analysis. A nondisclosure agreement does not answer what recipients can coordinate using the information.

Worked example: a repair-capacity benchmark

In this hypothetical project, three competing regional repair networks contribute records to benchmark B-1. A proposed subscriber dashboard shows repair categories, average delay, realized price, customer industry and upcoming available capacity by depot. Contributors will also receive the dashboard. The advertised business purpose is understanding common failure patterns.

The owner completes the map below before making any data available. The map does not label a field universally lawful or unlawful. It identifies what the stated task needs, what strategic information could be exposed and what the fictional team decides to hold or redesign.

Test what the dashboard makes inferable

In hypothetical B-1, a depot code is replaced with a region label. One competitor is the only contributor operating a particular repair category in that region. The revised chart therefore still reveals its recent delay and capacity situation. Removing a name changes the display but does not remove the identifying context.

The reviewer tests likely recipient knowledge rather than inspecting the export alone. A contributor knows its own submitted records and may subtract them from a shared total. A publicly known plant closure can help identify another contributor. A filter sequence can expose a small cell that the default dashboard appears to combine.

Record these pathways with the actual planned output, contributors, available filters and customer audiences. Capture a representative result using invented demonstration records where possible. The aim is to provide specialist counsel with inspectable functionality, not to invent a numerical rule saying a fixed number of participants makes exchange safe.

Aggregation and delay need context

The Horizontal Guidelines treat aggregation and age contextually. A hard-to-attribute summary may present a different risk from individual information, but aggregation is not an automatic clearance. Information's useful age depends on the market and commercial cycle; a universal delay period cannot be imported from an unrelated example.

For hypothetical B-1, a quarterly historical chart might still describe an unresolved long repair backlog. Calling it old would conceal its current strategic usefulness. The team records the repair-contract cycle and which outstanding work remains visible. It holds the chart until a competition reviewer can assess the proposed exchange and market facts.

Technical redesign then follows the intended task. The hypothetical team proposes excluding price and capacity, removing revealing filters and documenting why each remaining field supports fault-pattern analysis. It does not announce that those changes guarantee compliance. The specialist review must examine the actual narrower operation, including any recipient who is also a competitor or contributor.

Decide whether the business purpose justifies this design

The completed hypothetical decision is to stop B-1's price-and-capacity dashboard and prepare a separate fault-pattern specification for further review. The record names excluded fields, unresolved output cells, contributor access and the person responsible for competition advice. If a commercial sponsor cannot explain why a strategic field is needed, its availability in the source system is not a reason to keep it.

Use due diligence to ask who contributes, who subscribes and whether contributors can inspect competitors' results. Use rights review to retain the disclosure boundary. The operational trade-secret guide addresses another layer; a trade-secret clearance does not replace the exchange analysis in this article.

VOID can coordinate an introduction using the owner's approved description of the narrowed package. Raw records, benchmark access and a final license require separate decisions. No interest metric or traffic estimate proves the package has buyers, and no proposed aggregation rule should be marketed as legal clearance.