An ABA practice initiative portfolio is the governed inventory of proposed, active, held, completed, and stopped changes across the organization. It includes regulatory and payer obligations, maintenance, corrective actions, experiments, and growth work. Each initiative has a benefit, owner, effort, dependency, capacity need, risk, decision, hold rule, sequence, evidence, and closure state. It prevents departments from committing the same people and systems twice.

Define the initiative portfolio

Eileen records small and large changes in one portfolio when they compete for scarce resources. Routine service work remains outside the portfolio but contributes to each role's available capacity. 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 initiative ID and type, originating decision, problem or opportunity, affected clients and teams, expected benefit, required obligation, sponsor, accountable and qualified owners, scope, sites and systems, effort by role, cash, vendor and facility needs, dependency, constraint, risk, safeguard, priority criteria, sequence, target window, entry gate, state, hold reason, change request, measure, acceptance evidence, open defect, benefit review, closure, and archive link.

Turn the plan into decision gates

Use a monthly portfolio council to approve tradeoffs. A high-value idea may wait when its clinical reviewer, implementation lead, data source, or training capacity is unavailable. Mandatory work may displace lower-priority changes but still needs a feasible plan. Teams cannot label an initiative complete while unresolved defects or adoption work remain hidden. Stopped initiatives retain the reason, spent resources, reusable evidence, and commitments that need cancellation. Portfolio views show current load by role and dependency alongside department-level views.

Protect current services and required work

Before admitting an initiative to the portfolio, inventory the staff, supervision, cash, systems, facilities, vendor support, and leadership attention it would consume. 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

Send an initiative's case-specific clinical choices to qualified clinicians and its legal, payer, workforce, privacy, security, finance, and facility choices to 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 portfolio decision, initiative scope, baseline, assumptions, allocated resources, workflow version, changes, exceptions, defects, and unresolved dependencies. 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

Use published intake criteria for proposed initiatives. A request states the problem, affected cohort, current evidence, expected benefit, required authority, rough effort, scarce roles, dependencies, risks, and deadline source. The portfolio owner returns incomplete proposals without turning them into invisible side work. Approved discovery has a time box and decision date. Discovery approval does not authorize implementation. At each state change, the portfolio owner records who decided, what evidence changed, what resources became committed, which alternative was rejected, and which downstream teams must accept the handoff.

A fictional example

Eileen reviews 28 initiatives. Nineteen have complete benefit, scope, owner, effort, dependency, risk, gate, and closure evidence. Three compete for one data lead, two duplicate vendor work, one lacks a clinical owner, one has no adoption measure, and two have no capacity. Six repair or combine. Three stay held. 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 portfolio readiness is 19 of 28, or 67.9%. Twenty-five initiatives validate, or 89.3%. Initiatives, tasks, milestones, people, hours, benefits, defects, and holds remain separate.

Control the main planning risk

A ranked list can hide impossible concurrency. The practice tests time-phased demand for each scarce role, system, vendor, facility, and decision-maker before approving starts.

Test hard cases

Test mandatory change, clinical program, revenue project, system upgrade, duplicated proposal, scarce reviewer, vendor dependency, paused initiative, scope increase, stopped work, completed change, and benefit review. 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 initiative portfolio 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 initiative portfolio, set a planning horizon, or authorize which changes should start, wait, stop, or share resources.

Use compliance guidance within its limits

When reviewing the initiative portfolio, 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 initiative portfolio, 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 initiative portfolio, 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 initiative portfolio, 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 initiative portfolio, 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.

Review shared dependencies before approving more work

Two initiatives can appear independently staffed while relying on the same clinical reviewer, data migration, trainer, vendor, or center leader. Show that dependency and its dated capacity in the portfolio. If a third initiative arrives, compare delay, pause, sequence, rescope, or rejection options before committing. Preserve required operations and corrective work outside the discretionary portfolio so a favorable project count does not consume the capacity needed for safe current services.

Related resources

Sources