How to Validate a Tablet Blister Packing Machine: IQ OQ PQ

Tablet blister qualification guide

Validating a tablet blister packaging process requires more than collecting a supplier’s IQ/OQ templates. The manufacturer must define the product, package, process, system boundary, intended use, risks and acceptance criteria; qualify the installed equipment; demonstrate operation across justified conditions; confirm performance with approved materials and procedures; and maintain control through the lifecycle.

This guide turns DQ, IQ, OQ and PQ into a tablet-specific evidence plan covering forming, feeding, sealing, inspection, rejection, coding and cutting. It also explains how URS, FAT, data integrity, deviations and continued verification connect without inventing universal settings, sample sizes, batch counts or timelines.

Validation boundary: the pharmaceutical manufacturer owns the validation strategy, approved protocols, product and package specifications, acceptance criteria, deviations, qualification decisions, process performance qualification and batch release. The equipment supplier provides only the contracted design, test and documentation support.

Direct answer

How do you validate a tablet blister packing machine?

DQ, IQ and OQ normally qualify the design, installation and operation of equipment. PQ or process performance qualification addresses performance of the process in its routine context. Terminology and document structure can differ between companies and jurisdictions, so define what each stage means in the site validation plan.

A tablet blister line is not validated forever after one successful run. Calibration, maintenance, monitoring, deviations, changes, periodic review and requalification keep the validated state supported throughout its lifecycle.

Qualification and validation

Separate equipment qualification from process validation

Equipment qualification establishes documented evidence that equipment is appropriately designed, installed and operated for its intended use. Process validation establishes evidence that the manufacturing process can deliver product meeting predetermined requirements consistently. They are connected but are not the same conclusion.

A machine can pass installation and functional tests before the site has completed process performance qualification for a particular tablet and blister. Conversely, process evidence from one product, material, tooling or line should not automatically be applied to a different configuration.

FDA’s process-validation guidance uses a lifecycle model: process design, process qualification and continued process verification. EU GMP Annex 15 describes lifecycle qualification and validation activities including URS, DQ, FAT/SAT, IQ, OQ, PQ, change control and requalification. Build the site’s approach from the applicable framework and product risk.

System boundary

Define what is inside the validated tablet blister system

State where the system begins and ends. The boundary may include tablet supply and bulk hopper, feeder, forming web, heating or cold-form station, inspection, lidding web, sealing, printing or embossing, perforation, cutting, rejection, transfer and interfaces to a cartoner or serialization system.

Also identify supporting utilities, exhaust, vacuum, compressed air, cooling, software, recipes, cameras, data storage and network interfaces. A function outside the equipment skid can still affect the package or a required record.

Draw the boundary and list interfaces. Assign ownership for each signal, material transfer, reject path, record and alarm response. This prevents a multi-supplier line from leaving important tests between contracts.

Intended use

Write the intended use before writing test cases

Qualification must relate to how the equipment will actually be used. Define the tablet products, dimensions and relevant physical properties; forming and lidding structures; blister drawings; forming route; pack formats; accepted output; inspection and reject needs; cleaning strategy; operating environment and downstream interfaces.

Identify regulated records and the intended role of the PLC, HMI, vision system and connected systems. State whether a value is merely displayed, used to control the process, printed to paper, stored electronically or transferred to another system.

If intended use is vague, testing becomes generic. A checklist may pass while the actual tablet feeds poorly, the material cannot form consistently or the final reject cannot be reconciled.

Validation plan

Define strategy, roles and deliverables before execution

The validation master plan or project validation plan should state scope, lifecycle stages, responsibilities, documents, risk methods, change and deviation handling, prerequisites, approval sequence and how supplier evidence will be used. The title of the document matters less than having an approved strategy.

Name the pharmaceutical manufacturer’s quality, engineering, production, maintenance, IT or automation, validation, laboratory and regulatory roles as applicable. Name the supplier’s design, documentation, software and test responsibilities. Do not leave final approval with the equipment vendor.

Define document numbering, version control, data review, raw-data retention and report requirements. A protocol should be approved before it is executed; a report should explain results and unresolved risk rather than merely repeat checkmarks.

Risk assessment

Use product and process risk to set qualification depth

Risk assessment helps determine which functions need direct measurement, challenge testing, alarm verification, mapping, data review or supplier evidence. Start with product quality and patient-relevant outcomes, then connect them to package attributes, process steps and equipment functions.

