Business & Strategy
IT-BCP for System Outages: Manual Workarounds, Contact Methods, and Drills for Ransomware
Advanced | 4 whiteboard pages · Task board: 4 columns (4 parent tasks, 12 subtasks)
Advanced: Assumes you know the technical terms and methods, and the steps are only outlined. Work through it on your own, guided by decision criteria and points to check.
An IT-BCP is a business continuity plan for ransomware or a major failure that takes business systems offline for days or weeks. You decide ahead of time which work continues by hand or on paper, how to reach people, and who calls the restart, then rehearse it. The template splits outage-to-restart into phases and tabulates what continues, how, and what waits. To start, copy the top tasks from your disaster BCP's priority list, noting how long each can stop and whether paper can carry it. The board checks pitfalls (recovery left to IT so business units lack procedures, staff contacts only in the dead system, no paper forms, nobody to decide on halting shipping or accounting), noting what happens, how to check, and a fix for each. Workarounds are ranked by impact and ease, then rehearsed. Restoring systems is IT's or the vendor's job; this plan covers the business side. The board has four A4 pages, and the four-column task board has four parent tasks with three subtasks each.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
IT-BCP for System Outages
How to use (4 pages): ① Write purpose and assumptions, list the work to keep (boards①–⑤) → ② Set methods per phase and check pitfalls (boards⑥–⑩) → ③ Decide manual workarounds and rank by impact (boards⑪⑫) → ④ Practice, then set contact methods and restart criteria (boards⑬–⑮)
1/4 Choose the work to keep
① Purpose of this plan (start here)
- Why you are building it e.g. Keep shipping to key customers even if business systems are down for 3 weeks
- Scope e.g. Head office and the logistics center, from order receipt to shipping and payment checks
- Period and team e.g. Build it in 3 months with 4 business-unit managers and IT
② Work to keep (copy from the BCP priority list)
| Tolerable downtime | Continue by paper or hand? | Owner | Priority | |
|---|---|---|---|---|
| Orders | e.g. 1 day | e.g. Continue (can run by hand) | e.g. Sales manager | e.g. 1 |
| Shipping | e.g. 2 days | e.g. Continue, but only for key customers | e.g. Logistics manager | e.g. 1 |
| Payment checks | e.g. 1 week | e.g. Partly. Billing can wait, but payment checks are needed | e.g. Accounting manager | e.g. 3 |
| Inquiries | e.g. Half a day | e.g. Continue (can be taken by phone) | e.g. Help desk lead | e.g. 2 |
③ How many days down (assumption)
- e.g. Assume at least 3 days and up to 3 weeks
- e.g. Basis is IT's estimate of recovery time
- e.g. Switch to manual work on day 1 instead of waiting to see
④ What is unavailable (assumption)
- e.g. Core system, internal email, internal chat, and shared folders are down
- e.g. Office PCs are unusable. Phones and paper still work
- e.g. Data exchange with partners is also stopped
⑤ Who decides (pitfall: no one decides)
- What happens: e.g. Nobody can decide whether to halt or continue shipping, so half a day is lost
- How to check: e.g. See whether you can name, for each task in ②, who decides to stop or continue
- The fix: e.g. Logistics director for shipping, finance director for accounting, with the next person named for absences
2/4 Map the time after the stop
⑥ Map the tasks in ② as a timeline from the stop to restart
- Start (the stop) e.g. In the morning the order system will not open. IT says to stop using it
- Phase 1 (day 1) e.g. Switch to manual work under the assumptions in ③ and ④, and the decider in ⑤ decides whether to keep shipping
- Phase 2 (days 2-3) e.g. Take orders on paper forms and limit shipping to key customers
- Phase 3 (days 4-7) e.g. Tell partners that billing will wait, and collect paper records in one place
- Phase 4 (week 2 onward) e.g. Confirm with IT the restore date and the data point in time
- Goal (restart) e.g. Once the criteria in ⑮ are met, re-enter the paper records and return to normal
⑦ Decide the work and method for each phase of ⑥
| Work that continues | Method | Work that waits | |
|---|---|---|---|
| Day 1 | e.g. Orders and inquiries | e.g. Take them by phone only and promise no delivery dates on the spot | e.g. New quotes |
| Days 2-3 | e.g. Shipping to key customers | e.g. Ship only items in stock and phone about shortages | e.g. Small shipments |
| Days 4-7 | e.g. Shipping overall and payment checks | e.g. Check only large payments daily | e.g. Issuing month-end invoices |
| Week 2 onward | e.g. Billing | e.g. Make invoices by hand from the paper records | e.g. Stocktaking |
⑧ Pitfall: leaving recovery to IT
- What happens: e.g. The systems come back, but business units have no procedures and cannot tell which orders came in during the 3 days of downtime
- How to check: e.g. See whether the owners in ② and the staff in ⑪ are business-unit people
- The fix: e.g. Business-unit managers write the workarounds, and IT owns the restoration steps
⑨ Pitfall: contact list inside the dead system
- What happens: e.g. Staff contacts exist only in internal systems, so no one can be reached on a holiday
- How to check: e.g. See whether you can trace everyone in ⑭ without using an office PC
- The fix: e.g. Print the contact tree, have the owners keep it, and reprint it when people change
⑩ Pitfall: no paper forms ready
- What happens: e.g. Handwritten orders have different fields per person and cannot be re-entered later
- How to check: e.g. See whether the paper forms named in ⑦ are printed and in place
- The fix: e.g. Create order and shipping forms and keep 50 copies of each at every site
3/4 Decide the workarounds
⑪ Manual workarounds for the work that ⑦ continues
| Manual workaround | Items needed | Owner and deputy | Re-entry after restart | |
|---|---|---|---|---|
| Orders | e.g. Take orders by phone and write them on paper order forms | e.g. Printed order forms and customer list (in a locked cabinet) | e.g. Sales manager, deputy is a sales lead | e.g. Sales enters them within 2 days of restart |
| Shipping | e.g. Paper shipping instructions and handwritten waybills | e.g. Shipping instruction forms and product list | e.g. Logistics manager, deputy is a warehouse lead | e.g. Logistics enters them from the shipping copies |
| Payment checks | e.g. Match bank statements against a printed list | e.g. Printed list of unpaid invoices | e.g. Accounting manager, deputy is an accountant | e.g. Enter from the list marked as checked |
| Inquiries | e.g. Take calls and write on paper intake forms | e.g. Intake forms and printed answers to common questions | e.g. Help desk lead, deputy is sales | e.g. Enter only the unanswered items |
⑫ Rank the workarounds in ⑪ by impact and ease of doing them by hand
Vertical axis: Impact of the stop (higher = bigger) / Horizontal axis: Ease of a manual workaround (further right = easier)
- Act first (big impact, hard to replace) e.g. Shipping. Make the forms and product list first, and practice it first in ⑬
- Hand out forms (big impact, easy to replace) e.g. Orders. Print order forms and keep them in place, and it runs right away
- Decide to wait (small impact, hard to replace) e.g. Payment checks. Check only large payments and decide the rest waits until restart
- Keep one line (small impact, easy to replace) e.g. Ordering office supplies. Just decide to ask by phone
4/4 Practice and fix
⑬ Five steps to practice, starting with the top-left task in ⑫
- Decide Scope and date of the practice e.g. Practice the shipping workaround for 90 minutes on a Wednesday in the second week of next month
- Read through Walk through ⑥ and ⑦ in order at the table e.g. Owners read aloud from the morning of day 1 through week 2 and beyond
- Do it by hand Process one case on paper forms e.g. Ship one order using paper alone, from order form to shipping instruction
- Test contact Check that the methods in ⑭ connect e.g. Time how long it takes to reach 4 managers by phone using the paper phone tree
- Fix and share Fix the procedure with what you learned e.g. Fix the form where fields are missing and redistribute it to every site
⑭ Contact methods when systems are down (internal, partners, customers)
| Usual method | Method when down | Who contacts whom, in order | |
|---|---|---|---|
| Internal | e.g. Internal email and chat | e.g. Use the paper phone tree and call mobile phones | e.g. General affairs manager → each manager → staff |
| Partners | e.g. Ordering systems and email | e.g. Phone. Use the paper list for contact numbers | e.g. Purchasing manager contacts the 10 main partners |
| Customers | e.g. Website and email | e.g. Phone. Also post on any notice channel that runs apart from internal systems | e.g. Sales manager, starting with the main customers |
⑮ Criteria for deciding to restart
- Conditions for judging it safe to use e.g. IT or the vendor says it is safe to use, and the statement is on record
- How to check the data point in time e.g. For each task in ②, the owner confirms up to which date and time the data was restored
- Who decides to restart and how to switch back e.g. The president decides to restart, and the staff in ⑪ re-enter paper records within 3 days
Task board contents
Not started 16 items
Pick work to keep
On page 1, write the plan's purpose and assumptions, and tabulate the work that continues during an outage with an owner for each. The work chosen here feeds every later page. Press Ctrl+F (⌘F on Mac) and type “3/4” to jump to page 3.
Copy priority work
Open your disaster BCP's priority-work list (or a per-department work list), copy the top four tasks into the rows of board ②, and fill in only the column for how long each can stop. Leave the other columns blank for now.
Write assumptions
Write the purpose, scope, and team on board ①, and how many days systems stay down and what is unusable on ③ and ④. Ask IT for its estimate of recovery time; once the evidence note is filled in, this is done.
Name the decider
On board ⑤, name who decides to stop or continue each task, plus a deputy for absences. Done when nothing conflicts with the owner column on ②.
Map the outage
On page 2, split the time from the outage to restart into phases and decide what work continues in each. Also check the pitfalls against your own company.
Draw the timeline
In the six steps of board ⑥, write one or two lines on what happens and what to decide at each point, from noticing the outage to restart.
Plan each phase
In the table on board ⑦, write for each phase the work that continues, how, and the work that waits. Done when every task from ② appears in some row.
Check the pitfalls
For the three pitfalls on boards ⑧ to ⑩, write what would happen in your company and how to check, and give each fix an owner and a deadline.
Decide workarounds
On page 3, decide the manual substitute and the items needed for each task you chose to continue on ⑦, and set the order of preparation. The forms and lists made here are the tools for the practice on page 4.
List workarounds
In the table on board ⑪, write for each task the manual substitute, the items needed, who does it and the deputy, and how to re-enter data after restart. Done when no more than two cells are empty.
Prepare forms
Create and print the paper forms and lists in the needed-items column of board ⑪, and decide where they are kept. Keep customer and partner lists in a locked place.
Rank by impact
Place the tasks from ⑪ in the four quadrants of board ⑫, and decide to practice first with the top-left task.
Practice and fix
On page 4, test the workarounds in practice and decide contact methods and restart criteria. Redistribute procedures fixed by practice and track them in the Fixed and shared column of the task board.
Run one rehearsal
Practice the top-left task of ⑫ following the five steps of board ⑬. Done when you have listed at least three things to fix.
Set contact methods
In the table on board ⑭, write the contact method and order for staff, partners, and customers when systems are down, then print and distribute a paper phone tree.
Set restart rules
On board ⑮, write the conditions for judging systems safe to use, how to check the data point in time, and who decides to restart. Done once IT agrees.