Equipment maintenance intervals: what the manual requires vs. what your SOP should set — and why inconsistency creates findings

Start with the citation test

When anyone — a QA reviewer, a monitor, a sponsor representative, or a senior colleague — tells you the manufacturer requires a specific task at a specific interval, ask one polite question: which page, and which section?

A manufacturer requirement is a verifiable fact that lives in a document. If it exists, the person asserting it should be able to point to the manual edition, the page, the section, and the sentence that sets the task and the interval. If they can, the discussion is over: you follow the manual, update your procedure to match, and train the team.

If nobody can produce that citation, you do not have a manufacturer requirement. You have an opinion, a memory, a habit carried over from another site, or a recommendation that hardened into a rule. Each may be worth considering on its merits, but none should be taught to a new coordinator as if the manufacturer had mandated it.

Sites get into trouble in both directions: an invented requirement collapses when an inspector asks for proof, while a real requirement dismissed after a search of the wrong manual edition is the opposite error. Keep the current manual in a known location, record its edition in the equipment file, and when a claimed requirement cannot be traced, note where the team searched and what they concluded. That short note, dated and initialed, is evidence of a controlled process.

Read what the manual actually does — and does not — say

Manuals usually contain three kinds of language, and confusing them is the root of most maintenance disputes.

First, there are direct requirements: statements that a task must be performed at a stated interval or before a stated limit is reached. These bind in the practical sense that your site accepted the equipment on the manufacturer's terms.

Second, there are recommendations: suggested intervals and inspection points, often written with words like "should" or "recommended" rather than "must." Recommendations deserve respect, and a site that departs from one should be able to explain why, but they are not requirements.

Third, there is silence. Many manuals say a great deal about safe operation and very little about how often a routine inspection should happen. Silence is not a hidden requirement. It means the manufacturer has left that judgment to the operator — which means it belongs in your SOP, with your reasoning attached.

Instead of arguing about whether monthly rotor removal feels required, classify the claim: requirement, recommendation, or site decision.

When the manual is silent, your SOP sets the interval

A site-set interval is not a weaker interval. Set properly, it is a defensible decision you can explain to any reviewer in two minutes. That means working through four questions and writing down the answers.

The first is use intensity. A centrifuge that runs many times a day lives a different life from one used twice a week, so intervals should follow actual use, not the calendar alone. A busy site may justify a short interval because wear accumulates faster; a quieter site may justify a longer one, provided the reasoning is honest and recorded.

The second is risk. What happens if this component degrades unnoticed? For a rotor, the consequences of a missed crack or corrosion are serious, so the interval should reflect that severity even if failures are rare. For a lower-risk item, a longer interval may be reasonable. Either way, the interval should follow a stated risk judgment, not habit.

The third is what the principal investigator (PI) and site leadership are willing to own. An interval in an SOP is a commitment made under the PI's oversight. Set it at a level the team can sustain in its busiest month, not an aspirational level that fails in practice.

The fourth is review. Equipment ages, workloads change, and manuals get revised. Set a point — an annual review works for most sites — to reconsider the interval against the record and any incidents.

Write the answers into the SOP or a short rationale kept with it — one paragraph is enough, so a monitor who asks why the site chose its interval gets the paragraph, not a reconstruction from memory.

Log every event, every time

Every maintenance and inspection event belongs in the equipment maintenance record, with the date performed and the initials of the person who performed it. Add what was done in plain words — rotor removed, inspected, cleaned, returned to service — and what was found.

Three habits keep the record strong. Log the event when it happens, not at the end of the month from memory, because reconstructed entries are easy to spot and hard to defend. Record unsatisfactory findings with the same care as satisfactory ones; a logged problem with a logged resolution signals a functioning system, while a record of nothing but perfect results invites harder questions. And when a scheduled event is missed or delayed, log that too, with the reason and the corrective step. A transparent gap is manageable; a silent gap discovered by someone else is a finding waiting to be written.

Inconsistency is the real finding-generator

Here is the lesson sites learn the hard way: reviewers rarely cite a site simply because a reasonable, documented interval differs from the one they would have chosen. They cite sites for inconsistency, because inconsistency tells a story no site wants told — that the written procedure and the actual practice are two different things.

The patterns are familiar. A site inspects monthly for a year, then skips several months with no explanation, then resumes. One coordinator removes and inspects the rotor while another does not, so the record shows two practices under one procedure. An SOP is revised, but the old form stays in circulation and entries appear on both versions.

Each pattern leads an inspector to the same conclusion: if the site cannot follow its own stated practice on something this visible, what else is drifting? A modest interval, followed and logged every time, protects a site far better than an ambitious one followed most of the time. Choose the interval you can keep. Then keep it.

When practice needs to change — a revised manual, a change in workload — change it through the procedure, not around it. Revise the SOP, note the effective date, train the team, and let the record show a clean transition. A documented change is control. Undocumented drift is a finding.

A practical routine to take back to your site

Pull the manual for one piece of equipment this week — the centrifuge is a good place to start — and test every maintenance claim your team repeats against it. Mark each claim as a requirement, a recommendation, or a site decision, with the page and section recorded for the first two. For each site decision, confirm that your SOP states the interval and that a short rationale explains it in terms of use intensity and risk. Check the record for gaps, mixed practices, and outdated forms. Then repeat for the rest of your equipment list, one item at a time.

That traceability is the goal. A site that can show either the manufacturer's words or its own documented reasoning for every task — and a matching record, without gaps — has little to fear from a question about a rotor.

---

Julio G. Martinez-Clark is Chief Executive Officer (CEO) of Amavita Research Services, a Miami cardiovascular trial site with more than 18,000 active cardiology patients and zero Food and Drug Administration (FDA) Form 483 findings, and CEO of bioaccess, a first-in-human contract research organization (CRO).