V5 Ultimate
Ultimate
PricingResourcesCompany
English (original)العربيةDeutschΕλληνικάEspañolFrançaisItalianoעברית日本語한국어NederlandsPolskiPortuguêsSvenska
Talk to us Log in Start free trial
Food & Beverage
  • Bakery & Confectionery
  • Food Processing
  • Ingredients & Dry Mixes
  • Sausage & Meat Products
  • Produce Packing
  • Pet Food & Pet Supplements
  • Dairy & Chilled Foods
  • Beverages & Liquid Manufacturing
  • Infant Formula
Pharma & Life Sciences
  • Radiopharmaceuticals
  • Pharmaceutical
  • Medical Devices
  • Veterinary Pharmaceuticals
  • Blood & Tissue
  • Diagnostics & IVD Kits
  • Reference Materials & Standards
  • OTC Topical Creams & Gels
Supplements & Personal Care
  • Dietary Supplements
  • Cosmetics & Personal Care
  • Cannabis & Hemp Manufacturing
  • Fragrances & Perfumery
  • Soaps & Personal Hygiene
  • Botanical Extracts & Essential Oils
Chemicals & Materials
  • Plastics & Resins
  • Agricultural Chemicals
  • Specialty & Industrial Chemicals
  • Printing Inks, Pigments & Construction Chemicals
  • Lubricants & Metalworking Fluids
  • Coatings, Adhesives & Sealants
Other Manufacturing
  • Consumer Products
  • Electronics & Electrical Assembly
  • Textiles & Nonwoven
  • Contract Manufacturing & Co-Packing
  • Packaging & Food-Contact Materials
  • Regulated Warehousing & Distribution
Explore all industries
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Why V5? Product & Features
Why V5?Product & Features
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Explore all industries
    • Bakery & Confectionery
    • Food Processing
    • Ingredients & Dry Mixes
    • Sausage & Meat Products
    • Produce Packing
    • Pet Food & Pet Supplements
    • Dairy & Chilled Foods
    • Beverages & Liquid Manufacturing
    • Infant Formula
    • Radiopharmaceuticals
    • Pharmaceutical
    • Medical Devices
    • Veterinary Pharmaceuticals
    • Blood & Tissue
    • Diagnostics & IVD Kits
    • Reference Materials & Standards
    • OTC Topical Creams & Gels
    • Dietary Supplements
    • Cosmetics & Personal Care
    • Cannabis & Hemp Manufacturing
    • Fragrances & Perfumery
    • Soaps & Personal Hygiene
    • Botanical Extracts & Essential Oils
    • Plastics & Resins
    • Agricultural Chemicals
    • Specialty & Industrial Chemicals
    • Printing Inks, Pigments & Construction Chemicals
    • Lubricants & Metalworking Fluids
    • Coatings, Adhesives & Sealants
    • Consumer Products
    • Electronics & Electrical Assembly
    • Textiles & Nonwoven
    • Contract Manufacturing & Co-Packing
    • Packaging & Food-Contact Materials
    • Regulated Warehousing & Distribution
PricingResourcesCompany
Start free trial Log in Talk to us
HomeGlossaryBlend Uniformity & Stratified Sampling
Lab · The complete guide

Blend Uniformity Stratified Sampling: Sampling-Plan Design

In short

Blend Uniformity Stratified Sampling is an approach that assesses in-process dosage-unit uniformity using samples selected from predefined run segments and process-specific risk points.

3,946 words · ~18 min read
Gowned technician collecting stratified tablet samples from a press into run-position containers
On this page
  1. 01What the sampling plan measures—and what it does not
  2. 02Map U.S. drug requirements without extending their scope
  3. 03Read FDA guidance status separately from its stated scope
  4. 04Define run strata, risk points, and sample allocation
  5. 05Execute the plan from collection through review
  6. 06Keep the run, sample, result, and decision connected
  7. 07Three worked cases: coverage, restart, and unequal strata
  8. 08Interpret variability before assigning an acceptance decision
  9. 09Reconcile system handoffs and recover sampling exceptions
  10. 10Control collection and interpretation failures without overstating their frequency
  11. 11Review the applicable controls and the complete sampling design
