SOP and Handover Documentation Before December Leave Season: The October Window

The processes you must document before December leave season are the ones exactly one person can run: payroll submission, payment-run approval, GST and CPF filing, goods receipt and despatch, and customer order entry. For most Singapore SMEs that is eight to twelve procedures — not a hundred. October is the window to capture them, because by mid-November your team is inside peak despatch and Q4 close, and by December the person who holds the knowledge is either on leave or on a plane. A handover document written in the week someone leaves is a list of passwords. A handover document written in October is a working instruction someone else has already tested.

Why does December leave season hit Singapore SMEs harder than any other month?

Because the absences cluster, and they cluster on top of the heaviest operational month of the year. Employees covered by the Employment Act accrue annual leave — seven days in the first year, scaling with service — and most employment contracts expire unused carry-forward at the financial year end or shortly after. That creates a predictable December stampede: everyone with a balance takes it at once. Add school holidays, and add foreign staff taking extended home leave in the December–January stretch because Chinese New Year 2027 falls on 17 February and the cheaper window is earlier.

Now overlay what December actually demands of a small company. Black Friday and Christmas despatch are still running. The year-end stocktake has to happen. The December payment run is the largest of the year and the one most targeted by supplier bank-change fraud. CPF contributions are due by the 14th of the following month, and your Q4 GST F5 falls due at the end of January. None of those pause because the person who normally does them is in Penang.

The failure is rarely dramatic. It looks like an invoice batch that nobody transmitted, a supplier payment released without the second check because the usual approver was away, or three days lost while someone reverse-engineers a spreadsheet. Each is small. Together they are the reason January feels like archaeology.

Which processes actually need documenting before December?

Apply one test to everything your business does: if this person is unreachable for ten working days, does the process stop, or does it slow down? Only the ones that stop go on the list. Everything else can wait for a quieter quarter.

For a typical Singapore SME of fifteen to sixty staff, the list that fails the test looks like this:

• Payroll run and CPF submission — including the salary spreadsheet, the CPF EZPay steps, and who approves before release.
• Supplier payment run — bank access, approval limits, and the bank-detail verification step that prevents fraud.
• Customer invoicing and e-invoice transmission — raising, sending, and confirming it actually went out.
• Goods receipt and despatch — the physical and system steps, including how a short shipment is recorded.
• Order entry and order exceptions — what happens when a customer changes or cancels mid-fulfilment.
• Bank reconciliation and month-end close — the sequence, not just the destination.
• GST computation and F5 preparation — where the numbers come from and which adjustments are manual.
• Customer and supplier escalation contacts — who to call at each key account when something breaks.

Eight to twelve items. If your list runs past twenty, you are documenting preference rather than dependency.

What does a usable handover document actually contain?

Most SME SOPs fail because they describe the happy path in prose and omit everything a stand-in genuinely needs. A usable document has five parts, and it can be one page.

Trigger. What starts this process — a date, an email, a system alert. "Every Tuesday and Friday" is a trigger. "When needed" is not.

Access. Which system, which login, and how the stand-in gets in. Do not write passwords into the document. Reference the password manager entry and make sure the stand-in has been granted it before the leave starts, not on day one of it.

Steps, with screenshots. Numbered, in order, with a screenshot of each screen where a decision is made. Screenshots age, but a stale screenshot still beats a paragraph of description.

The exceptions. This is the part that is always missing and always needed. What does this person do when the file will not upload, when the figures do not tie, when a customer disputes a charge mid-run? Ask directly: "What goes wrong with this, and what do you do about it?" The answer is the most valuable content in the document.

Limits and escalation. What the stand-in may decide alone, what requires a call, and whose number to call. Explicit authority limits during December are also your best defence against approval-pressure fraud — if the rule says payments above a threshold need two approvals with no exceptions, an urgent-sounding message from a director on leave does not override it.

How do you produce twelve SOPs in October without stopping the business?

Do not ask staff to write them. Writing is slow, people resist it, and the output is usually a tidied-up version of what they think they should do rather than what they do.

Record instead. Sit with the person the next time they run the process, screen-record it, and have them narrate — including the bits they apologise for. A forty-minute payroll run produces a forty-minute recording and, from that, a one-page written procedure someone else drafts the same afternoon. The expert spends forty minutes, not four hours, which is why this method actually gets finished.

Run it as a schedule, not a project: two processes a week through October, the owner or one nominated person responsible for turning each recording into a page. Store all of them in one folder that the whole team can reach — a shared drive or your ERP's document area is fine; a folder on one laptop is not.

Then do the step most companies skip. In the first two weeks of November, have the stand-in run each process with the expert watching but not touching. Everything that person has to ask is a gap in the document. Fix it that day. A procedure that has been executed once by someone other than its author is a procedure; anything else is a hope.

How do you keep the documentation from going stale by March?

Attach maintenance to an event rather than a calendar reminder, which everyone ignores. Two rules are enough for a small company: the person who changes a process updates its page in the same week, and every SOP gets a quick review when it is next used by a stand-in. Put a last-reviewed date at the top of each page so anyone reading it can judge how much to trust it.

The longer-term payoff is that this list becomes the specification for automation. Once twelve critical processes are written down with their exceptions visible, you can see which ones are genuinely judgement-based and which are manual only because nobody has built the alternative. That is a far better basis for a 2027 systems budget than a vendor demonstration — and it is the same document set you will want when you onboard your next hire, defend a grant application, or finally replace the spreadsheet that three people are afraid to touch.

October is quiet by the standards of what follows. It is the last month this year in which an afternoon can be spent on something that is not urgent, and it is the reason a December absence becomes an inconvenience instead of an outage.

Frequently asked questions

How long should each SOP be?

One page, or one short screen recording plus a half-page summary. If a procedure genuinely needs five pages, it is probably several procedures bundled together — split it. The test is whether a competent colleague who has never done the task can complete it from the document without calling the author. Length is not what determines that; the exceptions section is.

Should we buy SOP software for this?

Not for the first round. Shared documents in a folder your team already uses will carry eight to twelve procedures perfectly well, and buying a tool in October adds a selection-and-setup delay to a task with a hard deadline. Revisit tooling once you have fifty or more documented processes and version control has become a real problem — not before.

What if the person holding the knowledge is resistant to documenting it?

Usually that resistance is about job security, and it responds better to framing than to pressure. Present the exercise as protecting their leave — so their phone does not ring on holiday — rather than as replacing them. Recording rather than writing also helps, because it costs them forty minutes instead of an evening. If resistance persists after both, you have identified a business continuity risk that is larger than the documentation gap and worth addressing directly.