What Happens to Your Business If You’re Unavailable for a Week?

On Monday morning, your team can see there is a client delivery on Wednesday and a supplier order due Thursday. They cannot see what the client agreed to in your inbox, and the account used to approve the order sends its security prompts to your phone. You are unavailable for the whole week. The question for your continuity plan is what the team can actually do on Monday without hearing from you.

Start with a seven-day absence that begins unexpectedly. Treat the phone, personal inbox and your usual approval decisions as unavailable in the exercise. Set a practical target for the week. Staff and clients should know who to speak to, essential services should keep running at an agreed level, and decisions outside the cover person’s authority should have a clear route. A handover that works under those conditions can also help when you take an ordinary holiday.

Identify the work with a real deadline

1. Open a recent week’s calendar. Write down the work you did that somebody else depended on. Include approvals, short conversations, release decisions and commitments made in private messages.
2. Check what happens if each task waits. A routine proposal can often be rescheduled with a short message. A time-sensitive client obligation, critical supplier order or scheduled payroll needs closer attention. Check the actual terms and dates.
3. Set an operating level for the absence. Decide which services must continue, which can run at reduced capacity and which can pause. Identify who is affected by each change and who will tell them.
4. Give the urgent tasks owners. Name a first contact, backup and deadline. Ask them to describe the first action they would take and show that they can reach the instructions.

Focus on commitments and consequences. A founder running a consultancy might maintain one scheduled client presentation and pause new proposals. A founder who runs a small online shop might prioritise orders already accepted and support enquiries about existing deliveries. Look at the week your customers and suppliers are expecting. Their deadlines make it easier to distinguish a task that only feels urgent from one that has a tangible impact.

Put the calendar, current work and verified contacts in a work system the relevant people can reach. For each essential item, note what has been agreed, where the latest records live and what constitutes completion. “Send the revised estimate after Priya confirms quantities in the shared job record” gives a cover person somewhere to start. A task titled “Deal with estimate” leaves them guessing.

Set the limits of temporary authority

Write down what each person can decide, under what conditions and what to do beyond that scope. The client lead may be able to rearrange an ordinary meeting or send an approved status update. A material price change or new contract may need a different decision-maker. Confirm with your advisers, providers and existing agreements who can act where formal authority matters. Make the limits visible where the work happens.

Check financial and supplier arrangements before relying on them. Ask the bank, payroll provider or relevant system provider what authorised access and approvals are available. Review who can prepare an item, who can approve it and what happens if either is absent. If you cannot put cover in place, document the deadline, the service contact and the legitimate fallback, such as an agreed revised schedule. A list of intended permissions is useful once somebody has verified them in the system.

Prepare an activation message and a short handover

• Starting the arrangement. Agree who can put the cover plan into use, how they will reach the team and which channel carries current instructions.
• Staff and customers. Keep a short message ready that names a contact, says how to reach them and sets expectations for a next update. Share personal details about the absence only as appropriate.
• Suppliers and specialists. Save current details for urgent suppliers and the people who support your systems, premises or finance. Check whether they can speak to the named cover person.
• Decision record. Keep a simple log of what was agreed, who agreed it and when somebody next needs to act. Put customer or staff information in the appropriate protected system.

For a business with no staff, decide what you can pause quickly and what clients can do while you are away. Prepare a short message and an agreed route to send it, for instance through someone with a defined role and the relevant permitted access. A trusted contact might know whom to notify in a genuine emergency, while a professional provider may have a separate role. Confirm each arrangement beforehand. Keep the amount of information you share limited to what the person needs for the job.

Give each recipient the next step. “Maya is handling existing orders this week. Send questions about delivery to our support address and we will update you by Wednesday afternoon” is actionable. If you expect to miss a commitment, explain what you can confirm and when you will know more. Keep the next update in the handover log so someone else can deliver it if the first cover person becomes unavailable.

Make the second day easier than the first

Use the first morning to assign the existing deadlines and check for work that has arrived overnight. After that, set a brief daily check while you are away. The cover person can look at new work, confirm which deadlines are approaching and update the people waiting for answers. A short routine helps where enquiries come in through several channels or the person doing the cover is also doing their usual job.

Mark the point where the reduced schedule stops working. If the team can handle current orders but starts receiving more than it can ship, the cover person needs a defined response. Give them a threshold that reflects capacity, a way to tell customers about delays and an authorised route to pause new commitments if needed.

Test one day and plan the return

Give the cover person a test case from last week. Ask them to find the agreed customer scope, contact details and delivery status, then describe the decision they can make. Ask a second person to find the same information from the instructions. Use a dry run or approved test environment for any action that could trigger a payment, message, contract change or production update. Record what had to come from your memory or personal account.

Imagine the supplier asks for a change to payment details on day four. The cover person should be able to find the verification procedure and know which authorised person can decide whether to proceed. If the correct approver is unavailable, the procedure should say how to hold and escalate the request. Check this kind of exception in the exercise. A routine week may hide the decisions that most need written boundaries.

Plan a short hand-back. Ask for decisions made, commitments with upcoming deadlines, issues still open and temporary permissions to review. Confirm who owns each remaining action and when the ordinary arrangements resume. Then ask what nearly stopped the cover person getting their job done. Fix one dependency and run the same case again. The test is whether someone can show you where they found the information and which action they were authorised to take.