Sample policy · Patient transport

Crew clinical scope and competency policy (patient transport)

Statutory anchor: Regulation 18 (staffing), Health and Social Care Act 2008 (Regulated Activities) Regulations 2014 (SI 2014/2936). This policy also engages Regulation 12 (safe care and treatment). The sector-specific professional guidance sources for crew scope are the Joint Royal Colleges Ambulance Liaison Committee (JRCALC) clinical practice guidelines and HCPC standards for paramedics; these are not in the Verivius regulation manifest and must be checked against the live source before adoption. · primary source

1. What the regulation says

Sufficient numbers of suitably qualified, competent, skilled and experienced persons must be deployed in order to meet the requirements of this Part. (Reg 18(1): the headline duty)

receive such appropriate support, training, professional development, supervision and appraisal as is necessary to enable them to carry out the duties they are employed to perform. (Reg 18(2)(a): support, training, supervision and appraisal)

Regulation 12 adds the safe-care duty that governs clinical scope:

ensuring that persons providing care or treatment to service users have the qualifications, competence, skills and experience to do so safely, (Reg 12(2)(c) (staff competence))

The full text is at https://www.legislation.gov.uk/uksi/2014/2936/regulation/18 and https://www.legislation.gov.uk/uksi/2014/2936/regulation/12. Where this policy and the regulation diverge, the regulation wins.

2. Plain-English summary

You have to deploy enough suitably qualified, competent, skilled and experienced staff to meet Part 3. Staff have to receive appropriate support, training, professional development, supervision and appraisal. Where staff are health or social-care registered professionals, they have to be enabled to give their regulator evidence of meeting professional standards.

3. Purpose

This policy sets out how the Service defines crew clinical scope, checks competency, records training and responds when a crew member works outside their agreed role.

The Service must verify this policy against the current JRCALC edition, HCPC standards, Skills for Care Care Certificate standards and CQC Regulation 18 source material before adoption.

4. Sources to verify before adoption

5. Scope

This policy applies to:

The Service does not use this policy to expand a role beyond the person's qualification, registration, local competency sign-off or current clinical governance approval.

6. Role scope framework

The Service keeps a role-scope matrix for every crew role.

6.1 Registered paramedic

The Service verifies that each paramedic:

The Lead Clinician checks HCPC registration at recruitment, before renewal deadlines and when any concern is raised.

6.2 Registered nurse or other registered healthcare professional

Where the Service uses a registered nurse or another registered healthcare professional, the Clinical Lead records:

The Service does not assume that a professional registration automatically covers ambulance or patient transport practice.

6.3 Technician and associate roles

The Service defines the technician or associate role in writing.

The role-scope record covers:

The Clinical Lead signs off role scope before the Operations Manager deploys the person on relevant jobs.

6.4 Ambulance care assistant

The ambulance care assistant role supports planned patient transport.

The scope may include:

The Service verifies Care Certificate completion or equivalent induction for unregistered staff where the role requires it.

6.5 Driver-only role

Driver-only roles do not carry out clinical assessment, clinical intervention or moving and handling beyond the local role description.

The Operations Manager ensures that driver-only jobs are matched to patients whose booking information, risk assessment and escort arrangements make that role safe.

If the patient presentation changes, the driver stops, contacts the control point or clinical lead and follows the escalation process.

7. Training and competency sign-off

The Service keeps a training matrix linked to role scope.

The matrix records:

Training completion alone does not prove competence. The Clinical Lead or delegated competent assessor records practical sign-off where the task creates patient or staff risk.

7.1 Deployment approval workflow

The Operations Manager uses the following workflow before allocating a crew member to a patient journey:

  1. Confirm the journey profile: record the patient's known mobility, clinical, communication, escort and equipment needs.
  2. Match the role: check the role-scope matrix for the tasks each crew member may perform without direct supervision.
  3. Check current evidence: confirm registration where applicable, induction, training and practical competency sign-off.
  4. Resolve restrictions: identify supervised-practice conditions, expired evidence, return-to-work limits or tasks the person must not perform.
  5. Approve or reallocate: record who approved the crew mix, or change the allocation where the evidence does not match the journey.
  6. Reassess on change: if the patient's presentation or transport need changes, the crew stops, escalates and records the revised decision.

A rota entry is not evidence of competence by itself. The approval must be traceable to the current role-scope matrix and competency record.

8. Response to clinical skill outside scope

If a crew member performs a clinical skill outside their agreed scope, Staff record an incident immediately.

The Registered Manager and Clinical Lead:

The review does not treat good intent as proof that the action was safe. The Service records the reason for any return to duty or change in role.

9. Responsibilities

10. Recording requirements

Each deployment decision is recorded in the allocation or journey record before the Crew member starts the work. The record should include:

