Can Families Ask for One ABA and School Coordination Summary?

ABA School Coordination Summary

Use sections for agreed facts, school decisions, clinical decisions, recommendations, unresolved questions, record transfers, and actions. Give participants a correction window. Limit distribution to authorized recipients and avoid combining confidential information unrelated to the stated purpose.

Keep roles and education authority clear

The IDEA IEP-team rule defines required participants and allows other people with knowledge or special expertise at the discretion of the parent or agency.

The IEP review rule assigns development, review, and revision to the IEP team. An outside clinical recommendation supplies information rather than school authority.

Use the correct record-sharing route

34 CFR 99.30 states the content required when FERPA prior consent is the disclosure route. For a HIPAA covered provider, HHS describes permitted treatment disclosures, subject to applicable limits. Verify the route on each side before sharing.

Protect communication and professional boundaries

The ASHA AAC portal says AAC users should always have access to their tools or devices. The BACB Ethics Code addresses competence, client involvement, confidentiality, collaboration, documentation, and evaluation for covered behavior analysts.

A practical example

A joint summary records three agreed communication supports, one different behavior definition, two school actions, one clinical reassessment, and a pending record transfer. Each item names its author and due date.

Decide what the summary is for

A coordination summary can help the family see what information was shared, which decisions belong to each team, what remains unresolved, and who owns follow-up. It should not replace the IEP, clinical plan, medical order, consent, or source records.

Define the meeting, period, student, participants, purpose, and authorized recipients. Avoid creating a permanent combined file of unrelated education, health, family, or staff information.

Use sections that preserve authority

A useful structure includes:

• agreed factual information
• student and family priorities
• school decisions and source records
• clinical decisions and source records
• outside recommendations
• definition or data differences
• authorized record transfers
• open questions and actions
• correction and review dates

Name the author or responsible role for each item. Do not use “the team decided” when only one organization made the decision.

Keep sources and definitions attached

For any data point, state the setting, date, definition, denominator, supports, and collector. If school and clinic definitions differ, put them side by side. Preserve raw counts and avoid averaging incomparable series.

Recommendations should identify their source and limits. A BCBA recommendation remains clinical information for the school to consider. An IEP decision remains an education decision rather than a clinic order.

Include the student's contribution

Offer the student an accessible way to review relevant parts, state priorities, correct facts, and identify what should change. Keep AAC, interpreters, plain language, breaks, and a way to decline available. Label the student's account separately from caregiver, school, and clinical interpretations.

If the student wants a sensitive detail limited, discuss the available privacy choices and any governing obligations with the correct role.

Verify permission and distribution

Identify who prepares the document, where it is stored, who receives it, and which FERPA, HIPAA, consent, or other route applies. A consent to exchange one assessment does not automatically authorize a continuing joint record or broad redistribution.

Use secure delivery and maintain a recipient log when appropriate. When permission expires or is revoked, update future distribution while preserving records already lawfully maintained.

Give participants a correction window

Circulate a draft to authorized participants with a date for factual corrections. Preserve disagreements rather than forcing consensus. The school can correct its attributed information, the provider can correct its clinical information, and the student or family can add a statement through the applicable process.

Keep version history, author, date, and reason for changes. The summary should point back to controlling source records instead of overwriting them.

Follow the joint-summary example

The summary records three shared communication supports, one behavior-definition difference, two school actions, one clinical reassessment, and one pending record transfer. Each entry identifies the source, owner, due date, and affected plan.

The school definition counts leaving an area for more than ten seconds; the clinic definition counts any boundary crossing. The summary preserves both and assigns a future crosswalk question rather than combining the data. The student adds that AAC is sometimes stored during school transitions.

One school action addresses device access, while the provider's reassessment examines the clinic goal. A pending transfer has a named consent route and receipt owner. The document helps coordinate without making either plan control the other.

Close the loop on actions

At the next review, mark each action complete, overdue, held, or changed and attach evidence. A sent email is not the same as a received record, and a staff reminder is not proof that a support was implemented. Keep open work visible to the family.

Leave unnecessary material out

The summary usually does not need full clinical notes, medical narratives, unrelated family history, staff performance detail, other students' information, billing records, or every email. Include only what supports the coordination purpose and authorized actions.

Avoid a single blended “progress” score. School and clinic datasets can use different definitions, denominators, collectors, and settings. Report each series with its source and limits. Do not use the summary to create a new unofficial goal or service.

Decide who maintains the summary

One organization should own the controlled version and correction workflow, or the document should clearly state that each party maintains its own copy. Name the author, date, version, storage location, recipients, and next review. Avoid an editable shared file with no accountable owner.

When a participant leaves the team or permission changes, update access. Preserve required history and the records that support completed decisions. If the summary contains a factual error, route it to the responsible author and tell authorized recipients about the corrected version when needed.

Give the family a usable final copy

Provide the document in an accessible format and preferred language when required. Include contacts for school, clinical, records, privacy, and urgent questions. The family should be able to identify what happens next without reconstructing the meeting from several portals.

At the next coordination point, start with the open-action register rather than rewriting the whole history. Close actions with evidence, preserve disagreements, and create a new version only when substantive information changes.

Questions families can use

Ask who authors the summary, which permissions cover distribution, how the student contributes, how disagreements remain visible, which source records control, who corrects factual errors, and who confirms completion of each action.