Centrifuge Calibration and Speed Verification: Acceptance Criteria and Rotor Logs

A centrifuge that spins faster or slower than its display reports — or that stops early or late against its programmed run time — silently invalidates every relative centrifugal force (RCF) calculation built on that displayed speed, and in a swinging-bucket or fixed-angle rotor running near its rated maximum, an out-of-tolerance speed is also a safety issue, not just an accuracy one. Centrifuge calibration and speed verification is the scheduled quality-control procedure that catches this before it shows up as an inconsistent pellet, a failed separation, or a rotor incident. This guide covers what the check actually verifies, the acceptance criteria labs commonly apply, how to run the verification, how often to schedule it, and what a rotor log needs to record to support it.

What Centrifuge Speed and Timer Verification Checks

A centrifuge’s own control panel reports the speed it is commanding the drive motor to reach, derived from the same internal sensor the instrument uses to regulate itself. Calibration and verification exist because that internal sensor can drift out of true over time, exactly the failure mode an operator has no way to detect just by watching the display. A speed-verification event checks two related things independently of the instrument’s own readout:

• Rotational speed accuracy — whether the rotor’s actual RPM at one or more programmed set points matches what the display reports, measured with an independent, traceable reference instrument rather than the centrifuge’s own tachometer.
• Timer accuracy — whether the instrument actually runs for the programmed duration, checked against a separately verified stopwatch or chronometer. A timer that runs short under-processes every protocol that specifies run time by the clock rather than by a fixed number of revolutions.

Because every RCF calculation a lab relies on assumes the displayed RPM is the actual RPM, a speed check is the piece of centrifuge quality control that everything else — sample separation, pelleting consistency, protocol reproducibility — sits on top of.

Why This Is a Safety Procedure, Not Just an Accuracy One

Rotors are rated to a maximum speed for a reason: at high RPM, the stress a rotor’s material experiences during a run scales with the square of rotational speed, which is also why RCF itself scales with RPM squared rather than linearly. A centrifuge that is actually running faster than its display indicates — the failure direction that matters most for safety — can push a rotor closer to or past its rated maximum without the operator ever seeing that on the panel. Combined with routine rotor balancing checks, speed verification is one half of the pair of checks that keep a centrifuge operating inside the envelope its rotor was actually rated for.

Acceptance Criteria

Labs commonly apply a speed tolerance in the range of about ±1–3% of the programmed set point, though the specific figure a given lab uses should come from the rotor and instrument manufacturer’s published specification, not be assumed universal — tolerances vary somewhat by manufacturer and by rotor class, and a lab’s own SOP should state the exact figure it is checking against rather than leaving it implicit. Timer accuracy is typically checked to a tighter tolerance, since timer drift is cheaper to correct than speed-sensor drift and protocols are often more sensitive to it. As with any calibration, the criterion that matters is not simply “close,” but a documented pass/fail line set in advance, checked against a reference standard whose own traceability is established — see CASRAI’s guide to calibration certificates and metrological traceability for what “NIST-traceable” is actually claiming when it appears on a reference instrument’s own certificate.

How the Check Is Performed

Speed verification is a non-contact measurement in essentially every case — touching a spinning rotor to check its speed is not a viable or safe method. Two instrument types cover the overwhelming majority of practice:

• Optical/photoelectric tachometer — a reflective marker is placed on the rotor or drive shaft (visible with the lid open in centrifuges designed to allow this, or via a dedicated access port), and the tachometer counts reflections per unit time to derive true RPM independently of the instrument’s own sensor.
• Stroboscope — a strobe light is tuned until the rotor or a marked reference point on it appears stationary; the strobe’s own calibrated flash rate at that point is the rotor’s actual RPM. This method is common where a tachometer’s line-of-sight access isn’t practical.

Timer accuracy is verified separately and more simply: running the centrifuge for a programmed duration against an independently calibrated stopwatch or chronometer, and comparing the two elapsed times.

Whichever method is used, the reference instrument doing the checking needs its own current calibration and traceability — a tachometer or stroboscope that hasn’t itself been verified doesn’t establish anything about the centrifuge it’s being used to check.

How Often to Schedule Verification

There is no single interval mandated across every accreditation framework a lab might operate under; the common pattern in ISO/IEC 17025- and GLP-conscious labs is an annual full speed and timer verification, performed either in-house with a calibrated reference tachometer/stroboscope or through an accredited external provider, set out explicitly in the lab’s own SOP rather than left to informal judgment. See CASRAI’s guide to determining and documenting a calibration interval for the general reasoning — instrument use frequency, criticality of the work run on it, and the instrument’s own deviation history all inform whether annual is tight enough for a given centrifuge.

Outside the standing schedule, specific events should trigger an out-of-cycle re-verification regardless of when the next scheduled check is due: after the centrifuge is physically relocated, after any service event that touches the motor or drive assembly, after installation of a replacement rotor of a different rated class, or after any run that ends in an unusual noise, vibration, or apparent imbalance that could indicate the drive is no longer running true.