On this page · 11 sections
  1. 1What the sampling plan measures—and what it does not
  2. 2Map U.S. drug requirements without extending their scope
  3. 3Read FDA guidance status separately from its stated scope
  4. 4Define run strata, risk points, and sample allocation
  5. 5Execute the plan from collection through review
  6. 6Keep the run, sample, result, and decision connected
  7. 7Three worked cases: coverage, restart, and unequal strata
  8. 8Interpret variability before assigning an acceptance decision
  9. 9Reconcile system handoffs and recover sampling exceptions
  10. 10Control collection and interpretation failures without overstating their frequency
  11. 11Review the applicable controls and the complete sampling design
AI · Explain it for MY operation

How does Blend Uniformity & Stratified Sampling apply to your shop floor?

Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.

Your scale

01What the sampling plan measures—and what it does not

Blend uniformity stratified sampling is an operational approach to assessing uniformity through samples assigned to predetermined portions of a production population. Here, the focus is dosage units collected during compression or filling—not a quoted legal definition or prescribed protocol. A stratum is one predetermined portion, with boundaries expressed in a usable production coordinate, such as elapsed run time, cumulative unit count, or discharged mass. In this application of stratified sampling, each dosage-unit result retains its association with its stratum, so the observation describes both what was measured and where it belongs in the run.

Bulk-powder blend uniformity testing examines powder observations. Downstream dosage-unit sampling examines individual tablets or filled units. The distinction is the material and production stage represented: a powder result and a dosage-unit result do not silently substitute for one another. Naming the sampled material is therefore part of defining the question, not merely a labeling choice.

ApproachMaterial sampledSampling coordinateQuestion addressed
Bulk-powder blend uniformity testingPowder portionsDefined powder sampling locationsHow do sampled powder portions compare?
Stratified in-process dosage-unit samplingIndividual dosage unitsPredetermined run strataHow do units compare within and across run portions?
Unstructured in-process grab samplingUnits collected as grabsCollection points without predefined strataWhat do these collected units show?
Finished-product unit testingFinished dosage unitsSelected positions within the finished lotWhat do selected finished units show?

The observation unit also matters. Separately tested dosage units provide unit-specific results. A combined sample provides a result for the combined material, rather than separate results for its constituent units. Repeated measurements of one preparation describe measurement repeatability for that preparation; they are not additional independently sampled units. This article’s worked cases use one separately tested dosage unit as each observation. Keeping that definition explicit prevents a count of analytical readings from being mistaken for a count of sampled units.

02Map U.S. drug requirements without extending their scope

The legal discussion here concerns 21 CFR Part 211, titled Current Good Manufacturing Practice for Finished Pharmaceuticals. Practical examples of sampling during manufacture are not determinations that a particular product, facility, or operation falls within that part. Establish applicability before using the requirements below as the legal basis for a sampling procedure; the 21 CFR 211 overview provides related context.

Binding obligations and practical design choices

21 CFR 211.110(a) requires written procedures to be established and followed describing in-process controls and tests or examinations on appropriate samples of in-process materials of each batch. The same paragraph requires control procedures to monitor output and validate the performance of manufacturing processes that may cause variability in in-process material and drug-product characteristics.

For sampling-plan design, that purpose makes a practical question useful: which run positions should receive attention when evaluating possible process variability? Treat the answer as a documented design rationale, informed by process understanding and process validation, rather than as a sampling layout prescribed by this article. The legal obligation and the proposed allocation of samples are separate: citing the regulation does not, by itself, explain why a chosen allocation is suitable.

For production-and-process-control procedures, 21 CFR 211.100(a) assigns drafting, review, and approval to the appropriate organizational units, with review and approval by the quality control unit. That allocation includes changes to the written procedures. These are the regulation’s procedure-review responsibilities, not a substitute for explaining the technical basis of the sampling design.

Screen product and market scope before transferring the approach

