An ABA practice location and service-area register is a versioned map of sites and geographic offers by service, setting, modality, payer, team, and date. It separates marketing reach from entity authority, facility status, professional scope, payer participation, operational capacity, accessibility, telehealth, travel, safety, and case-specific clinical fit. A ZIP code inside a radius never proves that a client can be scheduled there.

Define the location and service-area register

Tarek stores physical sites, home-service zones, community areas, and telehealth jurisdictions as different location types. Every type has its own evidence, qualified owner, renewal date, and stop condition. Every row has a stable identifier, owner, custodian, source, effective period, state, evidence, exception, change trigger, next review, and relationship to the decisions it supports.

Choose fields that support the decision

Record location ID and type, address or geographic rule, entity and local registration, facility and permitted-use status, professional and telehealth pathways, insurance territory, payer and product, service and modality, operating hours, accessible route and equipment, emergency plan, staff and supervision, travel model, weather margin, system connectivity, capacity, source and effective date, reviewer, exception, hold, next review, and closure evidence.

Separate source facts from practice decisions

For each location and service area, record the license, contract, payer rule, property condition, system evidence, policy, or qualified judgment that supports operating there. The practice's supported, held, conditional, retired, or exception state appears in a separate field with an owner and date. A portal result, marketing statement, verbal comment, identifier, or old approval never silently becomes controlling evidence.

Set entry, review, and retirement rules

Define when a location or service-area row is created, when services may be scheduled there, who reviews it, which changes reopen review, and when the row is retired. Source expiry, staff changes, new sites, payer updates, system releases, incidents, audit findings, contract changes, and capacity shifts can trigger review. Historical versions remain available for older transactions and explanations.

Connect fields to real workflow gates

Trace which intake, scheduling, clinical, authorization, billing, safety, reporting, and continuity workflows rely on each location and service-area field. Software may surface a current state and block a defined release. Authorized roles decide exceptions and qualified clinicians retain clinical judgment. The operational record keeps each decision and author visible.

Make a bounded operating decision

The practice uses the register to answer a configuration question, not to label an entire address open or closed. A center may be ready for assessment under one payer while treatment rooms, staffing, or another product remain held. A home-service zone may be operational only on certain days and travel bands. When a source expires, the practice stops new releases that depend on it and routes existing clients through qualified continuity review. A map change never acts as an automatic clinical discharge. The record shows the affected configurations, interim limits, client communication owner, and evidence required to restore release.

Reconcile independent source populations

Reconcile the location and service-area register against licenses, leases, payer directories, schedules, claims, property records, site inspections, and staff or client reports. Differences receive an owner, consequence, next action, due date, and validation instead of disappearing through manual overwrites.

A fictional example

Tarek reviews 30 site-service configurations. Twenty-two have current authority, payer, access, staffing, safety, and capacity evidence. Two use a marketing radius as a release rule, two lack facility evidence, one has stale telehealth authority, one lacks an accessible entrance plan, and two exceed travel capacity. Six repair. Two remain held. The scenario is synthetic. It tests scope, evidence, state, exception, and denominator logic without establishing legal compliance, clinical quality, coverage, payment, licensure, competence, security, financial accuracy, client satisfaction, or outcome.

Calculate compatible measures

Initial release readiness is 22 of 30, or 73.3%. Twenty-eight configurations validate, or 93.3%. Sites, geographies, services, payer products, modalities, and client requests retain distinct denominators.

Control the main risk

One map can make legal authority and real capacity look interchangeable. Tarek preserves layered gates and requires the exact client-service configuration to clear before scheduling.

Test hard cases

Test new site, existing facility, home zone, telehealth border, community setting, inaccessible entrance, payer directory mismatch, travel surge, weather closure, temporary room loss, and location retirement. Each case shows the source, owner, current state, affected workflow, immediate safeguard, exception route, correction, validation, and retirement or next-review rule.

Close the review with open work visible

Before closing the review, confirm population completeness, source currency, decision authority, qualified ownership, evidence, cross-register links, exceptions, change triggers, workflow use, validation, unresolved work, and next review. The location and service-area register remains draft until every named reviewer completes the required review.

Use CASP as organizational context

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 location and service-area register, prove a row is complete, or grant authority for whether an exact service can be offered at a location or in a geography.

Apply voluntary compliance guidance carefully

When reviewing the location and service-area register, treat the OIG General Compliance Program Guidance as voluntary and nonbinding. Its discussions of risk assessment, policies, training, reporting, audits, corrective action, incentives, and oversight help test register design. Current law, contract, payer, professional, workforce, privacy, finance, and operational sources control each real decision.

Keep business orientation separate from authority

For broad business context around the location and service-area register, use the SBA Manage Your Business guide as orientation across finances, employees, compliance, marketing, emergencies, and closure. It gives no ABA clinical, payer, privacy, licensure, facility, credentialing, tax, or legal authority. The register cites current primary sources for every material state.

Preserve clinical decision rights

For professional duties reflected in the location and service-area register, apply the current BACB Ethics Code only to covered people and professional activities. The Code addresses competence, responsibility, client involvement, documentation, supervision, risk, evaluation, billing, and reporting. BACB has no separate corporate jurisdiction. Organizational ownership and register custody never replace qualified case-specific clinical judgment.

Scope privacy and security fields

For electronic PHI represented in the location and service-area register, use HHS risk-analysis guidance when a covered entity or business associate must assess risks and vulnerabilities to all electronic protected health information it creates, receives, maintains, or transmits. HHS minimum-necessary guidance informs role-based PHI access when that standard applies. Neither source mandates a particular database, register, score, spreadsheet, or vendor product.

Use cybersecurity and provider identifiers within limits

For cybersecurity and identifier dependencies in the location and service-area register, the practice can adapt the NIST Cybersecurity Framework as voluntary risk-management guidance while current legal and contractual requirements remain controlling. The CMS NPI fact sheet distinguishes individual and organizational identifiers and states that an NPI does not establish licensure, credentialing, enrollment, or payment. Identifiers connect records; they do not validate the underlying configuration.

Handle a location change as a new configuration

When a center moves or a service area expands, do not overwrite the earlier row. Create a dated configuration and recheck facility, access, safety, payer, professional, workforce, tax, insurance, privacy, travel, and clinical dependencies under their qualified owners. Keep the old location linked to visits and records from its effective period. Release the new configuration only after the applicable source registers and user-facing schedules agree.

Related resources

Sources