The declaration of conformity: a signed assertion, not an administrative formality

One page, several audiences, different reasons for asking

A retailer's assurance team wants it to close an onboarding checklist. An importer wants it because their own position depends on the manufacturer having one. An enforcement officer wants it as the entry point to the evidence behind a marking. A specifying engineer wants it to see which standards were used. Those readers are looking for different things in the same document, and the version that satisfies all of them is precise about the product identity, honest about the basis relied on, and consistent with the file behind it. Vague product descriptions covering a whole range are where most disputes about scope begin.

Signing is a personal act on behalf of a legal entity

Whoever signs is asserting on the company's behalf that the work supporting the statement has been done. That person does not have to have performed the testing, but they do need a defensible basis for believing it exists, which in practice means a documented handover from whoever compiled the file. Test houses and assessment bodies do not sign declarations; they issue reports and certificates that the manufacturer then relies on. Businesses where the signature migrates to whoever is available that afternoon have a governance problem rather than a paperwork one, because the signature is the point at which responsibility becomes attributable to a named individual.

What the document points at matters more than its layout

The useful content is the set of references: an unambiguous product identifier including variants, the legislation the manufacturer treats as applicable, the standards or other technical basis used, and where a third-party body was involved, that body and the certificate it issued. Everything on the page is a pointer into evidence held elsewhere. A declaration listing standards nobody actually tested against, or citing an instrument the product does not fall under, is worse than none, because it documents a misunderstanding in the manufacturer's own words and hands it to anyone investigating.

It expires quietly, without any expiry date printed on it

Standards get superseded, legislation gets amended and consolidated, product variants get added, registered addresses change and third-party certificates run out. None of that triggers an alert. A declaration issued some time ago can therefore be internally consistent and still misdescribe the product now being shipped. Practical control comes from tying declaration review to two triggers already running in the business: engineering change control, and whoever watches for revisions to the standards being relied on. Where neither exists, the declaration is a snapshot of a position the business has probably drifted away from.

The copies in circulation stop being under your control

These documents travel as attachments, get re-sent by distributors and occasionally get edited by people who need one to say something else. Buyers should therefore treat a supplied declaration as a claim to be verified against the actual goods, checking that model identifiers match, that referenced certificates exist and remain in force, and that the issuing entity is the one supplying. The form and required content vary between jurisdictions and product families and change over time; treat this description as background rather than as legal guidance, and rely on the relevant authority's published position when the answer needs to hold up.

Frequently asked questions

Is a test report the same thing as a declaration?

No, and confusing them is common. A test report records what a laboratory measured on a sample under stated conditions; it is evidence. The declaration is the manufacturer's own statement that the product meets the objectives of the legislation it falls under, which usually rests on test reports plus risk assessment, design records and production controls. A laboratory cannot make that statement for you because it has not seen your design reasoning or your manufacturing arrangements.

A supplier sent us a declaration signed by their test laboratory. Is that acceptable?

It suggests the supplier has misunderstood the document. The declaration belongs to the party placing goods on the market, and a laboratory signing on their behalf is not the arrangement these regimes contemplate. Go back and ask for one issued and signed by the supplying business itself, naming the products you buy. If they cannot produce that, you have learned something useful about how well they understand their own obligations before you commit further volume.

How long should we keep declarations, and who can ask to see one?

Retention expectations differ by regime and product type, and are generally tied to the period after the last unit was placed on the market rather than to the issue date. Enforcement authorities can normally request one, and customers ask routinely as a condition of supply. Because the periods vary, set your retention policy against the longest applicable to anything you sell, and store the declaration together with the evidence it points at rather than in a separate folder.