MedTech Terms
    The authoritative reference
    All terms
    Quality & RiskQuality System

    Design Controls

    Structured process governing the design of medical devices.

    Reviewed by Christian Espinosa, Founder, Blue Goat CyberLast reviewed May 5, 2026

    Definition

    Design controls (21 CFR 820.30) are an interrelated set of practices and procedures that are incorporated into the design and development process to manage design inputs, outputs, verification, validation, transfer, and changes.
    What the regulation says
    Design controls, as mandated by FDA 21 CFR 820.30, are a foundational element of the Quality System Regulation, ensuring that MedTech devices are designed and developed in a manner that addresses user needs and intended uses. Similarly, ISO 13485:2016, a globally recognized standard for medical device quality management systems, outlines requirements for design and development planning, inputs, outputs, review, verification, validation, transfer, and changes. The EU Medical Device Regulation (EU MDR) also implicitly requires a robust design control process by stipulating general safety and performance requirements that necessitate thorough design and development documentation and evidence.

    What this means in practice

    Design controls are required for almost all Class II and Class III devices and for select Class I devices listed in 21 CFR 820.30(a)(2). They form the audit trail (design history file) used by FDA, Notified Bodies, and internal auditors to evaluate design quality. Under QMSR (effective February 2026), design controls are preserved and aligned with ISO 13485 clause 7.3. The typical elements are: design and development planning, design inputs, design outputs, design review, verification, validation, transfer, and changes, with a design history file (DHF) collecting the evidence.

    Examples

    • A Class III implantable device team maintaining a phase-gated DHF with formal design reviews at each stage and an approved traceability matrix linking user needs to validation protocols.
    • A SaMD manufacturer using an electronic QMS to link software requirements (inputs) to code modules (outputs), unit tests (verification), and clinical usability studies (validation).
    Common pitfalls
    • •Treating verification and validation as interchangeable. Verification confirms outputs meet inputs; validation confirms the device meets user needs in its intended environment.
    • •Weak design inputs. Vague or unmeasurable inputs make verification impossible and are one of the most common Form 483 observations.
    • •Skipping formal design reviews or performing them without an independent reviewer, which invalidates the review evidence under 820.30(e).
    • •Poor design change control. Every post-transfer change requires evaluation, verification/validation as appropriate, and documentation before implementation.

    Frequently asked questions

    Only for the Class I devices listed in 21 CFR 820.30(a)(2) - primarily devices automated with computer software and a short specific list including tracheobronchial suction catheters and surgeon's gloves. All other Class I devices are exempt from design controls but remain subject to the rest of the QMS.

    Cross-references

    Part of

    A larger framework or document this term belongs to.

    Contains

    Sub-elements or required artefacts of this term.

    Precedes

    Comes before in a typical workflow or lifecycle.

    Grouped by theme

    Primary references

    3 sources
    Link health: 1 verified 2 unchecked· last checked 2026-06-20
    eCFR·1FDA·1ISO·1
    1. 1
      21 CFR 820.30 Design Controls
      Unchecked
      eCFRecfr.gov
    2. 2
      FDA Design Control Guidance for Medical Device Manufacturers
      Unchecked
      FDAfda.gov
    3. 3
      ISO 13485 Standard Page
      Verified
      ISOiso.org

    Inline markers like [1] jump to the matching reference above.