A quality system can appear complete on paper and still fail during an audit or regulatory inspection.
The problem is often not that a company lacks procedures. The problem is that its procedures, records, training documentation, and actual practices do not consistently agree.
Auditors and inspectors generally look beyond whether a procedure exists. They evaluate whether the procedure is adequate, current, understood, followed, and supported by objective evidence.
Here are seven common documentation mistakes that can weaken an otherwise capable quality system.
1. Procedures Describe the Ideal Process, Not the Actual Process
A procedure may have been written during quality-system implementation and never updated as operations evolved.
Employees develop workarounds. Responsibilities shift. New software is introduced. Approval steps change. Before long, the written procedure describes a process that no one actually follows.
This creates an immediate credibility problem during an audit. When an employee explains one process but the procedure says something different, the auditor must determine which process is controlled.
How to fix it
Walk through the procedure with the people who perform the work.
Ask them to demonstrate:
– Where the process begins
– What records are created
– Who reviews or approves the work
– What happens when the normal process cannot be followed
– Which systems, forms, and templates they use
Update the procedure to reflect the controlled process the organization intends employees to follow. Do not simply revise the procedure to legitimize an ineffective workaround.
For pharmaceutical manufacturers, written procedures affecting product quality must be approved by the appropriate organizational units and quality unit, and those procedures must be followed.
2. Responsibilities Are Ambiguous
Procedures commonly use phrases such as:
– “The department will review the record.”
– “Management will approve the investigation.”
– “Quality will be notified as appropriate.”
These statements do not clearly establish who is accountable.
Ambiguous responsibilities lead to missed approvals, delayed investigations, incomplete escalation, and inconsistent execution.
How to fix it
Identify responsibilities by role rather than by an employee’s name.
For example:
> The CAPA Owner shall complete the investigation and proposed action plan. The Quality Manager shall review and approve the investigation before implementation of corrective actions.
Clearly distinguish between the person who performs the work, the person who reviews it, and the person with final approval authority.
3. Records Do Not Demonstrate That the Procedure Was Followed
A procedure may require an evaluation, risk assessment, technical review, or effectiveness check, but the corresponding form contains only a checkbox.
A checked box may confirm that someone completed a step, but it often does not show what was evaluated, what evidence was reviewed, or how the conclusion was reached.
How to fix it
Design forms to capture the information needed to reconstruct the decision.
Depending on the process, records should identify:
– The issue or activity evaluated
– The evidence reviewed
– The acceptance criteria used
– The rationale for the decision
– The individuals involved
– The date the activity occurred
– Required follow-up actions
The record should allow an independent reviewer to understand what happened without relying entirely on the memory of the person who completed it.
4. Templates and Forms Are Not Properly Controlled
Organizations sometimes control their SOPs but overlook the Word documents, spreadsheets, checklists, and templates used to create quality records.
Employees may save local copies, modify formulas, remove required fields, or use an obsolete version.
The result is inconsistent information and records that no longer meet procedural requirements.
How to fix it
Determine which templates and forms affect quality or regulatory compliance and place them under appropriate document control.
At a minimum:
– Assign each form a unique identifier and revision
– Define who may modify it
– Remove obsolete versions from points of use
– Protect formulas and required fields when appropriate
– Periodically confirm that employees are using the current version
An electronic quality system does not automatically solve this problem. The organization must still control how templates are approved, issued, revised, and retired.
5. Activities Are Documented Long After They Occur
When employees are busy, documentation is sometimes completed at the end of the day, end of the week, or after someone discovers that the record is missing.
Delayed documentation increases the risk of inaccurate dates, reconstructed information, missing details, and unexplained discrepancies.
How to fix it
Procedures should clearly establish when records must be completed.
Employees should document activities when they occur or as soon as reasonably possible afterward. When a late entry is necessary, it should be identified transparently and include the date of entry, the date of the original activity, and an explanation when required.
Electronic records should preserve relevant metadata and audit-trail information. FDA has emphasized that electronic copies used as true copies must preserve the content and meaning of the original record, including applicable metadata.
6. Training Records Show Completion but Not Competence
A signed training acknowledgment proves that an employee received or reviewed a document. It does not necessarily demonstrate that the person can competently perform the assigned activity.
This is especially important for complex laboratory methods, manufacturing processes, inspections, investigations, and quality-system approvals.
How to fix it
Use training methods appropriate to the risk and complexity of the work.
Competency may be demonstrated through:
– Direct observation
– Practical demonstration
– Written assessment
– Review of initial work product
– Qualification samples
– Supervised execution
– Periodic reassessment
For medical-device manufacturers operating under the QMSR, the method used to evaluate the effectiveness of training or other personnel actions should be proportionate to the risk associated with the work.
7. Documents Are Revised Without Assessing the Broader Impact
A seemingly minor SOP revision can affect forms, training materials, validation documentation, software configuration, job descriptions, supplier requirements, or other procedures.
When these dependencies are not assessed, conflicting requirements remain in the quality system.
How to fix it
Add a documented impact assessment to the document-change process.
Before approving a revision, consider whether the change affects:
– Related procedures and forms
– Regulatory submissions or commitments
– Product or process risk
– Validated systems and processes
– Training requirements
– Supplier or customer agreements
– Records already in progress
– Implementation timelines
A document should not become effective until the organization is prepared to implement it.
A Practical Documentation Health Check
Select five recently completed quality records from different processes, such as a CAPA, complaint, supplier qualification, training record, and change control.
For each record, ask:
1. Was the current procedure used?
2. Was every required step completed?
3. Is the rationale for key decisions documented?
4. Were required reviews and approvals completed on time?
5. Does the record agree with related documents and systems?
6. Could an independent auditor reconstruct what happened?
This type of focused review often reveals more than simply reading the procedures.
Strong Documentation Should Reflect a Controlled Process
The purpose of quality documentation is not to create paperwork. It is to establish consistent expectations, preserve evidence, support sound decisions, and demonstrate that the organization remains in control of its operations.
Avendium helps life-science organizations evaluate and improve their procedures, records, document-control systems, and broader quality-system processes. A focused documentation review can identify weaknesses before they become audit findings or inspection observations.