ABA treatment plan review follow-up turns every decision and open question into accountable work. Record the owner, authority, affected component, priority, dependency, due date, interim control, evidence required for closure, client communication, verification, and escalation route. Separate clinical decisions, referrals, consent, payer tasks, training, system release, record corrections, and outcome checks. Keep overdue and blocked work visible rather than closing the meeting when minutes are sent.

Create one item per outcome

State the decision or question, plan component, source review, client request, required action, expected evidence, and relationship to other tasks.

Split compound minutes into tasks that can be owned and verified independently. A revised goal may require clinical wording, consent or review, system versioning, staff training, client communication, first-use observation, and later outcome evaluation. Linking these items preserves the dependency without assigning the whole chain to one vague owner. Keep Cora's requests visible beside the operational work they generated.

Assign the right owner

Choose the person or role with authority and capacity for the clinical, medical, access, payer, school, training, system, records, privacy, scheduling, or communication task.

Confirm that the named owner accepts the task and can reach the necessary source or system. Operations can coordinate a referral but cannot author the specialist response, and software can route a plan change but cannot approve it. Add a backup and escalation contact for urgent or time-sensitive work. When responsibility crosses organizations, identify the internal person who tracks the external loop.

Set priority and time

Record created date, due date, urgency, dependency, service or authorization impact, interim control, reminders, escalation point, and stop condition.

Use the source deadline and client risk to set priority rather than treating every action from the meeting as equal. A missing safety support or expiring authorization may require earlier attention than routine formatting. State what protects Cora while the item remains open and when delay changes the service or plan state. Automatic reminders should escalate to a person able to act, not just generate another notification.

Define closure evidence

Require the approved plan version, completed referral, verified source, consent record, readiness result, system test, accessible communication, corrected record, or other objective artifact.

Define closure evidence before work begins. “Done” may mean a referral was sent, while true loop closure may require acknowledgment, returned guidance, qualified integration, and an update to Cora. Separate completed from verified so a second reviewer can inspect the artifact. When the evidence is incomplete or expires, reopen or block the item rather than carrying a misleading green state forward.

Track connected release work

Link change comparison, approval, training, distribution, stale-copy removal, schedule, first use, integrity, adverse effects, and outcome review instead of calling plan signature complete.

Track the version from authorized source through every point of care. A signed plan can coexist with old data forms, untrained staff, or an unconfigured device. Verify the first eligible use in each relevant context and keep client experience and unwanted effects separate from integrity. If one context remains held, preserve that partial state and its owner while verified settings proceed under qualified review.

Report every state

Use open, in progress, blocked, overdue, completed, verified, cancelled with reason, and reopened. Report mature cohorts, raw counts, age, and dependencies.

Keep overdue and blocked tasks in their denominators until a source-valid exclusion or cancellation applies. Age open work by risk and dependency, and report counts beside percentages. A canceled task needs an attributable reason and a decision about any client impact. After correction, retest the failed path and retain the original state, evidence of repair, residual limitation, and final qualified closure.

Build Cora's review follow-up register

Cora's register turns each review decision into a bounded task with one accountable owner, the authority to act, required evidence, dependencies, interim control, due date, accessible communication, and closure test. It links plan changes to approval, training, distribution, first use, implementation checks, referrals, and outcome review while retaining blocked, overdue, cancelled, and reopened states. A reviewer should be able to trace every task back to the decision that created it and reproduce the evidence used to close it.

Work through Cora's example

Cora's review creates 12 follow-up items. Eight close by their due dates, two remain open within time, one is overdue, and one is blocked by a medical referral. At this snapshot, completed work is eight of the fixed 12-item cohort, or 66.7 percent. This is not a mature on-time closure rate because two items are not yet due. The blocked item stays visible with interim support. This fictional multisite review sets no universal meeting rule, clinical recommendation, legal conclusion, closure threshold, or outcome guarantee.

Address Cora's main review risk

Action lists fail when every item is assigned to the team or when completion means a box was clicked. Cora's register defines owner and closure evidence. Treat preparation, attendance, participation, decision, consent, release, implementation, and outcome as separate evidence. A well-run meeting can still produce a held decision, and a valid urgent action can occur outside the meeting.

Choose Cora's next action

The review owner escalates the overdue item, checks the medical dependency, verifies the eight closures, and sends Cora a current accessible status summary. Record the responsible role, authority, affected component and scope, interim control, due date, evidence needed for closure, accessible communication, correction route, and next review. Software may coordinate workflow. Qualified professionals make case-specific decisions within scope.

Protect Cora's access and choice

Keep Cora's AAC, interpreters, mobility, food, water, bathroom use, prescribed care, pain communication, health support, movement, rest, relationships, and emergency help available. Offer private and accessible ways to ask, disagree, decline, pause, withdraw when applicable, and correct the record. Proxy and professional input can inform review without replacing Cora's experience.

Apply current sources to Cora's review

The BACB ethics hub, current Ethics Code, CASP public summary, and BCBA Test Content Outline provide scoped professional, client-involvement, documentation, evaluation, and training context.

An evidence-based ABA framework and treatment-integrity practitioner guide, Essig review, impact study, and reporting review support contextual decisions, explicit evidence, and bounded conclusions.

ASHA supports continuous AAC access.

Rehearse Cora's review cycle

Test the review follow-up register with a client request, caregiver disagreement, missing participant, interpreter or AAC need, late evidence, changed definition, health concern, low integrity, payer deadline, unresolved authority, urgent safety action, held decision, overdue task, stale plan copy, and adverse effect after release. Confirm that access, attribution, authority, workflow state, and follow-up remain intact.

Close Cora's review record

Review the review follow-up register with Cora, the responsible clinician, affected participants, and the specialists named by the manifest. Preserve direct client input, sources, decisions, disagreement, versions, tasks, limits, and open findings. Keep the page draft and noindex until required clinical, client or family, AAC, access, medical, educational, payer, records, privacy, employment, and legal reviews are complete.

Related resources

Sources