News & Events

The Plan Nobody Has Ever Read Out Loud: Tabletop Incident Response Exercises for Law Firms, Medical Practices, and Accounting Firms

A paralegal can’t open a document. Then a second person can’t. Then the shared drive stops responding.

Someone calls the IT helpdesk. Nobody can find the support number because the contract is in email. The managing partner asks the single most expensive question in the building: “Do we pay?”

And the room discovers it cannot answer four basic things: Who is in charge right now? Who calls the insurance carrier and broker? Which phone numbers still work if email and the phone system do not? Who is allowed to tell a client what happened?

The firm has a plan. It has never read the plan out loud, let alone rehearsed it.

That is the difference between a document and a muscle. A plan you have never rehearsed is a hypothesis.

Why this is a regulated-industry problem, not just an IT one

For certain financial institutions covered by the FTC Safeguards Rule, 16 CFR 314.4(h) requires a written incident response plan addressing seven areas: goals; internal response processes; clear roles and decision-making authority; internal and external communications; remediation of weaknesses; documentation and reporting; and evaluation and revision after an event.

Those seven elements can be present on paper. That does not tell you whether your firm can execute them at 2 p.m. on a Tuesday. And coverage depends on your organization and activities, not simply whether you call yourself a law firm, medical practice, or accounting firm.

For covered entities and business associates, the HIPAA Security Rule requires security incident procedures under 45 CFR 164.308. The notification rule at 45 CFR 164.404 generally requires individual notification without unreasonable delay and no later than 60 calendar days after discovery of a breach of unsecured protected health information. A tabletop can expose whether your team knows who assesses the facts and gets the right people involved before the clock becomes a surprise.

For law firms, ABA Formal Opinion 483 addresses lawyers’ obligations to take reasonable steps to prevent, detect, and respond to data breaches, including when clients must be informed.

These obligations are not interchangeable. Rules vary by industry, jurisdiction, state, and client facts. This article is general information, not legal advice. Confirm your requirements with qualified counsel and your insurance carrier.

A useful starting point is CISA’s free Tabletop Exercise Packages. For broader incident response guidance, see NIST SP 800-61 Rev. 3.

The plan is written. The people have not practiced.

The plan may have been written by one person: the MSP, perhaps, or an IT generalist who has since left. It may live on the file server or in the email system that is now unavailable. It may name roles instead of people. The person with authority may be on a plane.

It may assume email works.

The hardest gaps are often human, not technical. Who has authority to make a decision? Who is comfortable speaking to clients? Who knows which matters, patient records, or tax returns cannot wait? “Hey Margaret, do you have the carrier’s number?” is not a reliable response procedure.

A tabletop is a facilitated conversation around a realistic scenario. No systems are changed. No one needs to pretend to be a forensic investigator. The goal is to make decisions, surface uncertainty, and record what your firm needs to fix.

A tabletop is cheap. An incident is not. The exercise exists to find the arguments in a conference room instead of during a real event.

Medical practice administrator and clinic manager reviewing a response timeline in a clinic back office

The four questions a tabletop actually answers

1. Who decides? Name the person with authority, and name a backup who has real authority if that person is unreachable. “The managing partner” is a title, not a contingency.

2. Who calls whom? Identify the carrier, broker, cyber counsel, MSP, and key clients who may need contact. Agree on the order and who is responsible for each call.

3. What still works? If email and your business phone systems are down, what is the out-of-band path? Personal mobiles? A printed call sheet? A group text? A secondary number?

4. What hurts most? Identify the systems and matters, patient records, or tax returns you genuinely cannot operate without for a day, and what you could live without for a week. That distinction helps decision-makers prioritize.

How to run a 90-minute tabletop for a 20–80 person firm

Hand this list to your office manager. Keep it practical. Keep it moving.

  1. Choose one scenario. Avoid a broad “what if we get hacked?” discussion. Pick ransomware that encrypts the file server and practice or document management system; a business email compromise involving a redirected invoice; a departed employee’s mailbox still receiving client mail; a lost laptop with client files; or a breach at a vendor the firm depends on.

  2. Invite six to ten people. Include the managing partner, office manager, the person who handles the insurance relationship, billing or bookkeeping lead, and outside IT. Invite outside counsel only if your firm has one identified.

  3. Leave the slides and laptops behind. No vendor pitch. No opening the plan on a laptop. Bring a printed one-page plan only. The point is to test what people can do under the real conditions, not what they can find with email and shared files working.

  4. Use timed injects. Start at minute zero with a report: a staff member cannot open a file. At minute 15, introduce a second symptom. At minute 30, the carrier asks a question. At minute 45, a client calls demanding answers. Let the scenario develop in real time.

  5. Assign a scribe. One person records decisions made, questions nobody could answer, and who said what. This is not a transcript; it is a record of where the response depends on assumptions.

  6. Do not solve problems during the exercise. If the contact list is missing, note it. Don’t stop to create one. Fixing issues mid-scenario turns a rehearsal into a project and hides the findings.

  7. End with owners and dates. Write every gap down. Put a name and a due date beside each item.

  8. Repeat. Put an exercise on the calendar annually and repeat after a real event or major system change.

