An ABA practice scenario plan models several plausible operating paths and the decisions each path requires. Base, upside, downside, severe-but-plausible, and recovery scenarios use explicit demand, staffing, authorization, collection, cash, facility, vendor, and incident assumptions. Each scenario names triggers, safeguards, owners, options, dependencies, and evidence. It prepares decisions without pretending to predict one future or turning a downside case into a client-care rule.

Define the scenario plan

Idris uses the same definitions and horizon across scenarios so leaders can compare them. He separates income statement results, cash timing, qualified service capacity, client access, and operational risk. The record connects source evidence, decision authority, capacity, cash, client and workforce effects, dependencies, measures, uncertainty, actions, and proof needed for the next state.

Choose fields that support the decision

Record planning horizon, baseline and source date, scenario name, probability language if used, demand, referral and conversion inputs, active-client cohort, service and attendance, staffing and supervision, authorization timing, payer mix, rate, submission and collection lag, payroll and other cash outflows, facility and vendor events, restricted cash, opening liquidity, contingency, client and workforce safeguard, leading indicator, trigger, decision owner, permitted action, dependency, recovery condition, review date, and actual path.

Turn the plan into decision gates

Predefine staged responses. A slower collection signal may freeze discretionary spend, revise hiring timing, or increase follow-up while protected payroll and client-safety needs remain funded. A demand increase does not authorize service starts beyond qualified capacity. A facility loss can move only the services whose legal, payer, clinical, access, staffing, and consent gates clear elsewhere. Leaders review triggers monthly and after material events, record the chosen action, and update the model without rewriting the original scenario.

Protect current services and required work

Each scenario starts from the staff, supervision, cash, systems, facilities, vendor support, and leadership capacity available after existing service and control commitments. Planning begins with net available capacity. A proposed change cannot borrow hidden labor from documentation, supervision, incident response, client communication, payroll, payer deadlines, maintenance, or recovery.

Preserve qualified decisions and direct input

Scenario-specific clinical choices stay with qualified clinicians, while legal, payer, workforce, privacy, security, finance, and facility choices stay with authorized owners. Clients, families, and affected staff receive accessible ways to identify priorities, burdens, access needs, side effects, and workable alternatives. Their input is evidence, not a ceremonial signoff.

Keep versions, assumptions, and open work visible

Preserve the approved scenarios, shared baseline, assumptions, trigger decisions, resource responses, workflow versions, changes, exceptions, defects, and unresolved work. Forecast updates never rewrite the earlier forecast. A closed milestone can link to later validation without pretending that adoption, benefit, payer acceptance, clinical quality, or financial return has already occurred.

Build decision-grade evidence

Validate scenario mechanics before leaders use the outputs. Each formula has one unit, each cash item appears once, opening balances reconcile, and timing matches the model period. Test delayed authorization, delayed collection, staff attrition, cancellations, payer mix, site costs, vendor charges, taxes, debt, restricted funds, and recovery lag separately before combining shocks. Sensitivity tables show which inputs drive liquidity, service capacity, and client access. A second reviewer checks arithmetic and source mapping. Scenario approval means the model supports planning, not that the predicted path will occur.

A fictional example

Idris models five scenarios with 12 locked inputs each, creating 60 scenario-input records. Forty-five have source, range, owner, trigger, and linked action. Five double-count cash, three omit supervisory capacity, two lack client safeguards, and five use inconsistent horizons. Ten repair. Five remain uncertain and receive contingency. The scenario is synthetic. It tests scope, capacity, evidence, state, and denominator logic without establishing clinical quality, legal compliance, payer approval, staffing, funding, safety, client satisfaction, financial return, or outcome.

Calculate compatible measures

Initial scenario-input integrity is 45 of 60, or 75.0%. Fifty-five validate, or 91.7%. Scenarios, inputs, clients, service hours, staff, dollars, triggers, and decisions remain separate.

Control the main planning risk

A detailed model can hide fragile inputs. The practice shows sensitivity, source date, range, and decision effect for every material assumption instead of burying uncertainty in one forecast.

Test hard cases

Test base case, referral upside, authorization delay, staffing loss, collection slowdown, payer termination, site closure, vendor outage, severe incident, restricted cash, recovery, and mixed conditions. Each case states the source, qualified owner, affected cohort, capacity and cash effect, client and workforce safeguard, dependency, decision, evidence, validation, and next review.

Close the review with unresolved work visible

Before closing the review, confirm source currency, authority, scope, capacity, resources, dependencies, assumptions, client and workforce effects, measures, exceptions, side effects, benefit evidence, corrective work, and open decisions. The scenario plan remains draft until every named reviewer completes the required review.

Place the planning method within organizational scope

Use the CASP Organizational Guidelines public overview for high-level business, clinical-operations, and risk-management context. CASP sells the detailed guidance. The public page does not prescribe this scenario plan, set a planning horizon, or authorize what leaders will do when observed conditions cross defined operating triggers.

Use compliance guidance within its limits

When reviewing the scenario plan, treat the OIG General Compliance Program Guidance as voluntary and nonbinding. Its discussions of leadership, risk assessment, training, reporting, audits, corrective action, incentives, and oversight inform planning checks. Current law, payer, professional, workforce, privacy, finance, facility, contract, and legal sources control actual obligations.

Use business-planning sources as orientation

For broad business context around the scenario plan, use the SBA Manage Your Business and Write Your Business Plan pages as orientation. They give no ABA clinical, payer, facility, workforce, tax, privacy, safety, or legal authority. Page-specific sources, qualified owners, operating evidence, and current conditions support every material commitment.

Preserve clinical authority and client involvement

For professional duties affected by the scenario plan, apply the current BACB Ethics Code to covered people and professional activities. It addresses competence, responsibility, client involvement, documentation, supervision, risk, evaluation, billing, and reporting. BACB has no separate corporate jurisdiction. Plans allocate resources and request decisions without transferring qualified clinical judgment to owners or software.

Include leadership and workforce evidence

For worker participation and safety conditions in the scenario plan, use OSHA's management leadership and worker participation pages as general guidance about goals, resources, accountability, reporting, participation, and response. The pages do not create a universal ABA planning model. Workers need usable routes to surface workload, access, safety, and implementation problems without retaliation.

Keep technology-risk planning scoped

For technology and information dependencies in the scenario plan, the practice may adapt the NIST Cybersecurity Framework as voluntary cybersecurity risk-management guidance. It does not replace HIPAA, state law, payer contracts, clinical authority, or the broader operating plan. Cybersecurity assumptions, risks, controls, incidents, and recovery work remain visible within the portfolio rather than hidden in a separate technical backlog.

Test connected events, not only one variable

A downside scenario might combine delayed payer enrollment, one supervisor's leave, and a technology migration occurring in the same month. Show which events are independent, which share a cause, and how their combined demand affects current services, cash, staffing, access, and decision capacity. Define early indicators and gated responses before choosing them. The scenario is a planning case, not a prediction or permission to bypass each domain's normal authority.

Related resources

Sources