EU digital platform regulation: milestones worth checking

Talking about “European platform regulation” as if it were a single law leads to mistakes. The European Union has adopted different instruments to address different issues, ranging from obligations for intermediary services to competition conditions and the protection of media pluralism. To reconstruct a useful timeline, the first step is to define which law it follows. In this guide, the main thread is the Digital Services Act, known by its English initials, DSA. Other frameworks are mentioned only to prevent their areas of coverage from being confused. This distinction matters because several rules may concern the same companies without being the same legal instrument, sharing the same purpose or following the same legislative timetable. A timeline that combines them without identifying them can therefore give readers a misleading impression of what happened and when.

It is also important to separate four dates that are often conflated: the Commission’s proposal; agreement or adoption by the institutions; entry into force following official publication; and the date from which obligations must be met. These expressions are not interchangeable. A political announcement may signal an intention, but it does not by itself establish which text was adopted or when it began to apply. The strongest approach is to check the legal act and its timetable against institutional documentation. EUR-Lex’s overview page on the DSA is a useful starting point; to verify a specific article, the regulation as published in the Official Journal should be consulted. In a carefully written chronology, each date should be paired with a description of the event it records, rather than presented as a bare number that readers have to interpret.

The DSA establishes a framework of obligations for online intermediary services. EUR-Lex’s overview presents it as a digital services law and explains that its requirements vary according to the type and size of service. It is therefore inaccurate to describe it as a general ban on harmful content or as an identical obligation for every website. The purpose and scope of each obligation depend on what the law says and on the category of service concerned. A general summary may help readers understand the subject, but it cannot replace the wording that determines which service or actor is covered by a particular requirement.

This distinction matters when describing the background. EU competition policy can affect large digital companies, but it is not synonymous with the DSA and does not necessarily have the same aims or mechanisms. Similarly, European rules on media freedom and pluralism address concerns specific to that sector. The fact that several laws affect technology companies does not make them one legislative sequence. Before adding a milestone to a timeline, check whether it belongs to the same instrument, amends an existing law or responds to a different framework. That check also helps prevent a reader from attributing a requirement to the wrong act. The names of the instruments, their scope and the event being dated should remain clear even when a short overview discusses them side by side.

During the legislative process, Parliament press releases can help identify moments in the negotiations, but they should be read for what they are: institutional communications about a stage of the process. The European Parliament’s press release of 12 April 2022 on the Digital Services Act reports an agreement related to the law. That milestone should not simply be presented as the date of entry into force, and it does not replace the legislative text when establishing the final scope of obligations. An agreement is relevant to the history of a law, but a reader still needs to know what kind of agreement the source reports and what later legal steps followed.

The next step in a rigorous chronology is to check the adopted act and its legal reference. The EUR-Lex record makes it possible to identify the instrument and consult associated legislative information. When checking the record against the published document, log the adoption date, publication date and entry-into-force date indicated by the regulation separately. If a secondary source uses “approval” to describe a political agreement, preserve that qualification in the wording rather than silently treating the terms as identical. A date explains something only when it is also clear what happened on that day. This method gives readers a way to trace the account back to the relevant institutional record and reduces the risk that a negotiation announcement will be mistaken for the final legal act.

A law may enter into force on one date while providing that its provisions apply from another. The distinction matters to users and companies alike: entry into force identifies the point at which the act becomes part of the EU legal order, whereas application determines when its obligations begin to operate, according to the legal timetable. For both dates under the DSA, the appropriate reference is the regulation itself, not a news report about its adoption. A timeline should therefore retain both dates when they differ, and explain what each one means instead of using “in force” as a general label for every stage.

The timetable need not be uniform for every regulated party. Some obligations may depend on the service category or on conditions laid down in the law itself. A simplified timeline can offer an overview, but it cannot replace checking the provisions that apply to a particular company. The practical question is not only “when was it adopted?” but “which obligation, for whom, and from what date?” When an institutional summary does not specify an exception or a particular date, it is better not to infer one. The relevant article should be located before turning an assumption into a factual statement. Readers should also distinguish a general start date from any timing rule that the text expressly ties to a category of service or another condition; the legal provision, rather than an approximate summary, determines the answer.

Enforcement also has an institutional dimension. The European Commission explains that each Member State must appoint a Digital Services Coordinator, responsible for matters relating to the application and enforcement of the DSA in that country. The Commission and national coordinators share supervisory and enforcement responsibilities. This helps explain why compliance is not handled by a single EU office, although the precise allocation of powers depends on the law and on the action taken by the authorities. A general description of the system should not imply that every authority can perform every task, or that the Commission’s role makes national coordinators irrelevant.

When adding later actions to a timeline—for example, an appointment, investigation or decision—check who carried it out, under which power and on what date. A general page about coordinators describes the framework, but does not by itself prove that an authority has opened proceedings against a particular platform. Likewise, an investigation should not automatically be described as a proven infringement: the procedural status and the outcome of a case are different facts. Institutional documentation is especially useful for following these steps, while legal texts define the powers that authorities may exercise. Keeping these distinctions visible helps readers understand whether a dated event concerns the structure of supervision, a specific action or a final finding, without implying more than the source establishes.

Readers can use a straightforward check to orient themselves: first identify the law; then classify the event—proposal, agreement, adoption, publication, entry into force, application or supervision—and finally verify it using an appropriate source. Press releases help place announcements and agreements in context. Commission pages help explain the supervision framework. EUR-Lex and the Official Journal make it possible to confirm the text and its legal dates. If the sources do not support a particular day, the timeline should leave it out or explain the limitation, rather than fill the gap with an approximate date. This source-by-source approach also makes it easier to see whether two accounts refer to different stages rather than contradicting each other.

The evidence gathered here makes it possible to sketch how the DSA works and to guide readers through its legislative history, but it is not an exhaustive inventory of every amendment, national decision or enforcement action. Nor does it establish, without consulting the relevant text and case file, how an obligation applies to a particular platform. For a timeline ready for publication, link the primary document that supports each date and describe the stage accurately. That method avoids the most common error: confusing an adopted law with a law whose every detail is already applicable. Where an account cannot be verified against the source material, the appropriate response is to state the limit, not to make a more definite claim than the documents allow.