ABA practice client arrival and departure operations coordinate the period from approaching the site through an accountable handoff into service and from service completion through an authorized departure. The workflow joins schedules, accessible communication, identity, authority, custody restrictions, transportation, waiting, delays, attendance, missing-person response, emergencies, privacy, and records. Clear states show who is expected, present, responsible, waiting, transferred, delayed, or unresolved.

Define the client arrival and departure operation

Cyrus maps vehicle, pedestrian, transit, rideshare, school, family, and provider transportation paths. He separates permission to receive operational updates from authority to pick up, consent, obtain records, or make treatment decisions. Each client has an accessible arrival and departure method plus a defined exception route. The arrival, presence, handoff, and departure record has a named owner, defined scope, current sources, qualified decision boundaries, version, evidence location, exception route, change triggers, and retirement state.

Choose fields that support the decision

The working record captures client and date; scheduled service and site; expected arrival and departure windows; transport method; accessible route and communication; authorized handoff people and source; custody or safety restriction; identity check; actual arrival; responsible staff acceptance; belongings and medication route; delay contact; presence state; service transition; actual departure; receiving person; failed pickup; transportation issue; missing-person or emergency action; incident; owner; reconciliation; and closure. Each field supports a defined decision or later trace. Optional narrative stays short and points to the underlying evidence.

Use the artifact for bounded decisions

Define who owns the client at each transition and what evidence changes that state. Staff use purpose-limited identity checks and receive only the authority information needed for the handoff. Early, late, unexpected, and failed pickups have separate routes. Emergency and mandated actions proceed through policy without waiting for routine intake or scheduling work.

Keep responsibility visible through handoffs

For each arrival or departure, identify who observes the client status, who may decide the response, who carries it out, and who accepts completion. Handoffs include the current state, affected people and services, urgent safeguard, due time, evidence, and next contact. Unanswered work remains visible on the next shift.

Handle exceptions without erasing the control

An arrival or departure exception records the requested departure, reason, source, affected people and services, qualified approver, scope, start, expiry, monitoring, communication, and stop rule. Preserve the original requirement and the actual decision. Repeated exceptions trigger design review because they may reveal unrealistic staffing, space, vendor, system, or scheduling assumptions.

Validate the artifact in operation

Shadow morning and evening flows, tests accessible contact channels, reconciles the roster with observed presence, and samples authorized handoffs. Drills cover a late vehicle, an unrecognized adult, a custody alert, a missing client, an inaccessible entrance, and a system outage. Every unresolved person stays visible until accountability is restored.

Reconcile records with the conditions people encounter

Compare approved records with current rooms, doors, schedules, people, equipment, alerts, work orders, and recent incidents. Differences receive owners and resolution states. This reconciliation keeps the client arrival and departure operation connected to daily operations instead of allowing paperwork and site conditions to drift apart.

Protect communication, access, privacy, and safety

Arrival and departure operations preserve needed AAC, interpreter support, effective communication, accessible routes, privacy, emergency help, mobility, prescribed care, food, water, and bathroom access as applicable. Workers can report hazards and clients or families can report barriers through usable channels. Routine review never delays emergency action or another required protective route.

A fictional example

Cyrus locks 24 arrival-departure periods. Eighteen have current schedules, access, authority, identity, accountable transitions, delay routes, and complete records. One accessible route fails, one pickup authority is stale, two delays lack updates, and two departures lack receiving-person evidence. Four repair. Two remain open. The scenario is synthetic. It tests source, role, access, safety, evidence, and denominator logic without establishing clinical quality, legal compliance, payer approval, safe performance, satisfaction, or outcome.

Calculate compatible measures

Initial arrival-departure integrity is 18 of 24, or 75.0%. Twenty-two validate, or 91.7%. People, scheduled visits, transport legs, handoffs, delays, incidents, and open periods remain separate.

Address the main client arrival and departure operation risk

A signed attendance record can still leave responsibility between two adults unclear. The practice records the exact handoff event and receiving role at each boundary.

Test hard cases

Test early arrival, late pickup, rideshare, school transport, unrecognized adult, changed custody restriction, inaccessible entry, elopement concern, medical event, outage roster, forgotten belongings, and site evacuation during pickup. Each case states the source, owner, affected people, access and safety conditions, evidence, exception, immediate safeguard, correction, acceptance result, and next review.

Close review with unresolved work visible

Before closing the review, confirm scope, sources, authority, actual site conditions, access, staff readiness, vendors, incidents, evidence, exceptions, corrections, and fresh validation. The client arrival and departure operation stays draft until every named reviewer finishes the required review. Open work retains its owner, age, effect, and next action.

Place the arrival, presence, handoff, and departure record within organizational scope

Use the CASP Organizational Guidelines public overview for high-level business, clinical-operations, and risk-management context. CASP sells the detailed guidelines. This page presents an editorial client arrival and departure operation and does not claim that the public overview prescribes its fields or decisions.

Find the authorities that govern the site

The SBA license and permit guide says requirements vary with activity, location, and government rules. USA.gov helps locate state and local governments. The practice treats both as orientation and verifies actual zoning, building, fire, facility, business, accessibility, and other requirements with current responsible authorities and qualified advisors. For client arrival and departure operations, the practice records which site authority supplied each requirement and when it was last confirmed.

Build usable access into the operation

The DOJ Title III overview addresses equal opportunity, effective communication, reasonable modifications, service animals, physical access, and related duties for covered public accommodations, subject to the law's standards and defenses. The practice keeps legal analysis with the responsible specialist and tests whether people can use the actual route, communication method, policy, and service. Accessibility testing for client arrival and departure operations should cover the route and communication task with the people who must actually use it.

Connect the control to emergency planning

OSHA emergency-preparedness guidance says an emergency action plan is required when another OSHA standard triggers 29 CFR 1910.38 and recommends planning more broadly. Current 29 CFR 1910.38 lists required elements and its small-employer oral-plan condition. Ready Business is voluntary general preparedness guidance. Separately verify state-plan, building, fire, licensing, and local rules. Emergency planning for client arrival and departure operations should identify the triggering hazard, responsible role, alternate route, drill or test evidence, and unresolved condition.

Match infection and exposure controls to the setting

The CDC core practices address infection prevention across settings where healthcare is delivered. Current 29 CFR 1910.1030 governs covered occupational exposure to blood and other potentially infectious materials. The practice first classifies the setting, task, workforce exposure, and applicable state-plan requirements, then assigns cleaning, PPE, exposure, and evidence controls to the responsible roles. Exposure controls in the client arrival and departure operations record should connect each identified risk to cleaning, PPE, response, and training that fits the actual task.

Keep chemical information available during work

OSHA's Hazard Communication overview and current 29 CFR 1910.1200 support a written program, chemical list, labels, accessible safety data sheets, and training when the standard applies. Align purchasing, storage, actual tasks, contractor use, spill response, and disposal with the governing federal or state-plan sources. Chemical controls tied to client arrival and departure operations should show the product, location, user, safety data, training, and correction history.

Separate incident records and reports in the workflow

OSHA's recordkeeping page distinguishes recording, reporting, and electronic submission. Its severe-injury reporting page describes federal clocks for covered work-related fatalities and severe injuries. The practice keeps these routes separate from emergency response, clinical records, privacy review, payer or licensing notice, insurance, and local-authority reporting, and checks state-plan differences. If client arrival and departure operations contributes to an incident, the practice should preserve the event facts once and route each required record or report to the correct owner.

Related resources

Sources