Maps to
QMSR / ISO 13485: §820.30(b)
ISO 13485: §7.3.2
Requirement text
The organization shall document design and development planning. As development progresses, planning shall be documented and updated as appropriate.
What changed
Under old Part 820, section 820.30(b) required manufacturers to establish and maintain a design and development plan that described or referenced the design and development activities and identified responsibility for implementation. The regulation was relatively brief, leaving significant discretion to the manufacturer on how to structure planning documentation.
ISO 13485:2016 clause 7.3.2 is more prescriptive in several ways. First, it explicitly requires that planning output be documented and updated as the design progresses — not merely established at project start. The plan must address design and development stages, the review(s) needed at each stage, and the verification, validation, and design transfer activities appropriate to each stage. ISO 13485 also explicitly requires that responsibilities and authorities for design and development be defined, and that interfaces between different groups involved in design be managed to ensure effective communication and clear assignment of responsibility.
A key structural difference is the ISO 13485 requirement to plan for design transfer activities from the outset, rather than treating transfer as a separate downstream event. Part 820's planning requirement did not explicitly call out transfer planning. ISO 13485 also requires that planning be updated as the design evolves, creating a living document obligation rather than a static initial plan.
The FDA preamble to the QMSR final rule (February 2024) noted that this alignment with ISO 13485 planning requirements strengthens the expectation for ongoing plan maintenance. Companies whose design plans are created at project kickoff and never updated — a common pattern under Part 820 — will need to adopt a more dynamic approach to planning documentation.
Atomic constraints
- •Planning must be documented.
- •Planning must be updated as development progresses.
- •Resources and responsibilities must be defined.
- •The design and development plan must define the design and development stages.
- •The plan must identify the review, verification, and validation activities appropriate to each design stage.
- •Responsibilities and authorities for design and development must be defined in the plan.
- •Interfaces between different groups involved in design and development must be managed to ensure effective communication and clear assignment of responsibility.
- •Design transfer activities must be planned from the outset as part of the design and development plan.
- •The plan must be maintained as a living document and updated to reflect actual design progress, scope changes, and resource changes throughout the project.
Common gaps
Static design plan never updated after initial approval
majorMany Part 820-era design plans are created at project initiation and archived. ISO 13485 7.3.2 explicitly requires that planning documentation be updated as the design and development progresses, reflecting changes in scope, timeline, resources, and activities.
Missing interface management between groups
moderateISO 13485 7.3.2 requires that interfaces between different groups involved in design and development be managed to ensure effective communication and clear assignment of responsibility. Many legacy QMS plans identify team members but do not define how cross-functional interfaces (e.g., between R&D, manufacturing, quality, regulatory) are managed.
Design transfer not addressed in planning stage
moderateISO 13485 requires that design transfer activities be planned from the outset as part of the design and development plan. Many Part 820-era plans do not mention transfer until the project is nearing completion, creating gaps in resource allocation and timeline planning for manufacturing readiness.
Static design plans
moderateDesign plans are treated as one-time documents rather than 'living' documents that are updated as the project evolves. ISO 13485 §7.3.2 requires plans to be updated as appropriate during the design and development process.
Missing transfer activity definitions
moderateThe design plan fails to define specific activities needed for the transfer of design to production. ISO 13485 requires 'design transfer activities' to be part of the plan.
Evidence signals
- •
FILE_EXISTS
Design.*Plan
- •
CONTENT_MATCH
Does this document define specific milestones and responsible parties for design activities?
Audit defense
Our Design and Development Plan (Doc ID: [your document ID]) acts as the central roadmap for [your product]. It defines the sequence of activities and assigns roles (e.g., Quality vs. Engineering) to ensure independent oversight from day one.