Product or jurisdiction contextAuthority addressedApplication boundary
U.S. finished-pharmaceutical operations within Part 211’s scope21 CFR Part 211Apply the cited obligations to operations determined to be within scope; assess the sampling design separately.
Food, supplements, devices, and chemicalsGoverning product and market rulesDetermine the applicable framework before transferring this article’s U.S. drug-law discussion.
Other jurisdictionsRules governing the relevant product and marketDetermine local applicability rather than treating U.S. provisions as universal requirements.

This screening table is a practical applicability check, not a declaration that any listed sector is categorically covered or exempt. Keep two questions distinct during review: which authority governs the operation, and why the proposed sampling approach is appropriate for that operation.

03Read FDA guidance status separately from its stated scope

Draft status and stated topics

FDA’s Considerations for Complying with 21 CFR 211.110 is a draft, not for implementation, and contains non-binding recommendations. Its stated purpose is conditional: when finalized, it will describe considerations for complying with 21 CFR 211.110 to ensure batch uniformity and drug product integrity.

The draft’s summary also identifies quality considerations for drug products manufactured using advanced manufacturing and discusses how manufacturers can incorporate process models into commercial manufacturing control strategies. These are stated discussion topics—not a new mandatory review checklist for a stratified sampling plan.

PAT scope and practical design questions

The FDA PAT framework encourages voluntary development and implementation of innovation in pharmaceutical development, manufacturing, and quality assurance. Keep that purpose separate from a proposal to use a particular measurement technology or replace physical sampling. For related terminology, see PAT and real-time release.

As practical design questions—not FDA-listed required review elements—ask the following before assigning a process model or PAT measurement a role in the sampling strategy:

  • What quantity is measured, and how does it relate to the sampling question?
  • Which production interval does the measurement represent?
  • What decision would the measurement inform?

Record the answers in the proposed measurement strategy. If that proposal changes an existing strategy, use them to frame its change-control assessment. This keeps the proposal specific: a defined measurement representing a defined interval and informing a defined decision, rather than a general appeal to innovation.

04Define run strata, risk points, and sample allocation

The following is a practical design approach, not a prescribed regulatory sampling pattern. Start by defining the production population: which batch, which run or run segments, and which dosage units the plan is intended to represent. Specify whether an observation is an individual dosage-unit result or another explicitly defined measurement. Choose a primary coordinate that can be related to the units actually collected.

Choose a usable run coordinate

Possible coordinateDesign question
Cumulative unit countWhich counter defines the position, and how are rejected units handled?
Discharged massHow does the mass interval map to the dosage units collected?
Elapsed operating timeDoes the clock exclude stops, and how is collection time related to output?
Equipment positionWhich outlet, lane, or station produced the units, and what locates them along the run?

Record secondary coordinates when needed to resolve ambiguity. For example, equipment position alone may identify a collection location without distinguishing early from late production. Use consistent production context tagging to associate each collection with its planned run position.

Separate coverage from event questions

Define routine strata to cover the production population, then identify event-targeted collections separately. Candidate events include startup, a planned stop and restart, material replenishment, or a receiving-container change. Each needs a product-and-process rationale; this list neither ranks risks nor assumes that every event causes nonuniformity. Reference the relevant process event log entry when specifying the trigger.

  • Set each stratum’s start and end boundaries, including which stratum owns a boundary point.
  • Identify the intended physical collection point and its relationship to the primary coordinate.
  • Specify the selection rule within the stratum, such as a predefined position or a documented random selection.
  • For event-targeted sampling, define the trigger and the collection window relative to that event.

Several observations collected at one convenient moment represent that local window. Spreading observations across defined strata addresses different production positions. These designs therefore answer different questions, even when their total observation counts match.

Allocate units to a stated purpose

Distinguish the quantity collected, the quantity scheduled for testing, and any separately identified retained units. State whether allocation is intended to estimate within-stratum variation, compare strata, or examine a defined event. Base the proposed allocation on that decision question and available process information, considering the product and analytical method rather than applying a universal sample-count formula.

Finally, define what happens when routine and event-triggered windows coincide. Either collect separate observations or explicitly allow one collection to satisfy both purposes. If shared, identify both purposes without counting the same observation twice as independent evidence. Establish this convention before interpreting the dataset.

05Execute the plan from collection through review

