Atlanta Dental Office Storm and Power Plan: Rain, Ice, Tornado Warnings and Summer Outages

Picture two offices after a weekend of tropical rain: one in McDonough lost the Monday to a server that crashed when the power went and roads it could not reopen around, while a colleague's office in Dunwoody was rescheduling patients from home by eight o'clock. The difference between them was a plan.

This page is the storm chapter of our Atlanta dental IT guide; Legend Networking's service page for practices in the metro is the one for IT support for dental offices in Atlanta. Much of what separates a lost day from a lost week is decided months earlier: whether the server was on a battery that could shut it down cleanly, whether a copy of the schedule and the charts existed somewhere the water could not reach, and whether anyone at home could log in and call patients. What follows works through those decisions for the weather metro Atlanta actually gets, using the National Weather Service's and Georgia Power's own dated records rather than a generic "storm" checklist.

What takes dental offices offline in Atlanta, from Marietta to Decatur?

Metro Atlanta offices go dark for more reasons than hurricanes: tropical rain that floods roads and drops trees on lines, summer thunderstorms, ice that coats wires, tornadoes that give little time to act, and snow that strands staff without touching the building. Each one fails something different, so each needs its own line in the office plan.

The National Weather Service forecast office in Peachtree City issues the metro's warnings, and its event write-ups, together with Georgia Power's releases, give a better picture of local risk than any national average. The table below describes each event in plain words, with the source and its date. Where a source covers all of Georgia, the description stays statewide.

Table 1: Metro Atlanta's outage record, by kind of event

Three things stand out. First, the 2014 snow and the 2008 tornado are not power stories at all: one stranded people, the other hit buildings. A plan written only around "the power goes out" misses both. Second, none of these sources promises a warning time, so the plan cannot assume one. Third, Georgia Power reported metro Atlanta restoration as largely completed a few days after Helene while it moved crews elsewhere in the state; your plan has to cover the days in between.

Why does an inland practice in Henry, DeKalb or south Fulton need a plan for tropical storms?

Because tropical systems reach Atlanta as rain, falling trees and flooded roads, not as storm surge. Helene came ashore in Florida, yet Georgia Power called it the most destructive hurricane in its history, and the metro lost power and roads with the rest of the state. An inland office needs the same plan, built around power, roads and water.

It is easy for an Atlanta owner to file hurricanes under "coast problems". Helene is the correction. By the time the storm crossed Georgia it was a rain and wind event, and much of the damage across the metro came from trees on lines and roofs.

For a dental office, that translates into three separate failures that can arrive together:

• • Power goes when trees come down on lines, and it may come back in a different order from the houses where your staff live.
• • Roads close with flooding and debris, so staff and patients cannot reach an office that may still have power.
• • The building can take water through the roof or at ground level, which turns a scheduling problem into an equipment problem.

What the utility's releases tell an owner is that a tropical system can keep crews busy across the whole state at once, for days. The practical answer is not a separate hurricane binder. It is making sure the rain-and-flood line of your plan (next section) is written with Helene in mind: the evening-before closure call, the offsite copy, and the ability to reschedule from home.

How should an Atlanta dental office plan differ for rain, wind, ice, a tornado warning or a gridlocked commute?

Write a short line for each event type rather than one generic storm procedure. For each, settle four things in advance: who makes the call, what gets shut down and when, what staff keep doing from home, and the first thing checked afterwards. Rain and ice usually give you an evening to decide; thunderstorms and tornadoes often do not.

Recovery planners talk about two targets. The recovery time objective is how long the practice can go without a system before it hurts; the recovery point objective is how much recent work you can afford to lose. You do not need the jargon to use the idea. For each system, ask: "How long can we be without this?" and "If we restore it, how old can the copy be?" Then make sure the answers match how often the backup actually runs.

Table 2: The first decisions, by kind of event

Two notes on that table. The tornado row is deliberately short. A warning is not the moment to save a server, and no plan should ask anyone to stay at a desk to do it. The commute row is the one most Atlanta offices skip, and January 2014 is the reason not to: the building was fine, the people were the problem.

A one-page version for the front desk

Print one sheet with five headings (rain, wind, ice, tornado, roads) and three lines under each: who calls it, what the front desk does, and the message patients hear. Add your electric utility's outage number, whether that is Georgia Power or a local cooperative. Keep a copy at the desk and a photo of it on every manager's phone.

Which equipment in a Smyrna or Sandy Springs office belongs on battery, and why does a self-healing grid not remove the need?

