What to Do When an ABA Team Uses Unfamiliar Terms

Ask what the term describes

Is it an observable response, measurement, assessment hypothesis, procedure, payer label, credential, or billing state? The same word can carry different meanings across clinical, school, insurance, and everyday settings. Ask the speaker to name the context and authority.

Request an example and comparison

Ask what someone would see or count, the opportunity and time window, and what would count differently. The BACB Ethics Code addresses understandable communication and accurate representation for covered professionals.

Protect the person's language

Keep the person's AAC and preferred terms available. ASHA guidance supports communication across forms and partners. Ask how the person describes the experience and whether the clinical label changes access or treatment.

Track unanswered questions

Jia brings seven terms from a report. Five are explained with examples, one needs the author, and one is a payer term for billing. Meeting completion is 5 of 7 explained, with two routed questions. The family keeps the original wording beside each answer.

Build the plain-language terminology log

Use the plain-language terminology log to turn unfamiliar ABA, school, payer, credential, and billing language into examples and decisions the person and family can understand and use. Lock the person, review period, and eligible events before calculating any rate. Give each row a source, observed state, owner, next action, due date, and closure artifact. Keep the family's accessible summary linked to the detailed operational record so a new staff member can understand the current situation without relying on memory.

Collect only records that serve the named decision: exact term and quoted sentence; speaker or document; context; plain definition; observable example; comparison or nonexample; evidence source; affected decision; professional or payer authority; person's preferred language; unanswered question; owner; and response date. Label the author or issuing party, effective date, scope, and version of each item. A schedule screen, portal message, call note, clinical record, authorization, and billing artifact answer different questions. Preserve conflicting items together until the responsible role resolves the difference.

Work in an order that can be audited. Copy the term in context, ask which domain it belongs to, and request a plain definition plus a concrete example for this situation. Repeat the explanation in the family's words and invite correction. Link the term to the decision it affects, identify unresolved questions, and keep the original language beside the verified answer. Preserve the original event when a correction occurs, then add a dated correction with its author and reason. Store health, education, and financial details in approved systems, limit access by role and purpose, and avoid copying sensitive narrative into a broadly visible scheduling queue.

Keep each decision with the right person

Write the decision owner beside every open field in the plain-language terminology log. Each speaker explains terms used within their role. Qualified clinicians explain clinical concepts and judgments. Payers explain their status labels and decisions. Coding professionals interpret coding sources. The family and person can ask for understandable communication. A glossary entry cannot settle a case-specific clinical, legal, or coverage question. Administrative staff can collect evidence, calculate from verified inputs, and route questions. Software can flag omissions or conflicts. Neither should invent a clinical conclusion, disclosure authority, payer decision, family preference, or emergency instruction.

Turn the record into an understandable choice. Ask what changes if the term applies, which alternatives exist, and what evidence supports it. Families can request an interpreter, AAC vocabulary, visual or written explanation, another example, or time to review. Preserve the person's own language rather than replacing it with jargon. Explain which facts are confirmed, which are provisional, what could change, and what the person and family can do next. Use the person's usual communication. Provide language, disability, sensory, mobility, and AAC access throughout calls, meetings, visits, and written follow-up.

Prepare for the next conversation with specific questions: What does this word mean here? What would someone observe? What would count differently? Who has authority to use it? Which evidence supports it? What decision does it change? How does the person describe the experience, and which question remains unanswered? Read the answers back, name the owner and date, and send a written summary through an approved channel. When the contact cannot answer, ask for the role or formal process that controls the question instead of treating a convenient response as final.

Use a release gate and failure plan

The plain-language terminology log should define a release gate for the action at issue. Close a terminology question only when the exact context, plain definition, example, source or authority, decision effect, family understanding, and remaining uncertainty are recorded. Route unresolved clinical, payer, legal, coding, or privacy questions to the responsible role. A cleared gate applies only to the named person, staff, provider, site, service, communication supports, and time period. Recheck any field that can change before the visit, information transfer, service record, claim, fee, or return occurs.

Plan for realistic failures before the family is under pressure. Confusion persists when one word shifts meaning across teams, a label replaces observable facts, a function is inferred from timing, a payer status is treated as a clinical conclusion, a credential is treated as licensure, a percentage lacks a denominator, or staff answer beyond their authority. Record the observed problem rather than an assumed motive. Preserve the evidence, protect live safety and administrative deadlines, stop the affected action when appropriate, and tell the family what remains available while review continues.

Give the plain-language terminology log a written fallback for each high-impact failure. Name the trigger, person authorized to decide, immediate safe action, information needed, family contact, clinical or financial effect, alternate route, and review time. Immediate health, safety, emergency, or reporting duties use their applicable route while routine administrative correction continues.

Work through a realistic complication

Jia lists nine terms from an assessment and payer letter. Six receive plain definitions and examples, one clinical term returns to the report author, one payer code goes to member services, and one abbreviation is a document error. Completion is six of nine explained, with three distinct routed outcomes. State the numerator, denominator, unit, time window, and status of every excluded or open item before interpreting the result. A percentage cannot show which event was unsafe, burdensome, clinically significant, expensive, or still waiting on another party.

Add one later complication to the plain-language terminology log. A staff change, new health fact, school update, access failure, corrected service record, payer response, or family preference may invalidate an earlier decision. Link the new artifact to every downstream event that relied on the old state. Keep the history visible so the family and provider can see what was known at each point.

Verify the full cycle and improve the process

Update the log when a corrected report, plan, decision, or policy changes the meaning. Verify that the family-facing summary and source document align. Add useful confirmed terms to future accessible explanations while keeping person-specific conclusions in the proper record. A calendar entry, sent message, portal status, staff promise, or completed form is an intermediate artifact. Close the plain-language terminology log only when the expected real-world outcome and family-facing record agree. Name who performs that reconciliation and how an unresolved mismatch returns to the active queue.

Measure the plain-language terminology log with explicit units. Name the start and end event for every duration and every eligible event in a denominator. Report pending items by count and oldest age. Keep sessions, minutes, staff assignments, communications, forms, service records, claims, and households separate. Pair every rate with raw counts and relevant exceptions.

Finish with a short retrospective specific to the plain-language terminology log. Ask which fact was hardest to verify, which handoff or support failed, whether the person and family could communicate and participate, and which narrow control should change. Test the correction in the setting where the failure occurred. The examples on this page support planning; they do not establish another person's clinical need, legal right, coverage, or likely outcome.

Use plain language without erasing precision

The BACB Ethics Code addresses understandable communication and accurate representation for covered professionals. Plain language should explain the actual clinical concept, measure, source, or uncertainty rather than substitute a reassuring slogan. Keep the technical term beside the explanation when it appears in a plan, authorization, or record that the family may need to discuss later. Build a reusable question pattern: What did you observe? What comparison supports that statement? Which person made the interpretation? What decision follows? Which alternatives exist? This works for a clinical hypothesis, a score, a payer status, or a credential. Preserve unanswered questions on the meeting summary with owners and dates rather than filling gaps with guesses. Ask the speaker to distinguish a definition, a case-specific interpretation, and a required action because each needs different evidence.