How do you keep the same technicians with each child?

Give each child a small, steady team. That means one primary technician who runs most of the sessions, one or two trained backups who know the child and the plan, and one supervisor who sees all of them. The primary gives the child and family a familiar face week to week. The backups mean a sick day or a resignation doesn't hand the child to a stranger. Idaho's CHIS rules don't require this set-up, and the research on technician continuity in particular is thinner than you might expect. But the evidence we could find points the same way.

This guide covers what the evidence actually says, what the Idaho rules do and don't cover, how to build a primary-and-backup team for each child, how to train a new technician in before they work alone, how to handle turnover, and what to tell families.

What the evidence says, and what it doesn't

We looked for public research on whether keeping the same technician with a child improves outcomes in habilitative or behavioral intervention. We didn't find a study that tests this directly. Here is what we did find.

• Turnover is recognised as harmful, and it can be predicted. A 2015 survey of 96 behavior technicians at 19 agencies in Southern California (Kazemi, Shapiro and Kavner, Research in Autism Spectrum Disorders) opens by noting that turnover hurts service quality and the therapeutic relationship. The study didn't measure child outcomes. It asked what predicts a technician's intention to leave. The answer was satisfaction with training, supervision, pay and the job itself. Actual pay didn't track with intent to leave.
• Consistent caregivers are a widely endorsed practice in early childhood, but the outcome data is mixed. A 2018 study of infant-toddler classrooms (Horm and colleagues, Early Childhood Research Quarterly) found that continuity of care was linked to higher teacher ratings of self-control, initiative and attachment, and fewer behavior concerns, while children were in those rooms. It found no consistent link once children moved on to preschool. The authors say their results don't give clear support for the practice and call for more research. Child care classrooms are not CHIS sessions, so treat this as related evidence only.
• One person alone may not be enough either. A classic review in the Journal of Applied Behavior Analysis (Stokes and Baer, 1977) describes a study where a greeting skill taught by one adult usually didn't carry over to other adults. It carried over to more than 20 staff once a second adult trained it alongside the first. A skill that only shows up with one person is fragile.

Put together, the honest reading is this. Nobody has proven that one technician per child produces better outcomes. There are good reasons to keep the team small and stable, and good reasons not to make it a team of one. A primary technician with trained backups fits both.

