For GP practices and PCNs
Remote pharmacy technicians for your practice
Request remote technician support for work that has a clear process and can be completed through approved practice systems. Define the tasks and the local team responsible for queries and decisions.

Choose a workflow that can be handed over
Explain where tasks originate, what information the technician will see and what a completed task should contain. Identify exceptions that go back to a pharmacist, prescriber or other practice colleague. This is especially useful when several staff currently share the work and follow different informal processes.
Build supervision into the working day
Name the person available for questions during each session and agree the channel for escalation. A remote technician should not have to decide which of several surgeries owns a query. If work is shared across a PCN, specify priorities, contacts and access for each practice.
Prepare secure access and a visible handover
Arrange individual system permissions, approved equipment and a pre-start access test. Define where progress is recorded and who picks up outstanding work after the booking. Agree what happens during a system outage before the session starts.
Specify whether patient or pharmacy contact is part of the task. If it is, provide the approved communication route and describe the boundaries of those conversations.
Remote sessions
Ready before the session starts
Secure access, two-step sign-in and a named contact for escalation are agreed before any remote work begins.
Register your practiceDefine the exception route
For a medicines correspondence task, your brief might identify the task queue, the information to record and the colleague who reviews discrepancies. State how exceptions remain visible when the session ends. This helps prevent a remote work queue from becoming a separate, unmanaged inbox.
Professional requirements for the role
Great Britain requires GPhC technician registration. PSNI does not currently register technicians in Northern Ireland; check relevant qualifications and experience.
Specify the technician duties, local procedures and supervision. Dispensing, accuracy-checking and system qualifications each cover only part of the work in a GP practice. Identify who reviews decisions outside the agreed technician role.
State the country where the service is delivered. Onboarding, local service requirements and any funding conditions need checking for that assignment.
How we approach checks and bookings →| Shift | Day | Status |
|---|---|---|
| Locum GP, morning | Monday | 2 applied |
| Practice nurse | Tuesday | Offered |
| Clinical pharmacist | Wednesday | Booked |
For practices
Every shift in one place
Post pharmacy technician shifts, see who has applied and confirm bookings from one workspace.
Register your practiceQuestions about booking cover
Can a remote technician authorise prescribing decisions?
Do not build the booking around duties outside the technician’s professional role. State which work needs a pharmacist or prescriber and how those decisions are requested, documented and returned to the workflow.
Does the practice need to arrange systems access?
The brief should identify who provides and approves individual access, equipment and communication tools. Previous system experience does not provide access to your practice or remove the need for induction.
How much is the booking fee?
£19.99 + VAT per locum for each calendar day worked, including a part-day. Prices exclude VAT. The practice contracts with and pays the locum directly, including agreed expenses, separately from our fee. The same fee applies to GP, pharmacist, pharmacy technician and nursing cover.
Preparing for the work
Official professional guidance
Source review: . Use the current requirements for the country and service involved.
Our editorial policyRegister your practice for remote pharmacy technician cover
Register free, then send the dates, duties and support arrangements. We’ll review suitable availability and discuss the booking.