Put the server, network gear, phone system equipment and imaging computers on battery units that ride through short interruptions and shut down cleanly. Georgia Power describes a self-healing grid that restores many customers within seconds of a fault, and those seconds are still an outage to a server with no battery behind it.

Georgia Power's October 6, 2025 release, written a year after Helene, says its self-healing grid "isolates outages to the smallest area possible while automatically restoring power to as many as possible in seconds after an outage event occurs."

For an owner, that is good news with a footnote. A grid that reroutes power quickly shortens many outages. It does not make them painless for computers. A server writing to the practice database when the power drops can corrupt the database however brief the outage. That is the job of an uninterruptible power supply (UPS): a battery between the wall and the equipment that bridges short interruptions and, when an outage runs longer, tells the equipment to shut down properly.

What belongs on battery, in order of importance:

1. 1. The server (or the computer that holds the practice database, if you run Dentrix, Eaglesoft or Open Dental on a local machine). It needs a battery with a data connection to the server so the shutdown happens automatically.
2. 1. Network equipment: the firewall, main switch and internet modem. If these drop, cloud systems and remote access drop with them, even when the server survives.
3. 1. Phone system equipment that sits in the office, so the line does not go dead in the middle of a call.
4. 1. Imaging acquisition computers that sit beside sensors and pans, so an exposure in progress is not lost.

What does not belong on the same battery: printers, space heaters, and anything with a motor or a compressor. The battery is not there to keep the office open through an outage; it is there to survive the switch and to stop cleanly. How long any unit holds depends on its size, its age and what is plugged into it, so ask your IT provider to test it and write down the result for your office rather than relying on the box.

One more item is often forgotten: batteries wear out. A UPS that passed its test the year it was installed may not hold the server long enough to shut down today. Put the battery check on the same calendar as the rehearsal described below.

If imaging computers are the part of your office you worry about most after an outage, our guide to dental software and imaging support in Atlanta sets out the order for bringing the imaging server and operatory computers back up.

Where should an Atlanta dental office keep its offsite backup?

Somewhere a flood, a fallen tree or a tornado at your address cannot reach. The copy should include the imaging archive as well as the practice database, run often enough to match what you can afford to lose, and be proven by a real restore. Years of charts and X-rays depend on it, not just last week's work.

A storm does not pause your record-keeping duties, and a record that existed only on a server in a flooded office is a record you may no longer be able to produce. How long your practice must keep records is a question for your attorney or compliance advisor; the backup has to reach back at least that far.

Four tests for the offsite copy:

