Center-Based ABA During Power, Internet, and System Downtime

Classify the event before choosing a response

Power loss, internet failure, phone outage, inaccessible records, door-control failure, HVAC loss, alarm trouble, water interruption, and a vendor platform incident have different consequences. Record detection time, affected systems and rooms, known hazards, incident lead, and current state. The Ready.gov outage sheet gives general household and community orientation for power outages. The center must also follow current facility, fire, licensing, utility, insurer, privacy, payer, and local emergency requirements.

Handle immediate danger first

Call emergency services and follow site emergency procedures for fire, smoke, electrical hazards, medical emergencies, unsafe temperature, failed life-safety systems, flooding, or another imminent threat. Do not delay evacuation to save data or finish a session. Account for clients, visitors, and staff at the designated location. Keep communication and mobility supports with the person when safe. The incident lead records what is known while qualified emergency and facility authorities control their response.

Use hard gates for continued care

Before any service continues, verify a safe and accessible location, current client-specific health and safety information, AAC and backup, qualified assigned staff, required supervision, adequate lighting and temperature, bathroom access, secure records, and a functioning emergency contact route. A qualified clinician decides whether the planned clinical work remains appropriate. Operations confirms site and staffing gates. If a required condition is missing, pause, relocate, modify through the authorized route, or reschedule.

Keep current client information available securely

Approved downtime access should provide only the current information a role needs, such as client identity, contacts, allergies, medication or health instructions, mobility, communication, supervision, and emergency supports. Protect paper and offline records from unauthorized viewing, loss, and stale copies. Mark the version or as-of time. Never rely on an employee's memory for a critical health or safety instruction. Reconcile every temporary record into the governed system after recovery.

Preserve AAC and accessible communication

The ASHA AAC portal supports continual access to communication tools. Confirm device power, charger, battery backup, mount, vocabulary, and a tested low-tech option. Do not use a power outage as a reason to remove communication or require speech. Provide accessible family and staff updates through more than one channel when possible. Record a failed device or unavailable backup as an outage impact.

Protect privacy while normal systems are unavailable

Use approved forms, devices, contact lists, and storage. Limit discussion in hallways, parking areas, shared rooms, or personal messaging accounts. Verify identity before sharing client information by backup channel. Record who accessed a downtime file and where it went. A system outage does not suspend privacy duties. Route suspected loss, unauthorized access, or disclosure through the incident process while continuity work proceeds.

Record actual care and actual time

Document the service that truly occurred, its location, participants, start and end, interruptions, clinical changes, supports, incident actions, and the time the record was created. Preserve authorship and correction history. Staff time, service time, troubleshooting time, and closure time may have different payroll and payer treatment. Do not recreate a full session from memory days later or bill a scheduled duration as delivered care. Assign every temporary note an expected final record and reconciliation owner.

Tell families what changed

Use a verified contact route to state the known event, client status, pickup or schedule effect, next update time, and alternate plan. Avoid technical speculation. Ask whether the family can safely use the proposed change. Record reached, delivered, acknowledged, and unanswered as different states. If the center closes, clarify custody and pickup steps. If care continues elsewhere, verify site, transport, consent, payer, staffing, and clinical authority rather than treating relocation as automatic.

Recover through acceptance checks

Power, internet, or vendor availability is a technical milestone. Before normal operations resume, validate building systems, door and alarm functions, temperature, water, network, identity and access, application integrity, current client data, device charging, staff communications, and record queues. Then account for every scheduled visit, temporary record, medication or health action, payroll entry, authorization or claim hold, family update, and postponed task. Close the incident only when owners accept the evidence.

Measure both speed and completeness

Define detection, activation, safe-stop, communication, technical-restoration, and operational-acceptance times. Report affected clients accounted for, required contacts completed, temporary records reconciled, and corrective actions closed using explicit denominators. Keep postponed and partially delivered services visible. Fast reopening with missing client information or unreconciled notes is not success. Review repeated single points of failure, backup age, staff familiarity, accessibility, and family burden after each event or exercise.

Exercise the plan before an outage

Run a tabletop scenario with one unavailable leader and one failed backup. Ask staff to locate the current client roster, health and communication information, AAC power options, emergency contacts, paper records, and family message without opening ordinary systems. Test who can authorize evacuation, continuity, clinical modification, closure, and recovery acceptance. Record the time and any missing evidence. Use safe simulations and access checks rather than disconnecting life-safety equipment or creating clinical risk. Assign every finding an owner and due date, then retest the failed step. A binder on a shelf is not a tested downtime process until the right people can use its current contents under realistic conditions. Include an evening or weekend scenario, a family who cannot receive the usual channel, and a client whose ordinary backup requires power. Verify that every temporary form has a secure storage and reconciliation route.

A fictional downtime example

At 2:10 p.m., a center loses power and internet with 14 clients present. Staff reach the approved assembly area and account for 14 of 14 clients. Eleven clients have every continuity gate for the alternate indoor site; three require powered medical, mobility, or communication supports that cannot be verified there. Those three follow their individual plan and family route. Recovery remains open after power returns until 11 of 11 temporary service records and all 14 custody updates are reconciled.

Questions families can ask

Ask which events trigger evacuation, closure, or continuity mode. Confirm building gates, client information, AAC and batteries, staffing and supervision, privacy, approved records, contact methods, pickup, alternate sites, actual service time, payer handling, recovery tests, and reconciliation. Ask how the center accounts for every person and note. A useful downtime plan gives staff permission to stop care when the information, environment, or support needed for safe service is missing.