Guide

Plan the test before the build

Decide what the next build must prove, how you will check it, and what result is acceptable before making or testing it. Start small, then add the detail the product and decision require.

Revision 1

Download the test-plan template · Download the test matrix · Download the report template

Complete guide for assistants. Save filled copies in your project; this reference page does not store answers.

Keep going: risk reviews lead to action

Keep going (the procedures call it Advance Now) means take a useful step today. Treat risk analysis as a source of questions, opportunities and routes through the problem. Ordinary uncertainty, imperfect ergonomics, limited funds, unanswered checklist items or a long list of possible failures do not automatically stop the project. Preserve momentum. Help the inventor find the next useful action, carry it out with the tools and authority available, and keep the concern visible.

Keep a short list of unresolved concerns, possible routes, questions for the right person and work that advances now. Reuse existing risk and issue IDs. Hold only an affected activity when a concrete limit applies; continue other useful work. Carry the questions into supplier, professional and customer conversations.

Read the shared principle · Instructions for assistants · Roadblock and opportunity list

Start while the requirements are taking shape

Your Project Manager Bot coordinates the plan with the engineering role and the prototype role as soon as important requirements and failure risks emerge. Do not wait for finished hardware. Early planning can change the enclosure, connectors, materials, power supply, mounting, test access and number of samples that need to be made.

Identify the intended users, environment, target countries, product category, customer requirements and proposed claims. Link each important requirement and risk to an inspection, analysis, demonstration or test. Leave unresolved limits marked unknown, with an owner and action; never fill them with a plausible-looking number.

Use the design-risk review, critical-quality sheet and control plan already in the project. A development test investigates the design; a production control plan describes repeat checks during manufacture. Link them without assuming they serve the same purpose.

Read more: NASA — Requirements verification matrix · NASA — Product realization, verification and validation · NASA — Product verification planning

Choose the sample for the question

A prototype can be exactly the right test article. Its suitability depends on what you want to learn and how faithfully it represents the features being tested. A pass only supports the configuration, conditions and question covered by the evidence.

Read more: NASA — Product realization, verification and validation · ISTA — Getting started with design and testing

Lay out a test plan someone else can follow

Use the downloadable plan template as a working document and the test matrix as its index. A matrix names the tests; the plan and referenced procedures explain how to execute them. Keep proposed settings and criteria separate from approved values and actual results.

Read more: NASA — Requirements verification matrix · NASA — Product realization, verification and validation · NIST — Laboratory accreditation versus certification · NASA — Verification and validation plan outline

Electrical safety, EMC and radio: separate questions

Electrical safety addresses hazards such as shock, fire, heat and stored energy. EMC emissions concern unwanted electromagnetic disturbance; immunity concerns how the product behaves when disturbed. Intentional-radio requirements and RF exposure introduce additional questions. A pass in one area is not a pass in the others.

The engineering role records the product category, markets, power/charging arrangements, radio functions, installation and use, then asks a competent laboratory to confirm applicable requirements, editions and authorization/certification routes. Do not choose an electrical-safety standard or a radio rule just because its name is familiar.

Read more: OSHA — Nationally Recognized Testing Laboratories · eCFR — 47 CFR 15.31 measurement standards · eCFR — 47 CFR 15.212 modular transmitters · IEC 61000-4-2:2025 — ESD immunity test method · Tektronix — EMI precompliance during development · TÜV SÜD — EMC test planning and laboratory preparation

Drop testing: the product or the shipping package?

First choose the question: will a bare handheld product survive an accidental fall, will an installed assembly tolerate handling, or will the packaged shipment survive distribution? A shipping-package test does not automatically answer the bare-product question.

Choose an applicable method with a reason. IEC rough-handling guidance and ASTM/ISTA transport-package methods address different situations. Public scope pages help select a method; obtain the authorized procedure before claiming testing to it.

Read more: IEC 60068-2-31 — Rough handling shocks · ASTM D5276 — Loaded-container free-fall drop testing · ISTA — Getting started with design and testing

Submersion, splashes and water jets

Define the real exposure and the claim first: rain, splashes, a jet, temporary accidental immersion, continuous underwater use, or another liquid. IEC 60529 provides enclosure IP classifications; it does not by itself establish every environmental or safety property.

Do not substitute “one metre for thirty minutes” for a reviewed method. The applicable clause, enclosure size/reference points, intended use and claim determine the setup. Jet and immersion requirements differ; an immersion rating alone does not establish resistance to water jets.

Read more: IEC 60529 — Enclosure protection (IP Code) · TÜV SÜD — Ingress-protection testing overview

Example: turn “it must survive a fall” into a plan

Illustrative planning example only: a handheld enclosure is being considered. No height, number of specimens or pass result has been assumed. The open fields deliberately show what the team must resolve before a meaningful test.

Review failures, changes and what the evidence supports

The prototype role preserves raw results and reports the tested configuration, method and limits. Record failed, interrupted, not-run and inconclusive tests as well as passes. A report is separate from the plan: planned work is not performed work.

The engineering role reviews anomalies, changes and their effect on requirements. Trace corrective action to a repeat test and any necessary regression tests. A change in material, supplier/process, enclosure, PCB, firmware, antenna, cable, seal, packaging or intended use may affect prior evidence. Decide and record the retest scope; do not assume either that everything remains covered or that every test must be repeated.

Your Project Manager Bot links the plan and reports to the quality records and next project decision. Your Project Manager Bot carries validated manufacturing/inspection needs into the control plan; the marketing role uses only claims supported by the actual scope of evidence. A laboratory report, accreditation or checked form alone is not approval for every market or product variant.

Read more: NIST — Laboratory accreditation versus certification

Sources and access

Original A.N. Creation planning guidance, using public primary references. Catalog abstracts identify scope; they are not full test procedures. No paid standard was purchased or reproduced. Confirm the relevant edition, licensed access, test method and product/market requirements before formal work.

Design risks and quality planning · IP enclosure ratings · Prototype check sheet · Resources

How a check of the work is set up for a bot is in the hotbotspot tool library.

Everything here is a starting point. Work with artificial intelligence always needs tuning, so test it and dial it in for your own work, data and model before you rely on it.