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
HomeGlossaryRFT
Quality · The complete guide

Right First Time (RFT): Definition, Calculation and Batch-Level Use

In short

A practical guide to defining first-pass success, calculating batch-level performance and using production evidence without confusing a metric with product release.

4,067 words · ~19 min read
Right First Time (RFT): a gowned supervisor checks batch completion status on a tablet beside a bottle line
Right First Time measures work completed correctly without deviation, rework or retest.
On this page
  1. 01What RFT actually counts
  2. 02Define eligibility, failure rules and the reporting cutoff
  3. 03RFT vs FPY, final yield and related measures
  4. 04Calculate RFT: three worked batch-level cases
  5. 05Follow RFT from execution to reviewed reporting
  6. 06Map pharmaceutical duties without turning RFT into law
  7. 07Build a traceable RFT evidence model
  8. 08Separate failure categories from causes
  9. 09Use RFT trends without overstating prediction
  10. 10Reconcile interfaces and recover reporting exceptions
  11. 11Common RFT findings and practical controls
  12. 12Checklist for implementing and reviewing batch RFT
On this page · 12 sections
  1. 1What RFT actually counts
  2. 2Define eligibility, failure rules and the reporting cutoff
  3. 3RFT vs FPY, final yield and related measures
  4. 4Calculate RFT: three worked batch-level cases
  5. 5Follow RFT from execution to reviewed reporting
  6. 6Map pharmaceutical duties without turning RFT into law
  7. 7Build a traceable RFT evidence model
  8. 8Separate failure categories from causes
  9. 9Use RFT trends without overstating prediction
  10. 10Reconcile interfaces and recover reporting exceptions
  11. 11Common RFT findings and practical controls
  12. 12Checklist for implementing and reviewing batch RFT
AI · Explain it for MY operation

How does RFT 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 RFT actually counts

Right First Time (RFT) is the percentage of eligible batches or work items that meet predefined completion criteria on the first attempt, without disqualifying errors, deviations or rework. It is an operational metric, not a regulatory term. The definition and counting conventions used here represent industry practice, separate from the pharmaceutical requirements mapped later in this article.

The counting unit can be a batch, an operation or a record package. A reported percentage must name that unit: “batch RFT” and “record-package RFT” answer different questions, even when they draw on the same manufacturing activity. An operation-level result does not, by itself, establish whole-batch performance.

  • Execution RFT asks whether the manufacturing work met its first-attempt criteria. The batch execution history provides context for assessing what happened during processing.
  • Documentation RFT asks whether the associated records met their first-submission criteria without disqualifying corrections or returns. This is a distinct assessment, including when records form an electronic batch record.
  • Combined batch RFT can require both execution and documentation to pass, provided the metric’s written rules explicitly establish that condition.

A batch can fail RFT and subsequently become acceptable after appropriate resolution; that does not erase its first-attempt failure. Conversely, an RFT pass is not a batch-release decision. RFT describes first-attempt performance; authorised people retain responsibility for approval and release.

02Define eligibility, failure rules and the reporting cutoff

Write a metric definition before counting batches. The controls below are recommended operational practice, not prescribed regulatory RFT rules.

  • Specify the unit of analysis: for example, one manufacturing batch rather than each operation or packaged lot.
  • Name the process start and endpoint, cohort membership rule, reporting cutoff and metric-definition version. For example, group batches by endpoint date, then assess their status at a stated cutoff.
  • Record distinct statuses: process incomplete; process complete but assessment pending; assessed pass; assessed fail.

Define first-attempt success against the established execution sequence and its acceptance criteria. Planned repeated operations belong to that sequence; corrective repetitions recover an unsuccessful attempt. Being planned does not make an operation acceptable: its execution and results must still meet the metric’s criteria.

Adopt an explicit event-classification matrix. This illustrative policy separates RFT treatment from quality significance; assess quality impact independently.

Event categoryExample local RFT rule
Procedure departureFail for departure from the established execution sequence.
ReworkFail when corrective processing is needed.
Record correctionFail for substantive correction; allow defined clerical corrections.
Missing informationPending while evidence is sought; fail if required evidence remains absent at assessment closure.
Other locally selected eventsList each category, threshold and pass/fail treatment before reporting.

Set treatment of cancelled work and development runs in advance. For split batches and merged lots, specify whether parents or resulting lots count, preventing duplicate contributions. Retain excluded records with reasons; do not remove inconvenient outcomes.

Report incomplete work separately from completed batches awaiting assessment. Show pending assessments explicitly and label any assessed-only result provisional.

