GMP document control: which SOP version applies?

1. Separate requirements from your working method

This article addresses documentation in the EU GMP context of human medicinal product manufacturing. Assess the applicable requirements separately for other activities, including GDP and medical devices. The broad term life sciences does not define a single regulatory framework.

EU GMP Chapter 4, sections 4.1–4.5, covers document control, identification, approval and keeping documents current. Instruction documents need a defined effective date. The register below is our practical working aid; its columns are not a prescribed regulatory form.

As of 6 September 2026, the official index lists Chapter 4 and Annex 11 dated January 2011. The revisions consulted on in 2025 are drafts. Check their status again when updating your internal procedures.

2. Build a register that answers a practical question

Start with one defined process, such as deviation handling. Identify its SOP, forms and supporting work instructions. Avoid collecting unrelated files at this stage. Your register should answer one question: which document should the responsible colleague use for this activity today?

Check two entries with the people who use them. Can they retrieve the document through the stated route? Do the register, document and actual working practice agree? The list becomes useful when that connection works. Resolve conflicting entries with the document owner instead of choosing whichever file looks newest.

3. Move from a proposed change to an effective document

Define a short workflow with clear handovers. Our suggested five steps should be adapted to your quality system:

1. Explain the change: record the reason, affected process and proposed adjustment.
2. Assess the impact: consider linked forms, systems, training and other instructions.
3. Review and approve: designated reviewers and authorised approvers work on the same clearly identified version.
4. Prepare implementation: coordinate the effective date, distribution and the preparation users need.
5. Confirm the transition: provide the new document, control opportunities to use superseded instructions and update the register.

For example, an SOP approved on Monday may take effect on Thursday. Users still need the currently effective version until that date. The new version can be available for preparation, provided its status is unmistakable. Coordinate the transition across every affected shift.

Include review and implementation time in the work plan. Planning only the writing effort can leave approvals waiting in a queue. Clear responsibilities also make it easier to cover holidays or unexpected absence without losing track of unfinished changes.

4. Include paper copies and forms in the same workflow

A controlled folder does not complete distribution at the workplace. Identify where printouts are actually used: beside equipment, in a shift binder or at a workstation. Decide who replaces these copies and how the completed replacement will be recorded.

An unused form can also contain outdated instructions. Link the form version to its associated procedure. When a form changes, decide whether ongoing activities can continue on the previous template or require specific transition arrangements. The answer depends on the change and its impact.

Handle completed records under the applicable retention and correction procedures. A new template is not a reason to transcribe historical records onto the latest form.

For electronic solutions, establish the intended use and required controls. Version history, access permissions or an approval button do not demonstrate that the complete process is suitable. Our article on assessing GxP relevance helps with the initial system assessment. Discuss the practical workflow with users before selecting additional software features.

5. Finding an old version: establish the impact first

If a superseded SOP is found at a workstation, preserve the facts. Which version was present, since when and for which activities? Establish whether anyone actually used it. Record where it was found and control further unintended use through your procedure.

Compare the changes that matter. Were they editorial, or did they affect working steps, limits, checks or decisions? This helps determine which activities and records need examination. Involve the responsible quality function; simply renaming the file cannot answer the impact question.

Record and handle the event through the applicable deviation procedure. Investigate the distribution route as well: was a workstation missing from the distribution list, was a replacement unfinished, or was access unclear? Agree an appropriate follow-up action and check whether it works. Document what actually happened without backdating approvals or activities. The aim is to restore a reliable process while retaining a truthful account of the event.

6. Start with one process and reduce recurring work

Select a frequently used process with several document locations. Assign an owner, a reviewer and a manageable date for the first review. Resolve that process before extending the register across the company.

• Initial review: bring together effective versions, approvals, related forms and actual distribution points.
• Resolution: obtain decisions on conflicting information, complete responsibilities and implement changes under control.
• Practical check: ask a user and their deputy to retrieve the effective SOP and matching form.
• Routine operation: track pending reviews and incomplete transitions in a short working meeting.

Use retrieval time, pending approvals and unclear document status as internal working measures. There is no universal GMP target for these measures. Follow their development to choose the next bottleneck to address. For a scheduled audit, continue with the GMP audit preparation checklist. If several issues are competing for the same people, we can take on a defined package to help you organise your evidence.