Design outputs are the tangible specifications, documents, and criteria that translate design inputs into actionable manufacturing and quality requirements. In medical device development, design outputs serve as the critical bridge between user needs and physical product reality. Under FDA 21 CFR Part 820 and ISO 13485, design outputs must be documented, reviewed, and traceable to their corresponding design inputs. Failure to establish clear design outputs—or worse, losing traceability between inputs and outputs—is one of the most common findings during regulatory inspections.

What Are Design Outputs in Medical Device Development?

Design outputs are the measurable, documented results of the design process. They answer the question: "What exactly will we build, and how will we build it?" Design outputs include device specifications, component datasheets, manufacturing procedures, process parameters, inspection criteria, and labeling requirements. Each design output must be linked to one or more design inputs and must be verified before manufacturing begins. Design outputs are not the finished device itself—they are the detailed blueprints and procedures that enable manufacturing teams to produce the device consistently and safely.

The distinction between design inputs and outputs is subtle but critical. Design inputs represent what the device must do and what constraints it must meet. Design outputs represent how those requirements will be achieved. A design input might state: "The device shall deliver a dose of 10 mg ± 2 mg." The corresponding design outputs would include pump specifications, calibration procedures, material selections, and acceptance criteria to verify that the pump delivers the correct dose.

Design Outputs vs. Design Inputs: The Critical Distinction

Design inputs describe requirements; design outputs describe solutions. Design inputs originate from user needs, regulatory requirements, risk management, and business constraints. They are typically written before detailed engineering begins. Design outputs are created during the engineering phase and document how the design team solved the problems outlined in the inputs. A single design input can drive multiple design outputs, and a single design output can address multiple design inputs.

Consider a cardiology device example. A design input might specify: "The electrodes shall maintain contact with skin for at least 8 hours without loss of signal." This requirement generates several design outputs: electrode adhesive formulation specifications, adhesive thickness and surface area requirements, material compatibility testing results, skin irritation acceptance criteria, and adhesive shelf-life validation data. The relationship between each input and output must be documented and traceable.

What Must Design Outputs Include?

Device and Component Specifications

Device specifications define the physical and functional characteristics of the finished device and its critical components. These specifications include dimensions, material properties, biocompatibility data, mechanical strength, electrical performance, sterility assurance levels, and shelf-life. Each specification must include a measurement method, acceptable range, and the link to the design input that drove the requirement. Component specifications pull from supplier datasheets and internal testing but must be tailored to your specific application.

Manufacturing Instructions and Process Specifications

Manufacturing instructions translate device specifications into step-by-step procedures that production teams follow. These documents specify the sequence of assembly, the tools and equipment required, environmental conditions, handling procedures, and in-process inspection points. Process specifications for key manufacturing steps—such as welding, sterilization, coating, or molding—must include parameter ranges that have been validated to produce devices meeting the output specifications.

Acceptance Criteria

Acceptance criteria define the pass/fail boundaries for verifying that design outputs are met. Acceptance criteria must be objective, measurable, and reproducible. They are applied during verification testing (does the design meet the output?) and during manufacturing quality control (does the device meet specification?). Common acceptance criteria include dimensional tolerances, performance thresholds, appearance standards, and material test results. Vague criteria like "acceptable appearance" or "adequate performance" create regulatory risk and manufacturing inconsistency.

Labeling and Identification Requirements

Design outputs must specify all labeling and identification requirements, including instructions for use (IFU), warning labels, symbols, lot/batch codes, expiration dates, and sterilization indicators. Design outputs for labeling include the content, format, font size, location, and materials used for labels. Many regulatory submissions require samples of actual labels. Design outputs must also specify how labeling information is verified before devices are released for distribution.

Design Output Requirements Under ISO 13485 and 21 CFR Part 820

FDA 21 CFR Part 820.30(d) requires design outputs to be documented, reviewed, and approved before release to manufacturing. ISO 13485 Section 7.3.4 mirrors these requirements: design outputs must be recorded, reviewed, and approved. Both standards require that design outputs be reviewed against design inputs to ensure they address all requirements. Design outputs must be approved by qualified personnel before proceeding to design verification.

The regulations do not prescribe a specific format or level of detail for design outputs. However, regulatory inspectors and notified bodies expect design outputs to be complete enough that a qualified engineer unfamiliar with the project could manufacture the device and verify compliance with specifications. Documentation must be retained in the design history file (DHF) and must remain accessible for the life of the device plus any required retention periods.

Establishing Traceability Between Design Inputs and Outputs

Traceability is the ability to demonstrate how each design input flows through design outputs and into verification activities, risk controls, and manufacturing procedures. A traceability matrix maps each design input to its corresponding design outputs. This matrix must show that no inputs have been overlooked and that each output traces back to at least one input. Traceability also confirms that design changes are properly cascaded throughout downstream documents.

Electronic traceability tools are essential for managing complex devices with hundreds of inputs and outputs. Manual spreadsheets become unwieldy and error-prone. A requirements management tool with built-in traceability tracking allows teams to create, link, version, and audit all requirements and specifications in one place. Traceability reports can be generated to verify completeness and to demonstrate compliance during audits and regulatory submissions.

Common Gaps in Design Output Documentation

• Missing traceability: Design outputs exist but are not linked to design inputs. Regulators cannot verify that all requirements have been addressed.

• Incomplete specifications: Device or component specifications lack acceptance criteria, measurement methods, or rationale. Manufacturing teams cannot verify compliance objectively.

• Vague acceptance criteria: Criteria use subjective language like 'acceptable' or 'suitable' rather than measurable limits. This creates inconsistent quality and makes verification difficult.

• Failure to capture design changes: Design outputs are not updated when design inputs change. Downstream documents (DHR, DMR, IFU) become disconnected from the original design rationale.

• Missing design output review records: Design outputs are documented but review and approval records are incomplete or missing. Regulators question whether outputs were actually reviewed.

• Inadequate design output for software and risk controls: Software specifications and risk control implementation details are incomplete or buried in scattered technical notes rather than formally documented.

Design Outputs and Downstream Documents: V&V, DMR, DHF

Design outputs drive verification and validation (V&V) planning and execution. Each design output must have a corresponding verification activity that confirms the output was met. Verification activities include testing, inspection, analysis, or demonstration. V&V test protocols must reference the design output specifications and acceptance criteria. Test reports must document whether each output was verified and the results of that verification.

Design outputs also populate the Device Master Record (DMR). The DMR is the permanent record of manufacturing specifications, inspection procedures, and acceptance criteria. The DMR pulls directly from design outputs, ensuring that manufacturing consistently produces devices to the specifications that were verified during the design phase. When design outputs change, the DMR must be updated, and change control procedures must be followed to determine if existing devices are affected.

All design output documentation must be retained in the Design History File (DHF). The DHF is the complete technical record of the design process and includes design inputs, design outputs, V&V results, design reviews, traceability matrices, and design change records. FDA inspectors and notified bodies review the DHF to assess the quality and completeness of the design process. A well-organized DHF with clear design outputs and traceability is a regulatory asset.

💡  Matrix Req streamlines design output management by centralizing specifications, design inputs, and traceability in a unified requirements repository. Automatic traceability tracking identifies gaps or missing links. Built-in compliance checking ensures design outputs align with ISO 13485 and FDA requirements. When design outputs change, downstream impact analysis shows which V&V activities, risk controls, and manufacturing procedures must be updated—eliminating the risk of disconnected documentation.