ESPR market surveillance technical documentation checklist

Start the file with the product group, model or batch boundary, and the delegated act adopted under Article 4 that applies to that product. ESPR sets the framework, but the technical documentation must map to the product-specific performance requirements, information requirements, conformity assessment route, label or DPP obligations, and any standards or common specifications named for that product group.

The extraction record should separate binding requirements from implementation assumptions. For each requirement, capture the source citation, product variant, owner, test or calculation method, evidence artifact, and whether the proof belongs in the technical file, the DPP, the EU declaration of conformity, a label, instructions, or an authority-response pack.

For internal production control, Annex IV says the manufacturer establishes technical documentation that makes it possible to assess conformity with the delegated act. Treat that as a traceability matrix: each product requirement should point to the design, manufacturing, operation, calculation, examination, measurement, and test evidence that proves the claim.

The record should also identify what was not used. If a harmonised standard or common specification is partly applied, record the parts applied; if it is not applied, describe the solution used to meet the requirement.

The technical file should support the EU declaration of conformity as well as checks by importers, distributors, authorised representatives, and authorities. Keep the written declaration for each product model with the technical documentation for ten years after the product is placed on the market or put into service, unless the delegated act specifies a different period.

Importer and distributor records should not duplicate the full file blindly. They should show the checks each actor is responsible for: conformity assessment completed, technical documentation drawn up, required documents present, CE or other conformity marking present, required information supplied, and the DPP available where the delegated act requires it.

ESPR allows the DPP to carry compliance documentation such as declarations of conformity, technical documentation, and conformity certificates where specified by the delegated act. Use a DPP evidence register with the unique product identifier, relevant operator and facility identifiers, access-right basis, data source owner, last update, and proof that the DPP data matches the technical file. Screenshots alone do not establish those links.

Because the Commission registry, public portal, customs checks, and authority access operate around identifiers and access rights, DPP evidence should be tested as data. Keep scan results, link-resolution records, registry or identifier handoff records where relevant, and records showing that restricted updates are controlled.

For a passport registered under Implementing Regulation (EU) 2026/1778 from 6 August 2026, retain the verified-operator record, submitted identifiers and commodity code where applicable, selected model-batch-item level, unique registration identifier, version timestamps, and generated proof of registration. Proof remains available for 90 calendar days and can be regenerated. The registry's automated checks do not prove substantive conformity.

A competent national authority may request information and documentation needed to demonstrate conformity. Manufacturers, authorised representatives, and importers must provide the required material as soon as possible and no later than 15 days after a reasoned request. Distributors have 15 days to provide the information and documentation to which they have access. Separately, Article 36 requires economic operators to retain upstream and downstream operator, quantity, and exact-model information for ten years, unless the delegated act sets another period, and provide it within 15 days of a market-surveillance request.

Keep the technical file stable and maintain a separate authority-response log. That log should show what was requested, who responded, which technical-file version was supplied, the language and format used, any confidentiality handling, corrective action required, and the final authority outcome.

Before launch, confirm the product-specific delegated act, the coverage and status of each harmonised standard or common specification used, and the relevant Member State authority procedure. Keep the legal source next to each requirement, method, deadline and authority-response instruction.

Framework scope, working-plan priority and a successful passport registration are different findings. The product file needs the applicable product rule and evidence that each requirement is met.