RegOpsPro™

RP Guide™

A practical guide for turning the Responsible Person role into practical GDP oversight: clear accountability, visible risk, stronger escalation and inspection-ready evidence.

Practical guidanceRP oversightGDP governanceInspection-ready evidence

What this guide does

It gives the RP a practical route for strengthening oversight without turning every issue into a separate project.

Where it adds value

It helps users identify what to control first, what evidence matters and where escalation needs to be clearer.

How it should be used

Use this guide for judgement and sequence, then use the workspace and tools to create the actual working outputs.

Recommended RP implementation path

The RP system should be built in a practical order. Start with accountability, then move through control exposure, issue governance, evidence and leadership visibility.

1

Establish accountability before improving controls

The RP needs a clear position in the organisation: what the role owns, what is delegated, what must be escalated and where decision authority sits. This is the foundation for every later control improvement.

FocusRole scope, delegation, reporting lines and escalation expectations.
WatchInformal delegation or blurred ownership between QA, operations and the RP.
RiskThe RP appears named on paper but not active in real decisions.
2

Identify the highest-risk GDP exposure

Once accountability is clear, the RP should understand where control could fail: outsourced activity, supplier and 3PL oversight, temperature control, returns, traceability, complaints, recalls and product status decisions.

FocusWhere product quality, patient safety, traceability or licence exposure could be affected.
WatchControls that exist procedurally but are not connected to escalation logic.
RiskThe RP receives issues late because operational exposure is not visible enough.
3

Strengthen issue, CAPA and trend governance

A strong RP system is visible in how it handles deviations, CAPAs and repeat signals. The aim is not just to record issues, but to understand whether the GDP system is learning and improving.

FocusDeviation triage, CAPA quality, repeat events and trend visibility.
WatchMinor recurring events becoming normalised instead of escalated.
RiskInspection challenge because the system cannot show effective improvement.
4

Build evidence that can be retrieved and explained

Inspection readiness is not just having documents. It is being able to show the right evidence quickly and explain how the evidence proves oversight, decision-making and control.

FocusEvidence retrieval, decision rationale, mock inspection and recall readiness.
WatchEvidence scattered across systems with no clear narrative.
RiskA good control system looks weak because it cannot be demonstrated under pressure.
5

Make GDP risk visible to leadership

The RP should not operate in isolation. Material GDP risks, trends and unresolved actions need visibility in governance forums, management review and where appropriate senior leadership discussion.

FocusGovernance cadence, risk summaries, open actions and leadership decisions.
WatchManagement review that records activity but does not drive decisions.
RiskSenior management cannot demonstrate effective oversight of GDP risk.

Regulatory foundation and role boundary

The RP is part of the licence holder’s control system, not a substitute for it. The WDA(H) holder must provide the authority, time, information, competence and organisational support needed for the role to operate effectively.

Licence-holder responsibilities

Maintain the authorised operation, resource the pharmaceutical quality system, ensure the RP is available and enabled, notify applicable changes and make sure commercial or operational pressure does not bypass GDP controls.

RP responsibilities

Maintain oversight of GDP compliance, authorised activities, supplier and customer qualification, records, training, recalls, returns, complaints, outsourced activities and the approval of subcontracted operations, using proportionate delegation without transferring accountability.

Important boundary.
The RP should challenge, assure and escalate. Routine tasks may be delegated to competent personnel, but delegation must be defined, evidenced, monitored and supported by an effective deputy or continuity arrangement.

A practical RP governance rhythm

Oversight becomes credible when it is built into routine operating cadence rather than reconstructed for inspection.

Daily and event-driven

Material deviations, temperature events, suspected falsification, recalls, stock-status concerns, supplier failures and unusual transactions reach the RP through defined triggers.

Monthly or risk-based

Review open deviations and CAPAs, supplier and 3PL performance, complaints, returns, recalls, training, overdue actions, licence changes and emerging GDP risks.

Periodic management review

Present trends, recurring weaknesses, resource constraints, significant decisions and unresolved risks to the licence holder’s leadership with clear owners and deadlines.

Decision records and escalation

An inspection-ready RP decision shows what was known, what remained uncertain, what controls were applied and why the resulting action was proportionate.

A

Define the decision boundary

Record the product, batch, activity, site, route or supplier within scope and distinguish confirmed facts from assumptions.

B

Show the evidence basis

Identify the records reviewed, missing evidence, applicable procedure and any technical or regulatory advice relied upon.

C

Control uncertainty

Use quarantine, system status, segregation, supply restriction, additional monitoring or escalation while evidence remains incomplete.

D

Close the governance loop

Document the decision, rationale, owner, due date, follow-up, CAPA or risk transfer and the evidence required for closure.

Questions an inspector may test

The strongest preparation is to ensure these questions can be answered from routine records.

Role and authority

  • How is the RP appointed, trained and kept current?
  • How much time is available and how is accessibility demonstrated?
  • What is delegated, to whom and how is competence assessed?
  • How does the RP stop or constrain an activity?
  • How is deputy or absence cover controlled?

System effectiveness

  • How are material events escalated to the RP?
  • How are suppliers, customers and outsourced partners kept qualified?
  • How are recurring deviations and overdue CAPAs identified?
  • How does management review act on GDP risk?
  • Can recent RP decisions be retrieved and explained?

Primary references

Use current legislation, MHRA guidance and applicable GDP guidance as the controlling source. RegOpsPro summarises practical implementation and does not replace those documents.

MHRA GDP guidance

Overview of UK GMP/GDP expectations and inspection arrangements.

WDA(H) licensing and Guidance Note 6

Licensing route and guidance for applicants and holders of wholesale dealer authorisations.

RP appointment and contract RP expectations

MHRA Inspectorate guidance on effective appointment, training and external RP engagement.

Content status.
Practical guide reviewed 21 August 2026. Confirm that linked sources and your organisation’s procedures remain current before use.

What good looks like

A strong RP operating model should be easy to explain, easy to evidence and credible under inspection challenge.

Strong indicators

  • RP accountability is clear and current.
  • Delegation and cover arrangements are documented and competence-based.
  • Supplier, 3PL and temperature risks are visible to the RP.
  • Deviations and CAPAs show proportionate investigation and learning.
  • Evidence can be retrieved quickly and supports the inspection narrative.

Common weak points

  • The RP is involved late or only after operational decisions have been made.
  • Ownership is unclear between QA, warehouse, supply chain and outsourced partners.
  • Repeat issues are treated as isolated minor events.
  • Governance packs are descriptive rather than decision-focused.
  • Inspection evidence exists but is not organised around the control story.
Use the workspace for execution
The guide gives the qualified route and judgement points. The execution workspace turns that route into step-by-step implementation, actions, evidence and progress.
Use the tools for outputs
The toolkit library is where users create logs, scorecards, risk registers, CAPA support, governance packs and inspection artefacts.

Ready to apply the guide?

Move into the full RP execution workspace when you are ready to turn the guidance into structured implementation activity.