The First 10 Days: A School BCBA's Back-to-School Playbook

The first week of school creates a particular kind of pressure for a BCBA.

Schedules are changing by the hour. Teachers are learning students. Administrators are watching arrival, dismissal, transportation, and staffing. Old behavior plans are being pulled out of files. New referrals are already beginning to appear.

And the school BCBA feels the pull to prove value quickly.

That pull can lead to a predictable mistake: starting with recommendations before you understand the system that has to carry them.

Recent public discussion among school BCBAs has been remarkably consistent. A newly hired BCBA asked what to bring and what to do on day one. Experienced school practitioners kept returning to the same advice: learn the culture of each campus, observe before suggesting changes, understand the referral process, and build relationships with staff. One person put the implementation issue plainly: relationships with staff matter if you want plans run with fidelity.

That is not soft advice. It is technical advice about implementation.

Research with special education teachers has identified predictable collaboration breakdowns when BCBAs are perceived as condescending, blame staff when an intervention struggles, or recommend procedures that do not fit the classroom. Other research suggests many behavior analysts receive little formal training in consultation or school collaboration even though those skills are central to the job.

So your first deliverable should not be a perfect behavior plan.

Your first deliverable should be an accurate map of how support actually works in that school—and enough trust to improve one part of it together.

Here is a practical 10-day playbook.

Days 1-2: Learn the Building Before You Try to Change It

Start with the principal or site administrator. Ask for 20 minutes and keep the questions concrete:

• What are the two routines creating the most concern right now?
• How does a teacher request behavior support?
• Who decides what gets prioritized?
• Which teams already address attendance, discipline, MTSS, special education, and mental health?
• Where have behavior supports worked well here?
• What should I understand about this campus before I make suggestions?

Then get the operational basics: a campus map, bell schedule, staff directory, duty schedule, crisis procedures, referral pathway, and the meeting calendar. If you serve multiple schools, do this separately at every campus. Schools in one district can have very different histories, language, leadership practices, and tolerance for outside recommendations.

Do not confuse the written system with the working system.

The handbook may say referrals go through an MTSS team. In practice, the assistant principal may text the BCBA when a classroom is escalating. The organizational chart may show one chain of support while teachers rely on a veteran paraprofessional who knows every student and every transition.

You need both maps.

By the end of day two, create a one-page campus map with:

• key people and their roles;
• standing meetings;
• formal referral steps;
• informal routes that currently drive requests;
• high-risk routines and locations;
• current student-support priorities;
• questions that still need answers.

This is not bureaucracy. It prevents you from accidentally building a second system nobody will use.

Days 3-4: Observe Routines, Not Just Students

When a concern is raised, the fastest path is often to watch the student. That matters, but it is too narrow for the first week.

Observe arrival, transitions, lunch, recess, independent work, dismissal, and any routine staff identify as difficult. Watch what the environment asks of everyone.

Look for:

• how directions are delivered;
• how long students wait;
• where noise and crowding increase;
• whether expectations change across adults;
• what students can do when they need help or space;
• how reinforcement already occurs naturally;
• which parts of the routine depend on one particular staff member;
• what happens when a para is absent or the schedule changes.

This is the difference between observing a child who leaves the line and observing a dismissal routine with an eight-minute wait, competing adult directions, no clear finished activity, and a preferred playground visible through the gate.

The first description invites a student-fixing plan. The second gives the team changeable variables.

Do not arrive with a multi-page data sheet unless the question requires it. For these early observations, a simple three-column note is enough:

You are looking for leverage, not trying to complete an FBA on every student in the hallway.

Day 5: Ask Staff What Is Feasible

Now talk with the people who run the routines.

Avoid opening with, “What behavior strategies have you tried?” That question can sound like a test. Start with the work:

• Which part of this routine is hardest to run?
• What is already helping?
• When does the routine go better?
• What have people suggested that was unrealistic here?
• If we changed one small thing next week, what would save the most time or stress?
• What could we measure without adding another clipboard?

Listen for constraints without treating them as resistance.

“I cannot do that while teaching 28 students” is data.

“The visual disappears by lunch” is data.

“Only one para knows the plan” is data.

Teachers in collaboration research have reported valuing BCBA expertise while also describing recommendations that felt impractical or disconnected from classroom realities. If a strategy cannot survive group instruction, competing demands, and normal staffing disruptions, feasibility is not an afterthought. It is part of the intervention.

End the conversation by reflecting back what you heard. Do not promise a full solution. Say something like:

It sounds like the biggest breakdown is the five-minute wait after recess, especially when staffing changes. You already have a strong entry routine once students reach the room. Let me bring back one small option we can test without adding a new data system.

That response shows that consultation is a shared problem-solving process, not expert advice delivered from the doorway.

Days 6-7: Audit the Referral and Response System

By the second week, you will have individual requests. Before accepting all of them as separate cases, look for the pattern.

For each request, record:

