Documentation During Audits

During GMP audits and inspections, documentation is not background material
— it is the primary evidence base.

Inspectors use documents to determine whether activities were performed under approved conditions, whether controls were applied consistently, and whether the quality system can be trusted under scrutiny.

This article explains how documentation is reviewed, challenged, and tested during audits, why documentation issues escalate quickly, and how inspectors interpret what they see when SOPs, forms, and records are placed under audit conditions.

Why Documentation Is Central During Audits

Auditors and inspectors begin with documentation because documents establish the official version of how work should be performed and what evidence exists that it was done correctly.

Documentation shapes:

• the scope and depth of the audit

• which systems are examined next

• how much reliance inspectors place on explanations

When documentation is clear, current, and consistently applied, audits progress efficiently. When it is not, inspectors widen their review, probe more deeply, and begin testing system credibility.

The foundational role of documentation in inspection confidence is outlined in GMP Documentation & Data Integrity.

Types of Documentation Reviewed During Audits

Inspectors review multiple document types, each serving a different purpose.

Common categories include:

• SOPs and governing documents, to understand approved requirements

• forms and blank records, to assess how information is captured

• completed records, to verify execution and outcomes

• logs, reports, and summaries, to identify trends and oversight

Inspectors evaluate not just individual documents, but how these document types align with one another. Misalignment between SOPs, forms, and records often signals deeper control issues.

How Inspectors Request and Retrieve Documents

Document retrieval is itself a test of document control.

Inspectors assess:

• how documents are requested

• how quickly they can be retrieved

• whether retrieved documents are clearly current and approved

Delays, uncertainty about where documents reside, or confusion over versions raise immediate questions about document governance. The presence of uncontrolled or outdated documents during retrieval often prompts broader review.

Document Status and Version Control

Inspectors rarely rely on document labels alone. They verify document status through behavior and evidence.

Typical verification approaches include:

• checking version history and effective dates

• comparing SOP versions to records generated

• asking personnel how they confirm that the document is current

When personnel cannot explain how they know a document is current, inspectors question whether document control is actively managed or assumed.

Record Review Under Audit Conditions

Completed records are scrutinized more intensely during audits than during routine review.

Inspectors look for:

• completeness and accuracy

• logical sequencing of entries

• consistency across similar records

• evidence that activities were recorded at the time they occurred

Inconsistencies, unexplained gaps, or patterns of correction prompt inspectors to examine additional records and related systems. Weak recording practices often become apparent only when records are reviewed side by side.

Documentation and Personnel Interviews

Documentation and interviews are closely linked during audits.

Inspectors often:

• review an SOP

• examine records generated under that SOP

• interview personnel expected to follow it

They assess whether explanations align with documented requirements and recorded outcomes. When personnel describe practices that differ from SOPs or records, inspectors question whether documentation reflects actual operations.

Common Documentation Failures During Audits

Certain documentation issues recur across audits and inspections.

Common patterns include:

• inability to retrieve requested records promptly

• use of outdated or uncontrolled documents

• mismatched SOP and record versions

• incomplete, unclear, or inconsistent records

• personnel unfamiliar with documentation used in their work

Inspectors interpret these issues as indicators of weak system control rather than isolated errors. Findings often escalate because documentation failures undermine trust in execution.

Frequent inspection pitfalls related to documentation are analyzed in Avoiding Documentation Traps.

Inspection Readiness

Documentation performance during audits reflects upstream practices.

Strong audit outcomes depend on:

• clear SOPs

• controlled documents

• well-designed forms

• consistent recording practices

When these elements are aligned, documentation holds up under audit pressure. When they are not, audits expose gaps quickly.

How documentation is assembled and presented once requested is addressed separately in Evidence Preparation.

Regulatory Perspective

Inspectors do not expect documentation systems to be flawless.

They expect documentation to be reliable under scrutiny.

Audits place documentation under pressure.

Inspectors assess not only what documents say, but how they are retrieved, explained, and supported by records and interviews.

Documentation that holds up during routine operations is the same documentation that withstands audit scrutiny.

Weaknesses exposed during audits are almost always rooted in everyday documentation practices.

Explore more on Documentation & Data Integrity

Browse VerethiQ resources on documentation control, data integrity expectations, ALCOA+ principles, record review, SOP governance, and inspection readiness.