What are the stages of medical device prototyping?

Medical device prototyping typically moves through proof-of-concept (testing whether the underlying principle works), alpha prototype (early functional builds), bench prototype (performance testing against preliminary specifications using production-intent materials where possible), and works-like/looks-like or pre-production units (testing form and function together, used for design validation including human factors). The exact naming varies by organization and device type.

When do design controls start in the prototyping process?

Under ISO 13485:2016 Clause 7.3 and the FDA's QMSR (effective February 2, 2026), design controls must be in place when design and development activities begin. In practice, most teams begin formal design controls (design plan, initial design inputs) around the alpha prototype stage. Proof-of-concept work may predate formal design controls, but any POC data later used in a submission must be documented and traceable.

What is a works-like/looks-like prototype?

A works-like/looks-like prototype is a device model that simultaneously demonstrates correct functional performance (works-like) and the intended physical form that a user would interact with (looks-like). It is often the prototype used for human factors validation and simulated-use testing. Pre-production or pilot-run units built on actual production tooling are the most common form of this prototype type.

Can you 3D print medical device prototypes?

Yes, 3D printing is widely used in medical device prototyping for housings, mechanical components, and anatomical models. However, 3D-printed materials are almost always not the production-intent material. Test records generated using 3D-printed prototypes should document the material used, and those tests cannot substitute for verification or validation testing on production-equivalent devices unless the 3D-printed material is specifically qualified for production use.

How many prototype iterations are typical?

There is no standard number. Simple devices may reach works-like/looks-like in a handful of iterations; complex combination products or novel technologies may run dozens of iterations across years. The relevant design controls requirement is that each significant iteration is documented and that design reviews are conducted at planned stages. The number of iterations is a function of the design challenge, not a compliance variable.

What is the difference between design verification and design validation in prototyping?

Verification (ISO 13485:2016 Clause 7.3.6) tests whether the device you built meets the specifications you defined (design outputs vs. design inputs). It is typically done on bench prototypes or pre-production units under controlled conditions. Validation (Clause 7.3.7) tests whether the device as manufactured actually works for the intended user under intended use conditions. Validation must be performed on production-equivalent units. Both generate records that go into the Design History File.

What materials should I use for a bench prototype?

Where possible, bench prototypes should use production-intent materials, because performance and biocompatibility data generated using substitute materials may not be transferable to the production device. In practice, some prototype stages necessarily use substitute materials due to cost or lead time. The key is to document which materials were used, note where they differ from production intent, and plan the test program so that production-equivalent data is generated before design freeze.

Medical Device Prototyping: Stages, Methods, and How It Connects to Design Controls

Direct answer: Medical device prototyping typically progresses through four stages: proof-of-concept (testing core feasibility), alpha (early functional builds), bench prototype (performance testing against preliminary specifications), and works-like/looks-like models (final form and function before design freeze). Each stage generates evidence that informs or satisfies design inputs and outputs under ISO 13485:2016 Clause 7.3. Disciplined prototyping and design controls are not in conflict; the best teams run them together from the start. (As of July 2026.)

Prototyping sits at the intersection of engineering speed and regulatory discipline. Teams that rush past it tend to encounter their hardest problems after design freeze, when changes are expensive. Teams that prototype without a design controls framework often find their evidence is unstructured when it is time to write a Design History File (DHF) or submit a 510(k).

The good news: when prototyping is connected to design controls from the start, the two reinforce each other. Each prototype stage answers a question. Each question maps to a design input. Each answer becomes part of the DHF.

Why Prototyping Matters in Medical Device Development

FDA's design controls framework, now enforced through ISO 13485:2016 Clause 7.3 under the QMSR (effective February 2, 2026), does not prescribe a specific prototyping process. It requires that manufacturers establish a systematic design and development process with planned stages, reviews at each stage, and records showing that inputs were met by outputs. Prototyping is the practical mechanism through which most of that work happens.

Prototype data also feeds directly into submissions. A 510(k) requires performance data demonstrating substantial equivalence to a predicate device. A De Novo request requires a risk-benefit analysis supported by test data. PMA applications require clinical evidence, which for many devices is preceded by bench testing and, where scientifically justified, animal (preclinical in vivo) testing during the prototype phases. The earlier your prototypes generate submission-quality data, the smoother your regulatory pathway.

The Four Core Prototype Stages

These stages are not formal regulatory categories. They are conventional development phases used across the industry to describe the maturity of a prototype and the questions it is designed to answer.

Stage 1: Proof-of-Concept (POC)

The question it answers: Can this underlying principle work at all?

A proof-of-concept prototype is usually crude, often hand-built, and intentionally rough. The goal is not appearance or polish; it is confirming that the physics, chemistry, or biology behind the device idea behaves as expected. POC builds often use off-the-shelf materials, 3D-printed components, or bench-top setups.

Regulatory connection: POC work generally predates formal design inputs, which is fine. But any data generated at this stage that is later cited in a submission needs to be traceable to a documented protocol and controlled enough to be credible. Smart teams begin a project notebook at POC, even if formal design controls have not started.

Stage 2: Alpha Prototype

