Most practices approach this as a question about staff: what is a technician allowed to do, what is an assistant allowed to do.
That framing gets the law backwards.
Delegation is a duty the supervising veterinarian owes — to delegate appropriately, and to supervise what they delegated.
The staff member's credential is an input to that judgement, not a substitute for it, and the exposure when it goes wrong sits with the veterinarian.
Delegation is a duty, not a permission
State practice acts consistently place the obligation on the supervising veterinarian.
They are responsible for the proper delegation of duties, and for exercising a level of supervision appropriate to what was delegated — sufficient to ensure the person is competent and that their work aligns with the treatment plan and the veterinarian's assessment of the patient.
Read that carefully, because the direction matters.
The rule is not "a technician may perform X." It is "a veterinarian may delegate X, to a person they have determined is competent, under an appropriate level of supervision."
That reframing changes what a practice needs to have in place.
A list of what each role may do is necessary but not sufficient — the practice also needs a defensible answer to how the veterinarian determined this person could do it.
Two separate ways to get it wrong
They are distinct failures and they are separately disciplinable, which is worth knowing because practices tend to guard against only the first.
Improper delegation — assigning a task the person should not have been assigned.
Boards frame this as delegating professional responsibilities to someone the licensee knows, or has reason to know, is not qualified by training, experience or credentials.
Note "has reason to know".
That is not a standard requiring actual knowledge; it reaches the veterinarian who did not ask.
Failure to supervise — delegating a task appropriately, and then not providing the supervision the task required.
A correctly-assigned task performed at the wrong supervision level is still a problem, and it is the more common failure in a busy practice where the veterinarian is genuinely in the building but not genuinely available.
Which supervision level attaches to which task is covered in the supervision guide — this page is about the duty, not the task list.
A credential is not a competency finding
This is the part practices most often get wrong in good faith, and it is the sharpest point on this page.
State rules commonly place responsibility on the supervising veterinarian to determine the competency of the credentialed technician, permit holder or assistant to perform a given task.
A credential establishes what a person may lawfully be permitted to do.
It does not establish that this individual, on this task, is competent to do it.
The gap is obvious once stated.
A newly credentialed technician and one with eight years of emergency experience hold the same credential and are not interchangeable on a difficult induction. "They're an RVT" is not a competency determination — it is the beginning of one.
Where this bites hardest is drugs.
The prescribing veterinarian carries a specific duty to determine that the person administering has had adequate training to do so safely, in the manner prescribed.
That duty does not transfer to the person holding the syringe — and for controlled substances specifically, staff always act as the registrant's agent, never as an independent authority; see DEA registration, records and logs.
General information, not legal advice
The three questions for any task
Whatever the task, the analysis is the same three steps in the same order.
Skipping straight to the third is the usual error.
- Is it reserved? Diagnosis, prognosis, prescribing and surgery are the veterinarian's everywhere and cannot be delegated to anyone.
- Does your state restrict it further — to credentialed staff only, or at a specified supervision level?
- Is THIS person competent to perform it, and how did the veterinarian determine that?
- Is the required supervision level actually satisfied right now — not merely satisfiable in principle?
- Is the delegation and the competency basis recorded anywhere?
The fourth item is where busy practices fail in fact rather than on paper. "Direct supervision" is not satisfied by a veterinarian who is on the premises but unreachable in a consult, and the answer changes hour to hour rather than being a property of the roster.
Where the exposure actually sits
With the veterinarian and the practice — not with the staff member who performed the task.
A veterinarian is subject to discipline for improperly delegating care or treatment duties to a non-veterinarian, and separately for failing to properly supervise a non-veterinarian performing delegated duties.
Some states are explicit about specific instances: Utah, for example, treats delegating the administration of anesthesia or sedation to unlicensed assistive personnel as unprofessional conduct where the veterinarian is not providing direct supervision.
The asymmetry is the operationally important part.
An assistant asked to do something beyond what the practice may delegate is in an uncomfortable position; the veterinarian who asked is in a disciplinable one.
That is why delegation is a practice-level system rather than a staff-training topic.
Individual good intentions do not protect a veterinarian from a delegation model that was never designed.
Building a model that holds
What separates practices that can answer a board question from those that cannot is usually documentation rather than knowledge.
Write the scope down. A per-role task list, mapped to your state's supervision requirements, that says what may be delegated to a credentialed technician, to an uncredentialed assistant, and to neither.
Record competency, per person and per task. A sign-off when someone is cleared for induction, or for dental extractions where permitted, with who observed and when.
This is the artefact almost no practice has and the one that most directly answers the duty.
Make supervision legible. If a task requires the veterinarian on the premises and quickly available, the team needs to know who that is on any given shift and how to reach them — otherwise the requirement is theoretical.
Revisit it when staffing changes. A delegation model built around an experienced team quietly stops being accurate when that team turns over, which is precisely when a practice is least likely to review it.
NAVTA's related point is worth pairing with this: where credentialed technicians are scarce, hiring assistants into genuinely supportive roles is a better answer than assigning uncredentialed staff the same duties as credentialed ones — which both erodes the credential's value and pushes at the delegation limits.
What this means for your job postings
Two practical consequences, and they run in opposite directions.
If the role's tasks require a credential in your state, the posting must require one — and describing the work accurately is what gets you applicants who can actually do it. "Credentialed preferred" on a role that legally requires credentialing is a hiring problem waiting to arrive.
If they do not, say so explicitly.
Ambiguity filters out capable uncredentialed candidates who assume they are ineligible, which in a shortage market is self-harm.
And be careful what you call people.
In states that protect the abbreviations RVT, LVT and CVT, applying them to uncredentialed staff carries exposure — a separate question from what those staff may lawfully do, and covered in working without a credential.
Browse open technician positions to see how widely practices vary in getting this right.