To update an ABA plan after decision authority changes, verify the current legal source, scope, effective date, limits, and review path before changing permissions or relying on a new signer. Restrict sensitive records appropriately, recheck active consents and disclosures, preserve the client's direct participation and assent when applicable, identify every affected plan decision, and hold ambiguous actions for qualified legal or privacy review.

Authenticate the source

Obtain and verify the current order, law-based record, revocation, age or status event, or other controlling evidence through the approved route. Preserve provenance and review date.

Treat a reported change as an alert until the responsible organizational or legal process verifies it. Record the issuing authority, document or event type, person, effective date and time, scope, expiration or review condition, source location, verifier, and uncertainty. Protect the record and avoid unnecessary copies.

Preserve the prior authority state and when it stopped applying. A new contact form, verbal family report, changed address, or birthday may prompt review but does not by itself establish every legal consequence. Obtain qualified guidance for jurisdiction-specific questions.

Map authority precisely

Record who may decide, sign, access, receive, direct disclosure, or participate for each purpose, along with scope, restrictions, effective period, and conflicting evidence.

Use one row per permission or action. Consent to a treatment component, access to records, portal proxy rights, authority to direct disclosures, participation in planning, emergency contact, and financial responsibility may belong to different people. Avoid copying one role across the others.

When authority is shared, conditional, or limited, state the condition and resolution route. Mark expired and revoked permissions explicitly. Keep conflicting sources open until the qualified reviewer identifies the controlling evidence.

Protect records and privacy

Adjust role-based access, contact routes, portals, releases, recipients, confidential communications, and broadly visible notes. Preserve prior history and audit trails.

Create a minimum-necessary systems map. Update only the access and disclosure fields supported by the verified change, including portal roles, messaging recipients, releases, scheduling contact, and document routing. Remove stale access promptly while preserving required records and audit logs.

Do not reveal the content of the authority document more broadly than needed. Test the update with representative workflows, such as whether a portal user can still view records or a message continues to route to an expired representative. Escalate unauthorized access through the privacy and legal process.

Recheck the active plan

Identify consents, assent processes, goals, procedures, assessments, medical coordination, school and payer work, schedule, emergencies, and disclosures affected by the change.

Trace every active component and open task to its decision and disclosure authority. Determine whether existing consent remains valid, whether reconsent is needed, whether another person should receive information, and whether scheduled work must pause. Payer or school roles do not automatically settle clinical consent.

Review staff instructions, printed packets, vendor systems, and external recipients as well as the electronic plan. Keep immediate safety and lawful emergency routes separate. Record which components are unchanged and the evidence supporting that conclusion.

Include the client directly

Tell Mina what changed in an accessible format, invite questions and corrections, preserve AAC and privacy, and record her preferences, assent, dissent, or concern separately.

Explain the practical effects component by component, including who can make which decision, who may receive information, and how Mina can seek correction or support. Offer her preferred language, AAC, time, privacy, and a chosen support person. Avoid discussing sensitive authority details in a group merely because several people attended earlier meetings.

Mina's direct preference and ongoing assent or dissent remain important even when another person holds formal authority. Record them separately and activate the disagreement or safeguarding route when the change creates a concern.

Hold unresolved actions

Block only the action whose authority is unclear, preserve immediate safety and legal duties, assign qualified legal or privacy review, and document the resolution.

Use a field-level hold so unrelated accepted care continues. State the exact decision or disclosure blocked, interim support, qualified owner, due date, and evidence required. Prevent scheduling or automated messages from bypassing the hold.

At resolution, update the register, linked plan version, access systems, and recipients, then verify propagation. Keep residual uncertainty and failed notifications open. Communicate the final state to Mina and affected authorized people accessibly.

Build Mina's decision-authority change register

Create one row for each of Mina's eight active permissions and name the exact action or information it covers. Capture the governing document or other authority source, issuing body, effective and expiration dates, person or role authorized, scope and limits, privacy route, system access affected, clinical decision affected, verification owner, and open question. Preserve Mina's own communication and assent or dissent when applicable. Apply updates to the specific field supported by the source so a contact change cannot silently expand decision or disclosure rights across the record.

Work through Mina's example

Mina's record lists eight active decision or disclosure permissions. Four remain unchanged, two transfer to the new representative, one expires, and one has ambiguous scope. The count reconciles as 4 + 2 + 1 + 1 = 8. The six clear permissions can follow their verified states, the expired route is blocked, and the ambiguous item remains held for counsel. This is a field-level authority update for Mina's record; applicable law and the source document determine the final scope.

Address Mina's main risk

Updating a contact name can silently change access across the whole chart. Mina's register applies authority only to the action and information the source actually covers. Review the exact conduct and evidence instead of relying on a checkbox, signature, relationship label, or system status. Consent, assent, plan acknowledgment, clinical recommendation, payer authorization, operational release, claim acceptance, and payment remain separate.

Choose Mina's next action

Privacy staff correct role-based access, the clinician reviews affected plan decisions with Mina, and counsel resolves the single ambiguous item before use. Record the qualified owner, authority, affected scope, interim protection, due date, evidence required for closure, client and representative communication, correction route, and next review. Software may coordinate tasks while authorized people make decisions within their roles.

Apply current professional sources to Mina's decision

For Mina's decision, the BACB ethics hub identifies the current Ethics Code; the Code applies to covered individuals and addresses understandable communication, client and stakeholder involvement, informed consent and assent when applicable, assessment, risk, documentation, and continual evaluation. BACB has no separate jurisdiction over organizations. The BCBA outline is examination content rather than authority to practice. The CASP public summary concerns ABA treatment for autistic people and supplies high-level planning context. An evidence-based ABA framework supports integrating research, clinical expertise, client values, and context. Breaux and Smith offer assent-focused practice guidance while describing an evolving evidence base.

Keep authority, privacy, and access distinct for Mina

In Mina's record, HHS personal-representative guidance explains that applicable law determines representative authority and scope. Its involved-person guidance describes a separate path for directly relevant disclosures in specified circumstances. Receiving information never creates authority to disclose back or decide. HHS also distinguishes HIPAA authorization from consent; neither is a universal substitute for consent to care. ASHA supports continuous access to AAC tools or devices. The DOJ Title III overview describes effective communication and reasonable modifications for covered public accommodations, subject to the law's scope and defenses.

Close Mina's review

Review the decision-authority change register with Mina, the legally authorized person when applicable, the responsible clinician, affected staff, and the specialists named in the manifest. Preserve direct client communication, disagreements, versions, decisions, limits, records, and open findings. Keep this page draft and noindex until the required clinical, client or family, consent, authority, AAC, accessibility, privacy, medical, safety, ethics, payer, and legal reviews are complete.

Related resources

Sources