Regulation (EU) 2025/40Applies from 12 Aug 2026Independent publication - not legal advice
PackagingCompliance.help
The Packing Line - a working desk for the EU packaging regulation
Home / Station 10 - Declaration of conformity and technical documentation / Guide

Common Documentation Gaps: What Audits and Authorities Actually Find

The recurring findings, ranked by how often they appear: orphan reports, expired certificates, boilerplate declarations, missing applicability reasoning, stale standards. A self-audit list drawn from the pattern.

Published 24 October 2026Checked against the regulation text on 24 October 2026European Union

The short answer

Documentation findings are remarkably consistent across businesses and sectors, which makes them a usable checklist. The top of the pattern: evidence that does not attach (reports naming no specification version, certificates for a different site or material); evidence out of time (expired certificates supporting live placings, declarations citing superseded standards); declarations that transfer nothing (boilerplate compliance letters in place of threshold-specific statements); the missing applicability reasoning (no index, so no proof the assessment was systematic); and change silence (production reality drifted from the file, with no change records between). Each is unglamorous, each is findable by a half-day self-audit, and each is disproportionately damaging when an authority finds it first, because it impeaches the file's whole credibility.

Work the list as a quarterly self-audit, family by family, and file the results with their closures.

Attachment failures: evidence that floats

The audit test for attachment: pick any report in the file and state, from the report itself, which specification version, which production period and which manufacturing site it covers. Reports failing the test are re-anchored (a covering note tying them to their specification, signed and dated - honestly, as a note made now about evidence gathered then) or replaced by fresh testing where the anchor cannot be honestly reconstructed. Certificates get the scope test from the certification guide. The systemic cure is intake discipline: evidence enters the file only through the index, which refuses unanchored documents - a small tyranny at the inbox that saves the archive.

Time failures: the expired and the superseded

Every dated artefact in the file - certificates, declarations, test reports against dated standards, supplier statements - belongs on the evidence register with its currency date, and the register's exception list (expiring within ninety days, already lapsed, standards superseded since citation) is a standing agenda item, not an annual discovery. Standards currency deserves its own check: the citation in the Official Journal, not the standard's own cover, decides which version carries presumption, and the acts calendar's legal milestones include citation changes for exactly this reason. Time failures are the findings with the least excuse and the easiest prevention; their presence in a file tells an auditor the system has no calendar, which invites the deeper look nobody wants.

Silence failures: the drifted file

The deepest finding class is the file that was accurate at assembly and never touched again, while specifications, suppliers and law moved on. Its detection is comparative: sample production reality (current specifications, current supplier list, current artwork) against the file and count the divergences. Its prevention is the change machinery of this station - triggers routed, calendar joined, dispositions recorded - whose entire cost is a standing agenda and a register. Businesses should measure their own silence: the median age of unreviewed file sections, reported like any other quality metric. In conformity documentation, silence is not golden; it is the sound of a file expiring.

Reading findings by what they impeach

Not all findings weigh alike, and the self-audit should rank by impeachment value: the damage a finding does to the file's credibility as a whole. An expired certificate on a live line impeaches the calendar; an orphan report impeaches the intake; boilerplate where specificity was owed impeaches the assessment itself; silence impeaches the institution. Close in that order when resources force a choice, and record the ranking reasoning in the audit notes - it teaches the next auditor (internal or otherwise) that the business understands its own failure modes, which is the quality every other finding is really probing for.

A self-audit afternoon, narrated

A mid-size converter runs the list against twelve families in one afternoon. Yield: three certificates expired inside the quarter (one supporting live placings - re-issued by the supplier within the week, the placing period's reliance documented); one grade worksheet anchored to a superseded specification (re-run on the current version, result unchanged, worksheet replaced); two supplier declarations in boilerplate form (re-requested in threshold form, one supplier upgrading immediately, one escalated to the sourcing agenda); and an applicability index missing for the oldest family (built from its file in an hour, finding one requirement - a labelling element - that had genuinely never been assessed, and was assessed that week). Four findings closed, one requirement caught. That is the list's ordinary yield, and the arithmetic of quarterly repetition is why the station prescribes it.

Primary sources on the record

Legal status: Practice under Articles 15-18 and Annex VII of Regulation (EU) 2025/40. Application position for this topic: From 12 August 2026.

Follow the line

Station 10 - Conformity and documentation The EU Declaration of Conformity and Technical Documentation: Annex VII Explained Every packaging line needs a declaration that it conforms, and a technical file that proves it. The pillar guide to the PPWR's conformity system: what the declaration states, what the file contains, who signs, and how long it all lives. Station 10 - Conformity and documentation Annex VII Technical Documentation: The Complete Contents Checklist General description, design data, composition, the requirement-by-requirement evidence index, test reports, calculations and supplier documentation. Annex VII turned into an assembly checklist with the traps marked. Station 10 - Conformity and documentation Updating Declarations: Change Triggers and Version Discipline A declaration describes a specification; everything that moves the specification moves the declaration. The trigger list - materials, suppliers, standards, grades, labels - and the assessment of when a change is a re-issue and when it is a note.