For tablet blister packaging, risks may include incorrect cavity formation, tablet damage, missing or extra tablets, contaminated seal lands, incomplete seals, mixed materials, incorrect coding, failed rejection, cross-contamination, uncontrolled recipes and missing records.

Risk ranking is not permission to omit evidence without explanation. Document why a function is critical, controlled indirectly, covered by another test or outside scope. Revisit the assessment after design changes, deviations and process knowledge.

URS

Make the URS testable and tablet-specific

The user requirements specification should describe what the user needs and how acceptance can be demonstrated. Avoid untestable phrases such as “GMP machine,” “high accuracy,” “easy cleaning” or “Part 11 compliant” without defining intended use and measurable functions.

Maintain traceability from URS requirements through design review and executed tests. The blister machine URS guide provides a broader input structure.

Design qualification

What should tablet blister machine DQ demonstrate?

DQ demonstrates that the proposed design addresses the approved user requirements and intended use. Review the actual quoted configuration, not a family brochure. Confirm machine stations, tooling concept, materials of construction, access, cleaning, utilities, guarding, controls, inspection, reject path, data functions and interfaces.

Check traceability between URS, supplier functional or design specifications, drawings, component lists and test plans. Record gaps as actions or deviations with owners and due dates. Resolve design issues before they become installation or OQ problems.

DQ is also the point to confirm what the supplier will demonstrate at FAT, what remains for site testing and which documents will be delivered. A generic template received after fabrication cannot substitute for an approved design decision.

Design review inputs

Review the whole web path and every operator intervention

Follow the forming web from unwind through forming, feeding, inspection, sealing, coding, perforation and cutting. Follow the lidding web from unwind through printing or registration and sealing. Identify tension controls, guides, sensors, splices, stop positions and manual adjustments.

Review how tablets enter, circulate and leave the feeder. Include hopper access, level control, dust extraction, return paths, jams, manual filling, recovery after stop and line clearance. Manual touchpoints require defined operator authority and recorded decisions.

Review how rejected material is tracked from detection to physical separation. A camera result, PLC bit and reject actuator must refer to the same final pack after indexing and cutting.

Supplier assessment

Evaluate supplier capability without turning it into a compliance certificate

Assess whether the supplier can build and document the required configuration, control changes, manage software versions, calibrate test equipment, execute agreed trials and support deviations. Review example documents for structure and completeness before the order if they are contract deliverables.

A supplier audit or assessment informs purchasing and quality risk. It does not transfer validation responsibility or prove the finished process. Avoid statements that a supplier, country or certification makes every machine acceptable for every regulated site.

Use a quality or project agreement where responsibilities, records, notifications and approvals need formal definition. Align that agreement with the commercial contract so critical evidence is not treated as an optional service later.

FAT and SAT

Use FAT and SAT as evidence inputs, not automatic qualification

Factory acceptance testing can verify build, functions, materials, software, alarms, safety, change parts, documentation and run performance before shipment. Site acceptance testing can confirm the equipment after transport, installation and connection to site utilities. Their use within qualification should be defined by the manufacturer’s approved strategy and risk assessment.

EU GMP Annex 15 allows review of documentation and some tests performed at the vendor site when justified and when transport or installation is not expected to affect the tested function. Repeating or leveraging a test should be a documented decision, not a blanket rule.

FAT should use the purchased configuration and representative tablets, materials and format where practical. If substitutes are used, record what they do and do not represent. Predefine acceptance, deviations, retesting and final authority.

Installation qualification

What should IQ verify after installation?

IQ verifies that the installed equipment and supporting systems match the approved design and controlled records. Identify the machine, modules, serial numbers, tooling, major components, software and firmware versions. Confirm location, orientation, access, guarding, utilities and interfaces against approved drawings.

Check receipt and status of manuals, drawings, parts lists, certificates, calibration records and software documentation required by the project. Verify that measurement devices are identified and within the site’s calibration system. Record actual utility values using approved instruments where the protocol requires measurement.

IQ should also confirm installation of configured options. Do not accept an unchecked statement that the vision system, printer, reject confirmation, recipe storage or network interface is “included.” Verify the actual hardware, connection and version.

Utilities

Verify utilities at the point and under the conditions that matter

Electrical supply, protective earthing, compressed air, cooling, vacuum, exhaust and network services can affect operation. Define required quality, capacity, range and connection from the purchased design and site standards. Avoid copying generic values from another model.

