Incident response plan and tabletop
An incident response plan for the six common incidents, with who does what, who to tell and an exercise to rehearse it.
Ready to use. Buy it in your account: a one-time licence fee and a monthly fee, plus the AI it uses.
What it does
List your systems, your people and roles, your key contacts and the personal data you hold, and choose the incident to rehearse first. You get a plan for six common incidents (a hacked email account, payment or invoice fraud, a lost or stolen device, personal data sent to the wrong people, ransomware and a key service down), each with signs it has happened and steps with who does each, from your own people. We add three severity levels, who to tell for your country (in the UK the ICO, in the US each state's breach rules and the FBI's IC3), a decision log and a contact sheet from your own lines. You also get a message for staff, a notice for customers with placeholders, and a 60-minute tabletop exercise.
Who it is for
- Small firms with no written plan for when something goes wrong
- Businesses that hold customer, patient or payment data
- Owners whose insurer or clients ask for an incident plan
Quick start
- 01List your systems and peopleYour email, accounts software, devices and website, and who does what.
- 02Add your contactsIT support, insurer and bank, with their numbers.
- 03Choose the incident to rehearseThe exercise is written for it.
- 04Print it and rehearseKeep a printed copy, then run the exercise with your team.
What you give it
- Your systemsRequired, up to 25 lines
- Your systems, one per line, for example: Microsoft 365 email; Xero; 8 laptops.
- Your people and rolesRequired, up to 15 lines
- Your people and roles, one per line. Only these people are given steps.
- Key contactsOptional, up to 15 lines
- Key contacts with their numbers, one per line. They make up the contact sheet, word for word. Optional.
- Personal data you holdOptional, up to 400 characters
- The personal data you hold, so the plan covers it. Optional.
- The incident to rehearse firstRequired, choose one of 6
- The incident the tabletop exercise is written for.
- Anything elseOptional, up to 1,500 characters
- Anything else, such as cyber insurance or a past incident. Optional.
What you get
- Severity levels and roles
- Three levels with what each means, and an incident lead, deputy, technical contact and communications contact from your people.
- Six playbooks
- Signs it has happened and the steps, with who does each. Downloadable as a spreadsheet.
- Who to tell
- A checklist for your country: your bank, IT support, insurer, the data protection regulator and the police.
- Decision log and contact sheet
- The log's columns, and your people and contacts exactly as you gave them.
- Messages and exercise
- A message to staff, a notice for customers with placeholders, and a 60-minute tabletop exercise with a debrief.
- What to check
- Notes for you only: people not on your list, numbers you did not give, and anything stated as the law.
You can edit the result, then copy it, print it or download it as Word, Markdown, plain text or data. Every run is kept in your run history until you delete it.
An example
Fernside Accountants is a made-up business. Below is what was entered, then the tool's real result, unedited, made on 6 November 2026. Subscribe to run it with your own details.
What was entered
From Fernside Accountants’s Business profile
- What you sell
- Bookkeeping, payroll and year-end accounts for small firms in Leeds
- Your systems
- Microsoft 365 email
- Xero
- 8 laptops
- The shared drive
- Your people and roles
- Sam Patel: owner
- Priya Shah: practice manager
- Tom Reid: bookkeeper
- Key contacts
- BrightIT (IT support): 0113 496 0000
- Insurer's cyber incident line: 0800 765 4321
- Personal data you hold
Client names, bank details and payroll records
- The incident to rehearse first
Payment or invoice fraud
- Anything else
We have cyber insurance.
In your account this is a form you fill in, and the tool runs once you subscribe.
What the tool returned
Incident response plan
In short
This plan sets out who leads and who does what when something goes wrong at Fernside Accountants. It covers a hacked email account, payment or invoice fraud, a lost or stolen device, personal data going to the wrong people, ransomware and a key service being down. It also includes messages for staff and customers, a tabletop exercise on payment or invoice fraud, and how to keep the plan current.
How serious is it?
Level 1
Level: Level 1: minor
Means
One person or device affected, no personal data or money at risk, work carries on. Handle it within the day and note it in the log.
Level 2
Level: Level 2: serious
Means
Personal data, money or a key system may be affected, or several people are. Start the plan now, and the incident lead takes charge.
Level 3
Level: Level 3: critical
Means
Personal data has been exposed, money has been lost, or the business cannot work. Start the plan now, call outside help, and check what must be reported.
Who does what
Role 1
Role: Incident lead
Person: Sam Patel
What they do: Takes charge of the incident, makes the key decisions, and makes sure each decision is written in the decision log.
Role 2
Role: Deputy
Person: Priya Shah
What they do: Stands in for Sam Patel when they are unavailable and keeps the decision log and notification checklist up to date.
Role 3
Role: Technical contact
Person: Tom Reid
What they do: Works with BrightIT (IT support) to contain and fix the problem, and keeps a record of what is found and changed.
Role 4
Role: Communications
Person: Priya Shah
What they do: Tells staff, clients and others what they need to know, using only wording agreed with Sam Patel.
Playbooks
Playbook 1
Incident: A hacked email account
How you would know
- Colleagues or clients receive emails they did not send from a Fernside Accountants account
- Sent items or mailbox rules the account owner does not recognise
- Unexpected password reset or sign-in alerts on Microsoft 365
What to do
Step 1
Step
Ask the account owner to stop using the account, then contact BrightIT to reset the password, sign the account out everywhere and check for forwarding rules.
Who: Tom Reid
Step 2
Step: Keep evidence: screenshot the suspicious emails, rules and alerts, and do not delete anything. Start the decision log.
Who: Priya Shah
Step 3
Step: Decide how serious it is and whether to call the insurer's cyber incident line.
Who: Sam Patel
Step 4
Step: Check whether Xero or the shared drive were accessed with the same login, and change those passwords through BrightIT.
Who: Tom Reid
Step 5
Step: Warn staff, and contact affected clients using the agreed wording. Check the notification checklist.
Who: Priya Shah
Step 6
Step: Review the log, confirm with BrightIT what was found, and record what to change to prevent a repeat.
Who: Sam Patel
Playbook 2
Incident: Payment or invoice fraud
How you would know
- A client or supplier asks to change bank details, or an invoice arrives with details that differ from before
- Unusual urgency or pressure to pay quickly or keep a payment secret
- A payment in Xero or at the bank that nobody can account for
What to do
Step 1
Step
Stop any payment in progress and do not reply to the request. Check the request using contact details already on file, not those in the message.
Who: Tom Reid
Step 2
Step: If money has been sent, tell the bank straight away and ask what can be done. Tell Sam Patel at once.
Who: Sam Patel
Step 3
Step: Keep evidence: save the emails, invoices and Xero records unchanged, and start the decision log.
Who: Priya Shah
Step 4
Step: Ask BrightIT to check whether an email account was hacked, and treat it as a hacked email account if so.
Who: Tom Reid
Step 5
Step
Decide with the insurer's cyber incident line whether to report, and check the notification checklist, including the police.
Who: Sam Patel
Step 6
Step: Tell affected clients and staff using the agreed wording, then review how the request got through.
Who: Priya Shah
Playbook 3
Incident: A lost or stolen device
How you would know
- A laptop is missing, or left somewhere it should not be
- A colleague reports a laptop stolen or lost while travelling
- A device signs in or behaves unusually after being mislaid
What to do
Step 1
Step: Report the loss to Priya Shah straight away, noting when and where it was last seen.
Who: Tom Reid
Step 2
Step: Ask BrightIT to lock or wipe the laptop if possible and sign the user out of Microsoft 365, Xero and the shared drive.
Who: Tom Reid
Step 3
Step: Change the passwords the user had on the device.
Who: Tom Reid
Step 4
Step
Work out what client data was on the laptop, such as names, bank details or payroll records, and write it in the decision log.
Who: Priya Shah
Step 5
Step: Decide whether to report to the police and the insurer, and check the notification checklist.
Who: Sam Patel
Step 6
Step: Record the outcome, update the list of the 8 laptops, and review how devices are protected.
Who: Priya Shah
Playbook 4
Incident: Personal data sent or shown to the wrong people
How you would know
- An email, payroll file or document is sent to the wrong person
- A client or colleague reports seeing information that was not meant for them
- Shared drive access shows files open to people who should not see them
What to do
Step 1
Step: Stop further sharing: recall the email if possible and remove access to the file on the shared drive.
Who: Tom Reid
Step 2
Step: Note what was shared, with whom and when, and keep evidence without deleting it. Start the decision log.
Who: Priya Shah
Step 3
Step: Ask the wrong recipient to delete it and confirm in writing that they have done so.
Who: Priya Shah
Step 4
Step: Decide how serious it is, working out which client names, bank details or payroll records were involved.
Who: Sam Patel
Step 5
Step: Check the notification checklist and decide whether to tell the insurer and affected clients.
Who: Sam Patel
Step 6
Step: Tell affected clients using the customer notice, then review how it happened.
Who: Priya Shah
Playbook 5
Incident: Ransomware
How you would know
- Files cannot be opened or have strange new names or extensions
- A message on screen demands payment to restore files
- The shared drive or laptops suddenly stop working
What to do
Step 1
Step: Disconnect affected laptops from the network and Wi-Fi, but do not switch them off or wipe them. Tell Sam Patel.
Who: Tom Reid
Step 2
Step: Call BrightIT and the insurer's cyber incident line, and follow their advice. Start the decision log.
Who: Sam Patel
Step 3
Step: Keep evidence: photograph the ransom message and note which machines and folders are affected.
Who: Priya Shah
Step 4
Step: Decide about any ransom demand with the insurer, the police and legal advice. Nobody else should reply to the demand.
Who: Sam Patel
Step 5
Step: Work with BrightIT to check backups and what can be restored, and change passwords once it is safe.
Who: Tom Reid
Step 6
Step: Check the notification checklist and tell staff and clients using the agreed wording.
Who: Priya Shah
Playbook 6
Incident: A key service is down
How you would know
- Microsoft 365 email, Xero or the shared drive cannot be reached by several people
- Error messages that continue after restarting
- The provider reports a fault
What to do
Step 1
Step: Check whether it is one person or everyone, and check the provider's status page.
Who: Tom Reid
Step 2
Step: Contact BrightIT and the provider, and note the time and what was said in the decision log.
Who: Tom Reid
Step 3
Step: Decide which urgent work to do by other means, such as payroll deadlines, and who to tell.
Who: Sam Patel
Step 4
Step: Tell staff what to do and what not to do while the service is down.
Who: Priya Shah
Step 5
Step: Contact clients who are affected, using the agreed wording, and check the notification checklist.
Who: Priya Shah
Step 6
Step: When the service returns, check the data and record what happened and what to change.
Who: Tom Reid
Who to tell
- Your bank, straight away, if money has been sent or bank details may be known: ask them to stop or recall the payment.
- Your IT support or the provider of the affected system, to contain it and keep evidence.
- Your insurer's incident line, before you spend money on outside help: policies often say who to use.
- The Information Commissioner's Office (ICO), if personal data is involved: under UK GDPR a personal data breach that is likely to put people at risk must be reported within 72 hours of becoming aware of it. Check the ICO's guidance on what to report, and tell the people affected if the risk to them is high.
- The police, for fraud or cyber crime, through the national fraud and cyber crime reporting service.
- Any customer or partner whose contract asks you to tell them about incidents.
Decision log
Keep a log from the first minute, one line per decision, with these columns: Date and time, What we knew, What we decided, Who decided, Why.
Contact sheet
- Sam Patel: owner
- Priya Shah: practice manager
- Tom Reid: bookkeeper
- BrightIT (IT support): 0113 496 0000
- Insurer's cyber incident line: 0800 765 4321
Message to staff during an incident
Hi everyone, we are dealing with an incident and Sam Patel is leading. Please follow Priya Shah's instructions and do not use any device or account you have been told to stop using. Do not discuss the incident with clients, on social media or with anyone outside the firm. Send any enquiries to Priya Shah. Keep any suspicious emails or messages and do not delete them. If you notice anything unusual, tell Tom Reid straight away. We will update you as we can.
Notice to customers (fill in the brackets)
Dear [client name], we are writing to tell you about an incident at Fernside Accountants. [What happened]. This was discovered on [when]. The information involved was [what data]. [What we have done]. [What we will do next, and when you will hear from us]. In the meantime, please [what you should do, for example check your bank statements and be cautious of unexpected emails or requests to change payment details]. If you have any questions, please contact [contact name at Fernside Accountants]. We are sorry for the worry this may cause.
60-minute tabletop exercise
Incident: Payment or invoice fraud
Scenario
On a busy Friday, Tom Reid receives an email that appears to be from a long-standing client asking to change the bank details for next week's payroll payment. The message is urgent and asks Tom Reid not to call. The payment is due to go out through Xero that afternoon.
Steps
Step 1
Minute: Minute 0
What happens: Tom Reid notices the new bank details differ from those in Xero and the email wording feels slightly off.
Questions
- What should Tom Reid do before doing anything with the payment?
- How would you check the request using details you already hold?
Step 2
Minute: Minute 8
What happens
The client says they did not send the email. Meanwhile, a payment to the new details was already made earlier in the week for a different client.
Questions
- Who do you tell first, and how fast?
- What would you ask the bank to do?
- What evidence do you keep?
Step 3
Minute: Minute 15
What happens
BrightIT reports that a client's mailbox may have been used, and Fernside Accountants' own Microsoft 365 account also shows an odd sign-in.
Questions
- Which playbook do you also start?
- What does Tom Reid ask BrightIT to do?
Step 4
Minute: Minute 23
What happens: Sam Patel needs to decide whether to call the insurer's cyber incident line.
Questions
- Who decides, and what goes in the decision log?
- What does the notification checklist ask you to consider?
Step 5
Minute: Minute 30
What happens: Clients start to ask whether their bank details and payroll records are at risk.
Questions
- Who speaks to clients and what wording do they use?
- What must staff not say?
Step 6
Minute: Minute 38
What happens: The immediate situation is under control and the team is tidying up.
Questions
- What would you change in how bank detail requests are checked?
- Who updates the plan and contact sheet?
Debrief questions
- Debrief from minute 45: What worked well in the first hour?
- Where was it unclear who should act?
- Were the decisions written down as they were made?
- What do we need to change in our checks on payment requests?
- Which incident should we rehearse next?
Keeping the plan current
- Review this plan once a year and after any incident.
- Check the contact sheet, including BrightIT and the insurer's cyber incident line, and update any changes.
- Confirm the people in each role are still right, and update the deputy when staff change.
- Rehearse a different incident each time, such as ransomware or a lost laptop.
- Record changes and share the updated plan with all staff.
Only for you: not included when you copy, print or download
Check before relying on it
- Print the plan and the contact sheet, and keep a copy somewhere you can reach if your email and computers are down.
What the AI does
It does
- Writes the playbooks with your people
- Writes the staff message and customer notice
- Writes a tabletop exercise for the incident you choose
- Ignores instructions written into the notes
It does not
- Respond to an incident for you
- Give legal advice on what you must report
- Advise whether to pay a ransom
- Know about systems or people you did not list
Please check itCheck every step's owner and the contact sheet, check the notification rules that apply to you, and print the plan.
Limits
- Your systems: up to 25 lines.
- Your people and roles: up to 15 lines.
- Key contacts: up to 15 lines.
- Personal data you hold: up to 400 characters.
- The incident to rehearse first: choose one of 6.
- Anything else: up to 1,500 characters.
- Up to 25 systems and 15 people a run.
- For backups and ransomware recovery, use Security and recovery plans.
- Your workspace's monthly cap: a run that would take you over it pauses, and carries on where it stopped when you raise the cap.
Your data
- What you enter, the files you choose and the result are stored encrypted with your workspace's own key. Only people in your workspace can open them.
- To produce the result, what you give the tool (and the parts of your Business profile it uses) is sent to our AI provider, Anthropic. It uses it only to answer, and its terms do not allow it to train its models on it. We do not train on it either.
- Files you upload are deleted after 30 days unless you choose to keep them. You can delete a run at any time: what you entered, the result and the progress notes go; only the usage record stays, because it is part of your billing.
- Our service is hosted in the United States.
The full details are in our privacy notice.
Questions
How are runs charged?
A one-time licence fee of $800 (£800 in the UK), then $200 a month (£150 in the UK), including any tax that applies. On top, you pay for the AI each run uses, billed each month with your invoice and never more than the monthly cap you set. From your fourth tool there is no licence fee.
Can I change the result?
Yes. Choose Edit this result to change any wording or figure, and Restore the original result to go back. Copy, print and downloads use your edited version.
Is it ready to use now?
Yes. Sign in, open Tools in your account and choose Get started for this tool.
How is this different from Security and recovery plans?
Security and recovery plans checks your backups and plans how to get your systems back. This plan covers six kinds of incident, who does what, who to tell and how to talk to staff and customers.
Does it tell me what the law requires?
It gives a standard checklist of who to tell for your country, such as the ICO's 72 hours for a reportable personal data breach in the UK. Check the rules that apply to you.
If something goes wrong
- A step is given to the wrong person.
- List each person with their role, one per line, then run it again or edit the result.
- The contact sheet is empty.
- Add your key contacts with their numbers, one per line.
Still stuck? Use the enquiry form and say which tool and what you saw.