The Service also keeps the following records:

Records are kept in the Service governance records and are available for internal review, CQC review, commissioner review and external review where required.

11. Audit cadence

The Service uses the following Verivius default audit rhythm unless current HCPC, JRCALC, Skills for Care, CQC, commissioner or local source material requires a different rhythm:

Audit findings are recorded as improvement actions with an owner and review date.

12. Version control and review date

The Service keeps a controlled copy of this policy. The footer or document-control table records:

13. Related policies and records

Review cadence: annual or on regulatory change, whichever sooner. Owner: Registered Manager.

14. Sources and further reading

This template is based on CQC's guidance for providers and managers, the Health and Social Care Act 2008 (Regulated Activities) Regulations 2014, and other topic-specific legislation and guidance listed below. It is a starting point for adaptation, not a substitute for legal, clinical, HR, safeguarding or specialist professional advice.

15. When to seek further advice

Seek specialist advice where the issue involves serious harm, safeguarding, deprivation of liberty, restraint, children, professional misconduct, controlled drugs, radiation, termination of pregnancy, infection outbreak, water safety, employment dismissal, DBS barring referral, or regulatory enforcement.

16. Document control

Version Date Author Changes
v1.2 2026-07-21 Verivius (sample) Expanded the journey-allocation record to evidence current competence, passenger need, restrictions and approval.
v1.1 2026-07-19 Verivius (sample) Added the deployment approval workflow, decision evidence fields and linked companion policies.
v1 2026-06-10 Verivius (sample) Conformed to the Verivius policy standard.

This sample policy template was issued by Verivius. It is a template, not a substitute for legal advice or the provider's own policy-development process. Where this template and live law or regulator guidance diverge, the live source wins.

Awaiting final verification

The permitted crew clinical scope, whether any patient restraint is used (which would engage the Mental Capacity Act and restrictive-practice law), the competence framework and the current JRCALC and HCPC basis must be confirmed by an ambulance or patient-transport clinical lead for your service.

What good looks like here

Written from an ex-CQC inspector's chair, but the point is safe, well-led care your team can stand behind. Each row shows what strong evidence looks like, what thin evidence looks like, and where the expectation comes from.

