Sample policy · Ambulance

Crew clinical scope and JRCALC competency policy (ambulance)

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 professional guidance sources are the Joint Royal Colleges Ambulance Liaison Committee (JRCALC) clinical practice guidelines and the HCPC standards of proficiency for paramedics, which are not held in the Verivius guidance manifest. · 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 staff-competence duty that this policy operationalises:

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. Regulation 12 adds that the people providing care must have the qualifications, competence, skills and experience to do so safely.

3. Purpose

This policy sets out how the Service defines crew clinical scope, checks JRCALC currency, records competency 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, doctor or other registered healthcare professional

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

The Service does not assume that a professional registration automatically covers ambulance practice or use of JRCALC pathways.

6.3 Technician and associate roles

The Service defines each 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 and emergency care assistant

The care-assistant role supports patient transport, observation, comfort, moving and handling and escalation.

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. JRCALC currency and competency sign-off

The Service keeps a training matrix linked to role scope and the current JRCALC edition.

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, staff or public risk.

Staff do not quote JRCALC wording in this policy. The Service checks the current edition directly and keeps local competency standards aligned to it.

7.1 Deployment approval workflow

The Operations Manager uses the following workflow before allocating a crew member to patient-facing work:

  1. Confirm the job profile: record the expected patient need, interventions, equipment, vehicle and likely escalation route.
  2. Match the role: check the role-scope matrix for the tasks the crew member may perform without direct supervision.
  3. Check current evidence: confirm registration where applicable, induction, required 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 deployment, or allocate a different crew mix where the evidence does not match the job.
  6. Reassess on change: if the patient's presentation or required intervention 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 deployment record before the Crew member starts the job. 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 deployment record to show the exact scope version, current evidence, restrictions, approval and outcome.
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; original content preserved and renumbered.

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.

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.

An ambulance crew makes its most consequential decisions in the back of a moving vehicle or at the roadside, alone, on a person who is often acutely unwell and who had no say in who came for them. There is rarely a colleague to check the call in real time and rarely a second chance to make it. That is why the risk this policy guards is scope creep: a technician drawn into a paramedic task because the patient was deteriorating and help was minutes away, or a driver-only crew meeting a presentation the role was never meant to hold. The evidence trail matters because it is the only thing that can show, after the event, that the person who arrived was matched to what the patient actually needed before the shift began, rather than assumed from the rota. And when a crew member does step outside their agreed scope, the record of what was done, whether the patient was made safe, and whether candour, an HCPC referral and a CQC notification were each weighed as separate questions is what turns a near miss into learning rather than the next person's harm.

  1. Each crew member is matched to a job only when the role-scope matrix and their current competency record show they may perform that patient's likely tasks without direct supervision, so the person who arrives is competent for what they actually need. A traceable deployment decision happens before the shift, not a rota entry standing in for a competence check.

    Strong evidence: The allocation or deployment record made before the crew member starts the job, showing the role-scope matrix version used, the registration, training and practical competency evidence checked, any restriction or supervised-practice condition, and the named approver.

    Weak evidence: A rota entry treated as proof of competence, with no deployment record behind it; or a deployment record that names no role-scope matrix version and leaves the restriction field blank, so nobody could reconstruct why this crew member was judged safe for this job. Also weak: a crew mix approved for a job profile the booking information already showed it could not safely hold.

    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. Only clinicians whose professional registration is confirmed current make clinical decisions, checked against the live register with a dated result rather than a certificate taken on trust at interview, and re-checked before each renewal falls due.

    Strong evidence: Dated register-check records tied to each clinician (the HCPC register for paramedics, and the relevant regulator's register for any nurse or doctor used on a job), with renewal dates tracked and the check repeated at recruitment, before renewal and when a concern is raised.

    Weak evidence: A registration number held on file that was never confirmed against the live register, or a certificate photocopied years ago and never rechecked. Renewal dates kept nowhere in particular, so a lapse surfaces only when someone happens to notice, by which point the person may already have worked a role their registration no longer covered.

    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)

  3. Where a task carries patient, staff or public risk, a named competent assessor has signed the crew member off as able to do it in practice, so attending the training is not treated as proof of competence.

    Strong evidence: Practical competency sign-off records naming the assessor and the task, held alongside the training matrix, with the service's local competency standards aligned to the current JRCALC edition.

    Weak evidence: A training matrix all green where course completion is treated as competence, with no practical sign-off behind any high-risk task; or a local competency standard that names no JRCALC edition, so nobody can tell which version of the guidance the person was signed off against.

    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(2)(a), read with reg 12(2)(c)

  4. The clinical guidelines the crew works to are the current JRCALC edition, and the service can show which edition its local competencies and pathways are aligned to, so nobody is practising to a superseded guideline.

    Strong evidence: The record of the current JRCALC edition the service holds or accesses, the review of the training and role-scope matrix against the current release, and the update record where a JRCALC change affects a role.

    Weak evidence: A training matrix that references JRCALC with no edition and no date, so nobody can tell whether it reflects current guidance; or a new JRCALC release landing with no review of which local competencies or pathways it changes. Working to current JRCALC clinical guidelines is professional guidance rather than statutory in itself; the duty to provide safe care and treatment behind it is Regulation 12.

    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.

  5. When a crew member performs a clinical skill outside their agreed scope, the service's first move protects the patient, by making them safe and arranging clinical review, and the review does not treat good intent as proof the action was safe. The crew member is paused from the relevant task until the review is complete, rather than left on it.

    Strong evidence: The clinical-skill-outside-scope incident record showing the patient made safe, what skill was performed against the person's role and sign-off status, the task paused pending review, and the recorded reasoning behind any return to duty.

    Weak evidence: An out-of-scope event closed on the basis that no harm resulted or that the crew member meant well, with the person back on the same task before any review. The duty of candour owed to the person under Regulation 20 where its harm threshold is met, an HCPC referral and a CQC statutory notification are separate questions, none discharging another; a record that weighs none of them, or folds them into a single line, is thin.

    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)(a)-(b)

  6. Unregistered crew and driver-only vehicles are matched to patients whose needs their defined scope actually fits, and the crew know when to stop and escalate. A driver-only job goes to a patient whose booking information, risk assessment and escort arrangements make that role safe, not to whoever is free.

    Strong evidence: The written role-scope record for each unregistered role with Care Certificate or equivalent induction evidenced, and allocation records showing driver-only and care-assistant jobs matched to a suitable patient with a recorded escalation route for a change in presentation.

    Weak evidence: An unregistered role with no written scope, so basic observations or oxygen handling drift in without local authorisation; or a driver-only job given to a patient whose booking already flagged a risk the role could not hold, with no escort and no escalation recorded when the presentation changed. Matching driver-only jobs to a suitable patient and evidencing the Care Certificate for unregistered roles are Verivius and Skills for Care practice; the duty to deploy people competent for the work is Regulation 12.

    Our recommended baseline. Not a legal or regulatory requirement, but a sensible standard we suggest where the rules leave the detail to you. Adapt it to your service.

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