Operational Readiness, Startup & Ramp-Up
Bringing a new capability into routine operation means everything is new at once: people newly qualified, procedures never used in anger, materials flowing for the first time, systems freshly qualified, laboratory methods newly transferred. The deviation rate during ramp-up is the highest the process will ever see. Treating that as a temporary nuisance rather than as signal wastes the clearest information about the process the organisation will ever have.
What an explainer is not
A topic explainer is SPEQ’s synthesis of what a practice involves, cited to the standards that govern it. It does not reproduce their text, and it does not determine which of them apply to your product or process.
[ POSITION IN THE FRAMEWORK ]
7 DIMENSIONS · 22 LINKSReadiness is the moment a facility stops being a project and becomes a supply, and it fails in the gap between qualified equipment and a competent organisation — the second takes longer and is planned for less.
06 · QUALITY MATURITY — OPERATIONAL READINESS, STARTUP & RAMP-UP, REACTIVE TO ADAPTIVE
Startup begins when construction finishes. Readiness means equipment qualified; people and procedures catch up under production pressure.
A readiness plan exists covering equipment, systems and documents, with training scheduled and its adequacy assumed.
Readiness is defined across equipment, procedures, people, materials and systems together, with exit criteria that can be failed rather than declared.
Ramp-up is planned against process understanding rather than against demand, so rate increases follow demonstrated capability.
The organisation reaches steady state deliberately: the first months are instrumented, and the difference between planned and actual performance is investigated rather than absorbed.
SPEQ’s shared five-stage progression, labelled synthesis — not the FDA QMM rating scale. Where does your organization sit? Score your quality system →
07 · REGULATORY & EVIDENCE
GOVERNING STANDARDS · 5
Derived from the 5 standards SPEQ maps to this subject, across 4 regulatory bodies: FDA, EMA, ICH, PIC/S.
RECORDS & OBJECTIVE EVIDENCE
- Readiness criteria covering equipment, systems, procedures, people and materials
- Evidence against each criterion at the point of release to operate
- The ramp-up plan, with the capability data supporting each rate increase
- Competence evidence for personnel operating in the first production periods
- Startup-period deviation and investigation data, with what it changed
COMMON INSPECTION FINDINGS
- Production begun with readiness criteria declared met and no evidence against several
- Rate increased on demand rather than on demonstrated capability
- A deviation rate in the first months treated as normal for a startup rather than investigated
- Procedures written during production rather than before it
- Training completed on documents that were still changing
Readiness is not a milestone, it is a set of independent conditions
Operational readiness is routinely tracked as a single percentage on a project dashboard, which conceals the structure of the problem. The conditions are independent and each can block: people trained and demonstrably competent rather than merely trained; procedures that have been executed at least once by the people who will use them; materials qualified and flowing with the supply chain proven; systems qualified with their interfaces working; laboratory methods transferred and the laboratory able to absorb the volume.
The laboratory is the condition most often missed, because it is assessed on method readiness rather than on capacity. A method successfully transferred does not mean the laboratory can handle the testing volume a ramping line generates on top of its existing load, and the constraint surfaces as a growing backlog exactly when release time matters most.
Procedures survive contact with users or they do not
Procedures written by technical authors and approved by managers have not been tested. The first time a procedure is executed by the operator it was written for, under time pressure, is when its ambiguities become visible — and if that first time is during commercial production, the ambiguity is resolved by improvisation and appears later as a deviation.
The cheap intervention is a dry run: the actual users executing the actual procedures on the actual equipment before it matters, with the authors watching and the findings fed back. It is scheduled out of ramp-up plans routinely because it looks like rehearsal for something that has already been validated. It is not — validation demonstrates the process performs; the dry run demonstrates that people can execute it.
Ramp-up deviations are Stage 3 data
Process validation is a lifecycle: design, qualification, and continued verification. The ramp-up period sits at the start of continued process verification and generates an unusually dense stream of information about where the process is fragile, which parameters drift, and which procedural steps are hard to execute consistently.
Organisations that triage ramp-up deviations as a queue to be cleared lose that. Organisations that analyse them as a set — looking for the clusters, the repeated steps, the equipment that features disproportionately — get a map of the process’s weak points at exactly the moment when changing it is still cheap. The same deviations, read either way; the difference is whether anyone stands back from the queue.
SPEQ interpretation — plan the stabilisation, not just the start
Startup plans end at first commercial batch. What follows — the stabilisation period during which the process is technically validated but not yet routine — is usually unplanned, unresourced and staffed by a project team already being redeployed. That is the period in which the deviation rate is highest and the technical knowledge is most concentrated in people who are leaving.
The recommendation is to plan stabilisation as a phase with its own exit criteria: a defined deviation rate, a defined right-first-time level for batch records, laboratory turnaround within target, and the process knowledge transferred to the people who will hold it. Naming the phase is most of the benefit, because it stops the project team dissolving at the moment the process most needs them.
FREQUENTLY ASKED
What is usually missed in an operational readiness assessment?
Laboratory capacity. Readiness is assessed on whether methods have been transferred, not on whether the laboratory can absorb the testing volume a ramping line adds to its existing load. The constraint then surfaces as a growing backlog exactly when release time matters most.
Why run a procedure dry run if the process is validated?
Because validation demonstrates that the process performs, and a dry run demonstrates that people can execute it. Procedures written by technical authors and approved by managers have not been tested until the operators they were written for run them under realistic conditions — and ambiguity discovered during commercial production is resolved by improvisation.
How should ramp-up deviations be treated?
As a data set, not a queue. They arrive at the start of continued process verification and carry the densest information the organisation will ever get about where the process is fragile. Analysing them as a set — clusters, repeated steps, equipment appearing disproportionately — produces a map of weak points while changing the process is still cheap.
What are sensible exit criteria for a stabilisation phase?
A defined deviation rate, a right-first-time level for batch records, laboratory turnaround within target, and process knowledge demonstrably transferred to the people who will hold it. Naming stabilisation as a phase with criteria is most of the value, because it stops the project team dissolving when the process most needs it.