Keep denominator changes versioned through documented change control, with effective dates and affected cohorts. A tighter definition can lower reported RFT without proving execution worsened; identify definition changes alongside trend breaks.

03RFT vs FPY, final yield and related measures

These are operational conventions, not regulatory definitions. Some organisations use RFT and FPY interchangeably, so the local definition matters more than the label. For this article, first pass yield (FPY) means units passing a specified operation on their first attempt divided by units entering that operation. Batch RFT instead counts batches and can include execution and record-package conditions.

MeasureCounting unit and boundaryTypical calculationTreatment of recoveryWhat it helps explain
Batch RFTBatch; defined execution and review scopeQualifying first-time batches ÷ eligible batches × 100%Does not erase a first-attempt failureBatch-level execution and documentation reliability
First pass yieldUnit; specified operationFirst-attempt passing units ÷ entering units × 100%Recovered units excluded from first-pass numeratorOperation-level first-attempt performance
Final accepted-unit yieldUnit; defined process boundaryFinally accepted units ÷ units introduced × 100%Includes recovered units ultimately acceptedFinal usable output
Material yieldMass or quantity; explicit, comparable basisOutput quantity ÷ input quantity × 100%Recovered output counts within the stated basisMaterial conversion or loss
Rolled throughput yieldDefined sequence of stagesProduct of stage FPY fractions × 100%Stage recovery does not restore first-pass statusCombined first-pass performance across stages

Final accepted-unit yield tracks units, whereas material yield needs a stated mass or quantity basis. Label any theoretical-versus-actual yield comparison separately. Recovery can improve final accepted output without changing what happened on the first attempt.

For rolled throughput yield, align stage boundaries and populations. Multiplying unrelated monthly percentages does not establish an observed batch-level result; that needs linked batch or unit histories.

04Calculate RFT: three worked batch-level cases

RFT (%) = first-pass successful eligible items divided by all assessed eligible items, multiplied by 100. For a final cohort result, all eligible items must have an assessment under the chosen reporting convention. The hypothetical cases below use batches as the RFT counting unit; their failure rules are operational assumptions, not regulatory thresholds.

Case 1: Count failed batches, not failure events

Assume one monthly cohort contains 50 eligible, fully assessed batches. Five have disqualifying rework, four have disqualifying record corrections, and two appear in both groups. These are the only disqualifying categories in this example.

  • Unique failed batches = 5 + 4 − 2 = 7.
  • Successful batches = 50 − 7 = 43.
  • RFT = 43 ÷ 50 × 100 = 86%.

Subtracting nine category entries from 50 batches would count the overlap twice. Event counts cannot be subtracted directly from batch counts: multiple disqualifying events on one batch produce one failed batch in this binary metric. Use batch identifiers in the batch execution history to deduplicate the affected population.

Case 2: Keep three measurement boundaries separate

Assume 20 fully assessed batches contain 500 units each: 20 × 500 = 10,000 units. At the selected operation, 9,400 units pass initially and 600 require rework across two batches. Rework recovers 500 units; 100 are scrapped. One additional batch has only a disqualifying documentation correction. There are no other disqualifying events.

  • Operation-level unit FPY = 9,400 ÷ 10,000 × 100 = 94%: units passing initially at the selected operation.
  • Final accepted-unit yield = (9,400 + 500) ÷ 10,000 × 100 = 99%: accepted units after recovery.
  • Combined batch RFT = 17 ÷ 20 × 100 = 85%: batches passing both the manufacturing and documentation rules.

The two rework batches and the separate documentation-only batch give three distinct failed batches. First pass yield, accepted-unit yield and combined batch RFT answer different questions; these percentages are not interchangeable results.

Case 3: Report pending assessments explicitly

Assume 36 eligible batches have reached the process endpoint at cutoff. Of these, 32 are assessed: 28 pass and four fail. Another four remain pending.

  • Provisional assessed-batch RFT = 28 ÷ 32 × 100 = 87.5%.
  • Assessment coverage = 32 ÷ 36 × 100 = 88.9%, rounded to one decimal place.

When the four pending batches resolve as two passes and two failures, the completed-cohort result becomes 30 ÷ 36 × 100 = 83.3%, rounded to one decimal place. Preserve the original cutoff snapshot with its pending count and coverage. Identify the later figure as the updated, completed-cohort result rather than silently replacing the provisional report.

Case 4: No eligible assessed batches

