ABA Family and Learner Service Experience Check-In Log

Use one copy for a clearly dated period. Record who communicated, how they communicated and what access support was available. Positive, mixed, neutral and difficult experiences can all be documented without converting them into a score.

Start with context rather than a conclusion. A short entry is enough when it preserves the important details. Leave a field blank when the information is not known.

This ABA service experience tracker for families is a family-owned conversation log. It is not a satisfaction survey, clinical data sheet, quality rating, incident report, grievance, treatment plan, consent record or emergency tool.

Families and Caregivers / Progress, Quality, Rights and Ethical Care.

What this log can and cannot establish

The log can help a family describe access, communication, respect, understanding, participation, choice, burden and routine fit for one defined period. It can preserve the exact feedback shared, the responsible recipient's response, an action or correction and the next check-in.

Important boundary: This log cannot score quality, satisfaction, effectiveness, safety or compliance. It cannot diagnose, establish cause, decide clinical appropriateness, medical necessity, consent, assent, abuse, neglect, retaliation, fault, urgency or treatment change, or aggregate the entry as research data. It cannot replace an emergency, incident, mandated-reporting, grievance, clinical, payer or records process.

The BACB Ethics Code for Behavior Analysts addresses professional responsibility, clients and stakeholders, communication, documentation, behavior-change programs and supervision within its scope. A family log cannot determine whether conduct complies with the code or whether a clinical change is required.

Define the experience period and reporting voices

Context fieldEntrySession, meeting or service periodDate, time, setting and service typePeople and roles presentLearner communication method and supportFamily member or support person reportingInterpreter, AAC or accessibility support availableSource records reviewedSeparate incident, clinical or payer record, if any

Keep the learner's communication, a family observation, a staff explanation and a written record attributed to their respective sources. Do not merge several months or unrelated service types into one entry merely to form an overall judgment.

Name the source beside each entry. Record uncertainty in plain language. A later correction should remain visible rather than silently replacing the first account.

Describe the experience without scoring it

Check-in topicLearner communication or family observationContext and supportQuestion or feedbackArrival, transition or beginningCommunication access and understandingChoice, pause, refusal or assent-related behaviorRespect, privacy and personal spaceActivities, goals and interestsEnvironment and sensory accessSchedule, pace and recovery timeFamily effort, clarity and routine fitEnding, handoff or follow-up

Use concrete descriptions. “Selected the break icon twice and returned after the visual timer” preserves more information than “good session.” “Covered ears when the vacuum started and moved to the hallway” is different from deciding that the setting is unsafe or that treatment caused distress.

Include the setting when it matters. Note any support that was offered. Avoid labels that hide what was observed.

Keep experience, clinical data and formal routes distinct

Record layerWhat it may containResponsible sourceWhere it is routedLearner communicationObservable words, AAC, gestures, actions or other communicationFamily experience noteContext and family observationProvider clinical dataDefinitions, measures and clinical interpretationTreatment decisionRecommendation or plan updateIncident or safety recordOrganization-specific event documentationComplaint, grievance or appealFormal process and determinationPayer or authorization recordProduct-specific notice or decisionDelivered-service recordWhat service occurred

A family check-in may inform a conversation, but it does not become clinical data merely because it is shared with a BCBA. A favorable note does not prove effectiveness. A concern entry is not automatically a formal grievance or incident report.

Keep formal record numbers in their proper systems. Cross-reference them only when useful. Do not copy a clinical conclusion into this log without naming its source.

The CMS person-centered care overview describes care responsive to a person's goals, values and preferences through communication and collaborative planning. It does not define an ABA experience measure, quality threshold or required response.

Capture what supported or burdened the experience

FactorWhat happenedWho reported itWhat may need explanation or follow-upCommunication supportChoice or predictabilityRelationship or staff approachActivity or materialEnvironment or sensory conditionTiming, transportation or routineFamily instruction or paperworkOther service or life circumstance

Do not assign cause from a single event. Several factors may occur together, and the family may not know which one mattered. “We noticed” or “the learner communicated” is more accurate than stating that a treatment procedure caused the experience unless the responsible source has made and documented that conclusion.

Neutral wording leaves room for review. It also protects disagreement. The follow-up question can be more useful than a premature explanation.

Prepare feedback in the learner's and family's words

Feedback fieldEntryWhat the learner communicatedWhat the family wants the team to understandWhat should continue, if anythingWhat felt unclear, difficult or burdensomeQuestion or review requestedPreferred communication and access supportRecipient, role and delivery channelDate sent and record retained

The AHRQ shared decision-making overview describes collaboration that combines available evidence and professional knowledge with a person's goals, preferences and circumstances. Feedback can contribute to that conversation without deciding the clinical answer or proving that a decision was informed.

Preserve acknowledgement, response and action separately

Follow-up layerDate, source and exact entryOwnerStatus or next dateFeedback deliveredAcknowledgementClarification requestedClinical response, if anyOperational response, if anyAction promisedAction actually completedFamily correction or disagreementNext experience check-in

An acknowledgement is not agreement. A response is not a treatment-plan change, and a promised action is not evidence that the action occurred. If the feedback becomes a request, concern, grievance or incident, preserve the separate route and reference number.

Record dates for each layer. Name the person or role responsible for the next step. Close an item only when the recorded action is complete.

Use the appropriate route when the issue is not ordinary feedback

Urgent medical or safety needs belong with the appropriate emergency or responsible clinical route. Suspected abuse, neglect, reportable events, privacy concerns, grievances, payer appeals and records requests may each have a specific process. This log neither identifies the correct legal route nor establishes whether a threshold has been met.

The AHRQ SHARE Approach presents a clinician-facing process that includes participation, option comparison, values and preferences, a decision and evaluation. It does not turn a service-experience log into a clinical decision, quality measure or formal complaint process.

Review the next period without declaring a trend

Review questionDated entryWhat remained the same?What changed, and according to whom?What learner communication was preserved?Was an access support available?Was a promised action observed?What question remains open?Is a different formal route active?Next review owner and date

Two entries can help a family prepare a question, but they do not establish a statistical trend or treatment effect. Keep the source and context with each observation.

Preserve corrections and privacy

DateEarlier entryCorrection, disagreement or new informationSourceWho received itNext step

Store the log in an appropriate location and avoid adding sensitive details that are not needed for follow-up. Ask the responsible organization which secure channel should receive clinical, educational, financial or identifying information. This log cannot determine privacy compliance or authorize disclosure.

Fictional example: a mixed experience during one clinic session

This fictional example describes no real learner, family, provider or service.

Context. Samir attends a clinic session at North Star Pathways on November 6. His mother, Priya, observes the final 30 minutes. Samir communicates with speech and a picture board.

Experience note. Priya records that Samir selects the swing icon and joins that activity after the technician shows two choices. Later, a loud cart passes the room. Samir covers his ears, moves toward the door and selects the break icon. The technician opens the quiet room and Samir enters. Priya records these events without rating the session or deciding why they happened.

Feedback. Priya tells supervisor Laila Brooks, BCBA, that the choices and quiet room seemed useful to Samir. She asks how the noise response and break communication will be reviewed and whether the quiet room can remain available. She does not request a treatment change in this entry.

Response and follow-up. Laila acknowledges the note and schedules a November 9 clinical conversation. Operations confirms only that the quiet room is expected to be available; it does not issue a clinical recommendation. No action is marked complete beyond the acknowledgement and scheduled conversation.

The example does not establish quality, effectiveness, safety, cause, assent, consent, compliance, satisfaction, medical necessity or an appropriate clinical change. It is not an incident report or grievance.