Updating a technical file when the product moves on and the old file does not

Products move on, and files must move with them. A ceramic mug that gains a new glaze is, for file purposes, a partly new product: its surface, its behaviour with hot drinks, and its risk profile may all change, even when its shape and handle stay the same. A file that still describes the old glaze will mislead anyone who reads it, including the pottery owner who signed it.

Updating should start with a change log entry, dated, stating what changed, why it changed, and who approved it. That entry becomes the anchor for all other updates, because every document that mentions glaze, finish, or hot drink behaviour can then be checked against the same change, rather than being updated in isolation.

Crazing after hot drinks is a key behaviour to re-examine. A new glaze may craze, which is the formation of fine cracks in the glaze surface, after repeated exposure to hot drinks, while the old glaze did not. The updated file should describe how the new glaze was tested with hot drinks, what was observed, and what judgement follows, such as a care instruction, a glaze adjustment, or a decision to revert.

Other documents may also be affected. A supplier note for the old glaze no longer describes the mug, a test note for the old glaze no longer supports the new mug, and a listing that describes the old glaze's appearance may need updating. The change log should list every affected document, so none is forgotten.

Illustration: a pottery brand updates 40 mug files after a glaze change and imagines that 20 of them, in round illustration terms, still contain a reference to the old glaze in a forgotten corner, such as a photograph caption or a supplier note. Those figures, as presented in Updating a technical file when the product moves on and the old file does not, are invented, not measured. They show why updating must be systematic: a single missed reference can mislead a reader who finds it and assumes it describes the current mug.

A systematic update uses a search, not memory, to find every mention of glaze, finish, or colour in the file, and updates each one, or marks it as historical. That search takes time, but it prevents the old glaze from haunting the new file.

Old records should be kept, marked as superseded, rather than deleted or overwritten. A reader who needs to understand a complaint about an old mug, or to trace why a glaze was changed, needs the old record intact, with its date and its context. Deleting it erases history and makes future learning impossible.

• Log the glaze change with date, reason, and approver.
• List every document mentioning glaze, finish, or hot drink behaviour.
• Test the new glaze with hot drinks and record crazing observations.
• Keep old glaze records marked as superseded, not deleted.

Files often go stale through small changes that never trigger an update. A glaze tweak, a clay supplier change, or a firing temperature adjustment may each seem too small to warrant a file update, yet together they can transform a mug. The remedy is a rule: any change to materials, process, or finish triggers a file review, however small the change seems at the time.

Another staleness cause is to update the product and the listing, but not the file, because the file feels like paperwork rather than part of the product. In fact, the file is the product's record, and a product without a current record cannot be explained, defended, or improved on the basis of evidence.

Close by telling the people who sell, pack, and answer questions about the mug what changed, in plain words, so listings, care instructions, and customer answers reflect the new glaze, not the old one.

Review the updated file as a whole, reading it as if it were a new file for a new mug. If it reads coherently, with no old glaze references left unexplained, the update is complete. If it does not, the remaining references are the next edits.