A static reading with the line stopped may not represent utility behavior during simultaneous forming, sealing, feeding, rejection and downstream operation. Determine which utilities need observation under representative load during commissioning or OQ.

Record the measurement location, instrument, units, date and actual result. If a central utility is qualified separately, reference the applicable system evidence and verify the local connection and operating need.

Calibration

Map measurements to decisions before testing begins

Identify which instruments measure or influence forming temperature, sealing conditions, pressure, vacuum, force, web position, speed, timing, weight or other relevant variables. Decide whether each is an indication, a control measurement or a reference for acceptance.

Calibration status alone does not prove that the measurement represents the physical condition of interest. Sensor location, response, range, resolution, mapping and comparison method may matter. Define how the site will verify measurement channels and how out-of-tolerance findings are assessed.

Use calibrated test instruments appropriate to the required range and uncertainty. Record raw results rather than only “pass.” Link each instrument to its certificate and status at the time of execution.

Operational qualification

What should OQ prove for a tablet blister machine?

OQ demonstrates that the installed equipment functions as intended across justified operating conditions. Test normal operation, defined limits, alarms, interlocks, stops, restart, manual modes, recipes, access levels, inspection, rejection and interfaces. The range comes from product and process development, material capability, design limits and risk assessment.

Do not automatically test every parameter at the equipment’s physical maximum. Challenge the range relevant to intended use and known interactions. Where two variables interact, design the study to expose that interaction rather than changing one factor in isolation without scientific reason.

Predefine stabilization, sample locations, number of observations, measuring method and acceptance criteria. Include edge lanes, start-up, steady operation, planned stops and restart when these conditions can change the output.

Forming qualification

Challenge cavity formation across lanes and operating conditions

For thermoforming, evaluate heating, forming pressure or vacuum, plug assistance where fitted, web transport and cooling. For cold forming, evaluate tool geometry, laminate direction, force, draw behavior and web handling. Use the exact quoted station and tooling route.

Measure attributes connected to package risk, such as cavity geometry, wall or corner condition, flange flatness, registration and visible damage. The relevant attributes and methods depend on the approved pack design; do not impose a universal thickness or tolerance.

Sample across the web and through time. A central cavity from a short run may miss edge-lane, warm-up or restart effects. Preserve labeled samples and raw measurements so later investigations can trace patterns.

Tablet feeding qualification

Demonstrate fill performance without unacceptable tablet damage

Tablet feeding depends on product shape, dimensions, coating, score, friability, dust, static, surface behavior and batch variation. Test with the commercial product or a scientifically justified representative that covers the physical challenge. A placebo should not be assumed representative merely because its dimensions match.

Evaluate missing, extra, damaged, misoriented or displaced tablets; feeder replenishment; low and high hopper levels; stops; restart; interventions and recovery. Define whether defects are prevented, detected and rejected.

Inspect tablets before feeding, after feeding and in finished blisters. Use approved criteria for chips, cracks, coating damage or other relevant conditions. Relate feeder settings and change parts to a controlled recipe or setup record.

Sealing qualification

Develop and verify a justified sealing operating window

Sealing performance is influenced by the forming and lidding structures, heat-seal coating, temperature, force or pressure, contact time or line rate, alignment, tool condition, flange geometry and contamination. There is no universal setting that validates every blister.

Define relevant package tests and their acceptance criteria before OQ. Seal strength, package integrity, appearance and product stability answer different questions. Use the methods that address the identified failure modes; do not treat one passing result as proof of every attribute.

Challenge the intended operating window and transitions. Record actual values where required and compare lanes or positions. Include response to contaminated seal land where a safe, justified challenge can be designed without introducing uncontrolled product risk.

Inspection and rejection

Prove detection, tracking and physical separation as one system

Define the defect library for tablets, cavities, lidding, print and code. State which defects the inspection system is intended to detect, under which product, format, lighting, contrast and speed conditions. Build controlled challenge samples with traceable identity.

Challenge every relevant lane and position, plus start-up, stop, restart and maximum intended rate where timing may change. Verify that the correct finished pack is rejected after sealing and cutting. Test reject confirmation, full-bin response, secure collection, access and reconciliation.

Report both missed challenges and false rejects according to the approved statistical and operational approach. Avoid universal claims of perfect detection. The validated capability applies only to the defined challenge set and configuration.

