Test ABA practice management software with one sample family packet, a clinician-reviewed treatment plan, a scheduling exception, and a billing handoff.
An ABA practice can carry family priorities, source records, and scheduling needs into the first clinician review. The clinician confirms the information, documents their findings, and releases the reviewed plan for the next team.
If you are evaluating practice management software for applied behavior analysis (ABA), ask the vendor to run one sample family through that sequence. Include a corrected intake response and a session that needs billing follow-up. Those two exceptions show how the software handles changes after the first person enters the data.
Test ABA intake to treatment plan in one software demo
Start with a fictional learner, Alex, and a family that has requested afternoon appointments. The caregiver submits an intake packet before the first conversation. They describe a communication preference, name a routine they want to discuss, and share a prior report. The scheduler still needs to confirm availability. The clinician needs to confirm who wrote the report and when it was prepared.
Give the same packet to each vendor. Ask an intake coordinator, clinician, scheduler, and biller to take turns with the record, using their own roles when the vendor can provide sample logins. Save the screen or export that supports each answer. You can record the evidence in the EHR demo scorecard.
At each handoff, have the next person open the record independently. Ask them to find the current information, its source, and the person who owns any open question. Record where they re-enter a value or ask another team to explain its meaning. This gives your team a concrete way to compare vendors after the call.
What to collect from parents before the first plan
Start with information the clinician can use in the interview. Ask which routines matter to the learner and family, how the learner communicates their preferences, and what the family wants the team to understand about those routines. Offer space for a description in the family's own words. Ask which topics they would prefer to discuss in person.
Collect administrative details alongside the clinical intake. These can include the best way to reach the family, appointment availability, prior reports they have shared, and access or communication needs. For example, Alex's caregiver indicates that written reminders are easier to use. The coordinator confirms where the family wants reminders sent and records who can update that preference.
Make it possible to see who supplied each answer and when. If two caregivers complete portions of the packet, preserve the source of each response. Give the clinician a way to open the original report rather than relying on a summary typed during intake. The intake field handoff guide shows how to record the source, destination, and correction owner for each field.
Carry family input into the clinician's review
The clinician opens the packet before the interview. They can quote or summarize a caregiver's account with its source, then record their own findings after the conversation and assessment. The CDC overview of autism interventions describes progress in ABA as “tracked and measured.” For a software evaluation, ask the clinician to show how the plan identifies what the team will track and how later observations can be traced to the current plan.
In Alex's sample record, the caregiver adds a correction after the original packet arrives. The clinician compares the two entries, confirms which response reflects the family's current preference, and records it in the reviewed plan. Ask the vendor to show where a later reviewer can find the earlier answer and the confirmation date. If a form changes while referrals are open, repeat the test with both versions. See the intake form version guide for a way to run that comparison.
Ask which staff can review a plan and which staff can record session observations. The BACB Registered Behavior Technician Handbook describes RBTs as practicing under “the direction and close supervision” of a supervisor or requirements coordinator. Use the demo to see how your practice's review assignments and staff permissions appear in the proposed workflow.
Give the scheduler a reviewed plan and a clear next step
After the responsible clinician reviews the plan, give the scheduler the proposed service, the plan version, confirmed family availability, and any unresolved item. For Alex, the clinician has completed the plan review and the scheduler can see the family's afternoon preference. An operations teammate is checking the effective date on the authorization.
Have the scheduler open a sample appointment on a date outside the authorization range. Ask what the scheduler can see, whether the software warns them or routes the exception, and who can clear it. Then move the appointment to a date inside the sample range and check which warning changes. Inspect both the schedule and the record rather than relying on a demo slide.
Use the same test for a second staff member who takes over the referral. They should be able to tell who is checking the date and when to follow up. The clinician's reviewed plan remains identifiable while staff resolve the scheduling question. In your demo notes, record which screen each person uses and whether the handoff works when they are in different systems.
Trace a session and an exception before billing
Give the biller two fictional sessions. One has a signed note and an authorization that covers the sample date. The other has a signed note and an authorization date that needs review. Ask the biller to locate the appointment, the person who provided the service, the signed note, and the relevant authorization from the billing entry.
CMS lists “Eligibility and benefit verification,” prior authorization, and health claims as distinct categories in its adopted transaction standards. Ask staff to show each status in the proposed system. In the sample, operations checks the effective date, records the result, and alerts the biller that the exception is ready for review.
Ask what happens after a correction. Can the biller find the original exception and see who resolved it? If a status lives in a separate system, find out when the billing team receives the update and what happens if the update fails. Bring one approved sample workflow from your own team to confirm the steps with the people who will use it. The billing handoff worksheet provides a way to record who owns each step.
Score the demo with the same acceptance checks
Use this table during each demo. For every row, write down the screen or export that shows the result, who produced it, and any setup the vendor needed. Record which checks you observed directly and which still need a demonstration in your proposed configuration.
| Stage | Give the vendor | Ask the next person to show |
|---|---|---|
| Family intake | A packet and one corrected answer | The current response, original response, source, and date |
| Clinician review | A prior report and notes from the first conversation | Which information came from the family and which findings the clinician recorded |
| Plan handoff | One reviewed plan and a later draft revision | The version approved for the next team, its reviewer, and open questions |
| Scheduling | Two possible dates and one authorization that covers only one | The exception on the uncovered date, its owner, and the status after rescheduling |
| Billing | Two signed session records and one unresolved authorization date | The encounter evidence, the held item, and what clears it for review |
Write a concrete pass condition for each stage. For example, “The scheduler can find the current plan version and the authorization follow-up owner without reopening the family packet.” Give a partial score when a person can complete the task with a documented manual step, and note who would own that work. If the vendor needs a separate module or integration, record the boundary and ask to see the actual transfer.
End the demo by handing the same record to someone who missed the first walkthrough. Ask them to find the reviewed plan, explain why the second session is held, and identify the next owner. Their ability to answer from the record gives you evidence of what survives a normal shift change.
Frequently Asked Questions
What should an ABA practice collect from parents before the first treatment plan?
Collect family priorities, communication preferences, relevant prior records, and practical scheduling needs. Save who provided each response and when, so the clinician can confirm it during the interview.
What should ABA practice management software show in a demo?
Ask the vendor to run one sample record through family intake, assessment and plan review, scheduling, and billing. Include an updated family response and an authorization exception so each team can show what it sees and who resolves the next step.
How should staff handle an intake answer that changes?
Keep the source and date of the earlier answer, record the updated information, and assign the appropriate reviewer. Ask the next team to identify the current value and how they know it was reviewed.
What should the scheduler receive when the plan is ready?
Give the scheduler the current plan status, proposed service, confirmed availability, and any open authorization or staffing question with a named owner. In the demo, verify that scheduling changes leave the reviewed plan intact.
What should a biller check before submitting a session?
Have the biller trace the session record to its signed note, service details, and applicable authorization. Give the biller an exception and ask where it appears, who resolves it, and what evidence clears the hold.
