A 4-step absence coverage plan

The previous lesson set a weekly follow-up rhythm, but a rhythm that depends on one person being present breaks at the first holiday. Owners discover this late: a branch supervisor travels for a week, approvals pile up, a customer calls and nobody knows where their order stands, and work only moves again the day they return.

The problem is not the holiday, which is planned in advance. It is that work steps are tied to names instead of roles, so when the name is away the step goes with it. The fix is a coverage plan written before the absence, switched on with a date and off with a date.

Why one absence stops the work

• Approval sits with one person: the whole chain stops when they are away.
• The knowledge is in their head: details were never written down, so a colleague cannot finish the work even if willing.
• No named deputy: the team is told to manage, so everyone hesitates for fear of exceeding their authority.
• No end date: a permission granted verbally stays open long after its owner is back.

The four steps

1. List only the steps that actually stall

Do not cover everything the employee does, only the steps that block others. Ask one question per step: if it is not done today, is a customer, a supplier or an employee waiting? If not, defer it. In most small businesses the list is short: approving a purchase request, issuing an invoice, releasing stock, answering a customer enquiry.

2. Name one deputy per step

The deputy is a specific person by name, not a team and not whoever is available: a deputy shared between two people means each waits for the other. With two branches, pick the deputy from the same branch, because the person closest to the work understands it fastest.

3. Set the deputy's limit and what escalates to you

Coverage does not mean handing over full authority. Give the deputy a clear ceiling: an amount, a decision type, or a customer category. Anything above it escalates to you. That protects the deputy from an awkward decision and you from a surprise.

4. Switch coverage on with a start and an end date

The end date is the most important line in the plan. Coverage with no end turns into a permanent permission nobody intended, the riskiest thing to come out of a holiday. Set both dates in advance and let the system return the permission on the return day.

Coverage plan table

Step	Owner	Deputy	Deputy limit	Escalates to the owner
Approve purchase request	Purchasing officer	Warehouse officer	Up to SAR 5,000	Higher amount or a new supplier
Issue sales invoice	Accountant	Sales staff	Existing customers only	New customer or credit sale
Release stock	Storekeeper	Branch supervisor	Items in stock	Release that drops stock below the limit
Approve a discount	Sales manager	None	No authority	Every discount request

Note the last row: some steps have no deputy at all. Written down, that beats a deputy who decides without being authorised.

A WhatsApp scenario

The purchasing officer is away from 1 to 7 September. The owner sends one message to a system run from WhatsApp:

Enable purchasing coverage from 1 to 7 September, deputy is the warehouse supervisor, approval limit SAR 5,000

The system confirms: purchase approvals route to the deputy until 7 September, and anything above SAR 5,000 comes to you. When a SAR 8,200 request arrives during the holiday, the deputy does not approve it and it does not sit in limbo either: the owner gets a notice with the supplier, the amount and the reason, and one reply approves or defers it. On 8 September the permission returns to its owner without anyone asking.

The real benefit is the trail it leaves: who approved what, in which period, under which limit. The same applies to issuing invoices when the accountant is away.

Checklist before any absence

1. Have you listed the steps that stall without this person?
2. Does every step have a deputy named as an individual?
3. Does the deputy know their limit in writing?
4. Are the start and end dates set?
5. Do the team and affected customers know who to contact?
6. Do the permissions return automatically on the return day?

A common mistake

Writing the plan on the day the employee travels. A plan written under pressure forgets half the detail, and the deputy inherits a responsibility nobody walked them through. Write it once per role while the person is there, then switch it on when needed.