RP Guide™
Use this guide to understand how to implement the Responsible Person Operating Model in practice. It focuses on judgement, governance and challenge; use the Professional Workspace for detailed evidence capture, decisions, actions and QMS handoff.
What this guide is for
Use the Practitioner Guide™ to understand the judgement behind each stage of the RP Operating Model: what the control is trying to achieve, what good RP oversight looks like and where practical weaknesses usually appear.
How to use it
Read the relevant stage for implementation guidance, then move into the Professional Workspace to capture detailed evidence, decisions, actions and the QMS handoff.
Role and QMS boundary. The RP is part of the licence holder’s control system, not a substitute for it. Delegated activity must remain defined, competent, evidenced and subject to effective RP oversight. Formal approvals and controlled records remain in the organisation’s authorised QMS.
1. Role scopeDefine remit, authority and delegation.
2. Control mapTranslate GDP obligations into owned controls.
3. Supplier controlApply risk-based outsourced-party oversight.
4. Event decisionsUse clear containment and escalation logic.
5. Control systemMake routine oversight evidence retrievable.
6. CAPAConnect recurring signals to investigation and effectiveness.
7. Inspection storyMake the control system explainable under challenge.
8. Executive interfaceTurn material GDP signals into leadership decisions.
1
Define RP role scope, accountability and evidence boundary
What you are trying to achieve. Establish what the RP owns, what may be delegated, how the role interfaces with the licence holder and where escalation authority sits.
What good looks like
- Role scope and decision rights are explicit.
- Delegation has named competent owners and review points.
- Deputy and continuity arrangements are practical, not nominal.
Common failure points
- The RP is named but not routinely involved in material decisions.
- Delegation is informal or undocumented.
- Commercial pressure can bypass the escalation route.
Inspector / challenge lens
Show how the RP remit is defined, kept current and supported by sufficient authority and access.
Continue in the Professional WorkspaceUse the workspace for the detailed evidence, judgement, action, working output and authorised-QMS handoff for this stage.
2
Map GDP controls and ownership
What you are trying to achieve. Translate GDP obligations into a practical control system with clear ownership, review frequency and escalation points rather than relying on SOP presence alone.
What good looks like
- Critical GDP controls have named owners.
- Review cadence reflects risk and operational change.
- Control failures have visible escalation routes.
Common failure points
- Control ownership is assumed between Quality and Operations.
- Procedures exist but no one tests control effectiveness.
- Gaps remain local and do not reach the RP.
Inspector / challenge lens
Select a critical GDP control and show who owns it, how it is monitored and how weakness is escalated.
Continue in the Professional WorkspaceUse the workspace for detailed evidence, judgement, action and QMS handoff.
3
Strengthen supplier and 3PL oversight
What you are trying to achieve. Use risk to determine qualification, agreement, audit and performance oversight for suppliers, warehouses, carriers and outsourced activities.
What good looks like
- Oversight depth reflects supplier criticality.
- Agreement responsibilities match actual practice.
- Deteriorating performance changes the oversight plan.
Common failure points
- A questionnaire substitutes for service-specific assurance.
- Agreements are generic or operationally untested.
- Repeat supplier issues are normalised.
Inspector / challenge lens
Why is this provider still suitable today, and what evidence supports the current oversight level?
Continue in the Professional WorkspaceUse the workspace for detailed evidence, judgement, action and QMS handoff.
4
Define event decision and escalation logic
What you are trying to achieve. Make containment, evidence needs, RP involvement and decision authority clear before a GDP event occurs.
What good looks like
- Affected stock status is controlled immediately.
- Decision thresholds and evidence needs are understood.
- Escalation is timely and rationale is recorded.
Common failure points
- Events are handled differently depending on who is present.
- The RP becomes involved only after a disposition is proposed.
- Temporary workarounds become routine.
Inspector / challenge lens
Take a recent GDP event and explain containment, evidence, decision authority and the RP escalation point.
Continue in the Professional WorkspaceUse the workspace for detailed evidence, judgement, action and QMS handoff.
5
Maintain control-system evidence
What you are trying to achieve. Design routine oversight so that records demonstrate review and control, not just that documents exist somewhere.
What good looks like
- Evidence is current, attributable and retrievable.
- Records show review, exception and follow-up.
- Missing evidence triggers correction and escalation.
Common failure points
- Evidence is scattered across inboxes and local files.
- Records prove activity but not oversight.
- Inspection packs are reconstructed at the last minute.
Inspector / challenge lens
Show a routine oversight record and explain what it proves about control effectiveness.
Continue in the Professional WorkspaceUse the workspace for detailed evidence, judgement, action and QMS handoff.
6
Connect investigations and CAPA
What you are trying to achieve. Use deviations and recurring signals to drive proportionate investigation, root-cause challenge, corrective action and effectiveness review.
What good looks like
- Investigation depth follows risk and recurrence.
- CAPA addresses causes rather than symptoms.
- Effectiveness criteria are defined before closure in the QMS.
Common failure points
- Training is the default CAPA.
- Recurring minor events are reviewed in isolation.
- Actions close without evidence of effectiveness.
Inspector / challenge lens
Show how a recurring GDP signal changed the investigation, CAPA or control design and how effectiveness was verified.
Continue in the Professional WorkspaceUse the workspace for detailed evidence, judgement, action and QMS handoff.
7
Build the inspection story
What you are trying to achieve. Connect responsibilities, controls, evidence, known weaknesses and improvement into a coherent narrative that matches real records.
What good looks like
- Staff can explain the system consistently.
- Evidence can be retrieved without reconstruction.
- Known gaps are visible with active controls and owners.
Common failure points
- The narrative is polished but records tell a different story.
- Evidence owners are unclear.
- Known weaknesses are hidden rather than governed.
Inspector / challenge lens
Follow one inspection theme from requirement to control, record, issue and improvement.
Continue in the Professional WorkspaceUse the workspace for detailed evidence, judgement, action and QMS handoff.
8
Create the executive governance interface
What you are trying to achieve. Convert operational GDP data into concise risk, trend, resource and decision information for senior management.
What good looks like
- Material risks and overdue actions are visible.
- Governance records decisions and accountable owners.
- Resource constraints and repeat signals drive action.
Common failure points
- Management review records activity but not decisions.
- Critical issues are diluted within large KPI packs.
- Actions remain open without escalation.
Inspector / challenge lens
What GDP information reaches senior management, and show a decision made because of an adverse trend or unresolved risk.
Continue in the Professional WorkspaceUse the workspace for detailed evidence, judgement, action and QMS handoff.
Regulatory foundation and applicability
This guide supports the Responsible Person role within a UK WDA(H) GDP system. Apply the actual licence scope, authorised activities, organisation structure and current GDP requirements to local decisions.
Source review baseline: 22 September 2026. Recheck current primary requirements where licence scope, route, jurisdiction or operating facts change.
Move from guidance to execution
Use the RP Professional Workspace to perform the detailed assessment and create the working evidence trail.