Assume a new product line closes its first month with three batches started and none yet through the process endpoint and assessment. The denominator is zero, so RFT is not calculable for that period. Report it as “not calculable (0 assessed of 0 eligible)” rather than 0%, because 0% would assert that every batch failed when none has been judged. The same rule applies to a filtered view, such as one product on one line, that contains no assessed batches.

Treat very small denominators with similar care: one failure in two batches gives 50%, which says far more about the sample size than about the process. Show numerator and denominator beside the percentage, and consider rolling cohorts once each period has too few batches to support a comparison; the FAQ on months with only a few assessed batches gives a worked example.

05Follow RFT from execution to reviewed reporting

Use this proposed operational workflow to connect batch evidence to a reproducible RFT snapshot, rather than assigning a score at execution close.

  1. Select the applicable metric definition and retain its version with the assessment.
  2. Identify cohort membership using the agreed eligibility rules; record why the batch belongs in the reporting period.
  3. Capture execution evidence in the batch execution history, retaining batch, operation and event identifiers.
  4. Connect exception records to their originating events. Keep the production event, its quality-system handling and its RFT classification as separate, linked records.
  5. Assess the batch against the selected rules, recording the assessor, decision time and rationale.
  6. Reconcile the reporting population against the cohort list, checking missing batches, duplicates and unresolved assessments before calculating the result.
  7. Publish the reviewed snapshot with its cutoff, definition version, population counts and unresolved-status treatment.

Retain three distinct timestamps: when the event occurred, when it was entered and when its RFT assessment was made. A process event log can organise this chronology. The reporting cutoff selects a snapshot; it cannot reveal delayed entry or later assessment and therefore cannot replace those timestamps.

Route classification disagreements to a named Metric Classification Review, assigning an owner and recording the resolution rationale. Keep unresolved disagreements visible, never silently passed. Batch disposition remains outside the metric calculation, as covered above; authorised people retain release decisions.

From batch evidence to an RFT snapshot
  1. 1
    Select rulesIdentify the applicable metric definition and its version.
  2. 2
    Identify cohortApply the population boundary before observing individual outcomes.
  3. 3
    Capture evidenceAssociate execution records and exceptions with batch identifiers.
  4. 4
    Assess batchesRecord pass, fail or pending with supporting reasons.
  5. 5
    Reconcile populationResolve duplicate, missing and unmatched reporting records.
  6. 6
    Publish SnapshotShow RFT, assessed counts, pending counts and cutoff.
  7. 7
    Review patternsSelect evidence-based improvement questions and track subsequent changes.
Keep execution evidence, reporting assessment and authorised batch disposition as separate decisions.

06Map pharmaceutical duties without turning RFT into law

Use RFT as a local operational metric, not as a regulatory definition or release criterion. The pharmaceutical provisions below establish procedure, review, investigation and validation expectations; they do not establish an RFT calculation. Keep those source-stated expectations separate from decisions about how records contribute to the metric.

Jurisdiction or product contextSource and categorySource-stated duty or guidancePossible RFT evidence connection
US drug-product operations governed by Part 21121 CFR 211.100(a) — binding regulationWritten production and process-control procedures, including changes, must be drafted, reviewed and approved by the appropriate organisational units, and reviewed and approved by the quality control unit.Link the batch assessment to the applicable procedure version and relevant change control records.
US drug-product operations governed by Part 21121 CFR 211.100(b) — binding regulationProduction and process-control procedures must be followed, with documentation at the time of performance. Separately, deviations from written procedures must be recorded and justified.Use execution documentation and deviation records as distinct inputs to the local classification, rather than treating a completed record as proof of first-time success.
US drug-product operations governed by Part 21121 CFR 211.192 — binding regulationAll drug-product production and control records, including packaging and labeling records, require quality-control-unit review and approval for compliance with established, approved written procedures before release or distribution. Unexplained discrepancies—including theoretical-yield percentages outside master-record limits—or specification failures involving a batch or its components require thorough investigation, even after distribution. Investigations must extend to potentially associated batches of the same drug product and other drug products. A written investigation record must include conclusions and followup.Connect review and investigation outcomes to the affected batch assessments. Keep the RFT classification separate from the authorised batch-release decision.
European pharmaceutical manufacturingEudraLex Volume 4 Annex 15, section 5.1 — official guidanceSection 5 applies to manufacture of all pharmaceutical dosage forms. It covers initial validation of new processes, subsequent validation of modified processes, site transfers and ongoing process verification.Identify the process lifecycle context when comparing RFT results; do not present the metric as a substitute for validation evidence.

