The design and development file builds itself
Design controls fail retrospectively more often than they fail in the moment. The records have to be made as the work happens.
Watch it explained
Ten minutes on design controls a reviewer will accept
The short version
A reconstructed design and development file looks reconstructed
Every device company knows it needs design controls, and most intend to keep them properly. But design work moves fast, records get made later, and by the time a submission is being assembled the file is a reconstruction instead of a history. So what decides whether design controls hold is whether the record was created at the moment the decision was made.
Where it comes apart
ISO 14971 risk files drift away from the design
Design controls begin well. Inputs are captured, outputs are defined, and a risk file gets started in a spreadsheet or a dedicated tool.
Then the design changes, as designs do. The output changes, the verification protocol changes, and the risk file does not, because updating it is a separate task in a separate place that nobody owns. Traceability breaks quietly. It is usually discovered during submission preparation, when someone tries to build the trace matrix and finds it does not close.
When risk controls attach to the design outputs they mitigate, a change to the output flags the risk that depends on it. The trace matrix is a view of live records, and nobody has to maintain it as a document.
What runs here
Design control and risk management in one record
Design inputs and outputs
Captured with their rationale, linked to the requirements they came from.
Verification and validation
Protocols and results attached to the outputs they test, so the evidence sits with the thing it proves.
Risk management under ISO 14971
Hazards, harms, risk controls, and residual risk, connected to the design outputs that implement them.
Design reviews
Recorded as they happen, with attendees, decisions, and actions.
Design transfer
The handover to manufacturing, with the records that show it was controlled.
Design changes
Every change assessed for impact on risk, verification, and the submission itself. Changes that reveal a systemic problem route into CAPA.
The design and development file
Assembles from the records above; nobody writes it as a separate document.
Common questions
Common questions
What replaced the design history file?
The design and development file. Under the QMSR, FDA no longer names the design history file as a separate record; ISO 13485 clause 7.3.10 calls it the design and development file. It is the assembled evidence of the design process: the records showing a device was developed in accordance with its design plan and the design control requirements. Most teams still call it the DHF.
Does ISO 14971 require specific software?
No. ISO 14971 sets out a risk management process: analysis, evaluation, control, and monitoring of residual risk across the product lifecycle. Nothing in it requires software. What software changes is whether the risk file stays connected to a design that keeps moving.
When do design controls have to start?
At the beginning of design and development, well before a submission approaches. The records are contemporaneous evidence, and a reviewer can generally tell the difference between records made as work happened and records assembled afterwards.
How does software in the device change this?
Substantially. IEC 62304 brings a software lifecycle process with its own documentation, and software risk has to integrate with the ISO 14971 file rather than sitting alongside it. This is one of the five areas the mapping session covers, because it changes the shape of the whole system.
Do we need design controls for a Class I device?
Most Class I devices are exempt from design controls, but not all: some Class I devices are specifically called out as subject to them. This is exactly the kind of determination the mapping session exists to make, because getting it wrong in either direction is expensive.
See which design control records your device needs
The mapping session establishes what applies to your product, including whether design controls apply at all, and how the whole system maps against QMSR readiness.
The map is yours to keep either way.