RegOpsPro™

RP-I Guide™

Use this guide to understand how to implement the Responsible Person (import) assurance function and its interfaces with the wider WDA(H) GDP system. Use the Professional Workspace for evidence capture, discrepancy decisions, actions and QMS handoff.

What this guide is for

Use the Practitioner Guide™ to understand the judgement behind each stage of the RP-I Operating Model: the statutory assurance boundary, its operational interfaces, what good looks like and where import-control 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 statutory RPi assurance function is specific. Wider supplier, transport, receipt, traceability, recall and deviation controls remain WDA(H) GDP-system responsibilities and must not be presented as if they are all statutory RPi duties. Formal approvals and controlled records remain in the organisation’s authorised QMS.
1. RP-I scopeDefine importer accountability and assurance boundary.
2. Evidence interfaceMap certification evidence and review routes.
3. Supplier & routeControl parties, carriers and handovers.
4. Receipt decisionProtect status until assurance is complete.
5. TraceabilityMaintain batch, consignment and movement visibility.
6. DiscrepanciesEscalate incomplete or conflicting import evidence.
7. Inspection defenceTest whether the assurance trail is reproducible.
8. Executive interfaceMake recurring import weaknesses visible to management.
1

Define RP-I import accountability, scope and evidence boundary

What you are trying to achieve. Define the importing organisation, applicable routes and products, the RPi assurance boundary, delegated checking and continuity arrangements.

What good looks like

  • The statutory assurance boundary is explicit.
  • Delegated checks are competent and controlled.
  • The interface with RP, Quality and Operations is clear.

Common failure points

  • Wider GDP activity is incorrectly described as statutory RPi responsibility.
  • Role scope varies by person rather than route.
  • Deputy arrangements are nominal.

Inspector / challenge lens

How is the RPi remit defined for the actual products and routes, and where does wider RP/GDP responsibility begin?

Continue in the Professional Workspace

Use the workspace for the detailed evidence, judgement, action, working output and authorised-QMS handoff for this stage.

2

Map import evidence interfaces

What you are trying to achieve. Define what certification evidence is required, where it originates, when it must arrive, who checks it and what happens when it is incomplete.

What good looks like

  • Evidence sources and timing are defined.
  • Authenticity, batch identity and completeness checks are reproducible.
  • Unresolved gaps have a clear hold route.

Common failure points

  • Evidence is treated as an administrative follow-up.
  • The importer relies on verbal assurance.
  • Contradictory records do not block onward movement.

Inspector / challenge lens

Show how required certification evidence reaches the importer and how a missing or inconsistent item is controlled.

Continue in the Professional Workspace

Use the workspace for detailed evidence, judgement, action and QMS handoff.

3

Control supplier, carrier and route interfaces

What you are trying to achieve. Place the statutory assurance within a controlled import route by making parties, handovers, temperature/security risk and agreement responsibilities visible.

What good looks like

  • Approved parties and routes reflect actual operations.
  • Carrier and supplier responsibilities are clear.
  • Route changes trigger review before use.

Common failure points

  • A corporate approval is assumed to cover every site or service.
  • Unapproved route changes occur under supply pressure.
  • Subcontracted handovers are not visible.

Inspector / challenge lens

Take one import route and show the approved parties, handovers and controls around the RPi assurance point.

Continue in the Professional Workspace

Use the workspace for detailed evidence, judgement, action and QMS handoff.

4

Control receipt, quarantine and status decisions

What you are trying to achieve. Ensure goods-in and status controls prevent applicable product moving forward before required assurance and related receipt checks are complete.

What good looks like

  • Quarantine/status logic is unambiguous.
  • Evidence review and goods-in records reconcile.
  • Only authorised roles can change status.

Common failure points

  • Temporary receipt workarounds become informal release routes.
  • Warehouse status changes precede evidence review.
  • The assurance outcome cannot be linked to the batch received.

Inspector / challenge lens

Select a receipt and show how status remained controlled until the required assurance was complete.

Continue in the Professional Workspace

Use the workspace for detailed evidence, judgement, action and QMS handoff.

5

Maintain traceability and movement evidence

What you are trying to achieve. Keep batch, consignment, route, receipt, location, status and onward movement connected so the assurance trail can be reconstructed.

What good looks like

  • Batch identity remains connected across systems.
  • Movement and status records agree.
  • Reconciliation gaps are investigated.

Common failure points

  • Batch and consignment references diverge between systems.
  • Traceability depends on one spreadsheet or inbox.
  • Quantity differences are adjusted without explanation.

Inspector / challenge lens

Reconstruct one imported batch from certification evidence through receipt, status and onward movement.

Continue in the Professional Workspace

Use the workspace for detailed evidence, judgement, action and QMS handoff.

6

Escalate import discrepancies

What you are trying to achieve. Use proportionate triage, containment and investigation for missing evidence, damage, quantity issues, temperature uncertainty and other import exceptions.

What good looks like

  • Discrepancies have clear severity and ownership.
  • Product/status exposure is contained.
  • Repeat issues alter supplier or route oversight.

Common failure points

  • Minor recurring discrepancies become normalised.
  • Commercial urgency drives premature status decisions.
  • The same evidence gap recurs without systemic action.

Inspector / challenge lens

Show a recent import discrepancy, the containment decision, escalation route and what changed afterwards.

Continue in the Professional Workspace

Use the workspace for detailed evidence, judgement, action and QMS handoff.

7

Build inspection defence

What you are trying to achieve. Make the RPi assurance system reproducible under challenge by connecting scope, evidence sources, checks, discrepancies and governance records.

What good looks like

  • Staff can explain the assurance system consistently.
  • Evidence can be retrieved quickly.
  • Known weaknesses and remediation are visible.

Common failure points

  • The process works operationally but lacks a coherent evidence trail.
  • Evidence is reconstructed for inspection.
  • Role boundaries are described differently by different teams.

Inspector / challenge lens

Follow one imported batch and demonstrate the assurance system without relying on retrospective explanation.

Continue in the Professional Workspace

Use the workspace for detailed evidence, judgement, action and QMS handoff.

8

Create the executive governance interface

What you are trying to achieve. Translate held consignments, recurring evidence gaps, supplier escalation, route issues and overdue actions into management visibility and decisions.

What good looks like

  • Recurring import signals are trended.
  • Material risks have owners and decisions.
  • Management can see where resource or supplier action is needed.

Common failure points

  • Governance reports only volumes and service performance.
  • Repeat evidence problems remain local.
  • Overdue actions do not escalate.

Inspector / challenge lens

What import-control information reaches management, and show a decision triggered by a recurring weakness.

Continue in the Professional Workspace

Use the workspace for detailed evidence, judgement, action and QMS handoff.

Regulatory foundation and applicability

This guide supports the statutory Responsible Person (import) assurance function and its interfaces with the wider WDA(H) GDP system. Confirm the actual product, import route, licence position and current Approved Country for Import requirements before applying the workflow.

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-I Professional Workspace to perform the detailed assessment and create the working evidence trail.