A maintained, source-linked tracker of the Dutch pension transition: what is a hard cut-off, what is a planning date, and how the chain of decisions actually fits together. The Dutch working title: "De Wtp-transitietijdlijn ontcijferd".
How to read this. This is independent interpretation of public sources, not official guidance and not legal advice. Dates and figures move as the law and supervisory pages are updated, so treat the tracker as a navigation aid and confirm every date against the official source before you act on it.
The Wet toekomst pensioenen (Future Pensions Act, abbreviated WTP) entered into force on 1 July 2023 and set in motion the largest reshaping of Dutch occupational pensions in a generation. For advisers and implementation leads, the hard part is not the headline. It is the chain. A single fund does not face one deadline; it faces a sequence of dependent decisions that run from the bargaining table through to the moment accrued entitlements are converted into the new system.
This article frames that sequence as a tracker. Rather than reprint a list of dates that drifts out of date the day it is published, the aim is to show how the links depend on one another, to separate genuine statutory cut-offs from softer planning milestones, and to give you a dataset you can keep current. The single fixed anchor everyone already knows is the final transition deadline of 1 January 2028. Everything else is best understood as a countdown to that point.
The WTP transition is a relay. Each stage hands an output to the next, and a slip early in the chain compresses the time available later. Read left to right, the core sequence runs like this.
The dependency matters because the dates are not independent settings on a dial. The transitieplan deadline gates the opdrachtaanvaarding; acceptance gates the implementatieplan; and the implementation plan, together with regulatory sign-off, gates the invaardatum. Plan dates that look comfortably ahead of 1 January 2028 can be tight once you account for data remediation and member communication, which are the stages that most often run long in practice.
Not every date in a transition schedule carries the same legal weight, and conflating the two is a common source of false comfort. It helps to sort each milestone into one of three buckets.
The discipline for an implementation lead is to label every row in the schedule with its bucket. A delayed soft date is a project management problem. A threatened hard cut-off is a governance and compliance problem, and it should be escalated as one. Treat the 1 January 2028 anchor as immovable and work backwards; treat intermediate dates as negotiable only to the extent the law and your supervisor allow.
The value of a deadline tracker is not a prettier calendar. It is a structured dataset that can be filtered, sorted, and reconciled against the official record. The table below defines the fields the WTPDataLab timeline dataset captures for each milestone, so the logic is transparent and each entry is auditable back to a source.
| Field | What it captures |
|---|---|
milestone_id | Stable identifier for the milestone, so references stay valid even if the label is edited. |
stage | Which link in the chain it belongs to: social partners, transitieplan, opdrachtaanvaarding, implementatieplan, or invaren. |
date_type | Hard statutory cut-off, regulatory or supervisory milestone, or soft planning date. |
nominal_date | The date as currently published, with an explicit note where it depends on the fund's chosen route. |
depends_on | The upstream milestone or milestones that must complete first, making the chain explicit. |
responsible_body | Who owns the deliverable: social partners, the pension provider, DNB, AFM, or another party. |
source_ref | Link to the official source for the date, so every entry is verifiable rather than asserted. |
last_verified | The date a human last checked the entry against its source, so readers can judge freshness. |
status | Whether the date is confirmed, provisional, or under revision in current policy material. |
Holding the data this way makes the dependency logic queryable. A single record might look like the sketch below. It is illustrative structure only: the values are placeholders, and the real nominal_date and source_ref must be filled from the official source.
{
"milestone_id": "transitieplan_final",
"stage": "transitieplan",
"date_type": "hard_statutory_cutoff",
"nominal_date": "CONFIRM_WITH_OFFICIAL_SOURCE",
"depends_on": ["sociale_partners_agreement"],
"responsible_body": "social_partners",
"source_ref": "rijksoverheid.nl | werkenaanonspensioen.nl",
"last_verified": "YYYY-MM-DD",
"status": "provisional"
}The tracker follows three rules so that it stays trustworthy as the picture changes.
Official sources lead. Each milestone is dated from primary material: the legislation and government explanation via Rijksoverheid and the cross-sector programme Werken aan ons Pensioen, supervisory expectations from DNB and AFM, and sector coordination from the Pensioenfederatie. Where data standards or analytical context matter, we reference standards work via SIVI and independent research from CPB and Netspar. We do not promote a fund's internal planning date into a legal deadline.
Qualitative where the number is unstable. Beyond the established 1 January 2028 deadline and the option to take up to a 10% lump sum at retirement (the bedrag ineens), we describe mechanisms rather than assert precise counts, euro amounts, or intermediate dates that shift with policy. Where a figure is genuinely needed, the tracker points to the source rather than freezing a number that may already have moved.
Maintained, with provenance. Every entry carries a last_verified date and a status. The dataset is reviewed and updated over time as the official pages change. That is the point of treating this as a living tracker rather than a one-off article: the WTP transition is still in motion, and a static list ages badly.
For an adviser or implementation lead, the workflow is straightforward once the data is structured. Start from your fund's chosen invaardatum and work backwards through depends_on to see which upstream milestones constrain it. Filter on date_type to separate the dates you can flex from the ones you cannot. Then sort by last_verified to find the entries most in need of a fresh check against the source.
The one idea to keep. The WTP transition is a dependent chain ending at a single hard anchor, 1 January 2028, not a flat list of dates. Track each milestone by its type and its dependency, verify it against the official source, and treat soft planning dates as the slack and statutory cut-offs as the wall.
Use the official homepages below as your entry points, then navigate to the current WTP transition pages. Official URLs and document locations change, so confirm the live page and the publication date before citing any deadline. When a date in this tracker and a date on an official page disagree, the official page wins.
Confirm the live page before relying on any date here: official sites are reorganised periodically, and the authoritative version is always the one currently published by the responsible body.