Once AEDs spread across multiple buildings, the job shifts from simple checks to program control. You need one record for each device, one owner for the program, and a repeatable way to track placement, serial numbers, supplies, inspections, responders, certifications, and state-specific requirements. That’s the work. The hard part isn’t any single inspection. The hard part is that nothing lines up.
Different AEDs were bought in different years, so their batteries expire in different months. Different states have different documentation requirements, so the records you keep for a California unit don’t automatically satisfy New York. Different buildings have different responsible parties, and the person who maintained the spreadsheet two years ago is now in a different role or a different company. By the time a facility manager has 12 AEDs across 4 buildings, the spreadsheet has either become a part-time job or it has quietly stopped reflecting reality.
This guide covers what changes when you scale past 2–3 AEDs, the four problems that always surface around the 10-device mark, the workflow facility managers actually use to keep multi-site programs audit-ready, and the specific compliance traps that hit multi-state operators harder than single-location facilities.
Why multi-location AED management is a different problem
A single AED on a wall is a calendar-reminder problem. One person owns it, knows where it is, and knows when the next thing needs replacing.
Multi-location management is fundamentally a data problem, not a maintenance problem. The physical inspections each take 90 seconds. What breaks is the coordination layer underneath — who owns which device, which records survived which staff transition, which state laws apply to which building, and whether the person who was supposed to do the December inspection at the Phoenix office actually did it or just said they did.
Three structural differences make multi-site harder:
⏱ Staggered expirations
Each AED’s battery was installed on a different date. Each pad set was opened or replaced on a different date. Each responder was certified on a different date. Twelve AEDs means roughly 36 different expiration cycles to track in parallel.
👥 Distributed responsibility
No one person can physically walk to every device every month. You have to delegate, which means you have to verify, which means you need a record that the inspection actually happened — not just a claim that it did.
🗺 State-by-state variance
California’s AED law isn’t New York’s, which isn’t Texas’s, which isn’t Florida’s. Multi-state operators have to track which compliance rules apply where, and which records satisfy which jurisdictions.
The 4 failure points that always surface around 10 devices
Past about 5–10 AEDs, multi-location programs run into the same four problems in roughly the same order.
1 The spreadsheet becomes unreliable
It starts as a Google Sheet with one row per device. By month 8, it has 12 columns, three people have edit access, two of them are no longer with the company, and the “last inspection date” column reflects what was promised, not what was done. Spreadsheets work for tracking what someone intended to do. They fail at tracking what actually happened.
2 Reminders attach to people, not roles
Calendar reminders go to individual email addresses. Bob in Atlanta is on the recurring monthly invite. Bob leaves. The invite still sends. Bob’s replacement never gets added. The Atlanta AED has now gone 4 months without an inspection, and nobody noticed because nobody was watching the absence of an inspection log — only the presence of complaints.
3 Records exist but aren’t centrally retrievable
Inspection logs are in a binder in the Phoenix office. Certifications are on a shared drive. The pad invoices are in someone’s email. When an auditor asks for two years of records, assembling them takes a week. When a lawsuit asks for them after a failed rescue, the gaps that emerge during that assembly become the basis of the case.
4 State-specific requirements get missed
The California unit needs documented medical direction renewal. The New York unit needs the collaborative agreement on file. The Illinois unit needs the training record for the designated responder. Each is a different document, on a different cadence, satisfying a different state statute — and a multi-state operator has to track all of them in parallel without confusing which applies to which.
⚠️ These four problems don’t stay separate. The unreliable spreadsheet feeds the absent reminders, which produce missing records, which surface during a state-specific audit — which is where the failed program gets discovered.
The workflow that works
Programs that manage 10+ AEDs across multiple locations without quietly falling apart share a common structure. Six components, in order:
- A single source of truth for every device. One record per AED that includes location address, building name, specific placement (floor, room, cabinet), serial number, manufacturer and model, install date, current battery install-by date, current adult pad expiration, current pediatric pad expiration (if applicable), designated responder, and applicable state.
- Role-based responsibility, not person-based. “The Atlanta AED coordinator inspects monthly” is durable. “Bob inspects monthly” is fragile. Define the role and the cadence. Onboarding a new person to the role takes 10 minutes. Onboarding a new person to a calendar-reminder-tied-to-Bob’s-Outlook takes a discovery process.
- Automated reminders tied to actual dates, not to memory. Battery expiring in November means a reminder fires 60 days out (early September) and 30 days out (October). Pads expiring in March means reminders in January and February. CPR certifications expiring in August means reminders in June and July. None of this is hard. All of it is invisible work that humans forget to do.
- Inspection records that are timestamped and tied to a specific person. Not “inspected this month” but “inspected on March 14, 2026 by Sarah Chen, AED coordinator, Atlanta location, AED serial 8847291, all 12 checks passed.” This is the format an auditor wants. This is also the format a lawsuit subpoena would request.
- Centralized record retention that survives staff transitions. Records in someone’s email don’t survive the person leaving. Records in a shared system owned by the organization do. Retention expectations vary by state, facility type, insurer, and internal policy — so the system has to outlive multiple employment cycles and make records easy to export when needed.
- State-specific compliance tracking layered on top. Each AED record carries its applicable state, and the system flags requirements that may apply to that device — medical oversight, EMS notification, training documentation, inspection records, or post-use reporting. This is the layer most spreadsheets skip entirely.
💡 AED Log is built around this exact six-component workflow, with multi-location as the primary design target.
The states where multi-location operators get caught
A few state-specific rules surface most often in multi-site audits:
🏛 California — H&S Code 1797.196
Requires local EMS notification, manufacturer-based maintenance and testing, testing at least biannually and after use, inspection at least every 90 days, and maintenance/testing records. California does not require a medical director for AED acquisition or placement.
🏛 New York — Public Health Law 3000-b
Requires a collaborative agreement with an emergency healthcare provider and designated trained individuals. Multi-state operators often have New York units that miss the collaborative agreement because it is a New York-specific requirement.
🏛 Illinois — AED Act
Requires manufacturer-based maintenance and testing, trained anticipated users, EMS activation and reporting after clinical use, and notification of the AED’s existence, location, and type to the local emergency communications center.
🏛 Texas — H&S Code Chapter 779
Requires an approved training course for expected users and notification to local EMS.
🏛 Florida — F.S. 401.2915
Encourages CPR/AED training for users, encourages EMS location notification, and requires EMS activation as soon as possible after AED use.
🗺 All other states
For deeper state-by-state requirements, the AED laws hub covers regulatory specifics. The point isn’t memorizing every statute — it’s having a tracking system that knows which state each device sits in and what that state expects.
What scaling AED management actually looks like in practice
Here is the practical reality at different program sizes:
| Program size | Manual viability | Common failure mode |
|---|---|---|
| 1–3 AEDs, single location | Manageable on paper | Single point of failure if coordinator leaves |
| 4–9 AEDs, 1–2 locations | Manageable on spreadsheet for ~12 months | Spreadsheet drift, missed expirations |
| 10–24 AEDs, 2–5 locations | Spreadsheet effectively broken | Reminders tied to people, records distributed |
| 25–49 AEDs, multi-state | Manual tracking actively dangerous | State-specific compliance gaps |
| 50+ AEDs | Requires dedicated software | Audit failures, lawsuit exposure |
⚠️ The degradation is gradual: There’s no specific Tuesday where the spreadsheet breaks. It degrades one missed reminder, one staff transition, one undocumented inspection at a time. The first time anyone notices is usually during an audit — or during an actual rescue when a device fails.
How AED Log handles multi-location programs
AED Log is built around the six-component workflow above, with the multi-location case as the primary design target rather than an afterthought.
Every AED is logged once with its full identity: location, building, specific placement, serial number, manufacturer, install dates, expiration dates, designated responder, applicable state. Inspection reminders fire automatically on a monthly cadence per device. Battery and pad expirations trigger alerts 60 and 30 days ahead. CPR/AED certifications track alongside device records. Every inspection is timestamped, attributed to a specific user, and exportable as an audit-ready record. All records survive staff transitions because they belong to the organization’s account, not to any one person’s email or laptop.
Multi-state operators get state-applicable rules surfaced per device. A California AED record flags California-specific requirements. A New York AED record flags the collaborative agreement. A program managing 30 devices across 8 states tracks 8 sets of state requirements without anyone having to remember which is which.
Pricing is tier-based, not per device. Adding the 25th AED costs the same as adding the 15th. Adding a new location — with unlimited users on every plan — costs nothing extra. This is the structural difference vs per-device competitors like AED 365, which charges ~$114 per AED per year and scales the bill linearly with program size.
Set up multi-location AED tracking in under 5 minutes
Free forever on 1 AED and unlimited users. No credit card. No trial clock.
✓ Unlimited users & locations
✓ Audit-ready from day one