Key takeaways
- A recovery plan sets two targets for each system: how long it can be down and how much data you can afford to lose. Everything else follows from those.
- Phones come first. 67% of Americans let unknown calls go to voicemail[1], so an outage that silences your line loses callers you never see.
- Keep backups separate from the systems they protect, so ransomware or a flood cannot destroy both. Test a full restore at least once a year.
- Privacy law raises the stakes: CCPA statutory damages for a breach reach $799 per consumer per incident[2].
What a disaster recovery plan is for
A disaster recovery plan answers one question in advance: if we lose the office, the network or a key system tomorrow, how do we keep serving clients and meeting deadlines? The cause could be a hurricane, a burst pipe, a fire in the building, a long power cut, a failed server, a lost laptop or a ransomware attack. The plan should not depend on which one it is.
For a law firm, the stakes go beyond inconvenience. Lawyers have professional duties to keep client information confidential and to stay competent with the technology they use, and ABA Model Rule 1.6(c) asks lawyers to make reasonable efforts to prevent unauthorized access to client information. A firm that cannot reach its files during an outage may also miss a deadline, which is a malpractice problem as well as a client service one.
Set two targets for each system
Recovery planning uses two simple measures. The recovery time objective (RTO) is how long a system can be unavailable before the damage is serious. The recovery point objective (RPO) is how much recent data you could afford to lose, measured as time since the last good copy.
| System | Suggested recovery time | Suggested data loss limit | Why |
|---|---|---|---|
| Main phone number | Minutes | None (calls are live) | New callers and clients with deadlines cannot wait |
| A few hours | Minutes | Court notices and client instructions arrive by email | |
| Calendar and docket | A few hours | None if possible | A lost deadline entry is a malpractice risk |
| Document management | Same day | One hour or less | Drafting and filing depend on current versions |
| Billing and trust accounting | Two or three days | One day | Important but rarely minute-critical |
The targets drive the spending. A system that must be back in minutes needs a design that does not depend on the office at all, while one that can wait two days can rely on restoring from backup.
Phones: make the number independent of the building
The main number is the firm's front door, and it is the system most firms forget until it fails. Callers who reach a dead line or endless ringing rarely try again later. Pew found 80% of Americans say they do not generally answer calls from unknown numbers, 67% let them go to voicemail and check it, and only 14% ignore voicemails altogether[3][1][4]. People rely on voicemail and callbacks working; when your line is down, neither happens.
- Host the number with a cloud phone provider so it can ring on mobile apps, laptops or forwarded numbers, not only desk phones.
- Set an outage routing rule in advance: if the office line is unreachable, calls go to a named group of mobiles or to an outside answering service.
- Record an outage greeting now, approved by an attorney, so it can be switched on in one step.
- Keep the provider's account login, support number and porting PIN in the plan, stored somewhere you can reach without the office network.
- If you use outside or AI answering, make sure it does not depend on your office systems to work.
Data: backups that survive the disaster
Backups only help if they survive whatever destroyed the original. A backup drive on the same shelf as the server is lost in the same flood, and a backup that is always connected can be encrypted by the same ransomware.
Keep three copies
The live data plus two backups, on at least two different kinds of storage, with at least one copy off-site and one that cannot be changed or deleted for a set period.
Back up cloud services too
Hosted email and document systems protect against their own failures, not always against accidental deletion or a compromised account. Check what your provider keeps and for how long.
Encrypt everything
Backups contain the same confidential information as the originals and need the same protection, at rest and in transit.
Test restores
At least once a year, restore a full matter folder and a mailbox to a clean machine and time it. A backup you have never restored is a hope, not a plan.
Write down the order
Decide which systems to restore first, using the recovery targets, so nobody improvises under pressure.
Ransomware and data breaches
Ransomware is now a common cause of law firm outages, and it combines a recovery problem with a confidentiality problem. Attackers often copy data before encrypting it. ABA Formal Opinion 483 says lawyers have a duty to notify current clients of a data breach that affects their information, and state breach laws add notification duties of their own. In California, CCPA statutory damages for a breach run from $107 to $799 per consumer per incident, or actual damages if greater[2].
- Use multi-factor authentication on email, remote access and practice management systems.
- Keep an incident response contact list: IT support, your cyber insurer's hotline, outside breach counsel and your malpractice carrier.
- Disconnect affected machines but do not wipe them before forensic advice; evidence matters for notification decisions.
- Follow the separate steps in the data breach response plan for notification and regulators.
People: who does what
Plans fail when nobody knows who is in charge. Name roles, not just tasks, and give each a backup.
- Incident lead: usually the managing partner or office manager, who declares the plan active and makes the calls on closure and communication.
- Phones and communication: switches routing and greetings, posts website and listing updates and drafts client notices.
- Systems: works with IT support on restores, access and security.
- Deadlines: runs the docket report and checks every deadline in the next 30 days against court closures and extensions.
- Staff welfare: checks on every person and sets realistic expectations for remote work.
Remote work is the default recovery mode for most firms, so make sure it works before you need it. In 2025, 35% of employed Americans did some or all of their work at home on days they worked[5], but many law firm staff have never logged in from home. Test it.
Vendors and contracts
Most small firms rely on outside providers for phones, email, document storage, practice management and IT support. The recovery plan is only as strong as those contracts. Review each one before you need it.
- Where the data is stored, how often it is backed up, how long deleted items are kept and how quickly the provider will restore an account.
- What the provider's own outage plan is, and how it tells customers about incidents.
- Who at the firm is an account administrator, and whether at least two people can log in if one is unavailable.
- How to export all your data if you need to leave the provider, and in what format.
- Confidentiality and security terms that meet your professional duties, including how the provider handles a breach.
Keep a one-page vendor sheet in the plan with each provider's support number, account ID and administrator names. Store it somewhere you can reach from a phone without the office network.
Example: a small firm's test day
Example, with a fictional firm. A seven-person firm ran its first recovery test on a Friday afternoon. The office manager announced a pretend flood: nobody could enter the building or use the office network. Within ten minutes the phones were switched to the outage greeting and rang on staff mobile apps. One paralegal could not log in to the document system from home because her laptop had never been set up for remote access; that was fixed the following week. Restoring a test matter from the off-site backup took two hours, longer than the firm's same-day target allowed for, so it changed its backup service. The test cost one afternoon and found three gaps that would have hurt in a real outage.
Keep the plan alive
Review the plan each year and after every real incident. Update contact lists when staff change, re-test phone routing whenever the phone system changes, and restore from backup at least annually. Coastal firms should do the review before June, as part of hurricane season readiness. Everyone else can fold it into the year-end checklist, so the plan starts each year current.
Frequently asked questions
What is the difference between disaster recovery and business continuity?
Business continuity is the wider plan for keeping the firm working through a disruption. Disaster recovery is the part that restores systems and data. A small firm can combine both in one short document.
How often should a law firm test its backups?
Restore a full matter folder and a mailbox at least once a year, and after any change of backup service. Time the restore against your recovery targets.
Do we have to tell clients about a ransomware attack?
Often yes. ABA Formal Opinion 483 describes a duty to notify current clients of a breach affecting their information, and state laws add their own notice rules. Get breach counsel involved early.
What is the first thing to fix in most plans?
The phone number. Make sure it can ring outside the office, with an approved outage greeting ready, because callers who cannot reach you rarely try again.
References
Pew Research Center (2020). Most Americans don't answer cellphone calls from unknown numbers (opens in a new tab) โ
California Privacy Protection Agency (2025). Updated Monetary Thresholds in CCPA (opens in a new tab) โ
Pew Research Center (2020). Most Americans don't answer cellphone calls from unknown numbers (opens in a new tab) โ
Pew Research Center (2020). Most Americans don't answer cellphone calls from unknown numbers (opens in a new tab) โ
U.S. Bureau of Labor Statistics (2025). American Time Use Survey - 2025 Results (opens in a new tab) โ