Keeping mains powered, battery powered and connected products safe from design to disposal

A desk lamp, a robot vacuum and a video doorbell look nothing alike, yet each one moves energy through a home in a way a person can touch, trip over or misunderstand. The lamp concentrates heat in a small shade, the vacuum stores energy in a pack that charges while nobody watches, and the doorbell keeps a radio link alive through rain, frost and a drained battery. Safety work starts by walking through those ordinary moments, not by opening a rule book and ticking boxes in the abstract.

Illustration: a maker of plug-in air purifiers tested 70 units in living rooms, bedrooms and kitchens, checking heat, cable strain and filter access after a month of daily use. Two units showed a cable entry that loosened when the purifier was moved for cleaning, so the maker strengthened that entry and added a move by the body, not the cable, picture to the instructions. The unit count is illustrative, and the lesson is to test a connected electrical product where it is moved and cleaned, not only where it is first plugged in.

Shock, heat and fire are often treated as separate chapters, but in a small appliance they share the same roots: thin insulation, a cramped enclosure, a motor that stalls, or a battery that keeps accepting charge after it should have stopped. When insulation wears, current finds a path it was never meant to take. When ventilation is blocked by dust or a curtain, heat builds until plastic softens. Either route can end with a burn, a shock or a fire, which is why the checks belong together in one pass over the product.

A connected product is never finished on the day it ships, because its behaviour can shift with an app update, a server change or a new phone operating system. A smart plug that once switched off after a set time might, after an update, stay on through the night. A door lock might accept a new way of unlocking that its first buyers never agreed to. Those are safety changes even when they arrive dressed as convenience, and they deserve the same review as a change to a mains cable.

That review should ask three plain questions before any update ships: what can this change switch on, switch off or keep running longer, who will notice if it goes wrong, and how does a user get back to a safe state without technical help. If the answers are vague, the update waits. A short note in the file, dated and signed by whoever approved the change, turns that pause into evidence instead of a forgotten argument.

The maker of the product shapes the design, chooses materials and components, writes the instructions and holds the technical record. A business bringing that product into the EU checks the shipment against the record, keeps its own supplier details and contact route, and makes sure the product can be traced if something goes wrong. A shop or marketplace seller checks the listing, the markings and the packaging, and passes warnings and complaints up the chain instead of quietly editing them away.

A convincing file reads like a short story of the product: what it is, who will use it, what could go wrong, what was tested, what was changed and what is still being watched. Photographs of the product as sold, copies of the instructions in the languages supplied, test summaries with the lab and the sample identified, and a log of complaints and updates all belong there. A file that only contains certificates, with no reasoning linking them to this product, invites the obvious question and has no answer ready.

Keep the file organised so a stranger can follow it in an afternoon. Use one folder per product family, one dated note per decision, and a short index at the front. When a question arrives from a customer, a retailer or an authority, the team should be able to open the index, find the relevant note and reply from the record rather than from memory. That speed is not bureaucracy for its own sake; it is what lets a small team act before a scattered problem becomes a pattern.

Pick one product you already sell and spend an hour with it in the place it is normally used. Plug it in with the charger a customer is most likely to substitute, run it blocked, dusty or half covered in the way a busy household might, and read the instructions as if you had never seen the product before. Write down every moment where you felt unsure, warm, confused or tempted to force a part. Those notes are the start of a real risk list.