Every PRIIPs Key Information Document resolves to three numbers a retail investor will actually read: a summary risk indicator, a set of performance scenarios, and a total-cost figure. Each of those is only as defensible as the data underneath it — and that is where most KID programmes run into trouble, not in the templating.
Below is the readiness checklist our team runs with clients before the production window opens. It is deliberately about inputs, because the output formats rarely change as much as the portfolios feeding them.
1. Confirm look-through to the lowest level
The summary risk indicator and the market-risk measure depend on a complete, consistent return series. For funds of funds and multi-asset vehicles, that means resolving look-through to underlying holdings — not stopping at the wrapper. If a sleeve is modelled with a proxy, document the proxy and its rationale now, while there is time to challenge it.
2. Rebuild the cost waterfall from source
Reduction-in-yield calculations are sensitive to one-off entry and exit costs, ongoing charges, and any performance fees. Pull these from the source agreements rather than last year's KID; carried-forward figures are the most common source of a restated disclosure.
The format is the easy part. The defensibility lives in the data lineage behind every figure.
3. Stress the performance-scenario inputs
Moderate, favourable, unfavourable and stress scenarios are mechanical once the inputs are right — but they inherit any gaps in the history. Check that the recommended holding period, the benchmark, and the observation window are all aligned across the range, and that newly launched share classes have a sound methodology for short histories.
4. Validate before you template
Completeness checks, tolerance bands and an exception report should run before anything is rendered to an EPT file. Catching a missing cost component at the data layer takes minutes; catching it after submission takes a refiling.
5. Map UCITS KIID dependencies
Where a UCITS KIID is still produced alongside the PRIIPs KID, reconcile the two so a single change in the data model updates both. Divergence between them is a frequent finding in supervisory reviews.
None of this is glamorous. But teams that treat the KID as a data problem rather than a document problem are the ones that move from a frantic quarterly scramble to a controlled, repeatable cycle — and that is the entire point of an enterprise data platform.