MTC: First Microsoft, Then the FAA Ground Stop—So What's Next, Given Everything Happens in Threes? 🚨 A Lawyer's Backup Plan for When Clio, Smokeball, or Your Practice Management System Goes Dark ⚖️
/Lawyers Need Backup Plans for Cloud Outages!
Last week gave lawyers two free lessons. Neither one cost us a client. The third one might. 😬
On Thursday, November 12, Microsoft 365 went down. Outlook, Teams, and Copilot stalled across the country. At the peak, Downdetector logged more than 130,000 Outlook problem reports in the United States, and the disruption stretched into Friday (Reuters). Microsoft later said the incident "was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change" (Deadline). It was not a cyberattack.
Then, on Friday afternoon, the Federal Aviation Administration ordered a nationwide ground stop. Travelers felt it at TSA checkpoints and departure boards. The failure, however, sat inside the FAA's air traffic control communications. Transportation Secretary Sean Duffy said a router being worked on during a copper wire upgrade began flooding other systems (BBC). The stop lasted more than four hours. More than 3,500 flights were canceled on Saturday alone (BBC). Homeland Security Secretary Markwayne Mullin could not rule out another outage (WUWM). Officials also said the two events were not connected (CNN).
Two unrelated failures. One common thread. A routine change to critical infrastructure took down systems that millions of people assumed would simply work. 🛫📧
Folk wisdom says everything happens in threes. I don't practice law by superstition. But I do plan for the third shoe to drop. For many of you, that third shoe is the cloud platform that holds your entire practice. It might be Clio, Smokeball, MyCase, PracticePanther, Filevine, or whichever practice management system runs your day. *Note that this editorial is not a criticism of any of these or other LPMs, just an example of what is out there.
The Hidden Dependency Problem 🔗
When Legal Technology Fails, Lawyers Need Resilience
I covered the immediate response in 🚨 Breaking News: Microsoft 365 Outage Update for Lawyers! and in my September post, BREAKING NEWS! Microsoft Outlook Outage: What Lawyers Need to Do When Microsoft 365 Email Fails. This editorial asks a bigger question. What happens when the system that holds your deadlines, contacts, trust records, and documents goes dark?
Here is the part many lawyers miss. Your practice management platform can stay "up" and still fail you. During the Microsoft outage, Smokeball's support hub warned that the disruption "may impact some areas of Smokeball, especially with emails" (Smokeball Support Hub). Smokeball's incident history also records an issue that was fixed only when "Amazon has resolved the issue" (Smokeball Status). That is not a criticism of Smokeball. It is a reminder that every cloud vendor rests on other vendors.
Ask yourself three questions:
Do you sign in to your practice management system with your Microsoft or Google account? If that login provider fails, can you still get in?
Does your calendar sync through Outlook? If the sync stalls, which calendar is the source of truth?
Does your backup system send its alerts by email? If email is what's down, who sees the alert?
A fallback that depends on the failed service is not a fallback. It is a second point of failure.
Picture an ordinary Tuesday. ⏰ You have a 10:00 a.m. hearing and a brief due at 5:00 p.m. Your practice management system will not load. The hearing notice, the judge's standing order, and opposing counsel's cell number all live inside it. Your client calls the main line and asks whether today's settlement conference is still on. You cannot see the calendar. You cannot open the file. You cannot send the client a secure message through the portal. None of this requires a hacker. It only requires one vendor's bad afternoon.
Solo practitioners feel this most. There is no IT department to call and no colleague with a printed docket. Small and mid-sized firms face a different problem. Everyone assumes someone else has the backup plan. In both settings, the fix is the same. Write the plan down, assign an owner, and test it before you need it.
What the ABA Model Rules Expect ⚖️
Protecting Law Firms from Practice Management Outages
The Model Rules do not require you to avoid the cloud. They require you to use it competently.
· Rule 1.1, Comment 8 asks lawyers to keep abreast of "the benefits and risks associated with relevant technology." Concentration risk is one of those risks.
· Rule 1.3 requires diligence. A missed deadline is still a missed deadline, even when the vendor caused the outage.
· Rule 1.4 requires reasonable client communication. Clients need to know how to reach you when your normal channels fail.
· Rule 1.6(c) requires reasonable efforts to prevent unauthorized disclosure. That rules out panicked workarounds, such as forwarding client files to a personal Gmail account. 🔒
· Rule 1.15 requires safekeeping of client property and complete trust account records. If your trust ledger lives only in the cloud, know how you would reconstruct it.
· Rules 5.1 and 5.3 make supervising lawyers responsible for reasonable measures. Your staff needs to know the plan, not just you.
ABA Formal Opinion 482 on lawyers' obligations after disasters is worth rereading too. It expects lawyers to plan for continued access to files and clients when ordinary systems fail. A ten-hour cloud outage is a small disaster. Treat it as a rehearsal.
🚨As always, check your own jurisdiction. Your state's adopted rules control.
Eight Backup Strategies for When Your Practice Management System Goes Dark 🛠️
Eight Ways Lawyers Can Prepare for System Failures
Map your dependencies. 🗺️ List every system your practice touches on a normal day. Note what each one relies on: login, email, calendar sync, payments, e-signature, and storage. My checklist in MTC: When Your Staff Leaves, Does Their Access Leave Too? 🔐 A SaaS Access Governance Checklist for Lawyers and Law Firms ⚖️ gives you a ready-made starting inventory.
Turn on your vendor's backup tools. 💾 Clio offers Data Escrow, which sends a weekly copy of your Clio information and documents to a secure location (Clio Help Center). Clio's standard CSV export, by contrast, covers structured data and not the document files themselves (SendtoCase). Smokeball offers a full data backup from its import/export settings (Clio Help Center). Whatever your platform, learn its export path now. Do not learn it during an outage. Third-party backup services exist as well. Vet any of them under Rules 1.6 and 5.3 before you connect them to client data.
Build an "outage go-bag." 🎒 Once a week, export the essentials: the next 30 days of deadlines and hearings, active client contacts, opposing counsel and clerk numbers, and current trust balances. Store them on an encrypted drive or in separate, firm-approved storage. Never keep the go-bag only inside the system it is meant to replace.
Follow the 3-2-1 rule. 🧮 Keep three copies of your data, on two types of media, with one copy offsite. I explained it in Help Prevent Your Law Office's Data Loss! and discussed it with Curtis Preston in 🎙️ Ep. 104: The Importance of Data Backup & Cybersecurity w/ Mr. Backup, Curtis Preston. Remember that sync is not backup. A sync tool will faithfully copy a deletion everywhere.
Keep a second docket. 📅 Mirror critical deadlines in a calendar that does not depend on your practice management sync. A printed weekly docket counts. Paper does not need a server.
Set up an independent communication channel. 📞 Decide in advance how clients, staff, and courts will reach you. Choose a channel that runs independently of the failed service, such as a firm phone line, a firm-approved texting tool, a website banner, or a voicemail greeting. Never disclose client information in a public notice.
Get status alerts by text. 📲 Clio, Smokeball, and Microsoft all publish status pages. If those alerts arrive only in Outlook, you will miss them when Outlook is the problem.
Review your contract and run a drill. 📑 Check your agreement for data export rights, incident notice, and service levels. I discussed those contract safety valves in MTC: Clio–Alexi Legal Tech Fight: What CRM Vendor Litigation Means for Your Law Firm, Client Data and ABA Model Rule Compliance ⚖️💻. Then run a 15-minute drill. Can your team reach a client, find a key document, and confirm tomorrow's deadline without your practice management system? If not, you have found your December project.
Don't Overcorrect 🧭
None of this means abandoning the cloud. Reputable cloud platforms are often more secure and resilient than the server closet many of us left behind. The lesson from the CrowdStrike meltdown, which I wrote about in Lessons Lawyers Can Learn from the Financial Impact of the Crowdstrike Software Error 💼💻, still holds. Technology fails. Professionals plan for it. My earlier tips in Maintaining Legal Operations During Internet Outages apply here as well.
So, What's Next? 🔮
Cloud Outages and the Lawyer’s Backup Plan
I don't know what the third outage will be. It could be your internet provider, a court e-filing system, a payment processor, or your practice management platform. I do know this. Lawyers who plan this week will barely notice it. Lawyers who don't may spend that day explaining a missed deadline. They may explain it to a client, a judge, or a bar counsel. None of those conversations is pleasant, and every one of them is avoidable.
Pick one strategy from this list and finish it before Friday. Next week, pick another. That is what competence under Rule 1.1 looks like in practice: small, steady, documented steps. ✅
Happy Lawyering!
Michael D.J. Eisenberg
MTC