• who requested support;
• the routine and setting of concern;
• what has already been attempted;
• whether there is an immediate safety issue;
• whether the concern is individual, classroom-wide, or system-wide;
• the next decision the team actually needs to make.

You may discover that five “student behavior” referrals all involve the same unstructured transition. Or that teachers are requesting FBAs because there is no accessible Tier 2 consultation process. Or that completed BIPs are not reaching the paraprofessionals expected to implement them.

This is where a BCBA can prevent becoming the district's behavior inbox.

Create a visible triage pathway. It does not need to be elaborate. A useful first version distinguishes:

1. immediate safety response;
2. brief classroom consultation;
3. targeted progress monitoring or Tier 2 support;
4. individualized assessment and plan development;
5. team or IEP processes required by policy and law.

Review it with administration and the relevant student-support team. Clarify what happens next, who communicates with the requesting staff member, and how urgent needs are identified.

The goal is not to keep students away from individualized support. The goal is to match the response to the question instead of using an FBA as the only door into behavior help.

Days 8-9: Build One Early Win With Staff

Choose one routine where the team has a reasonable chance of seeing improvement quickly.

The right early win is:

• important to staff and students;
• small enough to test within a few days;
• connected to something you observed directly;
• feasible with current resources;
• measurable with a light data system;
• designed with the people who will implement it.

Examples include:

• reducing wait time during a transition;
• adding a clear “finished” cue to independent work;
• placing a help or break response where it is actually needed;
• assigning one adult to give directions during dismissal;
• increasing behavior-specific praise during one fragile routine;
• moving materials so the first task step is ready before students arrive.

Define the adult action and the student outcome separately.

For example:

Adult action: Before students return from recess, the first task and a two-step visual are on each desk. The teacher gives one direction and points to the visual.

Student outcome: Number of students beginning the first task within two minutes.

Check the plan in the routine itself. Ask the teacher what needs to change. Then come back and review the result quickly.

The message is bigger than the strategy: When you bring me a real classroom problem, I will listen, work beside you, and help build something usable.

Day 10: Close the Loop

On day ten, summarize what you learned and what happens next.

Send a short update to the administrator and core support team:

• the routines observed;
• the strengths already present;
• the main system bottleneck;
• the early test and what happened;
• the referral pathway you recommend;
• the next two priorities;
• what you are deliberately not taking on yet.

Then return to the staff involved in the early win. Share the data, ask whether the change helped, and decide together whether to keep, revise, or stop it.

Closing the loop matters. Too many consultation requests disappear into observation notes, meeting agendas, or the BCBA's task list. Staff learn whether collaboration is worth the effort by what happens after they ask for help.

What Not to Do in the First 10 Days

Avoid these common traps:

Do not rewrite every inherited BIP. First find out which plans are active, understood, feasible, and producing useful data.

Do not turn every concern into an individual student case. Look for common routines and system conditions.

Do not lead with jargon. Translate the principle into an observable classroom action.

Do not mistake staff constraints for lack of commitment. Test what the environment can support.

Do not promise response times before you understand demand. Map the pipeline first.

Do not wait months to be useful. Listening is not passivity. Pair it with one visible, shared improvement.

Your Real First-Week Product

At the end of 10 days, you may not have completed a new FBA. You may not have trained the whole staff. You may not have solved the campus's most serious behavior concern.

But you should have something more foundational:

• a map of how the school actually works;
• a clearer referral and triage pathway;
• direct knowledge of the routines where support breaks down;
• staff input about what is feasible;
• one example of a change built and reviewed together;
• a short list of priorities the team understands.

School-based transdisciplinary work requires more than placing several experts around the same table. It requires shared goals, respect for each person's knowledge, and interventions that fit the environment where they must live.

That begins before your first recommendation.

Walk the campus. Learn the routines. Ask better questions. Make one useful change with people, not for them.

That is how a school BCBA proves value in the first 10 days.

References

• Light-Shriner, C., Pizzella, D., Schreiber, J. B., & Wahman, C. L. (2025). Collaborative practices of behavior analysts in school settings: Evidence from the field. Behavior Analysis in Practice, 18, 421-439. https://doi.org/10.1007/s40617-023-00883-0
• Mann, A., Grimes, L. M., & Leichman, E. (2024). The need for greater training in consultation for behavior analysts. Behavior Analysis in Practice, 17, 488-504. https://doi.org/10.1007/s40617-023-00872-3
• Reilly, A. M., Crowell, G. E., Thoele, J. M., DeAngelo, S., & Bak, M. Y. S. (2025). School-based transdisciplinary teaming to maximize behavioral supports. Behavior Analysis in Practice. https://doi.org/10.1007/s40617-025-01054-z
• Squires, M., Cutrer-Párraga, E. A., Morris, J. R., Miller, E. E., & Hansen, B. D. (2025). Navigating collaboration: Factors influencing special education teachers' relationships with BCBAs in diverse school contexts. Behavior Analysis in Practice, 18, 332-347. https://doi.org/10.1007/s40617-024-01009-w