Technical documentation: assembling evidence nobody may ask for until years later

The file is an argument, not a folder of certificates

A collection of test reports proves that certain measurements were taken. It does not explain which hazards were identified, why particular standards were selected, how residual risks were handled, or what links the tested sample to the units in the warehouse. Files that read as arguments start from the product description and its intended use, work through the hazard analysis, show how each identified issue was addressed in design or in information for users, and only then present supporting reports. Assessors and enforcement officers read for that thread. When it is missing, they start asking questions across the whole product rather than about one measurement.

Design evidence and production evidence answer different challenges

One half of the file explains why the design is capable of meeting the objectives: calculations, analyses, drawings, materials data, test results on representative samples. The other half explains why the units actually shipped behave like the sample: process controls, inspection arrangements, component specifications, supplier controls and change records. Manufacturers routinely build the first half well and neglect the second, which leaves them unable to answer the most damaging question anyone can ask, namely how you know the item on the shelf resembles the one that passed testing. Batch records and change history do most of that work.

Ownership gets awkward when someone else does the making

Where a contract manufacturer or an original design manufacturer holds the drawings, process detail and test data, the brand owner can find itself responsible for producing documentation it has never seen. Supplier agreements written for price and lead time rarely address this. Terms worth negotiating before volume commitments include a right of access to specified documentation, an obligation to notify design and process changes, agreement on what happens to records if the relationship ends, and clarity on which party responds to an enforcement request. Discovering the gap during an investigation leaves no negotiating position at all.

Retrievable means retrievable by someone still employed

Regimes generally expect documentation to remain available for a defined period after supply ends, and that period commonly outlasts staff tenure, file formats and the software that produced them. Native CAD files nobody can open, shared drives migrated twice, test reports held only in a departed engineer's mailbox and supplier data behind a portal login that expired are all ordinary failures. Keeping a rendered, self-contained copy of everything the argument depends on, indexed against the product and revision, costs very little at the time and is the difference between a prompt response and an admission that the evidence cannot be located.

A file that is not maintained becomes evidence against you

Every product change, standard revision or legislative amendment potentially touches part of the reasoning. Left alone, the documentation gradually describes something the company no longer makes, and an assessor comparing the file to a current sample sees the divergence immediately. Tie file review to the change process and to whoever tracks standards, and record the review even when nothing needed altering. What has to be inside the file, and how long it must be held, varies by jurisdiction and product family and is set by the relevant legislation, not by an article like this one, so verify the position with the responsible authority or a qualified adviser.

Frequently asked questions

Do we have to hand the technical file to a customer who asks for it?

Generally the obligation runs toward authorities rather than toward commercial counterparties, so a customer request is a contractual matter you can negotiate. Many manufacturers supply a summary, the declaration and selected test reports while keeping design detail confidential, sometimes offering review under a non-disclosure arrangement or by a nominated third party. Refusing outright tends to cost the order, so agree the position before a tender rather than improvising when a procurement questionnaire arrives.

Our overseas design manufacturer will not share the documentation. What are our options?

Treat it as a commercial problem with a compliance consequence. Options include paying for a documentation package as a defined deliverable, arranging escrow or third-party custody, commissioning your own assessment and testing to build a parallel file, or accepting that you cannot sell the product under your own name. Which is viable depends on volume and leverage. The one option that does not work is marking the goods and hoping the request never arrives.

How is the technical file different from our quality management system records?

They overlap but answer different questions. Quality system records show that the organisation operates controlled processes: audits, training, calibration, corrective actions. The technical file is product-specific and explains why this article satisfies the objectives that apply to it. A certified management system is evidence that the file was produced under discipline, not a substitute for the file itself, and assessors ask for both because each covers a gap in the other.