In patient transport the clinical decision is often made alone, in a moving vehicle, some distance from a second opinion, by whichever crew the allocator put on the job. That makes the allocation decision itself the safety control: the whole journey turns on whether the crew's registration, scope and competency actually stretch to the patient in the back. The failure mode is specific to this service, a patient whose condition can change between two sites matched to a driver-only or care-assistant crew whose scope, sign-off or current registration does not reach that far, discovered only when the patient deteriorates on the road. The role-scope matrix, the verified registration, the practical competency sign-off and the allocation record are what let the service prove, before the wheels turn, that this crew can safely carry this patient, and they matter most for the bank and agency crews a passenger and the receiving unit have no way of telling apart from the service's own staff.

  1. The crew put on a journey can safely meet the clinical, mobility, communication, escort and equipment needs recorded for that patient, so a driver-only or care-assistant crew is never matched to a patient whose presentation could change beyond their scope in a moving vehicle. A rota entry is not evidence of competence: the allocation traces to the current role-scope matrix and the patient's assessed need, not to who happened to be free that shift.

    Strong evidence: The allocation or journey record made before the crew starts the work, showing the role-scope matrix version used, the patient's known clinical and mobility needs, the tasks the crew may perform unsupervised, any restriction or skill not authorised, and the allocator and clinical approver where required.

    Weak evidence: A journey allocated straight from the rota with no link to the role-scope matrix, no record of the patient's needs set against the crew's scope, and no approver. The tell is a driver-only or ambulance-care-assistant crew matched to a patient whose booking already flagged a foreseeable clinical risk, resolved only once the patient deteriorated between the two sites.

    A legal duty. This comes from legislation that applies to your service, so meeting it is not optional. The exact provision is cited beneath the badge.

    Health and Social Care Act 2008 (Regulated Activities) Regulations 2014, reg 18(1)

  2. A registered paramedic, nurse or other registered professional carrying a patient is on the live professional register and working within their current scope of practice, checked against the register rather than assumed current. The failure that matters is a clinician still deployed on clinical work after their registration has lapsed, because the role can no longer lawfully be performed and the patient is being cared for by someone the register no longer covers.

    Strong evidence: The registration check against the live register (the Health and Care Professions Council for paramedics, the Nursing and Midwifery Council for nurses) at appointment, before each renewal deadline and whenever a concern is raised, with the renewal date actively tracked and any lapse escalated before further deployment.

    Weak evidence: A registration number copied to the staff file at interview and never confirmed against the live register, or renewal dates kept nowhere in particular so a lapse surfaces only when someone happens to notice. Worse, a clinician who carried patients on clinical jobs during a period their registration had already lapsed.

    What the regulator expects to see. Not a law in itself, but CQC judges you against it, so an inspector will look for it and expect a reason where you depart from it.

  3. For each task that creates patient or staff risk, a named competent assessor has signed the crew member off to perform it, and attending a course is not treated as proof they can do it safely. The observations, oxygen equipment, moving-and-handling, wheelchair-restraint and stretcher or carry-chair tasks a crew member carries out are ones they have been assessed as competent to perform, not ones that merely appear on a training certificate.

    Strong evidence: The training matrix linked to role scope alongside the practical competency sign-off records, showing a dated assessment by a named assessor for the risk-creating tasks, with expiry or review dates and any supervised-practice condition recorded.

    Weak evidence: A training matrix reading all green from course-attendance certificates with no practical sign-off behind it, or a competency for a risk-creating task marked complete with no assessor, no date and no note of what was actually observed. Training booked to be finished during probation while the person already performs the task unsupervised.

    A legal duty. This comes from legislation that applies to your service, so meeting it is not optional. The exact provision is cited beneath the badge.

    Health and Social Care Act 2008 (Regulated Activities) Regulations 2014, reg 12(2)(c)

  4. When a crew member performs a clinical skill outside their agreed scope, the service makes the patient safe first, records it as an incident and reviews it as a controlled process, rather than logging it as a near miss and putting the crew member back on the same task next shift. Good intent is not treated as proof the action was safe, and the separate duties are each weighed on their own: the duty of candour owed to the person where harm or possible harm occurred, any referral to the professional regulator, and any statutory notification to CQC, none of which discharges another.

    Strong evidence: The clinical-skill-outside-scope incident record showing the patient made safe and clinically reviewed where needed, the crew member's role, training and sign-off status established, the duty-of-candour decision opened or ruled out with reasoning, and the professional-regulator and CQC-notification questions considered as separate lines, with the crew member paused from the task until review is complete.

    Weak evidence: An out-of-scope skill logged as a near miss and closed, the candour decision left blank, no consideration of a professional-regulator referral or a CQC notification, and the crew member allocated the same task the following shift because they meant well and the patient came to no obvious harm.

    What the regulator expects to see. Not a law in itself, but CQC judges you against it, so an inspector will look for it and expect a reason where you depart from it.

  5. Bank, agency and subcontracted crew are held to the same registration, scope and competency evidence as employed crew before they carry a patient, because the passenger and the receiving unit cannot tell an employed paramedic from a same-day agency booking. The service verifies that evidence itself rather than assuming the agency has covered it.

    Strong evidence: For each bank, agency or subcontracted crew member, the service's own register check where applicable, the agreed role scope for patient-transport work, the local induction and the competency evidence checked before deployment, held in the same allocation record as for employed staff.

    Weak evidence: An agency crew accepted on the agency's assurance with no independent register check, no local scope sign-off and no induction, deployed the same day to a patient. A subcontractor whose crews never appear in the service's own competency records at all, so the service cannot show who carried its patients or what they were signed off to do.

    What the regulator expects to see. Not a law in itself, but CQC judges you against it, so an inspector will look for it and expect a reason where you depart from it.

  6. The clinical guidance the crew works to is the current edition and is genuinely reachable by them, and a registered clinician's knowledge is kept current for the duties assigned, so a decision made alone in a moving vehicle rests on live guidance rather than a superseded version. The service evidences that it follows and holds the applicable standard; the clinical detail itself lives in that named source, not in a local paraphrase that can quietly drift out of date.

    Strong evidence: The service's record of the current JRCALC edition it holds or accesses and how crew reach it, together with the clinician's continuing professional development or currency record for the duties assigned, checked against the live JRCALC and HCPC sources before adoption.

    Weak evidence: Crew working from a printed extract or local crib sheet of unknown vintage with no link to the current edition, or a service that cannot show which edition it holds or that clinicians can reach it in the vehicle. No record that a clinician's currency was refreshed when their assigned duties changed.

    The recognised standard from a professional or clinical body, such as NICE or a royal college. Not a legal duty, but the accepted mark of safe practice, and a departure needs a documented reason.

Related

Last verified 20 July 2026

Spotted something to improve?

These are sample templates, not the last word. If you would change a wording, or want to help us confirm a detail, tell us and we will look at it.

Related Verivius content

Want help adapting this to your service?

A Verivius consultant can read your adapted policy against the live regulation and your service shape. The work fits inside a Mock Inspection engagement or a shorter consulting brief. A 20-minute conversation is the fastest way to find out whether the fit is right.

Get started free

Free to start, no card. A 14-day trial when you subscribe.

Last reviewed 21 July 2026