An ABA practice contact-attempt and failed-delivery register records who the practice tried to reach, for what purpose, through which authorized and usable channel, when the attempt occurred, what delivery evidence exists, whether a response was required, why the attempt failed, and what alternate action follows. It keeps unreachable, undelivered, unopened, unanswered, refused, and wrong-recipient states separate and visible by urgency and age.

Define the contact-attempt and failed-delivery register

Your practice defines success for each communication. A sent text, delivered email, heard voicemail, confirmed portal message, reached person, and completed decision are different events. The workflow never assumes silence means agreement, refusal, informed notice, or loss of interest. The attempt, delivery, escalation, and aging log has a named owner, scope, current sources, role-limited users, qualified decision boundaries, version, evidence location, exception route, change triggers, and retirement state.

Build the required fields

The working record captures attempt ID, client and intended recipient, relationship and authority when relevant, purpose, urgency and deadline, preferred and allowed channel, accessibility and language, contact detail source, attempt time, sender, delivery state, acknowledgement definition, reply, failure reason, wrong-recipient exposure, alternate channel, repeated-attempt rule, escalation, welfare or emergency route, correction, next action, owner, due time, age, final disposition, and review. Each field supports a decision, handoff, measurement, access need, or later trace. Sensitive detail stays in the restricted source record while operational queues carry only purpose-needed instructions.

Use the artifact for bounded decisions

She selects the next step by purpose and risk rather than applying a fixed three-call rule. Routine reminders, clinical decisions, urgent safety issues, records, financial notices, and service closures can require different attempts and escalation. Staff limit repeated contact, honor restrictions, and route suspected wrong-recipient disclosures for privacy review.

Keep authorship, authority, and delivery distinct

A contact-attempt record identifies the source of contact details, the authorized purpose, the person making the attempt, the intended recipient and channel, and delivery or failure evidence. One person can fill several roles, yet the evidence remains attributable. Software may route and flag; qualified people make clinical, privacy, payer, legal, access, and financial decisions.

Handle changes and exceptions without losing history

A contact or delivery change records the prior state, new instruction, source, affected purposes and recipients, owner, effective time, expiry when applicable, system updates, communication, monitoring, and validation. Your practice preserves the history needed to understand messages already sent and decisions already made.

Validate the workflow with real communication tasks

Your practice reconciles the register with telephony, email, portal, mail, interpreter, and returned-message evidence. It tests disconnected numbers, full voicemail, bounced email, unread portal messages, inaccessible formats, and wrong recipients. Aging retains every open person-purpose episode.

Reconcile communication with operational state

Reconcile contact attempts with approved contact details, client instructions, scheduled services, message purpose, channel logs, delivery evidence, returned communications, and escalation records. Differences receive owners and resolution states. This trace prevents a correct message from announcing an incorrect operational state or a correct operational change from reaching the wrong person.

Protect direct client communication and dissent

The contact-attempt workflow preserves a direct, accessible return route, offers AAC and other supports, allows time to respond, and records correction, refusal, pause, withdrawal, or failed-delivery signals. Family involvement can support communication while preserving the client's voice, privacy, and applicable decision rights.

Work through a fictional example

Jocelyn locks 34 contact episodes. Twenty-six have purpose, recipient, authority, channel, access, attempt, delivery, response, failure, next action, and aging controls. Two texts fail, one letter returns, one wrong recipient responds, two episodes lack alternate routes, and two are closed without disposition. Six repair. Two remain open. The scenario is synthetic. It tests source, authority, access, privacy, delivery, evidence, and denominator logic without establishing clinical quality, legal compliance, payer approval, informed consent, satisfaction, or outcome.

Calculate the measures honestly

Initial contact-episode integrity is 26 of 34, or 76.5%. Thirty-two validate, or 94.1%. People, purposes, attempts, channels, deliveries, replies, failures, and open episodes remain separate.

Address the main contact-attempt and failed-delivery register risk

Counting attempts can reward repeated messages that never reach the person. Your practice measures defined delivery and required response states.

