An ABA practice site performance review examines one location's services, client access, clinical quality, staffing and supervision, schedule capacity, payer operations, facilities, safety, privacy, client experience, cash, controls, local variation, and open risks. It compares the site with its approved operating configuration and prior periods. The review supports local decisions while keeping professional, payer, legal, and enterprise authority with the proper roles.

Define the site performance review

Olive defines the site boundary and includes home, community, or telehealth work managed by the location only when the operating model assigns it there. Shared services retain their own accountability. The review has a charter, purpose, evidence cutoff, eligible cohort, source definitions, qualified participants, decision agenda, action record, escalation route, validation method, and next review.

Build the site-review fields

Olive records site and review period, approved service portfolio, client and waitlist cohorts, access and communication supports, clinical review evidence, outcomes and burden, qualified staff and supervision, schedule and room capacity, cancellations, authorization and claim states, receipts and direct costs, facility and equipment status, safety and privacy events, complaints and experience, policy variants, shared-service dependencies, control results, risks, decisions, owners, actions, validation, and next review.

Turn discussion into attributable decisions

Olive separates site-controlled work from shared-service and enterprise decisions. A site leader may adjust local schedules within approved rules while a qualified clinician decides clinical suitability and central payer operations owns a product issue. When a local variance works, the record shows whether it should remain local, become a controlled pilot, or enter enterprise change control. A temporary capacity limit includes client communication and continuity work. Site performance never becomes a league table that rewards excluding complex clients or hiding incidents.

Build a decision-grade evidence pack

The site pack includes counts and rates with the same eligible populations across periods. Olive segments access, service, cancellations, staffing, supervision, claims, and incidents by service or payer when useful. She reports small cohorts as counts and avoids unstable rankings. Direct client and staff input accompanies administrative data. Facility inspections, access barriers, unresolved repairs, system downtime, and shared-service delays stay visible even when the site cannot resolve them alone. Each external dependency has an internal owner and decision date.

Prepare the site review before the meeting

Olive prepares the site review with the local leader, clinical leader, facilities owner, payer operations, and shared services. The pack identifies which measures the site controls and which depend on central teams. Staff and client input arrives through accessible routes before conclusions are drafted. Local leaders can correct facts without suppressing unfavorable results. Decisions that require enterprise funding, professional authority, landlord action, or payer clarification receive a named route. The site keeps interim safeguards and updates affected families while it waits.

Protect urgent routes and qualified authority

Olive never delays emergency, safety, mandated, privacy, clinical, payroll, or payer-clock action until the next meeting. Case-specific clinical decisions stay with qualified clinicians. Employment, accommodation, payer, finance, privacy, security, facility, and legal decisions stay with their authorized roles. The review records the conclusion and linked source while restricting sensitive detail to approved systems.

Keep cohorts, clocks, and exceptions honest

Olive defines the event, eligible population, numerator, denominator, maturity window, exclusions, missing data, source date, and workflow version before reporting a measure. Pending, held, rejected, withdrawn, invalid, and incomplete items remain visible. Counts accompany percentages. Average time appears with range, oldest items, and start and end events. A changed definition creates a new series or a documented restatement.

Work through a fictional site review

Olive reviews 18 monthly site packs. Thirteen have comparable cohorts, clinical and access evidence, capacity, payer state, facility controls, risks, actions, and validation. One omits a closed room, one hides a supervision gap, one pools payer products, one lacks client input, and one uses a stale service list. Four repair. The supervision month remains held. The scenario is synthetic. It tests evidence, authority, decision, follow-through, and denominator logic without establishing clinical quality, legal compliance, payer approval, staffing, safety, client satisfaction, financial accuracy, or outcome.

Calculate the review measures honestly

Initial site-pack integrity is 13 of 18, or 72.2%. Seventeen validate, or 94.4%. Sites, months, clients, services, staff, rooms, claims, incidents, and actions retain separate denominators.

Address the main site-performance risk

A site can appear efficient by shifting work or risk to central teams. Olive includes shared-service dependencies and downstream rework in the site's operating picture.

Test the site review against hard cases

Olive tests new site, mature site, home program, closed room, staffing gap, access request, payer delay, facility repair, incident cluster, complaint, local variant, and shared-service failure. Each case states the source, qualified owner, affected cohort, immediate safeguard, decision, conditions, action, evidence, validation, and next review.

Close with unresolved site work visible

Olive confirms charter, source currency, cohort, authority, qualified participation, direct input, decisions, dissent, safeguards, actions, due dates, downstream updates, validation, recurring conditions, and open work. The site performance review remains draft until every named reviewer completes the required review.

Place the site review within organizational scope

Olive uses 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 site performance review, validate the evidence pack, or authorize conclusions about one location's access, quality, capacity, and controls.

Use compliance guidance within the review's limits

Olive treats the OIG General Compliance Program Guidance as voluntary and nonbinding. Its discussions of leadership, risk assessment, reporting, auditing, corrective action, incentives, and oversight inform review design. Current law, payer, professional, workforce, privacy, finance, safety, facility, contract, and legal sources control the decisions.

Use broad business orientation carefully

Olive uses the SBA Manage Your Business guide only as broad orientation across finances, employees, compliance, marketing, emergencies, and closure. It gives no ABA clinical, payer, privacy, safety, tax, facility, or legal authority. The evidence pack cites current primary sources for material conclusions.

Preserve professional accountability in the meeting

Olive applies 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. Review forums request and record qualified clinical decisions without transferring them to owners or software.

Include leadership and workforce voice

Olive uses OSHA's management leadership and worker participation pages as general safety-program guidance on goals, resources, accountability, reporting, participation, response, and nonretaliation. The pages do not create a universal ABA review method. Staff need usable routes to raise workload, access, safety, and implementation evidence.

Limit sensitive data and payer inferences

Olive applies HHS minimum-necessary guidance to role-based PHI access when the standard covers the use, disclosure, or request. Restricted clinical, personnel, legal, and security detail stays in approved records. The HealthCare.gov preauthorization glossary states that preauthorization is not a promise the plan will cover the cost. Authorization, claim acceptance, adjudication, payment, and client responsibility remain distinct.

Related resources

Sources