How do you keep a technical file and Declaration of Conformity in audit-ready condition?

Default hero background
Uncategorized
Jason van de Zande

Keep a technical file and EU Declaration of Conformity in audit-ready condition by maintaining complete, current technical documentation under strict document control, with clear versioning, traceable changes, and fast retrieval for market surveillance requests. Audit-ready compliance comes from routine reviews, disciplined updates after product changes, and a single source of truth for each product and model.

This matters most for non-EU manufacturers and online sellers because authorities can request documentation quickly, and marketplaces may also ask for proof that product safety information is organized and current. The goal is simple: no scrambling, no missing files, and no outdated declarations.

The sections below break down what to include, how to keep it current, and how to prevent the most common audit findings.

What should be included in a technical file and Declaration of Conformity?

A technical file should contain the technical documentation that demonstrates a product meets applicable EU requirements, including design information, risk assessment, test evidence, labeling, and traceability details. An EU Declaration of Conformity is a formal statement by the manufacturer that a product complies with the relevant EU harmonization legislation that requires a DoC, and it must match the exact product placed on the market.

In practice, the technical documentation should be organized so a market surveillance authority can understand what the product is, which rules apply, and how compliance was verified. While the exact contents vary by product and legislation, a strong technical file typically includes:

  • Product identification such as model, SKU, batch or serial logic, photos, and intended use
  • Design and manufacturing information such as drawings, bill of materials, critical components, and manufacturing controls that affect safety
  • Risk assessment covering reasonably foreseeable use and misuse, hazards, and risk reduction measures
  • Test reports and assessments supporting safety and performance claims, including relevant standards used
  • Instructions and safety information such as user manual content, warnings, translations, and placement rules
  • Labeling and traceability including product markings, packaging artwork, and economic operator details where required
  • Change history showing what changed, when, why, and what evidence supports the change

For the EU Declaration of Conformity, keep it consistent and precise. It should identify the product, the manufacturer, the applicable legislation, and the standards or other specifications used to demonstrate conformity. It also needs a responsible signature and date, and it must be updated when the product or applicable requirements change.

How do you keep technical documentation audit-ready over time?

You keep technical documentation audit-ready over time by treating it as a living system, not a one-time upload. That means applying document control, scheduling periodic reviews, and updating the technical file and EU Declaration of Conformity whenever the product, supplier, labeling, instructions, or applicable EU requirements change. Audit-ready compliance depends on speed, accuracy, and traceability.

A practical maintenance routine for document control looks like this:

  1. Assign ownership per product family so someone is accountable for updates and approvals
  2. Use version control with clear file names, revision numbers, and a change log
  3. Define triggers for updates such as component substitutions, a new factory, new warning text, new packaging, or new test results
  4. Run scheduled reviews at least annually, and also before peak sales periods or major listing expansions
  5. Keep evidence linked so each claim or requirement points to a test report, assessment, or controlled document
  6. Test retrieval by doing a timed internal drill to confirm you can compile the requested set quickly

In 2026, the enforcement environment is shaped by the General Product Safety Regulation (EU) 2023/988 (GPSR) and the Market Surveillance Regulation (EU) 2019/1020 (MSR). Together, they increase expectations around product safety information, traceability, and responsiveness to market surveillance. If you sell through marketplaces, audit-ready compliance also reduces the risk of listing interruptions caused by missing or inconsistent documentation.

What are the most common audit findings and how can you prevent them?

The most common audit findings involve missing or inconsistent technical documentation, outdated EU Declarations of Conformity, weak document control, and gaps between what is sold and what is documented. You prevent these findings by aligning every file to the exact product variant, maintaining a controlled revision process, and verifying completeness before products ship or listings go live.

Common findings and concrete prevention steps include:

  • DoC does not match the product because model numbers, brand name, or scope differs from what is sold. Prevent this by tying each DoC to a specific product identifier and keeping a variant matrix.
  • Outdated standards or legislation references on the DoC. Prevent this with a scheduled compliance review and a controlled template that is updated centrally.
  • Missing risk assessment or a risk assessment that does not reflect foreseeable use. Prevent this by updating the assessment when warnings, user group, or product design changes.
  • Test reports are incomplete or not traceable to the exact configuration tested. Prevent this by recording configuration details, critical components, and any deviations.
  • Labeling and instructions do not match the file such as different warning text, missing translations, or old packaging artwork. Prevent this by storing final released artwork and manuals as controlled documents.
  • Slow response to market surveillance because files are scattered across email threads and drives. Prevent this by maintaining a single source of truth and practicing retrieval drills.

Also plan for safety feedback. If you receive an accident report or identify a potential risk, document what you learned, what you changed, and how you informed relevant stakeholders. Under the MSR, the Responsible Person role is performed by an economic operator and must be able to inform the manufacturer about risks in line with Article 4, even though notifying serious risks to authorities is the responsibility of the Authorized Representative when that role is appointed.

How EARP helps keep technical files and Declarations of Conformity audit-ready?

We help keep technical documentation and EU Declarations of Conformity audit-ready by acting as an independent EU-based compliance partner focused on document control, completeness checks, and fast responsiveness to market surveillance requests. Our approach supports audit-ready compliance under GPSR and related EU product safety rules without distracting your team from product and sales operations.

  • Technical documentation intake and completeness verification using established checks for required product safety documents
  • Controlled storage and retrieval readiness so documentation can be made available to authorities when requested
  • Ongoing document control support including versioning discipline and update triggers after product or labeling changes
  • Clear role alignment between Responsible Person and Authorized Representative responsibilities under the MSR

If you want a practical path to audit-ready compliance, review our EU compliance services and then contact us to discuss your product range and documentation status via our contact page.

Related Articles