Treat execution as a sequence of evidence handoffs, not simply a list of samples due. The following proposed lifecycle connects the sampling plan to the actual run and keeps collection, testing, interpretation, and decisions distinct.

  1. Identify the applicable plan version and map actual run boundaries against its defined strata. Preserve the planned boundaries alongside the execution record.
  2. Collect and identify dosage units. Record their actual coordinates using the plan’s position convention, retaining the link between each sample and its collection activity.
  3. Transfer identified samples for testing, carrying their identifiers into the testing record so results can be associated with their original strata.
  4. Assemble collection records, results, and relevant run events for interpretation and authorized review. Retain the resulting human decision with that evidence.

A scheduled collection describes intent; its execution record describes what happened. Compare planned position with actual position, collection time, operator identity, and an event reference linked to the process event log. If collection occurs after a restart or outside its intended interval, retain both positions rather than silently moving the original boundary. Keep this comparison in the batch execution history.

For applicable U.S. drug laboratory controls, 21 CFR 211.160(a) requires the requirements in that subpart to be followed and documented at the time of performance. That legal obligation is separate from the individual execution fields recommended here.

From defined population to accountable decision
  1. 1
    Define populationSet the batch boundary and observation unit.
  2. 2
    Specify StrataMap output segments and justified event triggers.
  3. 3
    Confirm planIdentify the applicable version and collection instructions.
  4. 4
    Collect unitsRecord identities, actual positions, and collection events.
  5. 5
    Associate ResultsLink measurements to samples and method versions.
  6. 6
    Assess evidenceExamine strata, interpretation rules, and unresolved exceptions.
  7. 7
    Record decisionAuthorized people document conclusions and required actions.
Illustrative evidence handoffs; authorized people retain decision responsibility.

06Keep the run, sample, result, and decision connected

For U.S. drug laboratory records, 21 CFR 211.194(a)(1) requires a description of the sample received for testing with identification of its source. The specified information includes source location (where the sample was obtained), quantity, lot number or other distinctive code, date sample was taken, and date sample was received for testing. Keep the two dates distinct during sample login handoff.

An illustrative linked-record model

The following six entities are a proposed traceability design, not a required database schema or a description of software capabilities. Their additional fields support interpretation rather than expand the sample-description list above.

EntitySuggested content and relationships
Plan VersionVersion identifier; stratum definitions and intended collection coordinates.
Run SegmentRun identifier, stratum identifier, segment boundaries, and relevant plan version.
SampleSample identifier; laboratory sample-description information; explicit run and stratum references; physical collection location and represented production coordinate.
Test ResultSample reference, numerical value, result units, method version, and underlying data reference.
ExceptionIssue description and retained references to affected segments, samples, results, or plan version.
Review DecisionBatch and plan-version references; records considered, decision, rationale, and authorised reviewer.

Keep provenance separate from represented output

Physical collection location answers “Where was this sample obtained?” The production coordinate answers “Which part of the run does it represent?” For example, a discharge sampling point identifies a place; a recorded output interval identifies represented production. Store both rather than using one location label for both meanings. This distinction makes production context tagging useful for stratified interpretation.

Likewise, retain units, method version, and the underlying data reference alongside each result. A numerical value alone does not communicate its analytical meaning. Link the review to the actual records considered so the decision remains connected to its batch and sampling design.

A proposed sampling evidence model

Plan Version

Defines the prospective sampling design.

  • plan_id
  • plan_version
  • status
  • strata_definition
  • decision_rule_id

Run Segment

Locates strata within actual production.

  • run_id
  • batch_id
  • stratum_id
  • start_unit
  • end_unit
  • event_id

Sample

Connects collected units with origin.

  • sample_id
  • run_id
  • stratum_id
  • collection_time
  • unit_count
  • sample_status

Test Result

Preserves analytical value and context.

  • result_id
  • sample_id
  • method_version
  • assay_value
  • assay_unit
  • data_reference

Exception

Links departures to affected evidence.

  • exception_id
  • run_id
  • sample_id
  • event_type
  • recovery_status

Review Decision