Coding and cutting

Qualify the final identity and geometry of each blister card

Verify printed or embossed batch, expiry and other required information against approved artwork and coding rules. Challenge recipe selection, data transfer, line clearance, start-up, changeover, sensor response and rejection of missing or incorrect codes as applicable.

Evaluate lidding registration, print position, perforation, cut position, edge condition and card dimensions. Ensure that cutting does not enter the seal area or damage a cavity. Check that individual packs retain the correct relationship among product, code and inspection result.

If serialization or aggregation is downstream, define the interface and ownership. A valid code on the web is not the same as a reconciled final saleable pack.

Alarms and recovery

Test what happens after a fault, not only whether an alarm appears

Alarm verification should include the trigger, message, machine response, affected material boundary, reset authority, recovery steps and record. Examples may include web break, low material, temperature deviation, missing product, jam, guard opening, reject-bin condition and downstream stop.

Determine which packages are potentially affected during the delay between fault initiation, detection and stop. Define how the operator identifies, segregates or rejects them. Challenge restart because tablets, webs and index relationships can move during a stop.

Manual and maintenance modes require equal attention. Bypass, jog or setup functions should be controlled according to risk and access authority, with a defined return to production state.

Cleaning and line clearance

Qualify the controls that prevent mix-up and carryover

Review product-contact parts, removal, access, cleaning method, inspection, drying, storage and reassembly. Tablet dust can accumulate in feeders, guides, tracks, sensors and reject paths. The cleaning strategy comes from product and process risk; equipment qualification confirms that the design supports it.

Line clearance should cover tablets, forming and lidding rolls, printed components, codes, recipes, samples, rejects, tools and documents. Challenge changeover sequences and independent checks where required.

Cleaning validation, where applicable, is owned by the manufacturer and uses product-specific limits and methods. A stainless-steel grade or polished surface does not by itself validate cleaning.

Computerised functions

Base data-integrity testing on actual records and intended use

A PLC or touchscreen does not automatically make every function subject to 21 CFR Part 11, and it does not automatically satisfy Part 11. FDA’s scope guidance ties applicability to predicate-rule records maintained or submitted electronically and to electronic signatures. Define the records and business practice first.

Where electronic records are relied upon, test applicable user access, authority, recipe control, time reference, event history, review, export, retention, backup, restore, interface and change functions. Confirm what the system records during manual, maintenance, alarm, power-loss and restart conditions.

For paper-based or hybrid processes, define the authoritative record and reconciliation. Printed values, local electronic values and transferred data should not conflict without a controlled resolution path. See the Part 11 blister-machine checklist for a dedicated scope-first review.

Performance qualification

What should PQ demonstrate for a tablet blister process?

PQ demonstrates that the integrated process performs effectively and reproducibly under approved routine conditions. Use approved tablets, forming and lidding materials, tooling, recipes, utilities, environment, procedures, trained operators, sampling and test methods according to the manufacturer’s validation strategy.

Evaluate finished-pack attributes connected to the control strategy: correct tablet count and condition, cavity and seal quality, code and registration, cut geometry, inspection and rejection, accepted output and other product-specific requirements. Include relevant material lots, time, lanes and normal operating variability.

The number of runs or batches must be justified. FDA guidance expects a sound scientific basis and sufficient data for confidence; EU GMP Annex 15 permits a risk-based approach while noting three consecutive batches as generally acceptable for traditional process validation. Do not turn that general expectation into a universal rule for every project.

Sampling and statistics

Design sampling around the process pattern and decision

A sample plan should state the population, unit, locations, timing, attributes, method, rationale and acceptance rule. Include lanes, heads or positions that may behave differently. Capture warm-up, steady operation, replenishment, stops, restart and end-of-run where relevant.

Do not use a fixed sample number copied from another protocol without relating it to the defect, variability and decision. Attribute and variable data require different treatment. Detection challenges, seal measurements and accepted-output estimates may need different designs.

Record individual data when averages can hide lane or time patterns. Predefine how missing values, invalid tests, retests and deviations will be handled. Statistical confidence does not repair a biased or unrepresentative sample.

Acceptance criteria

Approve criteria before seeing the qualification results

Acceptance criteria should come from approved product and package specifications, development knowledge, material capability, intended use, risk assessment and applicable requirements. Distinguish an equipment function limit from a process operating range and a finished-product specification.

