Industry standards, met.
Also called: Regulatory requirements · Compliance scope · Conformity assessment · Applicable standards
Working out which safety and conformity rules a product must meet, what each one covers, and designing to them from the start.
Standards feel intimidating, but only a handful actually apply to any one product. Name them early, learn what each covers, and design to them from day one. Bolt compliance on at the end and you redesign instead. There is a worked table below.
What meeting industry standards is
A standard is a written agreement on how something must be built or behave so it is safe and works as expected. Some carry the force of law, like the UKCA marking a mains product needs before it can be sold; others are the technical benchmark a regulator or test house will hold you to. The word frightens people. It needn’t. The honest truth is that the universe of standards is huge, but the slice that applies to one specific product is small and knowable.
The job of this activity is not to read every standard ever written. It is to identify the few that genuinely apply to your product, understand what each one is actually asking of you, and then design to meet it from the first sketch. That last part matters more than anything. A standard met early is a constraint you design around, quietly, like wall thickness or material cost. A standard discovered late is a redesign, and sometimes a relaunch.
For a mains-powered kitchen appliance sold in the UK, the relevant slice is small enough to fit on one page. Here is what it looked like for the proofing box.
Five rows, one page, and suddenly the thing that felt like a wall is just a checklist. That is the whole point of naming standards early: it converts a vague dread into a finite list of concrete things to design for.
- Design the box, then ask the test house what’s wrong.
- Discover the surface temperature fails after tooling is cut.
- Find the food-contact liner isn’t certified, post-launch.
- Treat UKCA as paperwork bolted on at the end.
- Name the four applicable rules before any tooling.
- Turn each into a design rule the team works to.
- Specify a certified food-contact surface from day one.
- Build the technical file as you go, not at the end.
The left column is how most first products go, and it is rarely fatal, just expensive and slow. The right column costs you a morning of research up front and saves you a redesign later. I would take that trade every time.
How it fits the bigger picture
Identifying standards is activity 07.10.08 in the framework, coming early in Stage 07 Engineer, because everything downstream has to obey what it finds. Once the applicable rules are named, the next move is to run FMEA (07.10.09), the failure-mode analysis, which asks how the design could fail and ties many of those failure modes straight back to the safety standards listed here.
What it can do
It turns a frightening, open-ended subject into a short, named list of requirements you can design for. Done early, it protects the budget and the timeline by keeping compliance a constraint rather than a crisis, and it tells you exactly what the test house will check.
What it can’t do
It can’t certify the product for you; that is testing and conformity assessment further down Stage 07. And it can’t replace a competent test house or a specialist where the rules are genuinely borderline. Naming the standards is the map; it is not the same as walking the route.
See the full 10-stage process →
Try it yourself
List what your product physically does: does it plug into the mains, get hot, touch food, connect to anything? Each “yes” points at a family of standards. Write down the standard, one line on what it covers, and one design rule it forces. If you can’t find the rule, that’s the question to take to a test house. Keep it to a single page; the list is almost always shorter than the dread.
Want help framing what applies to your product? Start the Free Sprint → and the GPT will help you map the obvious requirements first.
Your standards checklist
Project notes: the slice that actually applied
▸ From the notebook · optional reading
Dan in Stockport was braced for a mountain of regulation. We spent a morning turning it into four lines, and the food-contact one nearly caught us out.
3 min read · click to open
Dan had read a forum thread the night before and arrived in Stockport convinced compliance would sink a £149 product. He had a printout. It was forty pages. “Half of this is for products we are not making,” I said, and we started crossing things out.
What was left after we crossed things out
The box plugs into the mains and gets warm, so the household-appliance safety standard applied (BS EN 60335, with BS EN 61010 sitting under the control electronics). The PCB switches a heater, so EMC was in. Dough touches the ceramic, so food-contact material rules were in. And to sell it in Great Britain it needed UKCA marking with a technical file behind it. Four families. Everything else on Dan’s printout was for cordless tools, toys, or radio products. None of it touched us.
The one that nearly bit us
I almost waved the food-contact requirement through, because the ceramic felt obviously inert. Then we worked it through properly: the dough sits warm against that surface for twelve hours, which is precisely the condition material rules exist for. The Stoke-on-Trent glaze we’d shortlisted wasn’t certified food-safe at temperature. We pushed the supplier for a certified glaze before tooling was cut. Caught at the design table, it was a specification line. Caught after the Manchester PCB and the first ceramic run were committed, it would have been a recall.
What naming it early cost vs saved
- Cost. One morning, plus a couple of phone calls to a test house to confirm scope.
- Saved. A glaze swap that would have meant new tooling, and a UKCA file that built itself as we went rather than in a panic before launch.
Dan’s forty-page dread became a one-page list he could actually act on. That is almost always how it goes once you stop reading the standards meant for other people’s products.
— Engineer stage, project notes, 2026
— Next in Engineer → Run FMEA