ABA Family Request, Response and Closure Tracker

Use one copy for one request. A request for records, a schedule change, a clinical review, an accommodation or a payer action may travel through different processes. Record the exact channel, source and role rather than assuming that one contact owns every next step.

This ABA family request tracker is an organization and follow-up tool. It is not a treatment request form, grievance, appeal, authorization request, medical record, clinical order, consent form or emergency route.

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

What this tracker can and cannot establish

The tracker can preserve what the family asked, when and how it was delivered, who acknowledged it, where it was routed, which response was attributed to which source, what action actually occurred and what remains open. It can also keep a correction from erasing the earlier record.

Important boundary: This tracker cannot determine entitlement, clinical appropriateness, medical necessity, coverage, authorization, compliance, fault, urgency, retaliation, satisfaction, outcome or closure. It cannot establish consent or assent, force action, invent a deadline, or replace an emergency, clinical, payer, appeal, grievance, records or privacy process. An acknowledgement is not an approval, a decision is not a completed action, and silence is not a denial or agreement.

The BACB Ethics Code for Behavior Analysts addresses professional responsibility, communication, documentation, records and involvement of clients and stakeholders within its scope. A family tracker cannot decide whether conduct complies with the code or create duties that belong to a professional, payer or organization.

Define one request before tracking it

Write the request as it was submitted. If the family later changes the request, add a dated revision instead of silently rewriting the original.

Request fieldEntryShort request labelExact request in the family's wordsPerson making the request and relationshipLearner communication or preference includedDate and time submittedSubmission channel and destinationAttachment or supporting recordRequested response, action or meetingDate requested by the family and reason, if anyAccessibility, language or communication support needed

Avoid combining several unrelated requests under one label such as “fix services.” A request to explain a plan, send a record and change a schedule may have three different owners. Split them when separate routes or decision makers are required.

Identify the correct route without deciding the answer

The family can ask the recipient to confirm ownership and routing. The tracker should not decide which law, policy, contract or clinical rule controls.

Possible routeWhat the family is askingResponsible source namedReference number or recordNext expected stepResponsible clinical teamScheduling or provider operationsPayer, authorization or utilization reviewBilling or claim supportRecords, privacy or release processAccommodation or communication accessComplaint, grievance or appeal processOther named process

A clinician may answer a treatment question without controlling payer coverage. A scheduler may confirm an opening without changing a treatment plan. A provider can acknowledge a records request without confirming delivery. Preserve these authority limits instead of treating the first responder as the final decision owner.

Preserve acknowledgement and routing separately

EventDate and timeSource and roleExact message or recordWhat is still unconfirmedDelivery confirmationAcknowledgementAssigned ownerReferral or transferExpected response date stated by sourceInterim update

Write “no acknowledgement located as of [date]” when that is the record. Do not convert the absence of a message into a decision. If an automated receipt provides a deadline, attribute it to that receipt rather than presenting the date as a universal rule.

Keep request, decision and action in different rows

LayerExact entrySource and dateOwnerStatusFamily requestSubmittedClarification requestedResponsible decisionExplanation or noticePromised actionAction actually completedFamily correction or disagreementRemaining item

“Approved” does not show that a schedule changed, a record arrived or a service was delivered. “Sent” does not show that the named recipient received a complete file. Record the observable completion event and its source.

The CMS person-centered care overview describes care responsive to a person's goals, values and preferences through communication and collaborative planning. The overview neither defines an ABA request process nor decides who has authority over a clinical, payer or operational request.

Track follow-up without inventing escalation rules

Follow-up dateContact or route usedQuestion askedResponse or no responseNext ownerNext date

Use the official contact and timeframe supplied for the specific process. This tracker does not create a response deadline or tell a family when to file a grievance, appeal or complaint. When a source identifies a formal route, record the route, source, date and reference number. Keep any ordinary follow-up log separate from urgent health or safety needs, which require the appropriate emergency or responsible clinical channel.

The AHRQ shared decision-making overview describes collaboration that brings evidence and professional knowledge together with the person's goals, preferences and circumstances. A request for a conversation is not the conversation itself, and the tracker cannot substitute for the responsible clinical or consent process.

Record the attributed response in full

Response fieldEntryDate, source and roleExact decision or explanationDocument, policy or clinical record citedEffective date or period statedConditions, limits or missing information statedAction promised and responsible ownerReview, correction or formal route offeredFamily question that remains unanswered

Keep a clinical explanation, payer notice, scheduling message and billing response as separate sources. If they conflict, preserve each account and request clarification from the responsible owner. Do not choose the controlling answer inside the tracker.

Confirm action before marking the request closed

Use the closure section only after checking what actually happened. The family can close its own tracking entry while still documenting disagreement, but the tracker cannot declare a clinical, legal, payer or organizational matter formally resolved.

Closure questionEvidence or entryWas the requested information delivered completely?Was the promised action completed?Does the completed action match the dated response?Was the learner or family communication addressed?Is a correction, appeal, grievance or review still open?Is a separate clinical, payer, scheduling or billing issue open?Family tracking status and dateRecord retained and storage location

Possible family tracking labels include “answered, action confirmed,” “answered, action pending,” “partially answered,” “rerouted,” “withdrawn by family” and “family tracking closed with disagreement recorded.” These are descriptive labels, not formal determinations.

The AHRQ SHARE Approach presents a five-step shared decision-making process for clinicians that includes seeking participation, helping compare options, assessing values and preferences, reaching a decision and evaluating it. That framework does not turn this tracker into a clinical decision aid or prescribe a response pathway.

Protect corrections, privacy and access

DateEarlier entryCorrection or disagreementSourceWho received itFollow-up

Store only the information needed for follow-up and use an appropriate secure location. Avoid placing sensitive clinical, educational, financial or identifying details in an ordinary text message or shared file merely because the tracker provides a blank field. Ask the responsible organization which secure channel to use.

If an interpreter, translated copy, AAC access, support person or accessible format is needed, record the request and attributed response. The tracker cannot determine whether a requested accommodation is legally required or sufficient.

Fictional example: a request for a plan explanation

This example is fictional and describes no real learner, family, provider, payer or decision.

Request. On October 3, Amari's father, Luis, uses Harbor Pine Behavior Services' portal to ask for a meeting with the responsible BCBA about a proposed change in afternoon session length. He asks for the current treatment-plan section that supports the proposal and requests a Spanish interpreter. He does not approve or reject the change in the request.

Acknowledgement and route. The portal receipt confirms delivery but names no decision. On October 4, coordinator Mira Chen says the clinical question was assigned to Devon Lee, BCBA, and the interpreter request was sent to access services. Luis records both routes separately.

Attributed response. Devon schedules an October 8 conversation and sends the current plan excerpt. During the meeting, Devon explains the clinical proposal and says no appointment calendar has yet changed. Access services confirms an interpreter attended. Luis records the explanation as Devon's clinical statement, not a payer decision or proof that the proposal is appropriate.

Action and closure. On October 10, scheduling sends a calendar that keeps the existing session length pending another family conversation. Luis confirms receipt of the plan excerpt and calendar. He marks his tracking entry “answered, action confirmed” while keeping a question about the next plan review open. The label records his follow-up status only.

The fictional entry does not establish entitlement, medical necessity, coverage, clinical appropriateness, consent, assent, compliance, satisfaction, fault or formal closure. No direction to accept a particular schedule follows from it.