Write measurable criteria with units, method and location. “Machine runs smoothly,” “good seals” and “camera works” are not adequate. At the same time, avoid inventing numeric limits where the product and method have not been defined.

If a result does not meet the criterion, open and assess a deviation. Do not rewrite the criterion after execution to make the test pass. Any justified protocol change needs controlled approval and transparent reporting.

Deviations

Use deviations to protect the meaning of the evidence

A deviation should describe what happened, when, where, affected tests and data, immediate control, investigation, impact, corrective action and approval. Link raw data and samples. Classify significance using the site procedure and actual risk rather than the inconvenience of repeating a test.

Retesting requires a justified plan. Repeating until a passing result appears destroys the evidence. If a test method, instrument, material or setup was invalid, explain why and assess all results it affected.

Close or formally assess open deviations before approving the next phase when they can affect that phase. Sequence should follow risk and prerequisites, not a calendar promise from the supplier.

Traceability

Build one chain from requirement to executed result

A traceability matrix should connect each applicable URS requirement to the design response and one or more tests or records. It should show status and unresolved gaps. It should not simply list document titles without identifying the evidence.

Traceability also prevents unnecessary duplicate testing. A justified FAT result may support an IQ or OQ requirement when the strategy permits it, while site-dependent functions still need site evidence. The matrix makes that decision reviewable.

Update the matrix through changes and deviations. At final report approval, every required item should be satisfied, justified as not applicable or carried as an approved action with a clear impact assessment.

Final reports

Qualification reports must explain the conclusion

A report should identify the executed protocol revision, dates, equipment and configuration, materials, participants, instruments, results, deviations, changes, unresolved items and conclusion. Summarize whether prerequisites and acceptance criteria were met.

Attach or reference raw data, electronic records, samples, photographs and calculations according to the document system. A report that contains only pass/fail checkmarks makes later review and investigation difficult.

The manufacturer’s authorized functions approve the report. Supplier signatures may confirm execution or technical observations but do not replace site quality approval.

Continued verification

Maintain the validated state after PQ approval

Monitor the attributes and process signals needed to detect drift or new risk. Review deviations, rejects, complaints, maintenance, calibration, inspection performance, material changes, recipes and trends at a frequency defined by the quality system.

Define conditions that trigger assessment or requalification: major repair, relocation, tooling change, material change, software or control change, expanded operating range, new product family, repeated deviations or adverse trend. Not every change requires full repetition of every test.

Use change control and risk assessment to decide the affected functions and evidence. Retain the rationale whether testing is added or existing evidence remains applicable.

Documentation package

Specify the supplier documents before placing the order

• approved equipment and functional specifications within the contracted scope;
• general arrangement, utility, electrical, pneumatic and applicable interface drawings;
• bill or list of major components and controlled software or firmware identification;
• product-contact material and calibration documentation where specified;
• operating, cleaning, changeover, maintenance and troubleshooting manuals;
• spare and wear-part lists and change-part identification;
• FAT protocol, raw results, deviations and final report;
• IQ/OQ protocols or support documents at the agreed level of customization;
• software function, backup, restore and account documentation where required;
• training, installation and site-support records within the contract.

Review document samples and language expectations before purchase. Define format, revision, approval, delivery milestone and ownership. Avoid assuming that a “validation package” has the same scope across suppliers.

Readiness checklist

Confirm these inputs before approving the qualification plan

Responsibility split

What the machine supplier can and cannot validate

The supplier can confirm design details, manufacture and inspect the contracted equipment, execute agreed FAT tests, provide controlled technical documents, support installation and assist with IQ/OQ execution. It can report performance observed with the identified samples, materials and configuration.

The supplier cannot approve the pharmaceutical manufacturer’s product, package, site procedures, electronic-record scope, validation strategy, acceptance criteria, PQ, commercial process or batch release. It cannot guarantee an inspection outcome or declare universal regulatory compliance.

Define responsibilities in writing and preserve the distinction in published claims. Clear boundaries help the buyer obtain the right supplier evidence without creating a false compliance promise.

Frequently asked questions

Tablet blister machine IQ OQ PQ FAQ

Sources and next reading

Official qualification and validation references

Use the current requirements applicable to the product, site and markets. These references define principles; they do not provide universal machine settings, sample sizes, batch counts, schedules or supplier guarantees.