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 file 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 manufacturer declaration as well as checks by importers, distributors, authorised representatives, and authorities. ESPR requires the written EU declaration of conformity for each product model to be kept with 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 and information such as declarations of conformity, technical documentation, and conformity certificates where specified by the delegated act. The technical file should therefore include a DPP evidence register, not just screenshots: unique product identifier, relevant operator and facility identifiers, access-right assumptions, data source owner, last update, and the proof that the DPP data matches the technical file.

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.

A competent national authority may request information and documentation needed to demonstrate conformity. ESPR sets short response windows in several operator duties, including 15 days for authorised representatives, importers, and distributors after a reasoned request, and Article 27 requires manufacturers to provide information and documentation as soon as possible and in any event within 15 days of receiving the 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.

This checklist intentionally stops at the ESPR framework and the grounded Commission DPP context. It does not name national authorities, national filing procedures, national penalty amounts, product-group thresholds, or final product-specific DPP fields unless those details are present in the applicable delegated act or another official source used for the specific product.

For a real product launch, the blocked items are the product-specific delegated act, any harmonised standard or common specification chosen for the product, and any Member State authority procedure that the company intends to rely on. Add those only after they are sourced and cite them next to the claim they support.