Check the current text of ICH Q10 for the scope of its continual-improvement guidance.

For supplements, food, devices and industrial chemicals, this RFT framework is operational practice. Apply the rules for the actual product and jurisdiction rather than extending the pharmaceutical rows to every manufacturer. A shared batch record reporting structure does not make the underlying legal duties identical.

Mapping records into RFT categories stays a local reporting decision; regulatory duties follow their own triggers.

07Build a traceable RFT evidence model

A proposed RFT reporting dataset can use five linked entities. Its purpose is to reproduce each batch classification and reported percentage, not to duplicate the quality records supporting them.

EntityFields and relationships to preserve
Metric definitionDefinition ID and version; eligibility, disqualification and pending-treatment rules; effective period.
BatchStable batch identifier, product, site and relevant lifecycle dates. Use consistent identifiers for joins and production context.
Exception eventEvent ID, affected batch IDs, source-record reference and relevant revision; separate reporting category, quality significance and cause classification.
Batch assessmentAssessment ID, batch identifier and definition version; passing, failing or pending status; assessment time and assessor; linked disqualifying events and failure reason. Record eligibility separately, with an explanation for exclusions.
Reporting snapshotSnapshot ID, definition version, cohort rule, cutoff, assessed population and denominator used, passing count, pending count, and the exact assessment IDs included.

Use production context tagging to organise batch, product and equipment references. Every disqualifying event should resolve to its source record: a free-text dashboard label alone cannot show which record supported the classification.

For example, an event linked to out-of-specification handling may carry a reporting category while its cause remains undetermined. Do not turn that category into a root-cause conclusion.

Snapshot versioning follows Case 3 above; the model adds the links that let a reviewer run from the reported percentage back to each batch classification and its supporting event.

A proposed RFT reporting dataset

Metric Definition

Versioned counting rules.

  • definition_id
  • version
  • unit_of_analysis
  • cohort_rule
  • failure_rule
  • effective_from

Batch

Production context and endpoint.

  • batch_id
  • product_id
  • process_revision
  • completed_at

Exception Event

Traceable event evidence.

  • event_id
  • batch_id
  • event_type
  • occurred_at
  • source_record_id

Batch Assessment

Classification against defined rules.

  • batch_id
  • definition_id
  • rft_status
  • assessed_at
  • assessor_id

Reporting Snapshot

Reproducible cohort result.

  • snapshot_id
  • cohort_id
  • cutoff_at
  • passed_count
  • assessed_count
  • pending_count
Linked records preserve measurement rules, batch evidence, assessment decisions and calculation history.

08Separate failure categories from causes

As an improvement practice, treat RFT failure categories as investigative starting points, not root causes. Unclear instructions, unsuitable work sequencing, equipment conditions and material variability are hypotheses to evaluate against batch evidence—not universal explanations for low RFT.

Observed RFT failureEvidence to examinePossible control to evaluate
Repeated record correctionOriginal entries, instruction versions, correction reasonsClearer work instructions
Execution sequence departureStep timestamps, dependencies, operator observationsRevised sequencing or prerequisite checks
Corrective processingProcess trends, equipment logs, material-lot differencesEquipment checks or material controls
Recurring handoff errorTransfer records, status changes, responsibility boundariesExplicit handoff acceptance checks

Keep failed-batch counts, event counts and event severity separate. One failed batch may contain several events; neither count establishes their consequence. Examine whether recurring categories share a mechanism before combining them into one improvement project.

Prioritise work using recurrence, consequence and the strength of causal evidence—not the largest event count alone. Use gemba observation to test explanations against actual work, then evaluate whether the proposed control addresses the supported cause.

09Use RFT trends without overstating prediction

Batch RFT describes work already performed. As industry practice, its trend can help prioritise attention before later operational problems, but it does not by itself establish causation, demonstrate process control or predict product quality. Treat a recurring loss as a question to investigate, not a forecast.

  1. Identify a recurring RFT loss in a comparable group of batches.
  2. Examine the supporting records to test possible explanations.
  3. Select a change, using change control where appropriate.
  4. Define the expected effect and the comparison period before assessing success.
  5. Compare later performance under a consistent metric definition; record whether the evidence supports the expected effect.

Before attributing a trend to the intervention, check whether product mix, a process revision or reporting rules changed. Compare like-for-like groups where those differences could explain the result.

For management review, pair RFT with assessed and pending batch counts, event severity, recovery burden such as additional labour hours, and relevant output measures such as yield or throughput. A higher percentage should not conceal fewer assessments, more serious events or greater recovery effort.