Test the artifact against hard cases

Your practice tests bounced email, full voicemail, returned mail, unread portal, changed number, interpreter, AAC, wrong recipient, contact restriction, urgent notice, refusal, and no response. Each case states purpose, person, authority, channel, access need, privacy route, source, owner, evidence, correction, validation, and next review.

Close review with unresolved communication visible

Your practice confirms scope, sources, people, authority, privacy, access, channels, systems, vendors, messages, failed delivery, incidents, corrections, and fresh validation. The contact-attempt and failed-delivery register stays draft until every named reviewer finishes. Open work retains its owner, age, effect, and next action.

Place the attempt, delivery, escalation, and aging log within professional and organizational scope

Your practice uses the CASP Organizational Guidelines public overview for high-level business, clinical-operations, and risk context. The current BACB Ethics Code applies to BCBA and BCaBA certificants and people with a completed application; it addresses understandable communication, involvement, consent and assent when applicable, confidentiality, documentation, and risk. BACB has no separate organization or corporation jurisdiction, so the practice assigns policy and workforce roles under all applicable sources. For the contact-attempt and failed-delivery register, this boundary separates organizational accountability from the clinical and legal authority assigned to qualified people.

Apply minimum-necessary rules precisely

For a HIPAA covered entity or business associate, HHS minimum-necessary guidance says the standard generally applies to uses, disclosures, and requests for PHI and calls for role-based policies. The guidance lists exceptions, including disclosures to or requests by a provider for treatment. Your practice confirms entity, purpose, route, exception, and any more protective law or contract before using this federal standard. Role-based review of the contact-attempt and failed-delivery register should record the communication purpose and access decision that supports each use, request, or disclosure.

Recognize confidential communication requests

Current 45 CFR 164.522 includes rights to request restrictions and confidential communications. Its exact duties differ for covered health plans and covered providers and include rule-specific conditions. Your practice routes applicability, acceptance conditions, denials, implementation, and exceptions to a qualified privacy or legal owner instead of treating a preference flag as the complete legal analysis. When the contact-attempt and failed-delivery register involves a restriction or confidential route, staff preserve the request, governing condition, decision, implementation evidence, and exception.

Separate representative authority from family involvement

HHS personal-representative guidance explains that applicable law determines who is a representative and the scope. HHS family-involvement guidance describes specified circumstances for sharing directly relevant PHI with people involved in care or payment. Receiving information from a family member does not itself authorize disclosure back or transfer decision authority. Your practice records the actual path and purpose. Decision-authority review for the contact-attempt and failed-delivery register should name who may receive information, who may decide, the source, scope, and expiration or review trigger.

Keep HIPAA permission distinct from the operating decision

HHS treatment, payment, and health-care-operations guidance explains specified HIPAA uses and disclosures that may occur without individual authorization, subject to the rule and other requirements. A HIPAA permission does not establish clinical authorship, legal representation, payer approval, or the best communication route. Your practice verifies each decision separately. Within the contact-attempt and failed-delivery register, teams document the HIPAA pathway separately from the operational approval, clinical authorship, and delivery choice.

Protect electronic communication systems

The HHS Security Rule page describes safeguards for ePHI held by covered entities and business associates and says risk analysis is foundational. Your practice maps electronic channels, devices, users, vendors, exports, access, delivery evidence, retention, and incident routes into the regulated entity's current security program. Non-HIPAA data still receives analysis under other applicable sources. Security review of the contact-attempt and failed-delivery register follows the message from creation through recipient verification, delivery, storage, correction, export, and incident handling.

Make communication usable

The DOJ Title III overview and effective-communication guidance address covered public accommodations and communication with people with disabilities, subject to rule-specific standards and defenses. ASHA's AAC portal says AAC users should always have access to their tools or devices. Your practice treats accessibility and communication support as operational requirements, keeps AAC available, and validates the person's completed communication task. Accessibility testing for the contact-attempt and failed-delivery register should confirm that the intended person can receive, understand, answer, and correct the communication using their chosen supports.

Related resources

Sources