Blog
A One-Page Incident Plan You Can Actually Use
Most cyber-insurance applications ask whether you have a written plan for when something goes wrong. In our review of 13 public carrier applications (November 2026), 11 asked about a written incident-response plan, business-continuity plan or disaster-recovery plan, and 7 asked for an incident-response plan by that name. Several also asked when the plan was last tested.
At a company of 50 to 250 people, the plan usually falls into one of two traps. It's either a 40-page binder a consultant delivered years ago that nobody has opened since, or there's no document at all because "we'd just call the IT company."
Neither helps at 9 p.m. on a Saturday. The good news is that what does help fits on one page.
What the terms mean
- Incident-response plan: what you do when you discover an attack or a breach. Who gets called, who decides what, and in what order.
- Business-continuity plan: how you keep operating, or get back to operating, when systems are down.
- Disaster-recovery plan: the technical side of getting systems and data back, usually from backups.
The carriers don't need three separate binders from a company your size. They need evidence that you've thought it through, written it down and practiced it.
What carriers are really asking
Behind the checkbox, the underwriter wants to know whether, in the first hours of an incident, your company will:
- Know who's in charge.
- Reach your IT people and your insurer quickly.
- Avoid making things worse, for example by wiping evidence or paying a criminal before talking to the carrier.
- Communicate sensibly with staff and customers.
Markel asks whether your plan specifically covers ransomware and when you last exercised it. Cowbell asks for a plan that's "tested and in effect," with named responsibilities. Those details are the difference between a plan and a document.
Why calling the insurer early matters
Most cyber policies come with a breach-response process: a hotline, approved law firms (often called breach coaches), forensic investigators and negotiators. Many policies expect you to notify the carrier promptly and to use its approved vendors. If you hire your own firms first, some of those costs may not be covered.
Read your own policy for the specifics, but the habit is simple: the insurer's claim number belongs on page one, not buried in a filing cabinet.
The one-page plan
Here's the structure I'd use. When I ran IT at a company of about 200 people, the version that actually got used was short enough to tape inside a cabinet door and keep as a photo on several phones.
1. Who's in charge. One name, plus a backup. This person decides on shutting systems down, calling the insurer and bringing in outside help. In most companies our size, it's the owner, the CEO or the head of operations.
2. Who to call, with after-hours numbers.
- Your IT person or managed-service provider, with the emergency line, not the general helpdesk.
- Your cyber insurer's claim hotline and your policy number.
- Your insurance broker.
- Your attorney, if you have one you'd want involved.
- Your bank's fraud line, if money might be involved.
3. Who speaks for the company. One person handles communication with staff, customers and anyone outside. Everyone else refers questions to that person.
4. The first-hour rules.
- Don't turn off or wipe affected computers until IT says so. Disconnecting them from the network is usually better than powering them down, because powering down can destroy evidence.
- Don't pay anyone or contact the attacker. That's a decision for later, with the insurer and counsel involved.
- Don't email about the incident from an account that might be compromised. Use phones or a separate channel.
- Write down what happened and when, as you go.
5. How to reach each other if email and the network are down. Personal phone numbers for the key people, kept somewhere other than your company systems.
6. The date it was last updated and the date it was last practiced.
That's it. If you want more detail later, it can go in an appendix. The front page should be readable in two minutes by someone who's stressed.
Practice with a tabletop
A tabletop exercise is a meeting where you walk through a made-up incident and talk about what each person would do. It doesn't touch any real systems, and 30 to 60 minutes is enough.
Pick one scenario. A simple one is: "It's Monday at 7 a.m. Nobody can open email or the shared drive, and there's a ransom note on the screens." Then go around the table. Who gets the first call? Who calls the insurer? What do we tell staff at 8 a.m.? Which customers need to hear from us, and when?
You'll find gaps, such as a phone number nobody has or a decision nobody knows they own. That's the point. CISA publishes free tabletop exercise packages if you'd like a ready-made scenario.
Keep it alive
People change jobs, providers change and phone numbers change. Put a recurring reminder on the calendar to review the page every six months and run a short tabletop once a year. Write the dates on the page. When the application asks whether your plan was tested, you'll have a real answer.
What to do Monday morning
- Draft the one page: who's in charge (plus a backup), who to call with after-hours numbers, and who speaks for the company.
- Find your cyber policy's claim hotline and policy number and put them at the top.
- Add the first-hour rules: disconnect, don't wipe, don't pay, don't use possibly compromised email, and write things down.
- Print it and share it with the people named on it, and keep a copy off your company systems.
- Schedule a 30-minute tabletop this month, using "we can't open email or the shared drive" as the scenario, and write down the date you ran it.
If you'd like help pressure-testing your one page, that's part of Shorehelm's readiness assessment.