10Reconcile interfaces and recover reporting exceptions

A practical RFT integration design separates three responsibilities: production records establish batch context, quality records identify relevant events, and a reporting layer applies versioned metric rules. Define the handoff through MES–QMS integration rather than letting each interface interpret RFT independently.

Use shared batch identifiers and retain source-system and source-record identifiers. Specify timestamp conventions, including time zone and the distinction between event time and import time. Maintain explicit mappings from source statuses to reporting statuses; an unfamiliar status should trigger review, not a default pass. Consistent production context tagging helps associate events with the correct batch.

Route duplicate imports, unmatched events, conflicting identifiers, delayed records and failed transfers into an exception queue with an assigned owner. Prevent duplicates from contributing twice. Reconcile source records against imported records and reported batch classifications, checking both completeness and identity. A reporting-interface failure is not itself a manufacturing RFT failure, but missing data must not silently become a passing batch. Use the pending-assessment treatment illustrated in the worked case above.

After recovery, reprocess the affected reporting data under the snapshot rule from Case 3 and record which classifications changed and why.

11Common RFT findings and practical controls

Use these analytical examples to diagnose measurement weaknesses, not as a list of reported inspection findings. The controls apply the definition, calculation and integration disciplines discussed above.

FindingWhy the result becomes misleadingControl
Counting only successful or released batchesUnsuccessful or pending work disappears from the denominator.Reconcile the cohort against the original population rule defined above.
Counting several events as several failed batchesOne batch contributes multiple failures.Aggregate disqualifying events by the declared unit of analysis, as in the calculation examples.
Removing the initial failure after recoveryRecovery rewrites first-attempt performance.Keep current acceptability, represented by the disposition code, distinct from first-attempt history.
Silently changing correction categories or exclusionsA rule change appears to be operational improvement.Version the definition and identify breaks in comparability.
Combining batch, unit and material percentagesDifferent denominators imply a false equivalence.Display the counting unit and denominator alongside every measure, including FPY and material yield.
Treating absent interface data as successMissing evidence becomes an apparent pass.Report unresolved records and assessment coverage; use the integration reconciliation described above.
Treating a high percentage as sufficient quality evidenceAn aggregate score hides batch-specific questions.Retain the separate evidence and authorised decision processes described above.

During metric review, trace a sample of reported classifications back to batch and event records. Investigate discrepancies in the reporting logic before interpreting a movement in RFT as process improvement.

12Checklist for implementing and reviewing batch RFT

Use this practical acceptance checklist before issuing an RFT report and when revising the metric. It is not a regulatory checklist or assurance of compliance.

  • Assign a named metric owner, document the definition, and identify who resolves classification disagreements and records the decision.
  • Confirm explicit cohort rules, process boundaries, failure categories, exclusions, reporting cutoffs and treatment of pending assessments.
  • Test calculations against known examples covering overlapping events, recovered work and delayed assessments; retain expected and actual results.
  • Trace sampled passing and failing classifications to underlying records, including relevant entries in the process event log.
  • Reconcile batch and event counts between source systems and the reporting dataset; explain unmatched records and duplicates.
  • Keep definition versions, individual classification changes and reporting restatements distinguishable, with reasons and effective dates.
  • At management review, present population size, evidence completeness and companion measures alongside RFT; identify limitations affecting interpretation.
  • Choose the next improvement question, assign an owner and specify its evaluation method. Where linked to CAPA, define the effectiveness check rather than adopting an unsupported universal RFT target.

Frequently asked questions

Q.Who should decide whether a minor documentation correction disqualifies a batch?+

For metric governance, assign the decision to a designated quality representative working with the RFT metric owner, rather than leaving it to individual reviewers. Agree examples before reporting starts: an immediately corrected transcription error might be treated differently from missing evidence of an operation. Record the classification and rationale against the batch record. Apply the same rule consistently and review disputed cases together. This operational classification should remain separate from the authorised batch release decision.

Q.Should supplier-caused failures count in a site's RFT result?+

For an end-to-end site metric, count supplier-caused failures when they affect an eligible batch and meet the agreed failure criteria. Tag supplier attribution separately rather than removing the batch to improve the headline result. A secondary controllable-loss view can support local improvement, provided its exclusions are explicit. Use lot genealogy to connect affected batches with the relevant material lots, and scrap reason coding where scrap occurs. Keep uncertain attribution visible until the cause is established.