Associates conclusions with responsible people.

  • review_id
  • plan_id
  • plan_version
  • batch_id
  • decision
  • reviewed_by
  • reviewed_at
Illustrative relationships, not a mandated database schema.

07Three worked cases: coverage, restart, and unequal strata

All three cases are hypothetical designs using separately tested dosage units, not composite samples. Counts, production rates, and assay values are teaching assumptions—not recommended minimums or product specifications. The calculations illustrate coverage, event-specific collection, and weighting; they do not establish a sampling plan suitable for a particular product.

Case 1: Equal-output coverage

Assume 120,000 tablets produced at a constant 30,000 tablets per operating hour, without interruptions. Production takes 120,000 ÷ 30,000 = four operating hours, or 240 operating minutes. Divide the output into six equal-output strata: each contains 120,000 ÷ 6 = 20,000 tablets and spans 240 ÷ 6 = 40 operating minutes.

The first stratum covers units 1–20,000; the last covers units 100,001–120,000. Collecting and separately testing four units per stratum produces 6 × 4 = 24 routine observations. These boundaries define coverage intervals, not the exact collection positions of the four units within each interval.

Case 2: Add a planned interruption

Retain Case 1’s assumptions, but add a planned 20-minute stop at 48,000 tablets. Collect four additional units immediately before the stop and four after restart, with no overlap with routine collections. The event adds 4 + 4 = eight observations, bringing the total to 24 + 8 = 32.

The stop occurs after 48,000 ÷ 30,000 = 1.6 operating hours, or 96 operating minutes. During the stop, operating time remains at 96 minutes and cumulative output remains at 48,000 tablets, while elapsed wall-clock time advances to 116 minutes. With no other interruptions, completion takes 240 operating minutes but 260 elapsed minutes. In this design, the batch record would distinguish all three coordinates so that before-stop and after-restart observations remain identifiable despite the unchanged output count during the pause.

Case 3: Equal samples, unequal output shares

Assume a separate 100,000-tablet batch with three strata representing 10%, 80%, and 10% of output: 10,000, 80,000, and 10,000 tablets. Test five units separately from each stratum. Assume stratum means of 92%, 100%, and 102% of label claim.

The pooled mean of the 15 observations is (5 × 92 + 5 × 100 + 5 × 102) ÷ 15 = 98.0% of label claim. If each sample mean represents its own stratum’s output, the output-share-weighted estimate is 0.10 × 92 + 0.80 × 100 + 0.10 × 102 = 99.4% of label claim.

These answer different questions: the pooled mean gives each sampled unit equal weight and, here, each stratum equal influence; the weighted estimate reflects each stratum’s production share. Do not choose the more favorable number. Neither calculation supplies an acceptance decision for individual strata. The analysis question and weighting convention need an explicit basis.

08Interpret variability before assigning an acceptance decision

Percentage relative standard deviation (%RSD) is 100 × sample standard deviation ÷ sample mean, with both quantities on the same measurement scale. It describes spread relative to the mean; it does not, by itself, establish whether dosage units are acceptable.

For practical analysis, distinguish within-stratum spread among units collected in one run segment, between-stratum differences in segment means, and a pooled summary across sampled units. A pooled %RSD does not distinguish these patterns on its own. Read it alongside stratum-level results and run position, potentially using a batch SPC overlay. The unequal-strata case above explains why weighting also matters.

For applicable U.S. drug manufacturing, 21 CFR 211.110(b) requires valid in-process specifications for the relevant characteristics to be consistent with final drug-product specifications, derived from previous acceptable process-average and process-variability estimates where possible, and determined using suitable statistical procedures where appropriate. Those qualifiers matter when establishing the specification basis.

As a practical review framework, keep three concepts separately identifiable: specification limits, statistical summaries, and the reason for the review decision. A predefined decision rule explains how results will be evaluated; a descriptive statistic summarizes what was observed. Record which rule was applied rather than treating a low pooled %RSD as a substitute for the decision rationale.

09Reconcile system handoffs and recover sampling exceptions

