What is an ABA practice tabletop exercise? An ABA practice tabletop exercise is a facilitated discussion of a realistic disruption in which participants apply current plans, make role-specific decisions, retrieve evidence, communicate, and identify gaps. It tests readiness without creating the real hazard. A useful exercise defines objectives, participants, scenario events, decision points, safety boundaries, observations, corrective actions and retests.

Choose one operational objective

Examples include testing a site outage, unavailable clinical leader, payer-portal failure, data-system disruption, severe weather closure, facility problem, urgent access removal or authorization deadline during staff leave.

Define what the team should demonstrate: activation, safe continuation or pause, information access, qualified decision routing, family communication, staff accountability, downtime records and recovery acceptance.

The CASP Organizational Guidelines public overview covers business operations, clinical operations and risk management. CASP sells its detailed guidance. This exercise design is editorial.

Set safety and authority boundaries

Use discussion, fictional records and approved test environments. Avoid recreating distress, exposing protected information, disabling production controls or rehearsing an unauthorized restrictive procedure.

Qualified clinicians decide clinical matters within scope. Emergency responders, payers, privacy roles and other authorities retain their domains. Facilitators should stop the exercise if real safety or operational risk emerges.

The current BACB Ethics Code applies to BCBA and BCaBA certificants and people who completed an application. It addresses competence, risk, confidentiality, documentation, supervision and continuity. BACB has no separate corporate jurisdiction.

Build a plausible scenario timeline

Start with a detection event, then release information in stages. A system outage can be followed by an unavailable leader, uncertain roster age, family contact failure and partial technical restoration.

Each inject should force a decision that the objective can observe. Give participants the same tools, plans and contacts available during normal work.

Observe evidence rather than confidence

Record whether participants can find the current plan, identify authority, access the approved backup, state safe-stop conditions, complete required communication and define recovery evidence. “We would handle it” provides weak assurance.

For HIPAA covered entities and business associates, 45 CFR 164.308 includes contingency-plan testing and revision as an addressable implementation specification under the current rule. Addressable does not mean optional; regulated entities follow the rule's evaluation and documentation requirements. A general tabletop can test broader continuity topics as well.

Include frontline participants

Invite the people who receive alerts, contact families, open sites, supervise care, maintain systems and reconcile records. Leadership should participate in decisions and resource commitments.

OSHA's worker participation guidance encourages worker involvement and prompt response within safety programs. It is general guidance. Frontline participation makes scenario findings more realistic.

A fictional platform outage

Willow Bend ABA is a fictional two-site practice. Its exercise begins with a scheduling and record-platform outage at 7:20 a.m. Twelve participants receive six scenario injects.

The team completes five of six defined decision objectives. Exercise success is 5 of 6, or 83.3%. It activates the continuity lead, retrieves the approved roster, holds billing, contacts both sites and defines recovery acceptance. It fails to identify who can approve access to the offline clinical-safety packet.

The gap becomes a high-priority corrective action. After authority and access are fixed, a short retest uses four relevant steps and passes 4 of 4.

Conduct a structured debrief

Ask what occurred, which decision stalled, which information was missing, what helped, and which plan or control should change. Separate individual knowledge from system design and resource gaps.

The HHS OIG General Compliance Program Guidance is voluntary and nonbinding. Its themes of risk assessment, reporting, auditing, investigations and corrective action support disciplined follow-through. Current requirements control actual response duties.

Track actions through retest

Each finding needs consequence, owner, immediate safeguard, action, due date and effectiveness test. Update affected plans, contact trees, access, training and systems through change control.

Useful measures include objectives demonstrated, participants completing assigned decisions, contact routes reached, recovery records reconciled, actions due and actions passing retest. Counts should accompany rates.

Build a yearly exercise cycle

Run several focused exercises across sites, shifts and unavailable leaders. Vary facility, workforce, clinical-interface, privacy, technology and payer scenarios. Include one cross-functional exercise before a high-risk launch.

Preserve scenario, attendance, observations, decisions, actions and retest evidence. Keep sensitive security and clinical details restricted.

Use facilitators and observers deliberately

The facilitator controls pace, releases scenario information and protects boundaries. Observers record decisions, evidence retrieval, communication and unresolved questions. They should avoid coaching participants through the expected answer during the exercise.

Give every participant a short briefing on scope and safety. Afterward, separate plan gaps, training gaps, access gaps and resource gaps so corrective action reaches the right owner.

Schedule the retest while the debrief is fresh. A completed action without a realistic retest leaves readiness uncertain. Preserve the original objective so the team can compare the same decision or evidence path.

Owner exercise checklist

Before the session, confirm the objective, facilitator, observers, participants, fictional data, safety boundaries, current plans, injects, expected decision evidence, stop authority and secure note location. During it, record what participants retrieved, decided, communicated and escalated, including unresolved questions and elapsed time where relevant. Afterward, classify each finding as plan, access, training, resource, authority or system work; assign consequence, owner, due date and interim safeguard; approve updates through change control; and schedule the retest. Keep attendance and completion separate from demonstrated objectives.

Limits of tabletop evidence

A discussion exercise cannot prove real-time performance, replace hands-on drills, validate a clinical technique, establish legal compliance or guarantee continuity during an actual emergency. Participants know the event is simulated, and facilitators may unintentionally help. One successful scenario covers only its stated objective, people, tools and assumptions. Use qualified reviewers for clinical, safety, privacy, payer, workforce and legal questions. Real incidents, hazards and required reports must follow active response procedures immediately, regardless of the exercise calendar.

A decision-pressure inject

During a scheduling-platform outage exercise, participants move to the documented downtime list. The facilitator then reveals that the list is six hours old, one center has lost internet and cellular service, and a family reports receiving two conflicting visit times. These injects test version control, alternate communication, authority, and prioritization without requiring participants to handle a real emergency.

Observers should record when the team recognized each condition, which source they trusted, who made each decision, what was communicated, and whether the safe default worked. Confidence or a lively discussion is not completion evidence.

Owner exercise questions

Before the session, define objective, scope, participants, assumptions, safety boundary, stop rule, records, and measures. After it, separate plan defects, training gaps, missing resources, unclear authority, and scenario artifacts. Assign corrective actions with owners and dates, then retest the changed steps. Preserve sensitive evidence in the right system and publish only what each audience needs. A successful tabletop finds useful weaknesses before a real event; it does not prove every situation is controlled.

Related resources

Sources