Map what stops when the network stops
List the tasks that stop completely when the network stops, such as email, calendar, and the approval queue. A general continuity plan hides the specific work that matters at nine in the morning. Record each task and its normal system. The list should be built with the assistant, not for them.
Decide which tasks can continue on a mobile device and which need a desk and a wired connection. A phone that can read email cannot always sign a document. Record the fallback for each task. The plan should distinguish reading from acting.
Confirm how the executive will reach the office when the calendar and chat are down. A missed call is easier to recover than a missed board vote. Record the mobile number and the backup route. The plan should not depend on the same network for both.
Set a fallback for calendar changes, such as a shared text thread and one named coordinator. Two people editing a paper calendar creates conflicts the network never had. Record the coordinator and the thread. The rule should be short enough to remember.
Build the offline fallback before it is needed
Keep a printed page with the key contacts, the building numbers, and the provider support lines. A contact list stored only in the cloud is unavailable during the outage it is meant for. Record the page and where it is kept. The list should be refreshed each quarter.
Test the mobile hotspot and the backup device on a normal day. A hotspot that has never been used often fails when it is needed. Record the test date and the data limit. The test should include the executive's own laptop.
Ask the provider for the escalation path and the account reference before an outage. A support number without an account reference adds minutes to every call. Record the reference and the contact. The office should not search for it during an incident.
Tell the key counterparties, such as the board chair or the bank, how to reach the office during an outage. A counterparty that calls the main line reaches a voicemail box. Record the alternate number and the window. The notice should be sent before it is needed.
Brief the executive on what will and will not work in the first hour. An executive who assumes email is flowing will make promises the office cannot keep. Record the briefing and the fallback channel. The message should be short and specific.
Protect approvals and the signature process
Decide how the office will approve a payment or a contract when the workflow tool is offline. A verbal approval that is never recorded is hard to defend later. Record the fallback approver and the evidence to keep. The plan should protect the control, not only the deadline.
Protect the signature process by keeping the matrix and the register accessible offline. A signer who cannot see the limits may sign outside them. Record the offline copy and its location. The copy should be current before the outage starts.
Note any document that was signed, sent, or promised during the outage and confirm it later. An offline promise can be lost in the rush to catch up. Record the promise and the owner. The follow-up should be part of the recovery.
Record the decisions made offline as soon as the network returns. A decision that exists only in memory can be reversed by the next person who reads the thread. Record the decision, the time, and the approver. The record should be created the same day.
Check the systems that resumed automatically against the ones that need a manual restart. A calendar sync that resumes without checking can duplicate or delete events. Record the check and the correction. The recovery should be verified, not assumed.
Recover, record, and review the outage
Keep a short outage log with the start time, the affected tasks, the decisions, and the end time. A log written days later will miss the decisions that mattered. Record the entries during the event. The log should be usable in the next review.
Review the outage within a week and change one part of the plan. A plan that is only tested by the next outage will repeat the same failure. Record the finding and the owner. The change should be small enough to finish.
Tell the executive what changed after the review and why. A continuity plan that lives only with the assistant fails when the assistant is away. Record the briefing and the updated page. The executive should know the fallback before the next outage.
Store the plan, the contact page, and the outage log with the office continuity file. A plan that cannot be found during an incident is not a plan. Record the location and the review date. The next assistant should inherit a working routine.
Related resources
Read also: network outage readiness study and vendor contact map.
Frequently asked questions
Should one assistant support the whole executive team?
Sometimes. It works when priorities are clear and executives share one operating rhythm.
What should happen before a consult?
List the meetings, inbox rules, recurring reports, and decisions that need support.
Ready to define the role?
Use a recent leadership week to scope the support that would make the biggest difference. The consultation is a working conversation, not a generic pitch.
Book a consultation