Performance Review and AWS Cycle on a Spreadsheet: Fixing the October Appraisal Crunch

If your performance reviews, increments and AWS decisions all live in one spreadsheet that only the owner can open, the fix is not a better spreadsheet — it is a dated timetable and one durable record per employee that survives the December payroll run. For a Singapore SME with no HR manager, that means review forms closed by the end of October, increments and the bonus pool agreed by mid-November, and signed payroll instructions in the hands of whoever processes December pay before the run starts. The reason for that sequence is specific to Singapore: AWS and bonuses interact with the CPF Additional Wage ceiling, and any increment you promise takes effect on 1 January 2027 — the same month several wage costs step up anyway.

Why does the October appraisal cycle break down in a Singapore SME?

It breaks down because three different decisions are being made in the same file at the same time, by the same person, with no order between them. Performance rating, salary increment and variable bonus are separate judgements with separate money attached, but in a single spreadsheet they collapse into one column of numbers that the owner adjusts until the total looks affordable.

The predictable results, every year:

• Supervisors submit reviews late because nothing forces a date, so the owner writes them instead — for staff they do not work with daily.
• Increment percentages get set against a total payroll figure that does not yet include the January CPF and wage-floor step-ups, so the budget is wrong before it is approved.
• The bonus number is decided in a meeting and remembered differently by two people in February.
• Nobody can reconstruct, six months later, why one person got 3% and another got 8%.

That last point used to be merely awkward. With Singapore's workplace fairness legislation coming into force and grievance-handling expectations rising, an undocumented pay decision is a harder position to defend than it was three years ago.

What does a spreadsheet-run review cycle actually cost you?

Count the hours honestly. In a 25-person company, chasing review forms, consolidating them, rebuilding the increment model twice and transcribing final figures into payroll typically consumes two to three full owner-days in November — the same November that carries Black Friday despatch, the corporate tax filing deadline and supplier cut-offs before Chinese New Year.

The cash cost is quieter. Transcription errors between the decision file and the payroll system produce wrong AWS amounts, which produce wrong CPF, which produce an amendment and a refund request. And because the increment file is never reconciled against actual payroll after January, an approved 4% that was keyed as 4.5% for three people simply becomes the new baseline.

How is AWS different from a discretionary bonus, and why does that matter in December?

AWS — the Annual Wage Supplement, commonly the 13th month payment — is not a statutory entitlement in Singapore. It is payable if your employment contract, letter of appointment or a collective agreement provides for it. If it does, the terms bind you; if it does not, it is discretionary. Many SMEs have contracts promising AWS that the owner believes are discretionary, which is a conversation worth having with your contracts before November, not after.

For CPF, both AWS and a discretionary bonus are Additional Wages, and Additional Wages are subject to a ceiling calculated per employee per year: the annual CPF salary ceiling of $102,000 less the total Ordinary Wages already subject to CPF that year. With the Ordinary Wage ceiling at $8,000 a month from January 2026, a fully-capped employee has far less AW headroom than one on $4,000 a month. Practically, this means the CPF payable on an identical $8,000 bonus differs between two employees, and it cannot be worked out until you know their actual OW for the year. Confirm the current figures against the CPF Board's own tables before you compute — do not rely on last year's spreadsheet formula.

Timing matters too. Bonuses are taxable in the year they are paid or awarded, and they land in the IR8A you will submit in early 2027. A payment pushed from late December into early January moves tax years for the employee. Decide that deliberately rather than by accident of the payroll date.

What should the October-to-December timetable look like?

Put dates on it now and publish them. A workable shape for a December financial year-end company:

• Early October: issue review forms with a hard submission date. Two pages maximum — objectives, what happened, rating, supervisor recommendation.
• End October: forms closed. No form, no increment recommendation; the owner defaults it.
• First week November: build the increment model on next year's cost base, including January CPF and wage-floor changes and the effect of the retirement and re-employment ages moving to 64 and 69.
• Mid November: owner signs off the increment schedule and the bonus pool as one document, with a total payroll cost figure on the front page.
• Late November: conversations held with staff; letters issued stating the increment, its effective date, and the bonus amount.
• Early December: payroll instruction issued once, from the signed schedule, with AW ceiling checks per employee.
• January: reconcile the first payroll of 2027 line by line against the signed schedule.

That final reconciliation is the step almost everyone skips, and it is the cheapest control in the list.

What does good-enough documentation look like without an HR system?

You do not need an HRIS to fix this, but you do need to stop using a spreadsheet as the system of record. The minimum viable version: a shared form that writes each review into one row per employee per year, a single approved increment schedule stored as a dated PDF, and letters generated from that schedule rather than typed. Anything that lets two supervisors submit at once without emailing a file around is already an improvement.

If you are choosing tooling, check whether your existing payroll software already handles appraisals and increment letters — most SMEs pay for that module and never switch it on. That is also the cheapest thing to confirm during an October software licence review, before January repricing. And whatever you adopt, keep employee records and itemised payslips in line with the Employment Act; the review file should sit alongside them, not replace them.

The test of whether this worked is simple. In March 2027, can one person answer "why did this employee get this number" in under two minutes, without the owner? If yes, the cycle is a process. If no, it is still a spreadsheet.

Frequently asked questions

Is a Singapore SME legally required to pay AWS?
No. AWS is not a statutory entitlement. It is payable only if provided for in the employment contract, letter of appointment or an applicable collective agreement — in which case the stated terms apply. Read your actual contracts before deciding, and if you intend to vary a contractual AWS, take advice first.

Do we have to give employees a written performance review?
There is no general legal requirement for a written appraisal. There are requirements around key employment terms, itemised payslips and employee records. That said, a documented, consistently applied basis for pay decisions is the practical defence if a decision is ever challenged, and it is becoming more important as workplace fairness obligations take effect.

Can we just do the whole cycle inside our payroll or accounting system?
Often yes, and it is worth checking before buying anything new. The parts that must connect are the approved increment schedule, the letters issued to staff, and the payroll run itself. If one system holds all three with an audit trail, that beats three tools stitched together — and it removes the transcription step where most AWS and CPF errors are created.