File 07: Technical documentation
The technical file as the product safety record: what goes in it, how it is kept current, and what an authority asks for first.
The file guide
Working guides in this file
07A lean technical file for a genuinely simple product A coaster set needs only a short technical file, but that file must still describe the wood, the finish, the size, and what happens after repeated washing, because simplicity does not remove the need for evidence. 07A pre launch check of a technical file that catches gaps while they are cheap to fix A pre launch check for a muffin tray file should open every document, compare it with the tray being sold, and record gaps, because a gap found before launch costs a note, while a gap found after launch costs a recall of listings and stock. 07Assembling a technical file when the product arrives from another maker An imported kettle file must be built from the maker's documents, the importer's own checks, and a clear record of what is missing, because a shipment arriving without papers does not arrive with a file. 07Documenting variants so a colour or size change does not hide a real difference Documenting lamp variants means building a table that shows, for each size, what is the same, what differs, and what was tested separately, so a larger lamp running hotter is not hidden behind a smaller lamp's result. 07Drawings, specifications and bills of materials that a reader can trust A coat rack file earns trust when its drawings match the finished rack, its specifications name the wood and fixings actually used, and its bill of materials lists every part that holds a coat. 07How a technical file supports a declaration, without the declaration doing the work alone A declaration for a night light is only as strong as the file behind it: descriptions, risk reasoning, and test notes that support each statement in the declaration, filed where they can be found. 07How long to keep a technical file, and how to decide in general terms Keeping a raincoat file for the right period means keeping it while the coat is sold and for a sensible period after, based on how long coats last, when complaints may arrive, and what a reader may need to check later. 07Keeping a technical file coherent when a product has many parts and functions A kitchen slicer file must stay coherent across blades, guards, handles, and attachments, so a reader can find each part's description, risk, and test note without hunting through separate departmental folders. 07Keeping a technical file digitally in a form you can actually find and share Keeping apron files digitally works only when files are named clearly, indexed in one place, backed up, and shared in a form that a reader can open without special software or a password hunt. 07The contents of a technical file, and why each part earns its place A technical file for a fabric tote should hold its description, materials, stitching details, risk reasoning, and test notes, each earning its place by helping a reader understand or check the tote. 07Updating a technical file when the product moves on and the old file does not Updating a mug file after a glaze change means recording the new glaze, its crazing behaviour after hot drinks, and the revised risk judgement, with the old glaze record kept visible beside it. 07Version control for a technical file so nobody works from an old draft Version control for a stool file means numbering every version, logging every change, and keeping one current version that everyone can find, so a hinge fix is not lost in an old draft. 07What an authority tends to ask for first, and how to answer without panic When an authority asks about a wax melt set, it usually asks first for identification, description, and the core safety file, in a clear order, and a calm, indexed answer helps far more than sending everything at once. 07Which supplier documents belong in a technical file, and how to check them Supplier papers for a leather wallet belong in the file only when they describe this wallet's leather, stitching, and hardware, and when their scope, date, and supplier match the wallet being sold.