Define the documentation, responsibilities, test evidence and handover boundary for a pharmaceutical blister machine before the purchase order—not after equipment reaches the site.
Machine documents support the buyer’s qualification work; the buyer’s quality system owns approval and product/process validation.
The commercial decision
Buy a defined evidence package, not a vague “validation included” promise
DQ, IQ, OQ and PQ describe related but different work. Their protocols, execution responsibility, acceptance criteria, language, format and approval route must be named in the quotation and contract.
1Define the regulated useProduct, pack, market, site quality system, electronic-record boundary and intended operation.
2Define supplier documentsDocument index, templates, drawings, certificates, manuals, test protocols and editable formats.
3Define execution ownershipWho writes, reviews, approves, witnesses, executes, records deviations and closes reports.
4Define acceptance evidenceConfiguration baseline, challenge materials, instruments, sampling, raw data and signed results.
Qualification lifecycle
Connect DQ, IQ, OQ and PQ without treating them as interchangeable
The exact lifecycle is governed by the buyer’s quality system and applicable requirements. A useful supplier response shows how each document traces back to the approved URS and how factory evidence can support later site work.
DQ
Design qualification
Confirm that the proposed design is suitable for the intended purpose and responds to approved user requirements.
URS response
Design and option baseline
Risk-review inputs
Open-item register
IQ
Installation qualification
Verify the delivered machine, utilities, components and documentation against the approved installation basis.
Equipment identity
Drawings and utilities
Instrument and calibration status
Software/configuration version
OQ
Operational qualification
Test defined functions and operating ranges against approved protocols and acceptance criteria.
Functions and interlocks
Alarms and challenges
Operating ranges
Inspection and rejection
PQ
Performance qualification
Demonstrate performance under the buyer’s approved process method using appropriate product, materials and controls.
Approved process conditions
Representative variability
Quality tests and sampling
Site-approved results
Important boundary: qualification of equipment supports—but does not replace—product and process validation, routine controls, batch release, cleaning validation, computerized-system validation or the buyer’s regulatory responsibilities.
Quotation-ready scope
Name every document and responsibility before comparing suppliers
“Complete validation package” is not a measurable specification. Ask every bidder to answer the same matrix and mark each item included, optional, excluded, buyer-supplied or subject to approval.
Document availabilityIndex, title, template/report status, revision, language, file format and expected approval stage.
Execution supportRemote or site work, prerequisites, witness points, travel boundary, test instruments and schedule dependency.
Customization boundaryStandard template versus project-specific content, URS traceability, product tests and change-control route.
Organize the index by delivery stageBefore purchase order, expect a URS response, preliminary configuration, exclusions and a proposed document index. During design, control approved drawings, component and option lists, software scope and risk-review inputs. Before FAT, approve the protocol, prerequisites, challenge materials, instruments, sampling and acceptance criteria. Before shipment, close the FAT report, deviations, manuals, certificates in scope, backups, spares and open items. At the buyer site, distinguish installation records, IQ/OQ support, SAT activity, training evidence and handover responsibilities. During operation, define service access, change notification, replacement-part traceability, calibration or maintenance information and the software-support boundary. This staged index prevents a late bundle of generic files from being mistaken for project evidence.
Before manufacture
Turn the URS into a traceable design baseline
Qualification begins with intended use and approved requirements. The supplier response should connect each relevant requirement to a proposed feature, document, test or declared exclusion.
Approved product, blister drawing, forming and lidding materials, print and coding inputs.
Accepted output definition, inspection strategy, reject handling and line-interface responsibilities.
Separate supplier evidence from buyer approval and site execution
Work item
Supplier contribution to define
Buyer/site contribution to define
Contract evidence
URS and design response
Respond to requirements, state configuration, assumptions and exclusions.
Issue and approve intended-use requirements and applicable-site standards.
Approved URS response and deviation list.
DQ support
Provide design documents, option list, drawings and risk-review inputs in the agreed format.
Review suitability for intended use and approve the design basis.
Named DQ protocol/report responsibility and signatures.
FAT
Prepare the agreed machine, protocol, instruments, test records and deviation workflow.
Approve prerequisites, supply agreed challenge materials and witness where contracted.
Approved FAT protocol, raw records, report and open-item register.
IQ/OQ support
Supply configuration records, drawings, manuals, certificates, test scripts or execution support as contracted.
Control site installation, approvals, quality procedures, calibrated instruments and final records.
Document index plus included/excluded execution activities.
PQ and process validation
Provide machine information and technical support within the contracted boundary.
Own product, process, sampling, site conditions, quality decisions and release.
Explicit boundary; never imply supplier documents equal site approval.
Change control
Notify and document agreed changes to configuration, software, components or drawings.
Assess impact on qualified/validated state and approve actions.
Change log, revised baseline and closure evidence.
Protocol qualityA useful protocol identifies purpose, scope, prerequisites, roles, the exact equipment and configuration, methods, instruments, acceptance criteria, data to retain, deviation handling and approval signatures. A document title alone does not establish that the protocol is usable.
Report qualityThe report should connect executed results to the approved protocol, identify actual materials and instruments, retain unexpected observations, list deviations and corrective actions, and state whether acceptance criteria were met. Blank templates are not executed evidence.
Handover qualityThe final package should match the shipped configuration and include the agreed revisions, native or editable files where contracted, backups, manuals, certificates in scope, open actions and a clear ownership route for post-shipment changes.
Factory acceptance
Design FAT evidence so it can support—not impersonate—qualification
A FAT can capture valuable evidence before shipment when the approved configuration, materials, methods and instruments are controlled. Whether any FAT record is reused later must be justified and approved within the buyer’s quality system.
Identify the exact configuration, tooling revision, software/recipe baseline and open items.
Record material identities, product challenge set, setup values, test duration and environmental conditions where material.
Define good packs, rejects, waste, stops, interventions, sampling and acceptance criteria before the run.
Retain raw observations, test results, signed deviations, corrective actions and final disposition.
State which tests must be repeated after transport, installation or site integration.
Assess 21 CFR Part 11 from actual record use—not from the presence of an HMI
Part 11 applies to electronic records and electronic signatures within its regulatory scope. A touch screen, PLC or recipe function alone does not establish applicability or compliance.
Define if the system will create or maintain regulated electronic records
Which records are required by predicate rules?
Which data are authoritative: paper, electronic or both?
Who creates, changes, reviews, approves and exports records?
What access, audit-trail, retention, backup and signature controls are required?
Do not accept a generic “Part 11 ready” label
Name the functions and configuration actually supplied.
Identify excluded infrastructure and site procedures.
Define test cases, roles and objective evidence.
Keep final applicability and validation decisions with the regulated user.
Test the configured blister process, not a generic machine description
Qualification evidence becomes useful only when it names the approved machine, product and packaging-material challenge. The protocol should cover the stations and risks that exist in the purchased configuration.
Forming and sealing Approved materials, settings, operating ranges, registration, seal evidence and defined defects.Installation and site interfaces Utilities, equipment identity, drawings, guarding, line signals, instruments and installation records.Product and finished pack Cavity drawing, representative products, coding, inspection, rejection and accepted-output evidence.
Station-level test families
Typical discussion areas include web handling, forming repeatability, product feeding, seal-process evidence, print and registration, cutting, inspection, rejection, safety functions, alarms, recipes, changeover and interfaces. Only the functions present in the approved configuration belong in the protocol.
For each test, name the challenge condition and the evidence that answers a decision. A temperature setpoint screenshot proves that a value was entered; it does not by itself prove a usable sealing process.
Finished-output evidence
Mechanical cycles and catalog speed do not establish acceptable production. A sustained run should define run time, packs per stroke, scheduled stops, interventions, total packs, accepted packs, rejects, waste and the disposition of defects.
Retain representative finished samples and records for seal, cavity, registration, cut position, coding and inspection results according to the approved sampling plan. The buyer should define which quality tests remain outside the machine supplier’s scope.
Buyer input checklist
Send these inputs for a usable documentation-scope response
Product and packDosage form, geometry, fragility, blister drawing, material grades, print/coding and samples.
Machine and lineSelected configuration, tooling, feeder, inspection, reject, cartoner interface, utilities and options.
Quality boundaryApplicable-site requirements, document language, approval workflow, records, signatures and data expectations.
Acceptance planFAT/SAT scope, run conditions, instruments, sampling, acceptance criteria, witness points and report ownership.
Also disclose what is still unknown
Open material grades, unfinished artwork, missing samples, unapproved blister drawings, uncertain line interfaces or an undefined electronic-record strategy can change the document package and test plan. Listing them early creates a controlled assumption; hiding them creates late rework.
Ask for a proposal that can be compared
Require suppliers to separate standard deliverables, project-specific customization, optional site services, buyer prerequisites, exclusions and change-order triggers. This makes the commercial comparison about the same evidence boundary rather than similar-sounding document labels.
Request outcome: a document index and responsibility matrix tied to the proposed machine configuration—not a generic certificate bundle.
Continue the project
Move from qualification planning to a configured machine scope
References describe regulatory principles and should be interpreted for the buyer’s product, market, facility and quality system. They do not certify a machine or replace advice from the buyer’s quality and regulatory teams.
Buyer questions
Blister machine IQ OQ PQ FAQ
What do DQ, IQ, OQ and PQ mean for a blister packaging machine?
DQ verifies that the proposed design is suitable for its intended purpose. IQ verifies installation against the approved design and supplier recommendations. OQ verifies operation throughout approved ranges. PQ verifies effective and reproducible performance using the approved process method and specifications. The buyer's quality system defines the final protocols and approvals.
Is supplier documentation enough to validate a blister packaging process?
No. Supplier documents and factory tests can support equipment qualification, but they do not replace site installation evidence, product and process knowledge, approved sampling, routine controls, deviation handling or the buyer's final validation decisions.
What should a blister machine qualification quotation include?
It should identify every document, its format and language, whether it is a template or executed report, customization scope, approval responsibility, FAT/SAT activities, site support, prerequisites, exclusions and commercial assumptions.
Can FAT results be reused during IQ or OQ?
They may support later qualification when the buyer justifies their reuse, the test was performed under controlled and representative conditions, the evidence remains valid after transport and installation, and the approach is approved in the buyer's quality system. Tests affected by installation or site integration normally require site verification.
Does every blister machine require the same OQ tests?
No. Tests should follow the approved configuration, intended use and risk assessment. A machine with vision inspection, recipe management, printers or downstream interfaces requires different challenges from a simple standalone machine.
Does 21 CFR Part 11 apply to every blister machine HMI?
Not automatically. Applicability depends on whether the system creates, modifies, maintains, archives, retrieves or transmits electronic records required by applicable FDA regulations, or uses electronic signatures in that regulated context. The buyer must define the record and signature boundary.
Who is responsible for PQ?
The regulated user normally owns the approved process, product, site conditions, quality decisions and final PQ approval. A supplier may provide machine information, test templates or contracted technical support, but the responsibility boundary must be written into the project scope.
When should requalification be considered?
The buyer should define a risk-based periodic review and assess requalification after changes that may affect the qualified state, such as relocation, significant component or software changes, tooling changes, extended shutdowns or recurring performance problems. A universal fixed interval should not be assumed.
Define the boundary before quotation
Request a Blister Machine Qualification-Scope Review
Send the product and blister definition, proposed machine configuration, URS, accepted-output target, inspection boundary and site documentation expectations. HIJ can respond with a project-specific document index, responsibility matrix and FAT-support scope for commercial discussion.
