RegOpsPro™Many organisations have an RP meeting, a quality dashboard and a standing agenda. Those arrangements can create the impression that Responsible Person oversight is well established. The weakness often appears between meetings.
A material temperature event is managed operationally but does not reach the RP until the monthly review. A supplier repeatedly misses agreed actions, yet each delay is treated as a separate issue. A returns decision is made correctly, but the evidence and rationale sit in different records. A delegated check is completed, but no one tests whether the overall process remains effective.
The problem is not necessarily meeting frequency. It is the design of the control system that should operate every day around the meeting.
The regulatory expectation is wider than scheduled review
The EU GDP Guidelines require a documented quality system that defines responsibilities, processes and risk-management principles. Senior management should periodically review the effectiveness of that system. That periodic review is important, but it is only one part of the control model.
The same Guidelines give the Responsible Person specified authority and responsibility for ensuring that the quality system is implemented and maintained. The RP should perform the role personally, remain contactable and may delegate duties but not responsibility. The listed responsibilities extend across records, recalls, training, supplier and customer approval, outsourced activities, self-inspection and decisions concerning returned, rejected, recalled or falsified medicines.
This points to a practical distinction. Governance meetings provide scheduled visibility and trend review. RP oversight also needs event-driven visibility, clear decision rights and evidence that actions were followed through when the issue could not wait for the next meeting.
MHRA inspection guidance reinforces the operational nature of the assessment. Inspectors may interview personnel, review documents and examine processes including stock control, storage, temperature monitoring, returns, purchasing, sales and transportation. A failure by the RP to fulfil legal duties may support a major deficiency classification. The control therefore has to work in real cases, not only in governance minutes.
Where oversight commonly breaks down
1. The signal stays inside the operational process
Warehouse, customer service, procurement, supply chain or a 3PL may manage the immediate task without recognising that it also creates an RP oversight question. The record is opened, but the significance is assessed only within the local process.
This is common where procedures say “escalate significant issues” without defining what significant means, who decides or how quickly the escalation should occur.
2. Escalation depends on individual judgement
Experienced colleagues often know when to involve the RP. The weakness appears during absence, workload pressure, organisational change or an unfamiliar event. If the route depends on knowing the right person rather than a defined trigger, the system is not reliably reproducible.
3. The dashboard is built from lagging information
Monthly counts can show deviations, excursions, complaints and overdue actions. They may not show the uncertainty, recurrence or connected supplier risk behind those numbers. A dashboard can therefore remain green while important exceptions are moving through separate systems.
4. The decision is visible but the reasoning is not
“Approved,” “acceptable” or “monitor” may record the outcome without showing the evidence considered, the uncertainties, the authority used or the conditions attached to the decision. Months later, the organisation can see what happened but cannot readily explain why the decision was proportionate.
5. Completion is mistaken for control
An action can be completed without reducing the underlying risk. The RP may see the initial decision and the target date but not the effectiveness result, a recurrence or a repeated extension. The oversight chain stops before the organisation knows whether the control worked.
A five-stage RP oversight loop
A practical operating model should connect routine systems to RP oversight without requiring the RP to perform every operational task. Five stages provide a useful structure:
Capture the event, exception, trend or change in the normal operational system. State what is known, what remains uncertain and whether immediate containment is already in place.
Apply predefined criteria to decide whether the matter requires immediate RP contact, same-day review, routine notification or inclusion in the next governance cycle.
Make the required authority and decision owner clear. Record the evidence considered, the conclusion, the rationale, any assumptions and the conditions that would change the decision.
Translate the decision into containment, correction, escalation, monitoring or CAPA with named ownership and realistic due dates.
Confirm effectiveness, identify recurrence and transfer material outcomes into trend review, management review or wider supplier and quality-system governance.
The response times in this model are operational design choices, not universal regulatory deadlines. Each organisation should set them according to its licence, activities, risks, procedures and applicable requirements. The important point is that the route is defined before the event occurs.
Build triggers around consequences, not department names
A trigger matrix is more dependable when it focuses on potential consequence. Examples that may require defined RP visibility include:
- possible impact on product quality, status, traceability or patient safety;
- suspected falsified, stolen or diverted product;
- a recall, potential recall or material market action;
- a significant or recurring temperature-control failure;
- a supplier, customer or 3PL event that may affect authorised activities;
- a licence, regulatory or inspection commitment at risk;
- repeated deviations, overdue CAPAs or evidence that an action was ineffective;
- an event outside an approved procedure, quality agreement or delegated authority; and
- a breakdown in RP or RP-I cover, access to records or decision support.
The list should not attempt to predict every event. It should help colleagues recognise consequence, uncertainty and recurrence, then route the matter to the right authority.
Where RP-I oversight connects
For applicable imports into Great Britain, MHRA guidance requires the RP-I to implement a system confirming that the required QP certification—and, where relevant, independent batch-release certification—has taken place. The checking activity may be delegated, but the RP-I remains responsible for ensuring that the checks are effective, and written evidence should be available for each relevant batch.
The same operating principle therefore applies: a completed check is not enough on its own. Discrepancies, missing evidence, repeat delays, unsuitable evidence routes and delegated-process failures need a defined escalation path and an effectiveness view. Where RP and RP-I responsibilities meet, the interface should show who receives the signal, who decides and where the evidence is retained.
A practical 30-day reset
- Map the signals. Identify where important GDP events and trends first appear: deviation systems, warehouse records, service reviews, complaints, transport monitoring, supplier correspondence and import checks.
- Define the triggers. Agree the consequence-based criteria, response route, cover arrangement and expected record for each level of escalation.
- Test recent cases. Select three recent events, including one exception, and trace how each moved from initial signal to decision, action and effectiveness review.
- Test absence and pressure. Run a short scenario when the RP is unavailable. Confirm that deputies, delegates and operational teams know the route and have the necessary access.
- Change the meeting agenda. Use governance meetings to review trends, recurring signals, overdue actions, ineffective controls and decisions already made—not to discover material events for the first time.
Five questions that expose the gap
Select one recent significant GDP event and ask:
- What made this an RP oversight matter?
- When did the RP become aware, and why at that point?
- What evidence and uncertainty informed the decision?
- How were ownership, escalation and follow-up controlled?
- What now demonstrates that the response was effective?
If the answers depend on reconstructing emails and memories, the meeting may be working while the oversight system between meetings is not.
Make day-to-day oversight visible
Use the free RP Oversight Log Builder to connect significant signals, RP review, decisions, actions and follow-up in one structured working view. Transfer any required controlled records and approvals into your organisation’s authorised quality system.
Primary references
- European Commission: Guidelines of 5 November 2013 on Good Distribution Practice of medicinal products for human use (2013/C 343/01)
- MHRA: Medicines—good manufacturing practice and good distribution practice
- MHRA: Acting as a Responsible Person (import)
Regulatory references checked on 1 October 2026.
Use boundary: This article provides practical operational guidance. It is not legal or regulatory advice and does not determine compliance for a particular organisation. Confirm the requirements applicable to your licence, products, territories and activities. Statutory responsibilities, professional judgement, approvals and controlled records remain with the accountable individuals and your organisation’s authorised quality system.