For a proposed interface between production and laboratory records, use stable batch, run, sample, and result identifiers. In an MES-to-LIMS handoff, reconcile expected records against received records and flag unmatched entries for review. Distinguish a duplicate transmission of an existing result from a genuinely additional test: receiving the same message twice should not create two tests. These are interface-design recommendations, not claims about a named application.

For drug manufacturing subject to Part 211, 21 CFR 211.68(b) requires computer-system input and output of formulas, records, or data to be checked for accuracy. Treat that obligation separately from interface design; a software certification claim is not the required accuracy check.

Consider a missed planned collection window. Retain the planned collection entry with its missed status. If a sample is collected later, identify it by its actual run position through sample login, and route the effect on the intended stratified assessment to the designated reviewers. Do not relabel that later sample as coming from the missed interval. Restoring a record transfer cannot restore an uncollected sample or establish what that interval would have shown.

Under 21 CFR 211.160(a), deviations from written specifications, standards, sampling plans, test procedures, or other laboratory control mechanisms must be recorded and justified. Keep that regulatory duty distinct from the illustrative recovery approach above.

10Control collection and interpretation failures without overstating their frequency

These hypothetical scenarios support practical review of a stratified sampling plan; they do not indicate observed frequency. The proposed controls depend on the site's process and quality procedures.

Potential failureEvidence affectedProposed control
Restricted access to a planned collection pointCoverage of the intended run positionReview an alternative collection arrangement.
Damaged or compromised sample transportSuitability of the sample for testingAssess sample suitability with its handling record.
A reported result associated with the wrong method versionBasis for interpreting the resultReconcile the method version before interpretation.
Retrospective changes to stratum labelsOriginal relationship between sample and run positionPreserve the original stratum mapping alongside any reviewed amendment, with a traceable audit trail.

Use the exception process above to address these events; assess plan amendments through the site's change control process.

11Review the applicable controls and the complete sampling design

Binding U.S. drug requirement

For drug operations subject to Part 211, 21 CFR 211.160(a) assigns drafting to the appropriate organizational unit and review and approval to the quality control unit. This covers specifications, standards, sampling plans, test procedures, and other laboratory-control mechanisms required by the subpart, including changes to them. Include this approval obligation when designing the change-control process for the sampling plan.

Practical readiness checklist

The following is an implementation aid, not an FDA-issued list of mandatory review elements. Use the corresponding sections above for detail:

  • Identifiable plan version—sampling lifecycle.
  • Defined population and run coordinate—what the plan measures.
  • Justified strata and event triggers—sample-plan design.
  • Unambiguous collection and testing allocation—design and execution.
  • Linked sample and result records—evidence model and sample handoff.
  • Specified interpretation rules—variability and acceptance.
  • Documented route for unresolved exceptions—exception recovery.

Frequently asked questions

Q.Can an existing stratification plan be reused when the batch size or run length changes?+

Treat reuse as a documented assessment, not a proportional rescaling exercise. As a planning practice, compare the revised run with the original rationale: do sampling windows still cover the intended process stages and risk points? Record that assessment under change control, supported by process validation knowledge; the drafting and approval obligation for plan changes is covered in the implementation review section above.

Q.How should a short run be handled when planned sampling windows overlap?+

Overlapping windows in a short run follow the shared-observation rule set out in the sample-plan design section: one result is never counted twice as independent evidence. The question-specific step is to decide, before the run, which windows will be merged, record that decision in the plan, and make the sample pull prompt show merged windows separately from collections that must still be taken on their own.

Q.What should the record show when an event-triggered sampling condition never occurs?+

As a recording practice, distinguish “trigger did not occur” from “trigger occurred but the sample was missed.” Identify the trigger definition, the period monitored, and the observations supporting its absence. Reference the relevant process event log, rather than leaving an unexplained blank. If the plan specifies an alternative collection, record whether it occurred. Use contemporaneous recording to preserve the observation; absence of a trigger does not establish product performance under that unobserved condition.

Q.Can dosage units from parallel presses or filling lanes belong to the same stratum?+

As a design practice, they can share a stratum when the intended comparison and grouping rationale support that choice; a common batch identifier alone is not the rationale. Retain press or lane identity through production context tagging, even if the analysis groups results. Consider whether separate equipment settings, interruptions, or feed paths warrant separate strata. Linking each sample to its equipment module preserves the option to examine equipment-specific patterns without reconstructing sample origins later.

