Ask a plant manager how long it takes to make a batch and you will get the processing time: a number measured in hours. Ask how long from the moment raw materials are dispensed to the moment that batch is released for sale, and the honest answer is measured in days — often 12 to 18 of them for a mid-complexity product, against a best-in-class benchmark of 3 to 5 days. The gap is not processing. The drug spends the overwhelming majority of its end-to-end life doing nothing at all: sitting in quarantine waiting for QC, waiting in a queue for batch record review, frozen on hold while a minor deviation gets investigated, waiting for a QA signature that requires three people to be in the same room. Value-added time — the actual mixing, granulating, compressing, filling — is a thin sliver of the whole. Everything else is dwell. The reason most plants cannot fix it is that they cannot see it: their cycle-time data lives in the MES for processing, the LIMS for testing, the QMS for deviations, and a spreadsheet for everything in between. iFactory stitches those clocks into one continuous timeline so you can finally see where the days actually disappear — and start getting them back.
End-to-End Batch Cycle Time
Where the Days Disappear in a Pharma Batch
Your batch processes in hours but releases in weeks. The difference is waiting — QC queues, record review, deviation holds. iFactory exposes the full timeline and shrinks the dwell, not just the processing.
12-18
Days: typical mid-complexity release
3-5
Days: best-in-class benchmark
60-70%
Right-first-time on paper records
<10%
Of cycle is value-added processing
Sources: ISPE Pharma 4.0 Framework · BioPharm International · GMP Pros Batch Review Benchmarks · FDA 21 CFR 211.192 · iFactory Deployment Data 2026
The Iceberg Under Your Cycle Time
When operations reports "batch cycle time," it almost always means the part above the waterline — the processing everyone can see and schedule. The release clock, the part that actually decides when product reaches the market and revenue is recognized, is mostly submerged. Quality waiting, testing queues, and review backlogs are where two-thirds of the calendar lives, and they rarely show up on the production dashboard at all.
Visible · What ops tracks
~1-2 days of actual manufacturing
RELEASE CLOCK STILL RUNNING
Hidden · Where the days go
QC sampling & testing queue
Batch record review
Deviation / OOS hold
QA release & QP signature
10-16 days of mostly waiting
The Four Places Days Quietly Pile Up
Every long cycle is the sum of four dwell pools. None of them are processing problems — they are flow and visibility problems. Each one looks small from inside its own department and enormous when you finally lay the whole timeline end to end.
01
QC Sampling & Testing Queue
The batch is made, sampled, and then waits its turn in the lab. Test runtime is short; the queue in front of it is not. Samples sit while the lab clears backlog, instruments free up, and analysts rotate.
Root cause: lab capacity treated as a black box, no live queue visibility
QA reviewers spend the first days of review just gathering data — pulling records from disconnected systems, chasing logbooks, waiting on instrument data that should have arrived automatically. Analysis only starts once everything is assembled.
Root cause: fragmented records across MES, LIMS, QMS, and paper
A single minor deviation can freeze a batch for days. When data is scattered, investigation teams spend most of their time finding information rather than reasoning about it. The deviation stays open, the batch stays on hold, days become weeks.
Root cause: investigation = data archaeology, not analysis
04
QA Release & QP Signature
Release is a team effort across QA, QC, and production with no single owner of the clock. The final sign-off waits on the slowest input, and nobody is watching the calendar between hand-offs.
Root cause: no owner of end-to-end flow time
Want to see which of these four pools is eating the most calendar in your plant? Book a 30-minute cycle-time teardown on a sample of your real batches.
Value-Added vs Waiting — The Brutal Ratio
Lean practitioners call it process cycle efficiency: value-added time divided by total lead time. In a discrete factory a good number is 25%. In pharma batch release it is frequently under 10% — meaning more than nine out of every ten calendar days a batch is alive, it is adding no value and earning no revenue. This is the single most important chart in the whole conversation.
Why You Can't Fix What You Can't See
The reason these days survive year after year is that no single system owns the end-to-end clock. Processing time lives in the MES. Test results live in the LIMS. Holds live in the QMS. The gaps between them — the actual dwell — live nowhere. iFactory's job is to own that timeline, stitching every system's timestamps into one continuous batch lifecycle.
Question
Siloed Systems Today
With iFactory Batch Timeline
How long did this batch really take?
Pieced together from four systems by hand
One timeline, dispense to release, live
Where is it stuck right now?
Whoever shouts loudest finds out first
Current dwell pool flagged in real time
Which step adds the most delay?
Anecdotal, argued at the release meeting
Ranked by measured dwell across all batches
Is this batch about to miss target?
Discovered when it already has
Predictive alert before the deadline slips
Did our improvement actually work?
Felt faster, no number to prove it
Trended cycle time, before and after
From 14 Days to 6 — Same Product, Same Quality
A representative mid-size sterile injectable maker, three product lines, a release target of 7 days and an actual average of 14 — every single cycle. The product was consistent and yields were strong. The delay was entirely flow: QA spent the first three days of every review just pulling data. Here is what changed once the timeline became visible.
Before · Siloed
End-to-end cycle14 days avg
Data gathering in review~3 days/batch
Right-first-time~65%
On-time releaseRarely hit target
Quality consistent, yields strong — the loss was pure waiting.
After · Unified
End-to-end cycle~6 days avg
Data gathering in reviewNear-zero, auto-assembled
Right-first-time90%+
On-time releaseTarget met consistently
More than half the calendar back — without touching the process.
What Working on the Whole Clock Returns
40-60%
Cycle time reduction from flow, not speed
Days
Of review data gathering eliminated
Live
Position of every batch on one timeline
90%+
Right-first-time with electronic records
Frequently Asked Questions
Isn't most of our cycle time fixed by the chemistry and the testing?
The processing and the actual test runtimes are largely fixed — but they are a small fraction of the end-to-end cycle. In a typical 12-18 day release, value-added processing is often under 10% of the calendar. The rest is queue, review, hold, and hand-off time, none of which is dictated by chemistry. That is exactly the time iFactory targets, which is why the gains come without changing your validated process.
Book a demo to see your own ratio mapped.
We already have an MES, a LIMS, and a QMS. Why isn't that enough?
Each of those systems owns one phase of the batch and timestamps only its own events. The dwell time lives in the gaps between them — the sample sitting in a queue, the record waiting for a reviewer, the batch on hold. No single system measures those gaps, so they stay invisible. iFactory connects to all three and reconstructs the continuous timeline, turning four disconnected clocks into one you can actually manage.
How does this shorten batch record review specifically?
Most review time is not analysis — it is reviewers gathering data from disconnected systems before they can even begin. When records, instrument data, and in-process results are auto-assembled into a single review-ready package, that front-loaded data-gathering largely disappears. Electronic batch records also auto-flag deviations and enforce entry rules, lifting right-first-time rates from the 60-70% typical of paper to 90%+, which means far fewer batches detour into investigation at all.
Ask support how it maps to your review workflow.
Will this compromise compliance to move faster?
No — faster comes from removing waiting, not from removing checks. Every review step, signature, and deviation evaluation still happens; they simply stop waiting on manual data assembly. The unified record is built for 21 CFR Part 11, EU GMP Annex 11, and the batch review requirements of 21 CFR 211.192, so the audit trail is stronger than a paper-and-spreadsheet process, not weaker.
How quickly can we see where our time is going?
The diagnostic comes first. iFactory can reconstruct the end-to-end timeline for a sample of recent batches from your existing system exports and show you the four dwell pools ranked by measured days — usually within the first engagement, before any deployment. That teardown alone typically surprises teams who have been blaming processing for a problem that lives almost entirely in the queues.
Your Next Batch Is Already Waiting Somewhere You Can't See
See Your Real End-to-End Cycle — and Where the Days Are Hiding
Book a 30-minute session with a cycle-time specialist. We will reconstruct the full timeline for a sample of your batches, rank the four dwell pools by measured days, and show you how much calendar is recoverable without touching your validated process.
1 Timeline
Dispense to release, every batch
4 Pools
Dwell ranked by measured days
Live
Where each batch is stuck, now
Predictive
Alert before a target slips
