The December Cover Plan: Keeping a Singapore SME Running While Half the Team Is Away

A December cover plan is one page that names, for every task your business cannot skip, the person covering it, the access that person will need, and the point at which they must stop and call someone. Built in October it takes an afternoon. Left until 23 December it never gets built at all, and the business spends two weeks phoning people on holiday for passwords. The goal is narrow and practical: keep answering customers, keep shipping, keep collecting money, and make sure no single absent person can stop any of it.

This matters more in 2026 than usual. Christmas Day falls on Friday 25 December and New Year's Day on Friday 1 January 2027, giving two long weekends back to back. Expect most small teams to be running at half strength from roughly 18 December to 5 January.

What actually breaks when half a small team is away?

In a company of ten, almost every task sits with exactly one person. The failures are predictable and they are rarely glamorous:

• The inbox nobody owns. Enquiries, quotes and complaints land in a shared mailbox that one person normally watches. Two weeks of silence costs real orders in January.
• Payments that cannot be released. One authoriser on the bank account, and that person is in Japan. Suppliers go unpaid, and the ones on stop-credit hold your January deliveries.
• Statutory dates that do not take leave. CPF for December wages is due by 14 January 2027. GST and IRAS deadlines do not move because your finance person is away.
• The systems key. Nobody can reset a staff password, restore a deleted file or approve a software renewal because the only administrator is unreachable.
• Delivery and stock. Couriers, warehouses and overseas suppliers run their own holiday calendars. A cut-off you did not check becomes a customer you did not serve.

How do you find your single points of failure in one afternoon?

Do not start with an org chart. Start with the week. Sit down with your two or three most senior people and list everything the business did in the last normal working week that a customer, a regulator or a bank would notice if it stopped. Aim for twenty to thirty lines, not a hundred.

Against each line, write one name: the person who does it today. Then read down the list and circle every name that appears with no second name beside it. Those circles are your single points of failure. In most ten person companies you will find between four and eight, and two or three of them will surprise you.

Now cut the list hard. Ask of each circled task: if this does not happen for two weeks, what is the actual consequence? Tasks that merely create a backlog can wait. Tasks that lose money, break a legal deadline, or let a customer down need cover. You are usually left with five or six items. That is the plan.

Who should hold administrator access over the holidays?

Someone must, and it should be decided deliberately rather than discovered in a panic. Two principles keep this safe.

First, at least two people must be able to get in to each critical system: the bank, the accounting software, the email and file platform, the website and the phone or WhatsApp line. One is a hostage situation. Second, access is granted in that person's own name, not by sharing a password. Add them as a second administrator or a second bank authoriser, with their own login. Shared credentials leave you unable to tell afterwards who did what, which matters if anything goes wrong and matters again under the PDPA if personal data is involved.

Write down what you granted, to whom, and on what date, with a line saying when it will be removed. Mid January, remove it. Temporary access that is never withdrawn is how a small company ends up with six administrators and no idea why.

What should the handover document actually contain?

One page per person going away, written by that person, not by you. Four headings is enough:

1. What I do that cannot wait, with the deadline for each item and who is covering it.
2. What the cover person needs, meaning the specific systems, the specific accounts and anything they will not be able to find on their own.
3. Live matters, listing any customer, supplier or dispute currently in flight and where it stands.
4. Where to stop, which is the most important heading and the one everyone skips. State the limit plainly: approve up to a named amount, agree a discount up to a named percentage, and beyond that call the owner. Give the phone number of the person to call and say what counts as worth being called about.

Ask for these by the end of November. A handover written the afternoon before someone flies out is a list of things they remembered, not a list of things that matter.

How do you keep a thinly staffed December from becoming an expensive one?

Quiet offices are where small frauds and small errors succeed, because the person who would normally notice is away. Three cheap controls carry most of the weight.

Keep two pairs of eyes on money leaving the business. Whatever your approval rule is in November, it still applies in December, and a covering staff member should never be both the person who sets up a payment and the person who releases it. Treat any request that arrives with urgency attached as a reason to slow down rather than speed up, particularly anything about changed bank details or an unexpected invoice.

Before the break, confirm one thing you have probably never tested: that you can actually restore a file from backup. Not that the backup ran, but that a file comes back. Ten minutes in December is worth a great deal if January starts badly.

What does good look like on 2 January?

Nothing dramatic. The mailbox has been answered, payments went out on time, no deadline was missed, and nobody on leave was called. Spend thirty minutes reviewing what the cover people struggled with and what access you need to withdraw. Keep the page. Next December you will be editing it rather than writing it.

Frequently asked questions

We are only ten people and we all know each other's jobs. Do we really need this written down?

Knowing roughly what a colleague does is not the same as being able to do it under time pressure with the right login. The written page is mostly about two things informal knowledge never covers: access, and the limit of someone's authority to decide. Both are the things that stall work in December.

Can we just ask staff to stay reachable while on leave instead?

It is not a plan, because it depends on a person choosing to answer. It is also poor practice, and with flexible work and fairness obligations arriving in 2027 it is worth building the habit of covering absence properly rather than leaning on goodwill. Agree one emergency contact and one genuine escalation threshold, then respect it.

When is the right time to start?

Late October. You need leave dates confirmed, time to add a second bank authoriser, which takes some banks a week or two, and time for handover notes to be written without rush. Starting in December means your plan arrives after the problems do.