Product Safety Triage: Which Regulator or Standard Applies?

Describe what the product is intended to do, for whom, in which environment, and how it will be marketed. Claims can change the regulatory path. A wellness-looking object may become a medical-device question if its intended use includes diagnosis, treatment, or prevention. A general household product may trigger additional requirements when intended for children, used around food, powered by a battery, connected by radio, or designed to support a load.

Write the exact proposed claims and prohibited claims. Separate what the concept might technically do from what the business intends to promise. Include packaging, website, instructions, sales scripts, and app text in the review scope. The FDA explains that medical device classification depends on intended use and indications for use; changing language after the design is complete does not erase the design implications.

Record category, age range, vulnerable users, foreseeable bystanders, professional or consumer setting, indoor or outdoor use, normal and foreseeable misuse, markets, sales channel, and who imports or manufactures. Then list mechanical, electrical, thermal, chemical, biological, software, privacy, ergonomic, and lifecycle characteristics. A small change in user or market can change testing, labeling, documentation, and responsible parties.

For U.S. consumer products, use the CPSC Regulatory Robot and Business Education Library as starting points. The CPSC explicitly frames the robot as basic guidance and notes that unique products may need different requirements. Save the generated or researched guidance with the concept revision and date. Do not display a passed screening question as CPSC approval.

List energy and exposure sources: moving parts, sharp edges, pinch points, stored force, heat, electricity, batteries, radiation, pressure, chemicals, allergens, small parts, cords, data, and software-controlled actions. Describe the sequence from hazard to situation to harm. Include assembly, cleaning, charging, maintenance, transport, storage, failure, repair, resale, and disposal—not only ideal operation.

For each hazard, identify an inherently safer design option, protective measure, information or training, evidence needed, owner, and residual risk. Warnings are important but should not be the first or only control when design can reasonably eliminate or reduce the hazard. Use recall databases to learn how similar categories fail, while remembering that absence of a recall does not prove safety.

Create an applicability matrix, not a logo collection. Columns should include authority or standards body, jurisdiction, product characteristic, trigger question, source, current interpretation, required specialist, evidence artifact, design effect, owner, and status. Consumer-product, medical-device, workplace, radio, environmental, transport, accessibility, privacy, and local requirements may overlap.

Standards can define test methods, construction, performance, markings, or processes, but access and applicability vary. UL Standards & Engagement provides standards information; the correct standard and edition still require review. Distinguish voluntary consensus standards, regulations, certification-program rules, customer requirements, and internal targets. Do not call them interchangeable.

Turn each pathway into design inputs and evidence: material declarations, drawings, risk analysis, software records, supplier controls, labels, instructions, test plans, representative samples, laboratory reports, traceability, quality records, or post-market processes. A test report applies to a named sample and configuration; design or supplier changes can invalidate its relevance.

Plan evidence before prototypes. If a battery compartment, guard, interlock, material, or user interface affects a requirement, include it in the relevant prototype and change control. For medical-device questions, FDA design controls illustrate the importance of controlled requirements, plans, responsibilities, verification, and validation. Do not import that label casually, but learn from the evidence discipline.

Define when work must stop for specialist input: uncertain intended use, children or vulnerable users, health claims, electrical or battery hazards, load-bearing or pressure functions, food or body contact, wireless certification, significant cybersecurity consequences, unresolved severe harm, conflicting standards, or a market commitment dependent on approval. Put gates before detailed engineering, supplier nomination, tooling, inventory, and public claims.

The output is a triage brief: known facts, sources, likely pathways, unresolved questions, risk controls, evidence plan, owners, and prohibited claims. Label it preliminary. Update it when the product, user, market, material, supplier, firmware, or claim changes. A readiness score can remind the team that a review is missing; it cannot perform or approve that review.

Product and revision; intended use; excluded use; users and bystanders; markets; channels and responsible parties; proposed and prohibited claims; energy and material sources; top hazards; foreseeable misuse; likely authorities; likely standards; current official sources and access dates; evidence needed; qualified reviewers; design implications; unresolved questions; escalation gates; owners; and next review date.

Use ConjureAnything to explore the concept and populate questions, then replace generated answers with official sources and qualified input. Keep the triage attached to the evidence pack so an engineer, test lab, regulatory specialist, supplier, and marketer work from the same declared scope. Safety is not a late checklist; it is a design constraint with a living evidence trail.