A plain-language ABA assessment summary should explain the referral question, strengths, methods, main findings, uncertainties, recommendations, alternatives, decision owners, and next steps in terms the client and family can use. It can accompany the technical report while preserving its source details. Families can request accessible formats, translation, AAC-compatible review, examples, definitions, and time for questions. A summary should not hide conflicting evidence or material limits.

Make the summary easy to use

Use one short section per question. Define technical terms at first use, pair percentages with counts, identify observation settings, state ordinary supports, and label recommendations by responsible clinician. Link every summary point to the full report section.

A useful summary answers the family’s actual questions

The summary can begin with the referral question and the client’s own priorities. It should explain what the assessment did, what was learned, what remains uncertain, which options were discussed, and what happens next. A shorter document is useful only if it preserves material context.

Ask for clear sections covering strengths and existing supports; methods, settings, and people; main findings with counts beside percentages; missing or conflicting evidence; health, access, or interdisciplinary questions; recommendations and alternatives; the client and family perspective; and named next actions.

Translate terms without changing their meaning

Technical language sometimes has a precise purpose. The summary can define a term and show a concrete example instead of deleting the concept. “Independent request” might be defined as speech, sign, or AAC before any prompt during a stated opportunity. “Baseline” can identify the measurement period before a planned change.

Ask the clinician to explain uncertainty words. “Consistent with,” “suggests,” and “establishes” should not be treated as synonyms. A result from one setting should not be summarized as a fact about every setting.

Preserve the denominator and conditions

“The client communicated in 70% of opportunities” is incomplete without the count, definition, supports, setting, and observation window. A clearer statement is “With AAC available and a familiar partner, the client made an independent help request in 7 of 10 defined opportunities across two clinic visits.”

Raw counts make small samples visible. They also prevent 1 of 2 and 10 of 20 from looking equally stable. If opportunities or definitions differ across phases, present them separately rather than combining the percentages.

Make the summary accessible to the client

Plain language may still need a different format. Ask about large print, translation, captions, visual structure, audio, AAC-compatible review, reduced text, or a supported meeting. Keep the person’s communication tools available and provide a way to correct, pause, disagree, or ask for another explanation.

Ask whether the client wants a separate summary, a shared family version, or both, subject to authority and privacy. A caregiver’s explanation can add context without replacing the client’s own statement.

Keep recommendations and decisions distinct

The summary should name who made the recommendation and what evidence supports it. It should also identify alternatives, expected review points, burdens, and material limits. The client or authorized decision-maker can then consider the recommendation through the applicable consent and assent process.

A clinical recommendation is different from payer authorization, staff availability, and claim payment. Keep those states in a separate operational section so the reader does not interpret a recommendation as approval or a scheduled start.

Link back to the technical record

Every material summary claim should point to the section, table, or graph in the full report. If a factual correction changes the technical report, update the summary too. Record the version, date, author, and relationship between the two documents.

Families can use the summary for discussion while relying on the full signed report for source details. The summary should never silently omit a material disagreement, safety concern, or limit that would change the decision.

Test the summary with real decisions

After reading it, the client and family should be able to answer: What was assessed? What did the clinician learn? What remains uncertain? Which choices are available? What is the next action, and who owns it? If those answers remain unclear, the summary may be shorter without being more usable.

Ask someone unfamiliar with the process to identify the recommendation and its limits from the document, subject to privacy. Confusion can reveal undefined terms, missing transitions, or a buried action. The goal is comprehension, not a reading quiz for the client.

Keep revisions synchronized

Give the summary and full report linked version identifiers. If a corrected date changes an eligibility period, graph label, or interpretation, update both documents and note the relationship. If a summary changes only for accessibility or clearer wording, preserve the clinical meaning and record the revised format.

Delivery should identify the recipient, format, date, and confirmation. A summary uploaded to an inaccessible portal has not met its communication purpose. Offer a feedback route for questions and corrections, then record which action the discussion changed.

Do not send the summary to a payer or school as a substitute for a required full report unless the applicable recipient accepts it and the authorized disclosure route covers the purpose.

Keep both files together so later readers can move from the accessible explanation to the complete source details without guessing which version controls.

Keep assessment authority and evidence clear

The CASP public summary places assessment and planning within its autism-treatment scope. The BACB Ethics Code addresses competence, understandable communication, client involvement, consent and assent when applicable, assessment, documentation, and evaluation for covered behavior analysts.

Make feedback accessible

The ASHA AAC portal supports continuous AAC access. For covered private practices, DOJ Title III guidance addresses effective communication and reasonable modifications, subject to scope and defenses.

Use the correct record route

For a HIPAA covered entity, HHS access guidance describes access to protected health information in a designated record set, subject to the rule's scope and procedures.

A feedback request, draft review, final report, and formal access request are different events.

A practical example

A two-page summary explains that Mina used speech or AAC to request help in 7 of 12 defined opportunities across two clinic observations. It identifies the familiar partner, visual schedule, and AAC access that were present. It also states that school was not observed and that caregiver report and clinic observation differed for one routine.

The summary gives three options for discussion, names the clinician responsible for each recommendation, and separates payer and staffing questions. Mina reviews a visual version and adds that the clinic task was easier than schoolwork. The clinician links that statement to the limitations section and avoids presenting the clinic percentage as a general skill rate.

Questions families can use

Ask which referral question each finding answers; what raw counts, settings, definitions, and supports were used; which evidence conflicts or remains missing; how the client corrected the summary; which recommendations and alternatives need discussion; which payer states remain separate; and where each summary point appears in the full report.

Related resources

Sources

Finni resources

Ready for the next step?

Find ABA care near you