Clean-in-Place Cycle: Parameters and Execution Evidence
A clean-in-place cycle is a single execution of a cleaning procedure that applies cleaning fluids to the internal product-contact surfaces of an identified equipment circuit without dismantling that circuit for cleaning.

On this page · 11 sections
- 1What a clean-in-place cycle covers
- 2US requirements by product type
- 3Design the flow path before setting phase parameters
- 4Check utilities, sensors and circuit readiness
- 5Execute the cycle against a defined circuit
- 6Coordinate controls and recover from interruptions
- 7Build a traceable cycle evidence record
- 8Review the evidence before assigning equipment status
- 9Worked cases: interrupted exposure, bypass flow and missing data
- 10Recognize failure signatures and choose targeted controls
- 11A practical implementation and review checklist
How does Clean-in-Place Cycle 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.
01What a clean-in-place cycle covers
A clean-in-place cycle is an individual cleaning execution that delivers cleaning fluids through or over designated equipment surfaces without dismantling the components included in its defined circuit.
Delivery may use circulation, returning fluid through the circuit; once-through flow, sending fluid onward without recirculation; or spray application onto internal surfaces. These arrangements can be combined. Execution may be manually controlled, partly automated or automated; automation does not define CIP.
Define the circuit by equipment identity and its included vessels, pipework, branches, valves and return or discharge boundaries. Identify excluded parts separately. A vessel interior and connected transfer line may receive CIP while a removable fitting receives dismantling and manual cleaning. Link those activities through the equipment identity, rather than treating the CIP record as evidence for the entire machine.
| Term | What it describes | Relationship to the cycle record |
|---|---|---|
| clean-in-place cycle | One execution intended to remove soil from the designated circuit. | Records what happened during that run. |
| cleaning procedure or recipe | Instructions defining the cleaning method and conditions. | Provides the reference for execution; see cleaning recipes. |
| clean-out-of-place cleaning | Cleaning removed components outside their installed position. | Separate activity linked to the relevant equipment. |
| sanitization | Treatment intended to reduce microbial contamination. | Identifies a distinct treatment, where included. |
| sterilization | A process intended to render items free of viable microorganisms. | Needs distinct process evidence, not merely a cleaning-complete indication. |
| cleaning validation | Documented demonstration that a cleaning process consistently meets defined acceptance criteria. | Uses execution evidence within the broader cleaning-validation lifecycle. |
The central evidence distinction is between execution and effectiveness: observed parameter completion documents execution against defined conditions. It does not independently demonstrate cleaning effectiveness or establish the cleaning-validation lifecycle. A completed phase sequence is therefore an execution result, not a substitute for evidence that the intended cleaning outcome was achieved.
02US requirements by product type
The mapping below separates binding US product requirements from practical CIP implications. The operational-relevance column is engineering interpretation, not additional law or official guidance. Device, cosmetic, chemical and non-US applications are outside this mapping.
| Jurisdiction and product scope | Binding provision | Operational relevance |
|---|---|---|
| US drug products under 21 CFR 211 | 211.67(a): Equipment and utensils shall be cleaned and maintained at appropriate intervals, with sanitization and/or sterilization as appropriate for the nature of the drug. | Define the intended treatment rather than treating every CIP run as sterilization. |
| US drug products under 21 CFR 211 | 211.67(b): Written procedures shall be established and followed for equipment cleaning and maintenance. | Connect the circuit-specific execution instructions to the governing procedure. |
| US drug products under 21 CFR 211 | 211.67(b)(5): Written-procedure topics include protection of clean equipment from contamination before use. | Plan how the cleaned circuit will remain protected. |
| US drug products under 21 CFR 211 | 211.67(b)(6): Written-procedure topics include inspection for cleanliness immediately before use. | Distinguish cycle completion from the pre-use check. |
| US drug products under 21 CFR 211 | 211.67(c): Records shall be kept of maintenance, cleaning, sanitizing and inspection as specified in the referenced provisions. | Connect the run record to relevant maintenance and inspection records. |
| US human food under 21 CFR 117 | 117.35(d): Food-contact surfaces must be cleaned as frequently as necessary to protect against allergen cross-contact and food contamination. | Consider the product transition when planning cleaning frequency. |
| US low-moisture human food under 21 CFR 117 | 117.35(d)(1): Food-contact surfaces must be in a clean, dry, sanitary condition before use. | Include the post-cleaning surface condition in handover planning. |
| US dietary supplements under 21 CFR 111 | 111.27(d): Equipment, utensils and other contact surfaces must be maintained, cleaned and sanitized as necessary. | Identify contact surfaces beyond the main vessel. |
| US dietary supplements under 21 CFR 111 | 111.27(d)(1): Equipment and utensils must be taken apart as necessary for thorough maintenance, cleaning and sanitizing. | Evaluate which components need separate cleaning rather than assuming CIP reaches them. |
As engineering practice, use the applicable product rule to inform the procedure, then use circuit design to determine the cleaning method and execution evidence. Translate that relationship into the sanitation and cleaning schedule; for supplement operations, keep the broader 21 CFR 111 context alongside the circuit instructions. These engineering choices are practice recommendations, not official guidance or additional statutory requirements.
03Design the flow path before setting phase parameters
In CIP engineering practice, parameter selection starts with the wetted route, soil and equipment geometry. An illustrative route is: solution source → pump → heater, where fitted → supply valve → vessel spray device or pipe circuit → return leg → return measurement point → selected recovery tank or drain. Mark bypasses, parallel branches, sample valves, hoses, seals and product-isolation boundaries. Identify which surfaces receive circulating solution, which need separate valve actuation, and which remain outside the circuit. A common return reading can conceal unequal delivery through parallel branches.
Selectable stages include product recovery, initial rinse, detergent application, intermediate rinse, additional chemistry where justified, final rinse, and draining or drying. Select and order these for the particular procedure; they are not a universal sequence. Identify any sanitizing or sterilizing operation separately, with its own purpose and conditions, rather than treating it as interchangeable with cleaning.
For each selected operation phase, define a setpoint: the target value; an acceptable operating range: the permitted band; a phase-entry condition: what permits the stage to start; an exposure-credit rule: when time counts toward the specified exposure; and a phase-exit condition: what permits progression. Heating, filling and displacement may occur after phase entry but before qualifying contact time begins. Specify which measurements qualify exposure and how excursions affect credited time.
| Parameter | Measurement location and unit | Entry or exit condition | Evidence limitation |
|---|---|---|---|
| Contact time | Qualified exposure interval; min | Count only while defined conditions hold | Phase duration can include unqualified time |
| Temperature | Supply and return sensors; °C | Named sensors within selected range | Bulk liquid readings do not establish every surface temperature |
| Chemical concentration or justified proxy | Specified supply or return sample; mass fraction or conductivity, mS/cm | Selected concentration range or justified proxy relationship | Conductivity depends on chemistry and temperature; carryover can interfere |
| Flow | Supply, return or individual branch meter; L/min | Selected circuit delivery condition established | Total flow does not establish branch flow |
| Spray delivery conditions | Device inlet pressure and flow; bar, L/min | Specified device operating conditions established | Inlet readings alone do not establish surface coverage |
| Rinse endpoint | Return sample or sensor; selected analyte unit or conductivity, µS/cm | Defined endpoint criterion met | Return quality does not establish absence of trapped residue |
Assess drainability and residual liquid separately from the nominal rinse endpoint: low points, hose sags and retained liquid can remain after the measured return meets its criterion.
04Check utilities, sensors and circuit readiness
Readiness checks establish whether the selected circuit can support the planned cleaning conditions; they do not demonstrate that the cleaning run succeeded. The following are circuit-specific engineering practices, not a universal qualification schedule.
- Confirm product intended for removal has been removed and any retained product is isolated from the cleaning circuit. Check hose connections against the selected route, confirm an available return destination, and inspect the drain route for obstructions.
- Check water suitability for its intended cleaning use, available heating capacity, chemical supply identity and quantity, and compatibility with wetted materials. Assess utility capacity under expected simultaneous demand, not merely whether a utility is connected.
- Check pump condition, potential air entrainment, and spray-device condition. A running pump alone does not establish effective liquid delivery; damaged or obstructed spray devices can undermine coverage.
For each observation used to judge the cycle, consider sensor location, operating range, maintenance condition and calibration status. A controller input can remain available while its measurement becomes untrustworthy through drift, fouling or poor placement. Confirm that the measurement represents the relevant circuit condition, rather than only the supply skid.
After changes to routing, contact surfaces, spray devices, measurement points or utility supply, review which cleaning assumptions and observations may be affected. Select reassessment scope and timing around that impact and the intended next use; targeted operational qualification checks may be appropriate before return to service. Base the decision on the change, not an arbitrary periodic requalification interval.
05Execute the cycle against a defined circuit
The following workflow is engineering practice for manual, partly automated and automated CIP execution, not a universal regulatory sequence. Use the phases selected for the equipment and cleaning procedure.
- Identify the run. Assign a distinct run identity linked to the intended equipment, procedure revision and circuit snapshot: the connections, branches and return route actually selected. Identify the preceding product or soil context where it affects procedure selection, linking relevant production context through the batch execution history.
- Confirm the lineup. Before introducing fluids, check physical connections, valve alignment and the return destination. A valve command records an instruction; position feedback reports the sensed valve state. Neither alone establishes the intended hydraulic route. Confirm that route through connection checks and suitable flow or return observations as fluid introduction begins.
- Execute each selected phase. Check entry conditions, capture observations during active exposure, and assess exit conditions before advancing. Record actual readings, times, transitions and operator interventions, including adjustments or pauses. A planned recipe or final completion flag does not describe what happened during exposure.
- Document manual actions as they occur. Use contemporaneous recording for connections, valve movements, observations and phase transitions, identifying who acted and when. Ask the same questions as for an automated run: which route was used, what conditions were observed, and why did the phase advance? This approach does not prescribe continuous electronic logging.
- Close and hand over. Record the actual last phase reached, observed drain or dry condition, outstanding exceptions and equipment status submitted for review. If execution stopped early, retain that endpoint rather than presenting the planned final phase as completed.
Workflow: Identify run and circuit → Confirm lineup and destination → Check phase entry → Execute and observe → Assess phase exit → Repeat selected phases → Record endpoint and exceptions → Hand over for review.
- Identify circuitLink equipment, route and procedure revision.
- Check readinessConfirm connections, utilities and measurement condition.
- Establish routeConfirm isolation, delivery path and return destination.
- Execute phasesRecord conditions, transitions and operator actions.
- Resolve interruptionsPreserve exceptions and document recovery decisions.
- Reconcile evidenceAssess observations, gaps and verification results.
- Assign statusAuthorized personnel decide suitability for intended use.
06Coordinate controls and recover from interruptions
For installations using controllers, supervisory systems, historians or manufacturing records, an optional integration pattern exchanges run identity, equipment identity, procedure revision, phase state and event timestamps. These are engineering and record-management practices, not a prescribed CIP architecture. In MES and SCADA integration, distinguish a command request from acknowledged execution: accepting a start message does not demonstrate that circulation began. Likewise, a controller’s completed state is not reviewed equipment status.
- Stale messages: check event age and sequence before using a received state; retain event time separately from receipt time.
- Communication loss: define whether local control continues safely or enters a hold, and reconcile buffered events after reconnection rather than assuming the missing interval was satisfactory.
- Duplicate run submissions: use a unique request identity and return the existing run reference rather than starting another cycle.
Define hold, abort and restart decisions in the local procedure, including who authorizes recovery. Specify hydraulic isolation and chemical containment appropriate to the circuit, supported where appropriate by interlock logic. Preserve the partial record, including the interruption cause, last confirmed phase, route and observations. Identify the conditions needed before resumption: a confirmed flow path, available utilities, trustworthy measurements and a safe fluid destination.
Recovery review addresses whether earlier exposure remains creditable, whether fluid condition changed during the interruption, whether contamination became possible and whether any route changed. Record the rationale for resuming, repeating a phase or starting again; exposure calculations belong in the worked cases below. Link a restarted run to the interrupted run instead of overwriting its history.
07Build a traceable cycle evidence record
A useful CIP evidence model keeps different record types connected without treating them as interchangeable attachments. The following is a practical design for paper or electronic records, not a list of legally mandated electronic fields.
- Intended settings answer: what conditions and sequence were planned?
- Observed values answer: what did the instruments or operators actually record?
- Event history answers: when did phases, route changes, alarms and interventions occur?
- Verification results answer: what did inspections or tests find?
- Review decisions answer: who assessed the evidence, what was decided and on what basis?
Illustrative relationship diagram; run_id is the common key: Run(run_id) → Execution context(route identity, executed configuration, procedure revision) Run(run_id) → Intended settings(phase, parameter, target, unit) Run(run_id) → Observations(phase, measurement point, timestamp, value, unit, data-quality status) Run(run_id) → Events(timestamp, change, exception) Run(run_id) → Verification(sample or inspection, result) Run(run_id) → Review(reviewer, decision, rationale)
Preserve the route configuration and procedure revision used during execution. A link that resolves only to today’s master record can obscure the historical state. Apply production context tagging to manual entries as well as instrument data.
For connected systems, document timestamp offsets and the common time basis so event order remains interpretable; clock drift monitoring supports this control. Select sampling resolution that can reveal relevant excursions. Distinguish a fresh measurement from a stale, held value, and identify missing intervals rather than silently filling them. Corrections should preserve the original entry, identify who changed it and when, and record the reason. These are practical data integrity controls.
Keep original observations and exceptions accessible from every summary through stable references. Connect sample results to the run, sample point, collection time, relevant phase or post-cycle condition, collection method and test method—not merely the equipment name. This lets reviewers interpret what each result represents without confusing test findings with continuous process observations.
Cycle Run
Identifies the executed procedure.
- run_id
- equipment_ids
- route_snapshot_id
- procedure_revision_id
- started_at
- ended_at
Route Snapshot
Preserves the execution boundary.
- route_snapshot_id
- asset_ids
- valve_states
- return_destination
Parameter Observation
Locates each measured condition.
- run_id
- phase_id
- tag_id
- observed_at
- value
- unit
- quality_flag
Exception
Connects interruption and recovery.
- exception_id
- run_id
- onset_at
- recovery_action
- evidence_refs
Verification Result
Links findings to sampling context.
- result_id
- run_id
- sample_point_id
- method_id
- result
- unit
Review decision
Records accountable equipment status.
- run_id
- reviewer_id
- decision
- decided_at
- restrictions
08Review the evidence before assigning equipment status
As an industry-practice review framework, authorized personnel commonly check circuit identity, procedure revision, required phase observations, deviations, and any procedure-defined inspections or analytical results. Apply the opening distinction between execution evidence and validation proof when interpreting a completed run.
- Visual inspection asks whether accessible surfaces show visible residue, retained liquid or other observable problems; it does not resolve inaccessible surfaces or invisible contamination.
- Rinse results address material recovered into the sampled liquid, with interpretation dependent on rinse coverage, dilution and the analytical method.
- Surface sampling addresses residue recovered from selected locations; recovery and site selection affect what the result represents.
- Microbiological checks address the organisms recoverable under the sampling and test conditions, not chemical residue removal.
Select checks for the residue, surface and intended product; no single technique is sufficient for every application.
Keep execution status, evidence-review status and suitability for the intended next use separate. A completed cycle can still have an open review or unresolved findings. Record any conditional restriction with its basis and permitted use. Authorized personnel decide whether to accept or withhold equipment use; an equipment hold tag can communicate the restriction.
Before handover, assess protection after cleaning, storage conditions, intervening maintenance and elapsed clean holding time against the site's established basis. Maintenance-to-production coordination helps identify work affecting previously reviewed equipment. Use the applicable US provisions identified in the regulatory mapping above. Where changed conditions undermine acceptance, route the equipment for reassessment rather than carrying its previous status forward.
09Worked cases: interrupted exposure, bypass flow and missing data
These engineering-practice examples illustrate review logic, not production specifications or legal acceptance limits.
Interrupted detergent exposure
Assumptions: a and b are qualifying exposure intervals in minutes before and after a fault; H is the procedure-defined target in minutes. Let a + b = H, a < H and b < H. All other exposure conditions qualify.
Under a procedure permitting accumulated exposure and credit across this interruption, credited exposure is a + b = H. Under an uninterrupted-exposure rule, the longest qualifying interval is max(a, b) < H: the target is not reached. Select the applicable rule before evaluating the run, not to accommodate its result.
Record consequences: retain interval timestamps, qualifying observations and fault details; link the exception; document the credit or recovery decision and resulting equipment status pending any remaining review.
Flow diverted through a bypass
Assumptions: steady liquid flow, no inventory accumulation, and only target-branch and bypass outlets. Q_total is inlet flow, Q_bypass is bypass flow, and Q_required is the procedure-defined target-branch minimum, all in L/min.
Measure Q_total upstream of the split and Q_bypass on the bypass before recombination. Conservation gives Q_target = Q_total − Q_bypass. Given Q_total ≥ Q_required and Q_bypass > Q_total − Q_required, Q_target < Q_total − (Q_total − Q_required) = Q_required. A satisfactory inlet indication therefore masks inadequate target-branch flow; a target-branch meter would observe that branch directly.
Record consequences: retain simultaneous readings, sensor locations and valve positions; link the exception; document routing correction and recovery, and keep equipment unavailable pending satisfactory review.
Phase completion with missing temperature data
Assumptions: the controller reports phase completion, but the exported return-temperature record contains a gap during exposure.
An attributable, contemporaneous backup may support reconstruction if it covers the same return location and interval with equivalent observations. Check sensor identity, timing and coverage as part of the documented assessment; see temperature monitoring. Preserve the original gap and identify the backup separately. Without equivalent observations, qualifying exposure remains unresolved despite phase completion. Do not invent or interpolate qualifying measurements.
Record consequences: retain the export, controller events and any backup; link the exception; document reconstruction acceptance or recovery, and record equipment status as awaiting review or dispositioned by authorized personnel.
10Recognize failure signatures and choose targeted controls
Use these engineering-practice pairings to guide investigation, not to diagnose a fault from a single signal. Compare observations from the same operating period before selecting a corrective action.
| Observation | Possible cause | Discriminating check | Targeted control |
|---|---|---|---|
| Delayed return heating despite warm supply | Thermal load, heat loss or unrepresentative measurement | Compare supply and return measurement locations and temperature trends. | Correct probe placement or address confirmed thermal losses. |
| Fluctuating flow with suspected air entrainment | Suction air ingress or inadequate liquid level | Inspect suction conditions, tank level and connections for air entry. | Repair leaks or restore stable suction conditions. |
| Poor vessel coverage despite apparently normal supply | Blocked, stalled or misaligned spray device | Assess spray-device condition, movement where applicable, and actual coverage. | Clean, repair or reposition the device; reassess coverage. |
| Retained liquid after draining | Trapped low point, obstructed drain or inadequate venting | Examine low-point drainage, valve position and vent condition. | Clear obstructions or correct drainage geometry and venting. |
| Plausible but unchanging sensor value | Stuck signal or nonresponsive sensor | Check sensor response against an independent observation during a known process change. | Repair the measurement chain; confirm dynamic response. |
For instrument investigations, preserve as-found and as-left calibration results before and after adjustment. Wrong-route and missing-record failures are addressed in the worked cases above.
Extending cycle time without identifying the mechanism may leave the problem unresolved: extra circulation does not necessarily restore spray coverage, drain a trapped pocket or make a frozen signal trustworthy. Target the confirmed mechanism, then check whether the intervention changed the relevant observation.
11A practical implementation and review checklist
Use these practice-based questions at implementation and run review. Assign each function to a named local owner; these are not prescribed job titles.
| Review question | Evidence to inspect | Responsible function |
|---|---|---|
| Is the circuit boundary identifiable? | Asset IDs, flow diagram, included branches and exclusions | Circuit owner |
| Is the procedure revision fixed for this run? | Run-linked procedure and approved changes | Procedure owner |
| Do measurement points represent intended conditions? | Sensor locations and rationale for representative readings | Engineering function |
| Are exposure-credit and recovery rules explicit? | Phase criteria, interruption decisions and restart instructions | Process owner |
| Do record gaps remain visible and verification results stay linked? | Audit trail, missing-data flags, manual entries and run-linked results | Record reviewer |
| Can authorized personnel distinguish execution completion from equipment-use status? | Completion record, disposition, restrictions and authorization | Status approver |
| Do relevant changes trigger review? | Change control covering equipment geometry, product or soil context, cleaning chemistry, utility conditions and control logic | Change owner |
At handover, can the next user establish which assets are available, for what intended use, and subject to which restrictions?
Frequently asked questions
Q.How can a manually controlled cycle produce a useful execution record?+
Apply the run identification and execution recording described above, using contemporaneous recording. What is specific to manual runs is observation timing. Document observation frequency: intermittent readings do not establish continuous parameter control. A data integrity risk assessment can help identify where independent checks or continuous recording would strengthen the evidence.
Q.What evidence connects a temporary hose to the circuit that was actually cleaned?+
Useful practice is to record the hose identifier, both connection endpoints, installation time and the applicable circuit drawing revision. Include the valve alignment and any adapters, bypasses or disconnected sections that affect the wetted path. A dated connection check or clearly identified photograph can supplement that record; an inventory entry alone does not establish the installed route. Connect returnable asset tracking with recipe procedure mapping so reviewers can distinguish the intended configuration from the configuration used during cleaning.
Q.Can detergent conductivity readings be compared when solution temperatures differ?+
Not reliably without understanding the measurement basis. In typical CIP measurement practice, conductivity is temperature-dependent, and compensation depends on the instrument settings and solution characteristics. Record solution temperature, whether conductivity is raw or compensated, and the reference temperature and compensation method where applicable. Compare results on a consistent basis using a relationship appropriate to the detergent and concentration range. Review as-found and as-left calibration when instrument performance is questionable. Conductivity alone may not distinguish detergent from other dissolved material.
Q.How should a product allergen change affect cycle selection in a food plant?+
For US human-food operations under 21 CFR 117.35(a), equipment cleaning and sanitizing must protect against allergen cross-contact and contamination of food, food-contact surfaces or food-packaging materials. As a practical selection step, compare the previous product’s allergens, the next product’s formulation, residue characteristics and affected equipment against the cleaning procedure’s demonstrated scope. An allergen changeover check can document that comparison. Do not substitute a sanitizing step for evidence of allergen removal; microbial control and allergen removal address different hazards.
Q.When can a shared return measurement represent parallel equipment branches?+
As an engineering practice, treat a shared return measurement as representative only where circuit studies support that interpretation for the operating configuration. Examine branch flow distribution, valve positions, restrictions, retained volumes and sensor location. A combined return can mask a poorly supplied branch because streams mix before measurement. Depending on the uncertainty, use branch-specific measurements, sequential routing or other demonstrated checks. Apply the relevant parameter tolerance band to the location it actually represents. A completed return trace alone does not demonstrate branch cleaning effectiveness.
Q.What should be reviewed when a cleaning chemical lot changes but the recipe does not?+
A practical review checks the received chemical’s identity, formulation, strength, expiry or retest status, storage history and applicable acceptance documentation. Compare these with the assumptions behind dosing and conductivity interpretation. An unchanged recipe can deliver a different working concentration if the stock strength changes. Record the chemical lot attributes and the lot actually dispensed. Distinguish a routine replacement meeting the existing specification from a formulation, supplier or strength change that warrants assessment through change control; lot replacement alone does not establish a need for requalification.
Q.How can a cycle record cover a shared circuit serving several production assets?+
A practical shared-circuit record uses a cycle identifier linked to each included asset and the configuration active during execution. Apply the circuit boundary described above. Where routing changes during the cycle, associate each route with its exposure interval and observations. Use production context tagging to preserve these relationships within the batch execution history. Assign cleaning status only to assets and surfaces covered by the documented route, rather than every asset connected to the skid.
Q.How should a maintenance intervention after cleaning affect the next equipment-use decision?+
Beyond the pre-use inspection in the regulatory table, as a practical assessment identify whether maintenance opened the product-contact boundary, introduced lubricants or debris, replaced wetted parts or changed drainability. Document the intervention and evaluate inspection, recleaning and any applicable sanitization or sterilization separately. An equipment hold tag can communicate unresolved status. The designated reviewer should document the next-use decision rather than relying solely on the earlier cycle’s completion.
Primary sources
Want to see how Clean-in-Place Cycle could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