Rotor Log Requirements

Speed and timer verification checks the instrument; a rotor log tracks the rotor itself, and both records are needed to support a defensible quality-control history. Because rotor life is generally rated by stress-cycle exposure rather than calendar time — a function of how many runs a rotor has completed at what speed, not simply how old it is — a rotor log should be maintained per individual rotor (by serial number), not per centrifuge, and should record at minimum:

• Rotor identification — manufacturer, model, and serial number, since a single centrifuge commonly runs multiple interchangeable rotors over its service life, each with its own independent history.
• Cycle or run-hour count — a running total of centrifugation cycles (or run-hours, depending on what the rotor manufacturer’s rated-life documentation specifies) so the rotor’s cumulative stress exposure can be tracked against its rated maximum.
• Speed history — the maximum speed used on each run, since rotor stress accumulates faster at higher RPM; a rotor run consistently near its rated ceiling accumulates fatigue faster than one run well below it, even at the same cycle count.
• Inspection findings — routine visual inspection for corrosion, cracking, chemical exposure, or physical damage, dated and initialed, separate from the speed-verification record for the centrifuge itself.
• Verification and service dates — when the centrifuge’s own speed/timer verification was last performed and is next due, cross-referenced to the rotor(s) qualified on it.
• Retirement or de-rating decision — the manufacturer’s rated maximum cycle count or service life, and the date a rotor is taken out of service (or de-rated to a lower maximum speed) once it approaches that limit.

The specific numeric rated-life limit is set by the rotor manufacturer and varies by rotor material and design — a fixed-angle aluminum rotor, a titanium high-speed rotor, and a swinging-bucket rotor do not share one universal cycle-count ceiling, so the log should reference the manufacturer’s own published rated life for that exact rotor rather than a generic figure. What an auditor or accreditation surveyor is checking for is not a specific number but evidence that the lab is actually tracking exposure against whatever number the manufacturer specifies, consistently, per rotor.

When a Check Comes Back Out of Tolerance

An out-of-tolerance speed or timer reading takes the centrifuge out of service for the affected protocols until it is corrected — continuing to run samples on an instrument known to be out of tolerance defeats the point of having checked it. CASRAI’s guide to what to do when a calibration check fails covers the general corrective-action sequence (impact assessment on work already run on the instrument, adjustment or service, re-verification before return to service, and documentation of the whole event); for a centrifuge specifically, an out-of-tolerance speed finding should also prompt a check of whether any rotor run near the apparent true (not displayed) speed exceeded its rated maximum during the period the instrument was drifting.

In-House Verification vs. an Accredited External Provider

In-house verification using a calibrated, traceable tachometer or stroboscope is a legitimate way to perform routine speed checks, provided the reference instrument itself carries current calibration and traceability — it does not remove the underlying traceability requirement, it just moves ownership of maintaining that chain in-house. Labs operating under a formal accreditation scheme (ISO/IEC 17025, CLIA, GLP) should confirm what their specific accreditation body accepts: some accept a well-documented in-house program with traceable reference equipment, others expect the periodic verification itself to be performed or witnessed by an accredited external provider. See CASRAI’s overview of what ISO/IEC 17025 actually accredits for how that traceability chain is defined and audited.

Frequently Asked Questions

How often should a centrifuge’s speed be verified?

There is no single interval mandated across every framework; the common pattern is an annual full verification, set explicitly in the lab’s SOP based on how frequently the instrument is used, the criticality of the work run on it, and its own deviation history, with out-of-cycle re-verification after relocation, drive-assembly service, or a run that produced unusual vibration or noise.

What tolerance should a centrifuge speed check use?

Labs commonly work within roughly ±1–3% of the programmed set point for speed, though the specific figure should come from the instrument and rotor manufacturer’s published specification and be stated explicitly in the lab’s own SOP rather than assumed.

Can a lab verify its own centrifuge speed, or does it need an outside provider?

In-house verification with a calibrated, traceable tachometer or stroboscope is a legitimate method, provided the reference instrument itself has current calibration and traceability. Whether a lab’s accreditation body accepts an in-house program or requires an accredited external provider for the verification event depends on the specific framework the lab operates under.

Why does a rotor need its own log separate from the centrifuge’s calibration record?

Rotor life is generally rated by stress-cycle exposure (how many runs at what speed), not by the age of the centrifuge itself, and a single centrifuge often runs multiple interchangeable rotors. Tracking cycle count and speed history per rotor serial number is the only way to know when an individual rotor is approaching its manufacturer-rated retirement point, independent of the instrument it happens to be installed in.

What happens if a centrifuge fails its speed verification?

It should be taken out of service for the affected protocols until the cause is identified and corrected, then re-verified before returning to use. The lab should also assess whether any rotor run near the true (rather than displayed) speed during the drift period exceeded its rated maximum.