Most labs treat an audit like a deadline, something to prepare for in the weeks before it happens. That works until an auditor asks for one specific document, and the lab has to go find out whether it exists. What holds up under review is rarely the paperwork assembled the week before. It’s the documentation that stayed audit-ready every week in between.
Every analytical lab already keeps some version of an audit trail. Staying an audit-ready analytical lab comes down to one thing: whether that trail is current between visits, not just before one. The connection between an event and the record that proves it happened either lives inside the lab, or it depends on whoever’s handling service.
Audit Prep in the Final Weeks Can’t Fix Months of Gaps
A pre-audit scramble can catch a missing signature or a mislabeled file. It can’t recreate a service event that was never logged, or explain why an instrument’s performance qualification no longer matches the method running on it today. Those holes form months before the audit, one skipped entry at a time, and no amount of last-minute review closes them once the auditor’s already asked.
What Auditors Actually Ask to See
A record reconstructed after the fact and one that was there all along look identical on the surface. Telling them apart is exactly what an auditor is trained to do under FDA GMP and ISO/IEC 17025, so what they ask for is specific:
- The qualification trail on a named instrument
- The service ticket behind a specific repair
- The training record for the analyst who ran a given batch
- The SOP version active on the date in question
Each has exactly one correct answer: a document that already existed. A lab that has to go looking for it has already signaled how the rest of its records are likely kept.
Where Audit-Readiness Breaks Down Between Visits
Producing that document on request comes down to how current the underlying records are. Some record gaps are purely internal habit and never touch a vendor. Others depend on how many companies have had a hand in the instrument.
Instrument Qualification That Falls Behind
Installation qualification (IQ), operational qualification (OQ), and performance qualification (PQ) establish that an instrument performs to spec at a given point in time. A repair, a firmware update, or a relocation changes that status, but nothing proves it unless the event gets tied back to the qualification record that same day.
When the technician who did the work and the person maintaining the qualification record aren’t on the same team, that connection depends on someone remembering to make it, instead of it being anyone’s job to begin with.
READ MORE: Is Your Analytical Lab Instrument Qualification Up to Date?
Maintenance Records That Don’t Connect Across Visits
A completed PM visit isn’t the same as a qualified instrument, and it isn’t a substitute for a formal PQ. Performance data has to carry over from one visit to the next and get checked against the same baseline, and that only happens reliably when the same provider ran the last visit too.
Split the work across vendors, and each one hands over a completion certificate with no visibility into what the last visit found.
READ MORE: How a Lab Instrument Maintenance Plan Catches What PM Misses
Service History Split Across Multiple Vendors
Add a second vendor and the problem compounds. When one company services the MS side of an instrument and another handles the LC side, the lab ends up with two partial histories instead of one instrument record. Reconstructing a single timeline from separate invoices after an auditor asks for it is slower and less convincing than producing one on request.
SOPs That Drift From Bench Practice
This gap doesn’t involve a vendor at all. A procedure changes at the bench long before the written SOP catches up, and if the version an analyst is following isn’t the version on file, the mismatch stays invisible until an auditor lines the two up side by side. At that point it reads as a control failure, even when the underlying change was routine.
Training Records That Don’t Match the Test System
In clinical and toxicology labs, CLIA requires competency to be assessed against the specific test system an analyst runs, twice in the first year and annually after that. Labs working under ISO/IEC 17025 face a similar requirement from a different angle: documented competence tied to the specific function an analyst performs, not a general certification renewed on a schedule.
A role-based training record doesn’t meet either bar, since it certifies that someone was trained on GC-MS broadly rather than that they were signed off on the specific method behind the sample an auditor is asking about.
What a Lab Can Fix Internally
The SOP and training gaps trace back to the same missed moment: the change happened, but nobody tied the record to it that day. Neither one involves a vendor, so the fix is entirely within the lab’s control.
- An SOP revision gets version-controlled the day it changes.
- A training record gets tied to the specific test system the day competency is signed off.
Do that consistently, and nothing depends on someone remembering to circle back later.
What Only a Single Provider Can Fix
Qualification, maintenance, and service history don’t respond to that same fix. The missing half of each record sits outside the lab, held by whoever touched the instrument, whether that’s the technician who did the repair, the team that ran the last PM visit, or any additional vendor who’s had a hand in it over the years.
One provider covering an instrument from installation through retirement keeps its qualification, maintenance, and service records on a single history, instead of scattering them across companies that never saw each other’s paperwork. No amount of internal logging discipline recreates a record that two or three companies never shared to begin with.
READ MORE: 7 Key Qualities to Look for in Your Next Analytical Instrument Service Provider
Conclusion
That connection breaks in two different ways, and each needs its own fix. A drifting SOP or a mismatched training record is a discipline problem, closed entirely by better internal ownership. Qualification, maintenance, and service history are a structural problem instead, one no amount of internal discipline closes, because the missing half of those records was never inside the lab to begin with.
A lab that only fixes the first half is still exposed on the second. Innovative Lab Services (ILS) has spent more than 30 years being the fix for that second half, holding qualification, maintenance, and repair documentation for multi-vendor instruments under one team instead of splitting it across several.
Wondering whether your instrument and service records would survive an auditor’s request, no matter how many vendors have touched your instruments? Contact ILS to see what a connected qualification, maintenance, and service record looks like across an instrument’s full life.