EU Data Act deadlines and compliance calendar

Article 50 controls the general application date and the later product and contract dates. Other articles set the switching-charge, national penalty-notification, model-clause, and evaluation dates.

Do not collapse these dates into one readiness deadline. The same organisation may need different owners for connected products, related services, data-sharing contracts, B2G request handling, cloud switching terms, and standards monitoring.

Connected-product teams should maintain a release calendar that distinguishes market-placement dates from general Data Act readiness. Article 3(1) has its own timing: it applies to connected products and related services placed on the market after 12 September 2026.

Before an EU release is cleared, record whether the item is a connected product, whether a related service is linked, which pre-contract information has been prepared, and how the user can access relevant product data and related-service data. Article 3(1) requires data to be directly accessible by default where that is relevant and technically feasible; otherwise the data holder must provide access under Article 4.

Contract owners need separate tracks for new contracts and older contracts. Chapter IV applies to contracts concluded after 12 September 2025, while certain older contracts become subject to Chapter IV only from 12 September 2027.

The calendar should therefore not mark every pre-existing contract as immediately remediated. It should identify whether the contract was concluded before or after 12 September 2025, whether it is indefinite, and whether it is due to expire at least 10 years from 11 January 2024.

Some Data Act calendar items are not one-off application dates. Data processing service providers and teams handling exceptional-need public-sector requests need operational clocks that start when a customer or authority triggers the process.

For cloud switching, track the charge phase-out and each contract or process period. For business-to-government (B2G) exceptional-need requests, track the deadline to decline or seek modification. That deadline is not the time allowed to supply the data: Article 18(1) requires production without undue delay, taking account of necessary technical, organisational, and legal measures, while a compliant request specifies its production deadline.

Standards work belongs in the calendar, but it should be labelled differently from binding application dates. Articles 33, 35, and 36 use harmonised standards, common specifications, implementing acts, and central repositories as implementation mechanisms.

Create standards-watch entries for Commission requests, European standardisation deliverables, Official Journal references, and central repository references. Do not treat a standards work item as a legal application date unless the source creates a binding trigger.

Use the compliance calendar as an evidence index. Each row should show why the date matters, which obligation it affects, who owns the work, and what proof is needed before the item is closed.

Keep internal target dates visibly separate from official dates. Internal dates can be useful for product release, procurement, legal review, or engineering work, but the row should not imply that an internal planning date is set by the Data Act.