Run Your ABA Clinic Weekly Operations Meeting in 45 Minutes
A weekly ABA clinic operations meeting should cover the scorecard, the issues behind red numbers, and decisions with owners and dates. Run it in 45 minutes with five to eight people, send the scorecard and issue list the day before, and keep updates out of the room.
The short answer: the agenda in one table
An ABA clinic weekly operations meeting should cover the scorecard, the issues behind the red numbers, and the decisions that follow. Run it in 45 minutes with five to eight people, send the scorecard and the issue list the day before, and end every issue with an owner and a date. Anything that is only an update goes in writing, not in the room.
Here is the whole meeting on one card. The segments adapt the common Level 10 format, explained below, to a 45-minute clinic meeting.
| Min | Segment | Input | Owner | Output |
|---|---|---|---|---|
| 3 | Check-in | One sentence each: something good this week | Facilitator | Everyone has spoken once |
| 8 | Scorecard | The eight numbers, read as on or off target | Operations director | Red numbers turned into issues |
| 4 | Priorities | Quarterly priorities, on or off track | Owner or CEO | Off-track items turned into issues |
| 3 | Headlines | Customer, staff or payer news, one line each | Anyone | No debate, issues added if needed |
| 4 | Last week's to-dos | Decision log from last week | Facilitator | Each marked done or not done |
| 20 | Issues | Ranked issue list | Issue owner | A decision, an owner and a date per issue |
| 3 | Conclude | Decision log | Facilitator | To-dos read back, meeting rated |
That adds up to 45 minutes. The rest of this guide explains why each piece is there and how to make it work in a clinic. It pairs with our ABA practice KPIs guide, which defines the scorecard used in the second row.
Where the format comes from, and what the evidence says
The structure is adapted from the Level 10 meeting from EOS One, a business-operating-system vendor. Its page describes a 90-minute format: segue (5 minutes), scorecard (5), rock review (5), headlines (5), to-do list (5), IDS (identify, discuss, solve) for one hour, and a conclude (5). Its scorecard is a table of weekly measurables, each with a metric, a goal and an owner. This is a vendor's published method, and we have adapted it. What it means for you: the shape is a proven habit for many teams, but copy the principle, not the clock. We halved the length and the issue time to fit clinic leaders who cannot give up 90 minutes.
Two HBR pieces support the design choices. Roger Schwarz writes that poor agenda design causes problems such as unprepared participants and people veering off track, and that "an effective agenda sets clear expectations for what needs to occur before and during a meeting." What it means for you: a pre-read and a fixed agenda are the cheapest fixes for drift.
Paul Axtell's article reports that Robert Sutton of Stanford, reviewing research on group size, concluded that "the most productive meetings contain only five to eight people," and that beyond a tipping point the quality of the conversation erodes. The page gives no study details. What it means for you: keep the room small and send the rest a written summary.
To be plain about the limits: this is practitioner advice and management commentary. None of these sources proves that a particular format improves ABA clinic outcomes. Treat the agenda as a sensible starting point and adjust it after a month of use.
Who attends and how big
Aim for five to eight people. At most clinics the core group looks like this:
| Role | Why they are in the room |
|---|---|
| Owner or CEO | Decides priorities and unblocks |
| Operations director | Owns the scorecard and runs follow-through |
| Clinical director | Speaks for delivery and supervision |
| Intake lead | Owns referral-to-start numbers |
| Scheduling lead | Owns fill and waitlist numbers |
| Billing or RCM lead | Owns authorization and claim numbers |
| Site lead, if multi-site | Brings local blockers |
If you have more people who want a seat, rotate site leads, or give them a written recap. The rule is that everyone in the room owns a number or a decision. Observers belong in the notes, not the meeting.
Pre-read: scorecard and issue list the day before
The meeting is only 45 minutes because the work happens beforehand. Use this checklist, owned by the operations director and sent by end of day Sunday or by 3:00 p.m. the previous workday:
- Scorecard updated, with the same formulas as last week.
- Each red number has a one-line cause guess from its owner.
- Issue list ranked by impact, with the owner named.
- Last week's decision log attached.
- Quarterly priorities with an on-track or off-track mark.
- No new slides, no long reports. One page of numbers, one page of issues.
Everyone reads it before the meeting. In the room, nobody presents numbers; they only react to them.
Pre-read, sent the day beforeScorecard updatedSame formulasA cause guess for each redFrom its ownerIssue list rankedOwners namedLast week's decision logAttachedOne page of numbers, one page of issues.The agenda, segment by segment
Check-in (3 minutes)
One sentence each: a win from the week, personal or professional. It is short on purpose. It makes sure everyone speaks early and sets a human tone before the numbers.
Scorecard (8 minutes)
Read the eight numbers as on target or off target. Do not discuss causes here. If a number is off, the owner says "that's an issue" and it goes on the list. The scorecard maps to the four areas leaders care about:
| Area | KPIs from the guide | Owner |
|---|---|---|
| Intake | Referral to first session; ready-to-start families waiting | Intake lead, scheduling lead |
| Scheduling | Delivered vs. scheduled; cancellation fill rate | Operations lead, scheduling lead |
| Revenue | Hours delivered vs. authorized; renewals at risk; billing lag | Clinical director, billing lead |
| Staffing | Supervision delivered vs. required | Clinical director |
The thresholds are yours. Set them from a few weeks of your own data, not from a blog post. For more on scheduling numbers, see our scheduling best practices guide.
Priorities (4 minutes)
Review the three to five priorities for the quarter. For each, say on track or off track. Off track becomes an issue. Do not describe progress in detail.
Headlines (3 minutes)
One line each: a payer notice, a staff change, a family concern. No discussion. If it needs a decision, add it to the issue list.
Last week's to-dos (4 minutes)
Read each commitment from the decision log: done or not done. Not-done items either move to the issue list or get a new date, once. The point is accountability, not blame.
Issues (20 minutes)
This is the meeting. Take the top issue and use three steps:
- Identify: state the real problem in one sentence. The first statement is often a symptom.
- Discuss: each person speaks once, briefly.
- Solve: the group decides, the owner is named, the date is set, and it goes into the log.
Plan for two or three issues, not seven. What is left stays on the list for next week. If an issue needs people who are not in the room, assign someone to talk to them and bring back a proposal, rather than guessing. If an issue turns out to be a long project, the decision is who will scope it and when the group will see the plan. A meeting that ends with clear next steps, even small ones, is doing its job.
Conclude (3 minutes)
Read back the decisions. Rate the meeting from 1 to 10 aloud. If the average drops below 8 twice in a row, change something.
Red flags in the weekly numbers
These are patterns worth a conversation. The cutoffs are set by your clinic and are not universal.
| Pattern | What it often means | First question to ask |
|---|---|---|
| Referral-to-start rising two weeks running | A stalled stage in intake or staffing | Which stage holds the oldest file? |
| Ready families up while fill rate falls | Open hours are not reaching waiting families | Is the short-notice list current? |
| Delivered vs. authorized falling behind | Cancellations or schedule gaps | Which clients are furthest behind pace? |
| Any renewal at risk | A deadline will be missed without action | Who submits it, and by when? |
| Billing lag growing | A blocked step between session and claim | Is it notes, review or submission? |
| Any RBT off track on supervision | A monthly requirement is at risk | Who books the contact this week? |
Do not read a single red week as a trend. Two in a row is the usual trigger to act.
Worked example: one meeting at a three-site clinic
Example (invented numbers, not a real clinic). A clinic with three sites starts with seven invited attendees, then cuts to six by moving one site lead to a written recap on weeks their site is green.
The scorecard takes 8 minutes. Six of eight numbers are on target. Two are off:
| KPI | Target | Last week | Status |
|---|---|---|---|
| Cancellation fill rate | 40% | 24% | Off target |
| Renewals at risk | 0 | 2 | Off target |
Two issues make the list, and they take 20 minutes.
Issue 1: the fill rate at Site B. The scheduling lead says the short-notice list has not been refreshed since September. The group decides to rebuild it from the ready-to-start list, owner scheduling lead, due Wednesday. A related post, same-day cancellation backfill, covers the ladder.
Issue 2: two authorizations ending within 30 days. The billing lead explains that a clinical document is missing for one of them. The clinical director commits to providing it within 2 business days, and the billing lead submits both by Friday.
In the conclude segment, the facilitator reads back two decisions, two owners and two dates. The meeting ends at minute 45. Next Monday, the to-do segment starts by checking those two items.
Scorecard: 6 of 8 on targetThree sitesCancellation fill rateOff targetRenewals at riskOff targetReferral to first sessionOn targetEach red number becomes an issue with one owner.The decision log and issue list templates
Copy these.
Issue list
| Rank | Issue | Owner | Raised on | Status |
|---|---|---|---|---|
| 1 | Open |
Decision log
| Date | Decision | Owner | Due date | Done? |
|---|---|---|---|---|
What good looks like
These are our recommendations, not research benchmarks:
- The meeting ends on time at least four weeks in five.
- Every attendee owns a number or a decision.
- At least 80% of to-dos are done by their date.
- Every issue closes with an owner and a date.
- Average meeting rating is 8 or higher.
Common mistakes
- No pre-read. It happens because the scorecard is built live. Fix: send it the day before, and cancel the scorecard segment if it is not ready.
- Metrics without owners. It happens because the data comes from software, not a person. Fix: every row has one named owner who explains it.
- Solving issues during the scorecard. It happens because red numbers are interesting. Fix: say "that's an issue" and move on.
- Too many attendees. It happens because leaving someone out feels rude. Fix: send a written recap, and rotate seats.
- No decision log. It happens because everyone remembers the decision differently. Fix: one person records it live, and reads it back.
If you want help turning your scorecard into a meeting that runs this way, book a workflow review.
This article is for informational purposes and is not legal, billing or clinical advice.
The usual meetingScorecard built liveIssues solved mid-scorecardNobody logs decisionsThe 45-minute meetingPre-read the day before"That's an issue," then move onDecision log read back


