Summary

  • The European Commission’s proposed Digital Networks Act would put four deadlines around voluntary telecom conciliation: one week for the national regulator to inform BEREC, two months for BEREC’s opinion, three months to convene the parties, and one month after the meeting for a written account.
  • That account must cover the parties’ views and possible next steps. It includes agreement terms only if both parties attended and an agreement exists; if both attended without agreement, it includes the regulator’s options for cooperation. Article 192 names neither the recipient nor a publication route.
  • BEREC’s March assessment calls the proposed mechanism voluntary and non-binding, and says its rationale, scope and expected use need clarification. The European Parliament procedure file still lists the proposal as awaiting committee decision.

A clock is easy to legislate

A commercial disagreement between a network provider and a content or technology company can sit for months in the gap between engineering and accounting. One side pays to carry traffic; another may say its network resources are being used on terms that do not reflect the traffic’s cost or value. Europe’s proposed answer is a structured meeting, not a tariff decree.

The Commission’s Digital Networks Act proposal, COM(2026) 16 calls the mechanism a facility for voluntary conciliation. Its surrounding recitals point to IP traffic handover, peering, transit, service-level agreements, traffic forecasts and cooperation between connectivity firms and adjacent digital businesses. They describe the problem as practical: arrangements should support reliable service without creating disproportionate or unsustainable investment needs for the receiving network provider. Benefits from rising traffic should be shared in a way that supports continued investment and resilience.

Article 192 then puts a timetable around the disagreement. A provider can request a meeting on a technical or commercial arrangement covered by BEREC’s proposed guidelines. Unless the parties agree otherwise, the national regulator of the requesting party convenes it. Within a week the regulator tells BEREC the case elements. BEREC has two months from the request to issue an opinion on those elements and options for effective cooperation. The meeting must happen within three months. The regulator has one month after it to provide a written account.

These clocks overlap. The two-month opinion is due before the three-month meeting deadline; the account may arrive as late as a month after that meeting. The proposal does not make every step wait for the previous one. It makes the institutions answerable for moving the file.

The last step creates a record, but not a named reader

Article 192 is unusually concrete about the contents of the account. It must include the parties’ views and possible next steps. If both parties attend and reach agreement, it should include the elements of that agreement. If both attend and no agreement is reached, the regulator’s proposed options for effective cooperation must appear. The account is not an ornamental minute sheet: the text gives it a minimum evidentiary job.

Then the draft stops short of identifying its audience. It does not say which parties or institutions receive the account, whether a public version is required, how commercially sensitive details should be handled, or how the account becomes evidence for the later review. Article 193 does require BEREC to publish a report on the effects of the guidelines and on conciliation, beginning 24 months after the Regulation’s application date and every two years afterward. The Commission would review ecosystem cooperation by month 36. Those are public checkpoints, but the proposal gives them no case-level reporting fields to work with.

The evidence gap is specific: Article 192 does not name the account’s recipient or publication path, and Article 193 does not set minimum case-level data for BEREC’s report. That leaves the public able to see that a review is required, but unable to tell from the draft what a reviewer must be able to count or verify.

A meeting is not a verdict

The line between conciliation and enforcement is deliberate. Recital 403 says the proposed guidelines should cover traffic handover and arrangements such as peering and transit. Recital 405 describes a structured, neutral forum supported by national regulators and BEREC, with BEREC opinions on individual cases, while preserving contractual freedom. The preceding recital says arrangements of a cooperative or voluntary nature should not be folded into the dispute-resolution machinery used to enforce obligations.

BEREC’s own Early Assessment, BoR (26) 52, published on 30 March, reads Articles 191–193 as a voluntary, non-binding conciliation mechanism. It supports taking a wider view of digital-market cooperation, but says the provisions’ rationale, scope and expected practical application need further clarification. That is a regulator pointing at the actual design question: the statute names a process, but the working conditions and public feedback loop still need definition.

The current legislative record is still open. The European Parliament’s procedure page for 2026/0013(COD) lists the status as “Awaiting committee decision” and records a committee draft report dated 20 October 2026. The proposal has not become law, and no conciliation result exists to measure.

The compromise worth asking lawmakers to write is modest and practical. Keep the commercial outcome voluntary; specify who must receive the written account; say what can be disclosed and what must be protected; and require BEREC’s later report to state how many requests, meetings, agreements and unresolved cases the mechanism produced. Four deadlines can make officials move. A defined record would let everyone else see whether the movement helped.

Sources