The question it answers: Can we build a functional version that begins to resemble the intended device?

Alpha prototypes are functional, though not necessarily manufacturable. They are built to test subsystem interactions, electrical or mechanical integration, software behavior, and preliminary human factors observations. Multiple alpha iterations are common. Materials may be substitutes for production-intent materials.

Regulatory connection: By alpha prototype, most teams should have formal design inputs documented under ISO 13485:2016 Clause 7.3.3. Alpha data begins building the body of evidence for design verification. Some teams use alpha phases to run preliminary bench tests that will be repeated on production-equivalent devices at the verification stage.

Stage 3: Bench Prototype (Engineering Prototype / Beta)

The question it answers: Does the device perform to its specifications under controlled test conditions?

Bench prototypes use production-intent materials and manufacturing processes to the extent possible. Performance testing begins in earnest. Biocompatibility testing is typically planned at this stage to account for final material selections, since ISO 10993 evaluations are material-specific. Sterilization method selection and packaging validation planning also begin here, since those choices affect materials.

Regulatory connection: Bench prototypes should be built to documented specifications. Test protocols and results at this stage form a significant portion of the verification record in the DHF. Any design changes driven by bench test failures must be documented under change control (ISO 13485:2016 Clause 7.3.9), even in development.

Stage 4: Works-Like / Looks-Like Models (Design Verification Prototype / Pre-Production)

The question it answers: Does the device perform correctly and does it match the intended form factor, including from a human factors perspective?

A works-like/looks-like prototype achieves two things simultaneously: it demonstrates the device's functional performance and its physical form as a user would encounter it. This is often the prototype used for human factors validation studies, where real users or simulated-use evaluations are conducted. See the Human Factors Engineering for Medical Devices piece in this series for detail on those requirements.

Pre-production prototypes (also called pilot-run units or engineering build units) are typically built using the actual manufacturing process and production tooling, though not necessarily at full production scale. FDA design validation under ISO 13485:2016 Clause 7.3.7 requires testing on production-equivalent units, making this stage directly submission-relevant.

Materials Considerations Across Prototype Stages

Material choice in prototyping has regulatory downstream effects.

Early-stage prototypes can use materials that approximate the final device, but any material used in human contact during bench or usability testing needs to be documented, because ISO 10993 biocompatibility evaluation is material-specific. Switching materials after biocompatibility testing is complete triggers re-evaluation and requires a change record.

Common material categories and their implications:

Material Type	Common Uses	Prototyping Consideration
3D-printed polymers (SLA, FDM, SLS)	Housings, mechanical components	Usually not production-intent; note in test records
Machined metals	Structural components, instruments	Can be production-intent; document alloy specifications
Medical-grade silicone	Seals, soft components, patient-contact surfaces	ISO 10993 eval needed if human contact planned
Off-the-shelf electronic components	Control systems, sensors	Confirm RoHS, component lifecycle when moving to production

The general rule: document what materials were used at each stage, and flag when materials differ from the production intent. This prevents gaps in the DHF when reviewers trace the chain from early prototype data to final specifications.

Rapid Iteration Without Losing Design Controls Discipline

Iterating quickly is a feature of good device development, not a sign of lack of rigor. The tension teams feel between speed and documentation usually comes from one of two problems: documentation that is too cumbersome to maintain in parallel with fast-moving work, or documentation that is so thin it does not actually capture what happened.

A few practices that maintain design controls discipline without slowing iteration:

Lightweight design input logs. Before starting a prototype build, write down what question this prototype is supposed to answer and what success looks like. Even a one-paragraph statement creates a traceable record.

Test-as-you-go records. Run test protocols as part of the build, not as a separate "documentation phase" afterward. Contemporaneous records are more credible and easier to assemble into a DHF.

Version control for designs. CAD files, firmware, and bill-of-materials should be under version control from early development. Knowing exactly what was built for each test avoids the common audit problem of not being able to confirm what version of the device generated a given test result.

Change documentation during development. Changes do not require a full change control process in the same way production changes do, but they should be noted. A short log of "what changed, why, and what tests were re-run" for each prototype iteration takes minutes and becomes extremely valuable during design review or submission preparation.

How Prototype Stages Map to Design History File Sections

DHF Section (ISO 13485:2016 Clause)	Prototype Stage Where Evidence Is Generated
Design plan (7.3.2)	Before POC or at POC
Design inputs (7.3.3)	Alpha through bench
Design outputs (7.3.4)	Bench through works-like/looks-like
Design review records (7.3.5)	At each stage gate
Verification records (7.3.6)	Bench and works-like/looks-like
Validation records (7.3.7)	Works-like/looks-like (production-equivalent units)
Design transfer (7.3.8)	Post works-like/looks-like, before production

How Buzzbox Media Supports Medtech Teams at Every Stage

Device teams in prototyping phases are also evaluating consultants, platforms, and service providers, and are beginning to think about market strategy. Prototyping is one step in the larger new product development process and connects directly to your Design History File and verification and validation work. Buzzbox Media works with medical device companies to build search visibility that connects them to buyers actively researching device development topics. See our medical device marketing services to learn how.