Care assistant scope of practice is where the most avoidable risk in aged care sits. Not because staff are careless, but because the boundary is rarely where people assume it is, and it moves between facilities. A personal care assistant who applied a simple dressing in their last job may work somewhere that requires a registered nurse for the same task. Nobody told them the rule changed, because everyone at the new facility already knew it.
The worker then faces a resident who needs something, a colleague who is busy, and a judgement call about whether this is theirs to make. Most of the time they guess correctly. The problem is the times they do not, and the fact that nobody finds out until something goes wrong.
[IMAGE: care assistant scope of practice - a personal care assistant checking a task against facility policy on a handheld device, alt text "care assistant scope of practice check at the point of care"]
Why scope is harder to pin down than it looks
Three things make this genuinely difficult for a frontline worker.
Scope varies by employer. Within the bounds of regulation and qualification, individual providers set their own delegation rules. A task permitted at one facility may be restricted at another for entirely reasonable local reasons, including past incidents or the availability of supervision.
Scope varies by resident. A task within a worker's general scope may be restricted for a specific resident because of a care plan direction, a behaviour support plan or a clinical instruction. The worker may be competent and still not authorised in this instance.
Scope varies by circumstance. Some tasks are permitted with supervision available and not permitted without. The same worker doing the same task is inside scope at 2pm and outside it at 2am, which is counterintuitive and easily forgotten.
No induction session can transfer all of this reliably. It is too conditional, and the conditions are exactly the thing people forget.
The question a worker actually needs to ask
Faced with a task, the practical question is not "what is my scope" in the abstract. It is narrower and more useful: am I permitted to do this specific thing, for this specific resident, in the circumstances I am currently in?
That is a question with a documented answer. It sits across the facility's delegation policy, the resident's care plan and the competency framework, which is precisely why it is hard to look up quickly. The worker would need to know which three documents to consult and how they interact.
Ask Norma changes the shape of that lookup. The worker asks the question as they would ask a senior colleague, in plain language, and gets the facility's own position back. They do not need to know that the answer lives partly in a delegation policy and partly in a care plan. The point is not that the information was unavailable before, it is that retrieving it required knowledge the person asking did not have.
This matters most for the workers least able to ask a colleague: new starters, agency staff, and anyone working a shift where the senior person is occupied elsewhere. Guidance on how assistants are supported in practice is covered in AI support for personal care assistants.
Checking before acting, not after
The sequencing here is the whole point. A scope check performed after the task is a documentation exercise. Performed before, it is a control.
Staff generally accept this in principle and skip it in practice, because the check historically took too long. When a lookup takes five minutes and involves finding a folder, a worker under time pressure will rely on memory. When it takes fifteen seconds on a device already in their hand, the calculation changes. Ask Norma makes checking cheaper than guessing, which is the only reliable way to change behaviour at the point of care.
There is a cultural dimension worth naming. In some teams, asking whether you are allowed to do something reads as inexperience. That perception is expensive, and leaders should counter it explicitly. A worker who checks is demonstrating exactly the judgement the role requires, and framing it that way in induction and supervision does more than any policy statement.
What to do when the answer is no
Discovering a task is outside scope creates a second problem: the resident still needs it. A check that leaves the worker stuck has solved nothing.
A useful scope answer should carry the next step. If this is not yours, whose is it, and how do you reach them. Facilities that document delegation without documenting escalation leave workers with a prohibition and no route forward, and the predictable result is that the task gets done anyway by someone who has decided the resident's need outweighs the rule.
This is worth testing directly. Ask Norma the scope question a worker would actually ask, then check whether the response tells them what to do next or merely what not to do. Where the answer stops at the prohibition, the underlying policy needs extending, because the gap is in the source material rather than the lookup.
The escalation side of this sits in the facility's clinical handover and escalation policy, and the two documents need to agree with each other. Where delegation policy and escalation policy have been written separately and never reconciled, workers find the gap quickly.
Competency is not the same as authorisation
These get conflated constantly. A worker can be entirely competent at a task and not authorised to perform it, and the distinction is not bureaucratic pedantry.
Authorisation reflects the facility's assessment of supervision, accountability and risk, not just the individual's skill. An experienced worker who has performed a task hundreds of times elsewhere is still working under this facility's delegation framework, and the framework exists because accountability sits with the provider.
Where a worker is competent but not authorised, that is a gap worth closing deliberately rather than informally. The route is assessment and documented sign-off under the workforce training and competency policy, not an informal understanding that this person is fine to do it.
Recording the check itself
A scope query is useful information about the facility, not just about the moment. Patterns in what staff ask reveal where the delegation framework is unclear.
If multiple workers ask the same scope question, the answer is not that those workers need reminding. It is that the policy is ambiguous, or that it is written in language that does not match how the task is described on the floor. Either way the fix belongs to the organisation.
The queries staff put to Ask Norma are the cleanest source of this signal, because they capture uncertainty at the moment it occurred rather than what people recall in a meeting. A worker who quietly checks something four times in a fortnight has told you more about where the framework is unclear than any survey will.
Reviewing recurring scope questions quarterly, alongside incident data, tends to surface the same handful of tasks repeatedly. Those are the ones to clarify in writing, because every worker who guessed instead of asking guessed about the same thing.
Where this connects to liability
Individual exposure concentrates at the scope boundary. A worker who acts outside scope, even with good intent and a good outcome, has taken on personal risk that the facility's framework was designed to prevent.
Being able to demonstrate that a worker checked before acting is meaningful evidence, both for the worker and for the provider. It shows a functioning control rather than an assumption of compliance. The broader picture of where these responsibilities fall is set out in nurse liability guidance.
Frequently Asked Questions
Q: What is care assistant scope of practice?
The set of tasks a care assistant is permitted to perform, determined by their qualification, the facility's delegation framework, the individual resident's care plan and the supervision available at the time. It is narrower and more conditional than most workers assume.
Q: How does Ask Norma help with scope questions?
It lets a worker ask whether a specific task is permitted for a specific resident in plain language, and returns the facility's own position without requiring them to know which policy, care plan or framework holds the answer.
Q: Does scope of practice change between facilities?
Yes. Within regulatory and qualification limits, providers set their own delegation rules. A task permitted at one facility may be restricted at another, which is why prior experience is not a reliable guide for a new starter.
Q: What should a worker do when a task is outside their scope?
Escalate to whoever is authorised, using the facility's documented pathway. A scope answer that does not tell the worker who to go to next leaves the resident's need unmet, which is how boundaries get crossed.
Q: Is being competent at a task the same as being authorised to do it?
No. Authorisation reflects the facility's assessment of supervision, accountability and risk. A competent worker may still require documented sign-off before performing a task, and closing that gap should be deliberate rather than informal.
Q: Should scope queries be reviewed by management?
Yes, in aggregate. Repeated questions about the same task indicate the delegation framework is unclear or written in language that does not match how staff describe the work. That is an organisational fix, not a training reminder.