What the Idaho CHIS rules say (and don't)

Idaho's CHIS rules are in IDAPA 16.03.26, Sections 180 to 186, effective July 1, 2026. We read them in September 2026, along with the CHIS chapter of the Idaho Medicaid Provider Handbook (dated August 17, 2026). Neither one requires a child to keep the same technician. Neither sets a rule for training a technician on a specific child before their first session.

Several parts of the rules still bear on this topic:

• Implementation plans. A qualified provider completes and signs an implementation plan describing how the intervention will be carried out (Section 183.02). Anyone who works with the child needs to know that plan.
• Fidelity. The rules define fidelity as "the consistent and accurate implementation" of services under the chosen model or protocol (Section 180.06). Every new person on a child's team is a new chance for the plan to drift.
• Supervision. Intervention technicians must be supervised by a specialist or professional who observes and reviews their services, and supervision must occur monthly (Section 184.02). The handbook explains the purpose:

Supervision must occur monthly to ensure staff demonstrate the necessary skills to provide the services correctly.

• Annual training. CHIS providers must complete at least 12 hours of training each calendar year, including one hour of ethics and six hours of behavior methodology or evidence-based intervention (Section 184.09). This is general training, not training on a particular child.
• Who provides the hours. Ongoing prior authorization requests list the CHIS hours requested and the qualifications of the people who will provide them (Section 183.01.c). If a staffing change alters who is delivering a child's hours, check the current handbook for what that means for an open authorization.

So the rules set a floor: a written plan, monthly supervision and annual training, with fidelity defined as consistent, accurate implementation. Keeping a steady team and training people in on each child is how many agencies meet that floor well. It is good practice, not a legal requirement.

Building a primary and backup team for each child

Here is how a small team might look at our fictional agency, Sagebrush Behavioral Services.

Role	Who	What they do for J.M.
Primary technician	Ava	Most weekly sessions. Knows the plan best. First contact for session-level questions from the family.
Backup technician	Marcus	One regular session a week, plus cover when Ava is out.
Second backup (optional)	Priya	Trained in on J.M. and scheduled now and then so she stays familiar.
Supervisor	Dana	Monthly observation of each technician on the team. Owns the implementation plan.

A few habits make this work:

1. Give the backup a regular session. A backup who only appears in an emergency is really a stranger with a file. One standing session a week, or every other week, keeps the child used to them and keeps them current on the plan.
2. Cap the team size. We'd suggest two or three technicians per child. More than that and "familiar" stops meaning much. Fewer than two and every absence is a cancellation.
3. Match hours to what each technician can carry. A primary scheduled right at their limit will burn out. In the Kazemi study, satisfaction with the job predicted whether technicians meant to stay, and every technician who leaves takes a child's familiar face with them.
4. Keep the pairings visible. Whoever builds the schedule should be able to see, for each child, who the primary and backups are. If that only lives in someone's head, it leaves when they do.
5. Write it down. Note each child's team in your records so a new scheduler or supervisor can pick it up.

Training a new technician in before they work alone

Idaho's rules don't set out child-specific onboarding, so this is a practice choice. We think it's a strong one. Before a technician runs a session alone with a child, a good sequence is:

1. Read the implementation plan and the child's current goals, with the supervisor available for questions.
2. Shadow the primary for one or more sessions, watching how the plan is carried out with this child.
3. Run part of a session while the primary or supervisor is present and gives feedback.
4. Get a supervisor's sign-off that they can run the plan as written.
5. Meet the family, so the first solo visit isn't also the first hello.

How many shadow sessions is enough depends on the child and the plan. Your supervisor should decide, not the schedule. Whether overlap time can be billed is a separate question. Check the current handbook and your authorization before you assume it can.

The hard part is remembering. When a gap needs filling at short notice, it's easy to assign whoever is free without asking whether they've ever met the child. A check at the moment of assignment helps.

Cover Tuesday 1:00–3:30

J.R. · Dana is out

Available staff

PK

Priya K.

18 of 30 hrs this week

Suggested

JB

Jordan B.

26 of 30 hrs this week

SL

Sam L.

24 of 30 hrs this week

Priya is on J.R.'s Tuesday session.

Priya hasn't worked with J.R. yet

Before her first session, confirm she's been trained on J.R.'s plan.

Not yetShe's trained

Replay

Handling turnover without starting over

Technicians will leave. The goal is that a departure costs the child a familiar face, not their whole team.

• Promote the backup. If the backup already has a standing session, they can step up to primary with little disruption. This is the main payoff of the primary-and-backup model.
• Use the notice period. If the departing technician gives notice, use those weeks for overlap sessions with whoever is taking over.
• Re-check the whole schedule, not just one child. A technician leaving usually affects several children. Look at every child they served and every week they were booked, so no session is left without a technician.
• Refill the backup slot. Once the backup becomes primary, the child has no backup. Train someone new in before the next absence finds the gap for you.
• Look at why people leave. The research points at training, supervision and the job itself. Exit conversations and regular check-ins about supervision quality are cheaper than constant rehiring.

What to tell families

Families notice changes in who comes to the door, and a surprise change can shake their trust faster than the change itself. Some things that help:

• Explain the team at intake. Tell families their child will have a main technician and one or two others who know the plan. Say why: so sessions go ahead when someone is sick, and so skills carry over to more than one person.
• Introduce backups early, ideally during a shadow session, not on the day they're needed.
• Tell families about planned changes before they happen. Who is leaving, who is taking over, when, and what the handover looks like.
• Be honest about why, within reason. "Ava is moving on and Marcus, who has been seeing J.M. on Thursdays, will take over" is enough. Families don't need staff details, and your own privacy and HR policies still apply.
• Let them see the week. When families can see who is scheduled, a change is something they can check, not something they hear about at the door.

The rules also require that a copy of the child's implementation plan be offered to the parent or legal guardian (Section 183.02). A change of technician is a natural time to remind families that the plan stays the same even when the person running it changes.

9:41

Hi, ErinK.T.'s week

Mon

Sam

3:30–6:00 PM

Tue

Dana

3:30–6:00 PM

Updated

Wed

Sam

3:30–6:00 PM

Thu

Sam

3:30–6:00 PM

Fri

Maya

3:30–6:00 PM

Message Sagebrush

Call the agency

WeekMessagesHelpProfile

Replay

Where Pairing fits

Pairing is scheduling software we're building for Idaho CHIS providers. When you assign a session, it suggests staff. The first time a technician is paired with a child, it asks you to confirm their training with that child. Parents can see their own child's week, view-only, and message the agency. Pairing is still in development, and we're talking with Idaho providers about what they need. If this is a problem at your agency, get in touch.

How this page was made

We read IDAPA 16.03.26 and the Idaho Medicaid CHIS handbook chapter directly, and the research sources listed below, in September 2026. Where the evidence is thin or doesn't come from CHIS settings, we've said so. Drafted with AI assistance and reviewed by the Pairing team.