Q.What information should accompany samples sent to a contract laboratory?+

As a handoff practice, send identifiers that connect each container to the product, batch, dosage form, stratum, collection point, and collection time or run position. State the requested test, method version, reporting units, and whether results are needed for individual dosage units. Include applicable storage and handling instructions and identify the contact for discrepancies. A structured sample login handoff should let the laboratory preserve the sampling design rather than infer it from container labels.

Q.How should a result reported in a different measurement unit enter the analysis?+

Keep the reported value and unit, then document any conversion to the analysis unit. For drug laboratory records, 21 CFR 211.194(a)(5) requires calculation records including units of measure, conversion factors, and equivalency factors. For example, assuming both values express analyte mass per tablet, 0.025 g/tablet × 1,000 mg/g = 25 mg/tablet. This does not establish percentage of label claim without the label-claim denominator. As a review practice, preserve the conversion alongside the result entry.

Q.How should a generic sampling template be adapted to a new product and process?+

Use the template as a structure, not as evidence that its strata suit the new process. As a design practice, replace generic windows with product-specific collection points, process stages, trigger definitions, sample identities, and analysis rules. Explain each selection using relevant process knowledge and the quality risk register. For drug laboratory controls, 21 CFR 211.160(b) requires scientifically sound and appropriate sampling plans and test procedures; copying a template does not itself demonstrate that basis.

Q.What can additional samples establish after a concerning result, and what remains unresolved?+

As an investigation practice, additional samples can characterize the units, locations, or periods they represent and help test a stated explanation. They do not, by themselves, invalidate the original result or establish the condition of unsampled units. Define the question before collecting more material. For drug products, 21 CFR 211.192 requires thorough investigation of unexplained discrepancies and specification failures. Keep additional testing within the OOS investigation, where applicable, rather than treating satisfactory follow-up results as an automatic resolution.

Primary sources

  • FDA draft guidance: Considerations for Complying With 21 CFR 211.110
  • eCFR 21 CFR Part 211
  • FDA PAT framework guidance
Software that covers Blend Uniformity & Stratified Sampling
V5 Ultimate (GMP)
V5 Ultimate is a full-lifecycle GMP platform for US and international manufacturers — cGMP under 21 CFR 210/211, EU GMP Parts…
Talk to us about Blend Uniformity & Stratified Sampling

Want to see how Blend Uniformity & Stratified Sampling could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.

Start free
Back to glossary
Where this term comes up
PharmaceuticalDietary Supplements
Inside V5
  • → Lab & QC — results against the limit, reviewed by a second person.
  • → eBMR / eDHR — the batch record fills in as the work is done.
  • → QMS — quality records next to the work they concern.
Example reports
V5Ultimate

Sample report

Electronic Batch Manufacturing Record (eBMR)

Plan & make

Electronic Batch Manufacturing Record (eBMR)View on screen or print
V5Ultimate

Sample report

Electronic Device History Record (eDHR)

Plan & make

Electronic Device History Record (eDHR)View on screen or print
V5Ultimate

Sample report

Item QC Specification

Test & release

Item QC SpecificationView on screen or print
V5Ultimate

Sample register

Sampling plans register (CSV)

Test & release

Sampling plans register (CSV)Download CSV
→ All example reports
Regulatory anchors
  • 21 CFR 211.110
  • ASTM E2709
  • ASTM E2810
  • USP <905>
Related terms
  • → Content Uniformity
  • → Potency Factor
  • → Weigh and Dispense
  • → Assay-Adjusted Charge

Next Step

Try V5 with your own records, or ask a question first. Ask V5 opens with an editable question; nothing is sent until you choose to.

Start your free trial Browse All Features

Showing the site for the United States. Local spelling, dates and prices are applied automatically; change the language at the top of the page.

V5 Ultimate
Ultimate

Warehouse, quality and manufacturing software for regulated operations.

ProductIndustriesPricingResourcesSecurity & TrustCompanyLegal Centre

© S.G. Systems, LLC