How to Perform Design Qualification
Verify a proposed design meets requirements before you build or buy.
What a how-to is not
A how-to is SPEQ’s practitioner method, not a procedure. It does not replace your own SOP, it is not a validated approach, and the judgement calls in it belong to your quality unit.
Design Qualification (DQ) is the documented verification that a proposed design of equipment, a system, or a facility is suitable for its intended purpose and meets the User Requirements Specification — before it is built or purchased. DQ catches design gaps when they are cheapest to fix, and anchors the rest of the qualification lifecycle.
- 1
Establish the URS as the reference
Establish the user requirements as the reference the design will be judged against, and confirm they are themselves in a fit state — current, approved, and specific enough to be verifiable. Design qualification performed against a vague or superseded URS produces a confident record of nothing; the first real activity is often getting the requirements into a condition where the exercise is meaningful.
- 2
Review the proposed design against requirements
Review the proposed design against those requirements systematically, requirement by requirement, recording where the design satisfies each and where it does not. Involve the people who will operate, clean and maintain the facility, because the requirements most often unmet by a technically correct design are the ones about access, cleanability and maintainability — and those are discovered in operation if they are not discovered here.
- 3
Confirm regulatory and GEP suitability
Confirm the design is suitable for its regulatory context and consistent with good engineering practice: materials appropriate for product contact, classifications and cascades achievable, instruments ranged for their operating points, systems drainable and cleanable, and the automation capable of the records the process will need. This is also where the critical aspects identified earlier are checked against what the design actually delivers.
- 4
Document gaps and resolutions
Record gaps as findings with owners and resolutions, and close them on evidence of the design change rather than on agreement that the point is valid. An unresolved gap carried into construction becomes a field change at best and a deviation at worst, and the difference in cost between resolving it here and resolving it later is the reason this activity exists at all.
- 5
Approve to proceed
Approve the design as fit to proceed, with the approval naming what was reviewed and against which version. Design qualification is a gate, not a document: the approval says the organisation accepts that building this design will produce something capable of meeting the requirements, and that acceptance is what later qualification stages verify rather than re-examine.
- !Skipping DQ, so a design gap surfaces expensively at IQ or in production.
- !Performing DQ without a complete URS, so there is no clear reference to verify against.
- !Reviewing the design for function but not for cleanability, access, and GMP suitability.
- !No documented resolution of identified design gaps.
How to Perform Design Qualification: frequently asked questions
Common questions on perform design qualification.
What is Design Qualification?
DQ is the documented verification that a proposed design meets the User Requirements Specification and is suitable for its intended purpose, performed before building or buying. It is recognised in EU GMP Annex 15 as the first stage of qualification.
Why do DQ before IQ/OQ/PQ?
Because DQ catches design deficiencies before they are built in — when they are cheapest to fix. Discovering a design gap at IQ/OQ or in production is far costlier, so verifying the design against requirements first protects the whole project.
What does DQ verify against?
Primarily the User Requirements Specification, plus applicable GMP and good engineering practice. Each requirement — especially GxP-critical ones — is checked against the proposed design, with gaps documented and resolved before proceeding.