A new courier has been selected. The warehouse system upgrade is booked. A contractor has changed the way it operates. The commercial team has agreed a new supply route.
Then Quality is asked to approve the change.
At that point, the change record is no longer controlling a proposal. It is explaining a decision that has already gathered momentum.
That is how apparently manageable operational changes become GDP problems. The procedure may exist, but the trigger arrives too late for the assessment to influence supplier selection, system design, licence strategy, validation, training or the go-live date.
The formal expectation is clear
The current EU GDP Guidelines state that critical distribution steps and significant changes should be justified and, where relevant, validated. Chapter 1 also requires a change control system that incorporates quality risk management and is proportionate and effective.
Chapter 7 further states that an audit of the contract acceptor should be performed before outsourced activity begins and whenever there has been a change to the outsourced activities. The audit frequency should be risk based and reflect the nature of the work.
For UK wholesale dealers, the legal and regulatory picture extends beyond the internal change record. The Human Medicines Regulations require compliance with the applicable GDP guidelines and include specific obligations around matters such as approved premises and named responsible persons. MHRA guidance also states that changes to the details of the original licence application must be notified, with standard variations including changes to the business process, named persons and site address.
The practical issue is therefore not whether an organisation owns a change control SOP. It is whether a proposed change reaches the right assessment before anyone treats implementation as inevitable.
Not every business change needs the same control
A risk-based system should not force every office move, software update or commercial decision through the same level of scrutiny. It should, however, identify any change that could affect:
- the quality or integrity of a medicinal product;
- storage, transport, security or traceability;
- the licensed supply chain or the particulars of the WDA(H);
- the authority, availability or duties of the RP or RP-I;
- a computerised system or data used to make a GDP decision;
- an outsourced GDP activity or the way a contractor performs it; or
- recall capability, complaint handling, returns or other critical interfaces.
The aim is not to label every proposal as significant. It is to make the significance decision early, document the rationale and route the change to the people who have the authority to decide.
A six-question test before go-live
Describe the operating change, not only the project title. A statement such as “new carrier,” “system upgrade” or “revised process” is too broad. Record what will be different in the route, handoffs, data, equipment, responsibilities, timings, subcontracting or evidence. Also record what is intended to remain unchanged. This exposes assumptions that otherwise sit outside the assessment.
Screen the proposal against seven lenses: product; premises and equipment; people and roles; process and route; computerised system and data; outsourced activity; and licence or contract. If the answer is “no impact,” explain why. A one-line conclusion without the reasoning is difficult to defend when the practical change is visible elsewhere.
Turn the assessment into preconditions. These may include an approved quality or technical agreement, supplier qualification, route risk assessment, validation or qualification evidence, approved procedures, completed training, agreed contingency arrangements, or a licence variation or notification where required. Planned actions are not the same as readiness evidence.
The process owner may propose the change and Operations may confirm practical readiness, but GDP decisions require the right quality authority. The RP should be involved where the change may affect compliance with the licence conditions or maintenance of product quality. In Great Britain, changes that affect the RP-I or the import assurance system require specific consideration. The governance model should define when consultation, approval or escalation is required.
Define the evidence before the deadline. Examples include an executed agreement, approved audit outcome, completed mapping or qualification report, tested system interface, user access review, successful mock recall, training completion report, approved risk assessment or confirmation of the regulatory route. A change should not be approved on the basis that the evidence will follow unless a justified and controlled exception has been agreed.
Implementation is not the finish line. Decide how and when the organisation will confirm that the change works in routine use. The check may review the first shipments, temperature performance, delivery exceptions, system audit trails, inventory accuracy, complaint signals, data retrieval or contractor performance. The measure, owner and review date should be set before go-live.
How the test applies to common GDP changes
New carrier or route
Early question: What has changed in journey time, temperature exposure, security, handoffs, subcontracting and exception escalation?
Typical evidence: Route risk assessment, qualification or justification, agreement approval, subcontractor visibility and a first-shipment review plan.
Warehouse system upgrade
Early question: Could the change affect stock status, traceability, access control, data transfer, recall retrieval or business continuity?
Typical evidence: Risk-based validation, interface testing, access review, backup and recovery testing, procedure and training approval.
Premises or layout change
Early question: Does the proposal affect approved premises, storage conditions, segregation, security, material flow or licensed particulars?
Typical evidence: Licence assessment, mapping or qualification, drawings, procedure updates, contingency and regulatory action where required.
Outsourced activity change
Early question: Is the service scope, method, location or subcontractor different, and has the contract giver assessed the resulting risk?
Typical evidence: Updated contract or quality agreement, competence assessment, audit requirement addressed, service controls and monitoring plan.
RP or RP-I change
Early question: Are authority, availability, competence, delegation and licence obligations addressed before the person starts or leaves?
Typical evidence: Notification or variation route, role documentation, handover, coverage and named-person confirmation as applicable.
New import or supply route
Early question: Does the legal supply route change, and are responsibilities, evidence handoffs and licence scope still clear?
Typical evidence: Documented route assessment, licence and counterparty checks, import assurance evidence, agreements and escalation criteria.
The RP should not become the approval route for everything
A broad change trigger does not mean the RP must personally approve every business change. That would create delay without improving control.
The stronger model is a two-stage route. First, a simple screen identifies potential GDP and licence impact. Second, defined decision rights determine whether the change can remain with the process owner, requires Quality approval, requires RP or RP-I input, or needs regulatory action before implementation.
This protects the RP role in both directions. Significant issues should not bypass the RP, but routine low-risk activity should not consume RP capacity simply because the change process lacks a clear triage rule.
Signs that change control has arrived too late
- The purchase order is raised before qualification or quality agreement approval.
- The go-live date is fixed before the licence route is assessed.
- Training is planned for after implementation.
- The first live shipment is expected to provide the evidence that the route is suitable without a justified concurrent approach.
- A contractor reports “no change to service” even though it has introduced a new location, system or subcontractor.
- The record closes when actions are completed but contains no planned effectiveness check.
- The “no GDP impact” conclusion contains no explanation that could be understood by someone outside the project.
These are not simply documentation defects. They show that the decision sequence has been reversed.
A practical 30-day reset
- Week 1 — Review recent changes. Sample the last ten operational changes, including projects that never entered the quality system. Identify where the first irreversible commitment occurred and when Quality or the RP became aware.
- Week 2 — Map the trigger points. Ask Procurement, IT, Operations, HR, Commercial and senior management what events start supplier onboarding, contracting, system configuration, role changes and go-live planning. Add a GDP screen at those points rather than relying only on the change control SOP.
- Week 3 — Define decision rights. Create a one-page triage guide covering the seven impact lenses, the evidence expected before implementation and the circumstances that require Quality, RP, RP-I, licence or senior-management input.
- Week 4 — Test the process with worked examples. Run four realistic scenarios through the route: a carrier change, a system upgrade, a warehouse change and a contractor using a new subcontractor. Capture where people interpret the trigger differently and use the examples in training.
Control the proposal before it becomes the plan
Effective change control does not slow every change. It slows the point at which an unassessed assumption becomes an operational commitment.
The most useful question is therefore not only whether a change record exists. It is whether the assessment still has enough time and authority to change the decision.
Primary references
- European Commission: Guidelines of 5 November 2013 on Good Distribution Practice of medicinal products for human use (2013/C 343/01) — in particular, Chapters 1 and 7.
- UK Government: The Human Medicines Regulations 2012 (SI 2012/1916) — see regulations 43, 45 and 45AA in the current text.
- MHRA: Apply for manufacturer or wholesaler of medicines licences — see “Make a change to a licence.”
- MHRA: Medicines—good manufacturing practice and good distribution practice.
Regulatory references checked on 5 November 2026.
Use boundary: This article provides practical operational guidance. It does not replace applicable legislation, regulatory or legal advice, the Responsible Person, the Responsible Person for Import, or an organisation’s authorised quality-system requirements.
RegOpsPro™