An ABA practice constraint register records the current limiting condition for a service, workflow, or initiative. Constraints may involve qualified workforce, supervision, client access, payer throughput, facilities, technology, vendors, cash, leadership, information, approvals, or downstream capacity. Each entry defines the affected flow, evidence, owner, duration, experiment, safeguard, decision, and release rule. It keeps teams from adding work upstream when the bottleneck sits elsewhere.

Define the constraint register

Gideon separates an observed constraint from a suspected cause. A long waitlist may reflect assessment capacity, payer delay, schedule mismatch, location access, family choice, or incomplete intake rather than total staff count. 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 process and service, constrained outcome, observed queue or delay, start date, affected cohort, current throughput, demand, capacity by stage, suspected and verified constraint, source evidence, competing explanation, owner, client and workforce consequence, immediate safeguard, experiment or change, expected signal, eligible population, decision threshold, resource request, dependency, state, release rule, downstream check, recurrence, and next review.

Turn the plan into decision gates

Change one bounded condition when feasible and watches the full flow. If assessment slots increase while authorization or staffing queues grow, the constraint may have moved rather than resolved. Report work in process, elapsed time, completion, rework, client access, and staff burden by stage. A safety, clinical, payer, legal, or access gate is never treated as waste to remove. The register distinguishes a required gate from an avoidable delay and routes changes to the roles with authority.

Protect current services and required work

When documenting a constraint, measure the staff, supervision, time, cash, system, facility, vendor, or leadership capacity already claimed by safe service and required controls. 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

A constraint affecting clinical care goes to qualified clinicians; legal, payer, workforce, privacy, security, finance, and facility constraints go to their 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 constraint's baseline, evidence, assumptions, decision, resource response, workflow version, changes, exceptions, defects, and unresolved effects. 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

Give every proposed constraint a falsifiable test. The test names the expected pattern if the constraint is real, a competing pattern, the data window, ordinary supports, and the decision threshold. Teams avoid experiments that create client risk, bypass payer or clinical gates, or overload staff. When the evidence is inconclusive, the entry stays a hypothesis. When the flow improves, check whether the benefit reached the intended client or operational outcome and whether another stage deteriorated. The constraint closes only after the release condition and downstream validation both pass.

A fictional example

Gideon reviews 18 constraint entries. Twelve have a defined flow, cohort, evidence, owner, experiment, safeguard, and release rule. Two lack stage data, one confuses demand with capacity, one omits client access, and two have no downstream measure. Four repair. Two remain hypotheses. 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 constraint-record integrity is 12 of 18, or 66.7%. Sixteen entries validate, or 88.9%. Clients, referrals, work items, stage hours, staff capacity, constraints, experiments, and completions retain separate denominators.

Control the main planning risk

Calling staff the bottleneck can drive hiring before the real constraint is known. The practice requires stage-level evidence and a measurable release condition before committing resources.

Test hard cases

Test assessment queue, authorization delay, supervisor capacity, room shortage, schedule mismatch, client access, interface error, cash limit, vendor delay, shifted bottleneck, required gate, and seasonal change. 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 constraint register 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 constraint register, set a planning horizon, or authorize which bottleneck currently limits a service or initiative and what evidence could change that conclusion.

Use compliance guidance within its limits

When reviewing the constraint register, 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 constraint register, 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 constraint register, 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 constraint register, 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 constraint register, 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.

Distinguish a real constraint from a chosen target

If assessment starts are limited to eight per month, identify whether the bottleneck is qualified clinician time, room capacity, payer readiness, family availability, documentation, or an internal target. Quantify the affected cohort and evidence period. A decision to hold volume below possible capacity belongs in the decision log, while a resource that prevents the next unit belongs in the constraint register. Recheck after each material change instead of carrying the label forward indefinitely.

Related resources

Sources