Accounting firm partner and staff reviewing printed checklists in a glass-walled meeting room

What the test often surfaces

These are the small failures that can make a written plan hard to use:

  1. The contact sheet is stored inside the system that went down.
  2. Nobody knows the carrier’s after-hours reporting number or policy number.
  3. The plan lists roles, not people, and the person with authority is unavailable.
  4. Nobody has agreed in advance who can decide whether to pay a ransom, shut down the network, or notify clients before the scope is understood.
  5. Email and the phone system are the same single point of failure.
  6. Nobody knows who can speak to clients, regulators, or the press.
  7. The plan has no timeline. A HIPAA notification deadline, state breach deadline, or client contract’s 24-hour notice clause appears as a surprise.
  8. A “temporary” workaround from a previous incident has quietly become permanent.
  9. Nobody knows whether the firm can operate on paper for a day.

The common thread is uncertainty. Your cybersecurity controls, endpoint security, email security, ransomware protection, and disaster recovery capabilities matter. But those tools cannot decide who speaks for the firm or which client call comes first.

What good looks like afterwards

A useful exercise leaves you with specific improvements, not just the feeling that the team had a good conversation. Your next version of the plan should include:

  • A one-page “first 60 minutes” sheet. Nobody wants to read a 40-page plan during a crisis.
  • Roles listed by name, with a named backup for each.
  • A contact sheet printed, stored offline, and updated quarterly. Include the carrier, broker, counsel, MSP, key vendors, and key clients.
  • One pre-agreed out-of-band communication channel.
  • A short decision framework for difficult questions, approved in advance by the people with authority.
  • A defined client spokesperson and clear, approved limits on what they can say.
  • Notification deadlines mapped to your obligations with counsel’s guidance.
  • An after-action report documenting what happened in the exercise and what needs attention.
  • An exercise cadence on the calendar, with an owner named beside it.

Insurers and examiners increasingly ask not only whether a plan exists, but whether it has been tested. A documented exercise and follow-up actions give you a clearer account of how the plan is maintained. They are not a guarantee of compliance or coverage.

Professional holding a printed emergency contact list beside a phone and notepad at a desk, with a closed laptop nearby

Run it internally or bring in an MSP? The trade-offs

An internal generalist knows your people and workflows. They may know which partner will lose their mind first. They can organize a small exercise without a procurement process.

But if they wrote the plan, they may be less likely to challenge its assumptions. They carry the same key-person risk the exercise may reveal. They may have limited perspective on what other firms have missed, and daily IT fires can crowd out time to schedule a rehearsal.

A managed services provider can bring an outside facilitator, scenario ideas informed by work across different environments, and a technical reality check: “That backup is listed, but has it been restored?” An MSP can also help document the exercise for your records.

There is a downside. An MSP can turn a tabletop into a sales pitch. Your firm can also mistake outsourced IT for outsourced accountability. The facilitator helps structure the exercise; your firm still owns the decisions.

The right approach depends on your people, time, and internal capability. Whether you run it yourself or bring in a facilitator, pair the exercise with the broader work of managed IT and business IT support. Your IT support for small business should help your team understand its systems, constraints, and practical options, not take decision-making authority away from leadership.

Final Word

The measure of readiness is not whether your firm has a plan. It is whether the right six people have sat in a room and discovered, in advance, that nobody had the carrier’s number.

For a law firm, medical practice, or accounting firm, that rehearsal is a practical part of law firm cybersecurity, medical practice IT, and accounting firm IT. It helps connect a written response to the people who must act, while highlighting where your existing business continuity arrangements may need attention. The details matter, especially for HIPAA compliance, FTC Safeguards, or GLBA compliance obligations.

If you are unsure where to start, a structured IT assessment can help you identify what your plan and systems need to account for. You can also contact A PC of Mind to discuss an assessment or tabletop exercise.