Q.How should RFT be introduced during a product launch or technology transfer?+

Introduce RFT as a learning measure with predefined eligibility rules, not an immediate comparison with mature production. Separate development, validation and routine commercial cohorts; use early failures to refine training and instructions through change control. For pharmaceutical validation, EU GMP guidance in Annex 15, paragraph 5.10 says process knowledge should be accessible to the manufacturing site, unless otherwise justified, and underpin validation activities. RFT can help organise learning, but is not a substitute for process validation.

Q.Can two sites compare RFT when their product mixes and batch sizes differ?+

Yes, but compare matched groups before ranking headline percentages. Align counting units, assessment endpoints and failure rules, then separate products by relevant complexity, process route and maturity. A batch-count metric gives a small batch the same weight as a large one; any mass-weighted measure should have a different label. Use batch comparison to examine comparable groups and production context tagging to identify mix differences. If an adjusted aggregate is needed, disclose the common weights and show unadjusted results alongside it.

Q.How should a month with only a few assessed batches be reported?+

Show the numerator and denominator beside the percentage. Assuming four eligible, fully assessed batches and three qualifying first time, report 3/4 batches, or 75% RFT. One additional failure among those four would change the result to 50%, illustrating the sensitivity of a small denominator. Mark the month as low volume and show a longer pooled period, calculated from total qualifying batches divided by total assessed batches, not an average of monthly percentages. Discuss the uncertainty in management review.

Q.How can continuous manufacturing define an RFT counting unit?+

For operational reporting, define a repeatable unit such as a fixed production interval or specified quantity of output, with clear start, end and assessment boundaries. State how startup, shutdown, diverted material and interruptions affect eligibility. Connect each unit to its process event log, so a failure cannot disappear through a convenient boundary change. Freeze the rule before calculating results and prevent overlapping units. This reporting unit is a metric convention, not a replacement for the applicable product or batch definition.

Q.When is step-level RFT more useful than a single batch-level percentage?+

Use step-level RFT when the batch result identifies a problem but not where improvement is needed. Define an eligible execution of each operation and count whether it met that step's first-time criteria. This can distinguish recurring documentation problems at dispensing from execution problems at packaging. Keep denominators visible because not every batch follows every route. Do not average step percentages to obtain batch RFT: several step failures may belong to one batch, while other batches have none.

Q.What risks arise when RFT targets are tied to individual bonuses?+

Individual bonuses can create incentives to delay reporting, relabel failures as minor corrections, avoid difficult work or pressure reviewers. Treat these as incentive-design risks, not proof of misconduct. Prefer team improvement goals balanced with reporting quality, recurrence and verified corrective-action results. Check whether a rising RFT result coincides with fewer reported problems but unchanged losses or complaints. Use a separate CAPA effectiveness check to test whether causes were addressed, and keep reviewers independent of the employee's bonus outcome.

Primary sources

  • eCFR 21 CFR Part 211
  • EudraLex Vol 4 Annex 15 (2015)
Software that covers RFT
V5 Ultimate (NCR / MRB)
V5 Ultimate opens a nonconformance record the moment a step fails, routes the Material Review Board, signs the disposition…
V5 Ultimate MES Software
V5 takes planned work orders to a kiosk at the line. Operators follow the configured steps, record weights and checks, and sign.…

Explore this topic

RFT sits inside this topic cluster in our glossary. Every neighbour is one click away.

Quality Tools & Investigation
26 related entries

Root-cause toolkit, SPC, capability and the rest of the QA practitioner's bench.

CAPANCRDeviationOOSOOTRoot Cause Analysis5 Whys8DFMEAFishbone / IshikawaRisk MatrixSPCCp / CpkPp / PpkMSAGage R&RAQLFPYYield ReconciliationSMEDOEEAudit ManagementISO AuditCustomer ComplaintSupplier ScorecardSupplier Risk Management
Talk to us about RFT

Want to see how RFT 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
Inside V5
  • → Score your compliance gap — then download the validation pack.
  • → Document control — one version in force, every change signed and explained.
  • → QMS — quality records next to the work they concern.
Related terms
  • → FPY
  • → Yield Reconciliation
  • → NCR
  • → Deviation
  • → CAPA
  • → OOS
  • → OOT
  • → Root Cause Analysis
  • → 5 Whys
  • → 8D
  • → FMEA
  • → Fishbone / Ishikawa
  • → Risk Matrix
  • → SPC
  • → Cp / Cpk
  • → Pp / Ppk
  • → MSA
  • → Gage R&R

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