• • Distance. The copy is outside the building, and not on a drive someone takes home to a house a few miles away in the same storm.
• • Completeness. It includes the practice database and the imaging archive, not only the database. X-rays and scans are often the largest part of a record and the part most likely to be left behind.
• • Age. It runs often enough that the newest copy matches what you decided you could afford to lose (Table 2's "how old can the copy be?").
• • Proof. Someone has restored from it recently, and the result was checked, not assumed.

For how dental backups are built, see how dental backup solutions work, and for a full list to work through, the dental backup and disaster recovery checklist. Legend describes its own service under dental backup and disaster recovery services.

What should staff in Alpharetta, Duluth or Lawrenceville be able to do from home when the roads close?

At minimum: see the schedule, call or message patients, move appointments and update the phone greeting. Ideally, providers can also read charts and images. All of it has to be set up and tested on an ordinary day, with multi-factor sign-in, because nobody can install remote access during an ice storm.

January 2014 is the Atlanta case for this. A light snow left thousands of drivers stranded on metro roads for hours, by the Weather Service's account. An office that lost nothing that day could still lose the next two days if nobody could reach the schedule from home. The same is true for a Helene-type day, when the office may have power but the roads to it do not.

Plan remote work by role, not by "everyone gets access":

• • Front desk: the schedule, patient contact details and the phone system's settings, so they can reschedule and change the greeting. If your practice software is cloud-hosted, check that it still works when your office's internet is down (it usually does, from home). If it runs on a server in the office, remote access depends on that server and the office network being up, which is one more reason they belong on battery.
• • Providers: read access to charts and imaging for the patients they need to call back, through the same secure route.
• • Office manager: the ability to see whether the backup ran and whether the office systems are online, or a single number to call that can tell them.

Two security rules hold regardless of the weather. Remote access should require multi-factor sign-in, and it should run through a route your IT provider manages, not a remote-control app someone installed on a front-desk PC years ago. And treat any storm-day message asking for a password as suspect, whoever it claims to be from.

For how a managed plan in Atlanta handles remote access, the schedule and the imaging archive day to day, see managed IT for Atlanta dental practices.

What should a Kennesaw or Peachtree City office check before patients come back in?

Check the building, then the power, then the network, then the server and its last backup, then imaging, phones and the schedule, in that order. Each step depends on the one before. Write down what you found, so a problem that appears next week can be traced to the outage rather than guessed at.

Table 3: Reopening checks after an Atlanta outage

Imaging gets its own line because it fails quietly. A sensor computer can look normal and still fail to find its device, or point at a database location that has changed. Check one real image on each machine before the first patient who needs one, not at the moment you need it.

If water reached any equipment, stop at step 1. Equipment that has been wet should be inspected before it is powered on, and that is a conversation with your IT provider and, where it applies, your insurer.

What should your IT provider be doing while an Atlanta office is down?

It should tell you what it can see from outside your building, help you shut down and restart in the right order, confirm the backup, and arrange a visit if one is needed. Ask your provider exactly how each of those works for your office; the answers belong in your written plan, not in a phone call on the day.

Here is what Legend Networking publishes about itself:

• • 24/7 monitoring.
• • Helpdesk staffed 24/7 at 1-800-794-1588, one general number, so there is no second number to hunt for in a storm.
• • In-house engineers; no outsourced first-level triage.
• • Headquartered in Dallas.

What that does not mean is equally important to an owner writing a plan. This page does not promise how quickly anyone arrives or how long a restore takes, and no provider's marketing should be read that way. Those are questions to put to any provider, including Legend, in the list below. The one Georgia project Legend has documented publicly is the completed installation and opening of FLOSS Dental in Roswell, a technology installation rather than a storm recovery.

For Legend's own description of how it works with practices across the metro, see its page for dental IT support in Atlanta. Legend's published record: Served over 3,500 practices since 2004 · 22+ years in dental IT (since 2004) · 4.8 rating · 173 Google reviews.

How can an Atlanta dental practice rehearse its storm plan without closing for a day?

Run a short tabletop exercise once a year, using events that have actually happened in metro Atlanta, plus a real restore test from the offsite copy. Talk through each scenario as a team, note every point where nobody knew the answer, and fix those gaps before the season, not during it.

A tabletop exercise is a meeting, not a drill: the team sits together, someone reads a scenario, and everyone says what they would do. It takes an hour and it finds the gaps that a binder hides. Use scenarios built from Table 1 rather than generic ones:

1. 1. A late-June thunderstorm after closing. Power is out at the office overnight; most staff have power at home. Who finds out first? Who decides whether to open in the morning? Does the server's battery shut it down cleanly, and how would you know?
2. 1. An ice forecast for tomorrow. Who calls the closure, and by when? Who updates the phone greeting from home? Who reschedules, and can they reach the schedule?
3. 1. A tornado warning during a long procedure. Where do patients and staff shelter? Who is responsible for the patient in the chair? (Equipment is not on this list.)
4. 1. A Helene-type weekend. Rain is forecast for Thursday and Friday. Do you close Friday? Is the offsite copy current on Thursday evening? What if water is found on Monday?
5. 1. A gridlock afternoon. Light snow begins and the roads seize. What is the rule for sending people home? Who can work tomorrow, and from where?

Alongside the tabletop, do three practical checks:

• • Restore test. Ask your IT provider to restore a sample of records and images from the offsite copy and show you the result.
• • Battery test. Confirm each UPS still supports a clean shutdown, and replace the ones that do not.
• • Contact list. Update every phone number on the front-desk sheet, including staff, the utility, the IT provider and the vendors for your practice software and imaging.

Spring is a sensible time to hold it, ahead of summer thunderstorms and the tropical season, but any fixed date works better than "when we get to it."

What to ask your IT provider about storms and outages

Use these questions with your current provider or any provider you are considering. Good answers are specific to your office and come in writing.

Sources for the storm record on this page

Every weather and utility description on this page comes from the primary source with that source's date. Georgia Power's statewide statements are statewide and are not assigned to any town. All sources were accessed October 23, 2026.

• • National Weather Service Peachtree City/Atlanta: The Atlanta Tornado, March 14, 2008; January 28, 2014 winter storm; February 11–13, 2014 winter storm.
• • Georgia Power: September 30, 2024; October 6, 2025; late-June thunderstorms, release dated July 27, 2023; Winter Storm Fern, January 26, 2026.