Following a previous FDA inspection that led to an issued 483, an organization implemented corrective actions that included training Quality Assurance personnel to increase the frequency of data backups on standalone HPLC systems. The training was completed, personnel understood the new requirements, and the change was intended to strengthen data integrity controls.
HOWEVER: The SOP was never updated to reflect this change.
As a result, FDA observed inconsistent backup practices: data backed up at the new frequency and some data backed up at the old frequency. Without a clear procedural anchor, even well-intentioned staff reverted to varying practices, creating exactly the kind of variability that SOPs are designed to prevent.
This wasn’t just any 483 observation. This was a repeat finding. The original issue involved inadequate data backup frequency, a fundamental data integrity concern. The corrective action addressed the what (increase backup frequency), but failed to address the how (update the governing SOP).
This scenario exemplifies process-procedure drift: when actual practices evolve, but documentation lags behind. It often occurs when:
- Urgency overrides thoroughness: Corrective actions are implemented quickly to address inspector concerns, but the documentation update is treated as a secondary task
- Siloed responsibilities: Training departments update training materials while document control waits for formal change requests that never arrive
Every CAPA should explicitly identify which SOPs, work instructions, or forms require revision. The CAPA should not be closed until all documentation is updated, approved, and effective. Even when changes originate from corrective actions, they must flow through your change control system.
It is imperative to train personnel on new requirements contained in the SOP. The sequence should be: update SOP, approve SOP, train to new SOP, and then implement with verification.
Quality takes building a culture of alignment. The most robust quality systems are those where documentation and practice are continuously aligned. This requires:
- Leadership commitment to treating documentation as a living system, not a compliance checkbox
- Cross-functional collaboration between QA, training, document control, and operations with proactive document reviews to catch procedural drift
- A questioning attitude that asks, “Does our SOP reflect what we actually do?”
This 483 observation serves as a powerful reminder: in the eyes of FDA, if it’s not documented, it doesn’t exist. Most importantly, if it’s documented incorrectly and not adhered to consistently, you’re not in compliance.
The 483 discussed in this post reads as follows:
…..The responsibilities and procedures applicable to the quality control unit are not in writing and fully followed.
Specifically, SOP …,“Audit Trail Review”, is deficient. As part of corrective actions to a previous FDA 483 Observation, Quality Assurance personnel were trained to increase the frequency of data back up from … to… on the … Chromatographic software’s, used for HPLC analysis, stored on standalone PC; however, SOP…,does not reflect this updated requirement. Consequently, we observed instances when data on the HPLC… were backed up on … and … and data on the HPLC … were backed up on … and … instead of … The failure to back up data at an appropriate frequency is a repeat observation from the previous inspection.
