When hiring speeds up, HR cannot slow down

A hiring spike is usually described from the front: how fast the roles get filled, how many candidates move through the pipeline, how quickly a shortlist turns into an offer. Filling several roles at once is a real problem on its own, and it is not this one.

This is about what happens behind the roles once they are filled. Every hire that lands adds to a set of obligations that do not scale with the hiring campaign, they scale with the person: a contract to issue, a CPF entry to get right, a pay slip to produce correctly, in some cases a work pass to wait for. A spike does not make any single one of these harder. It makes them happen five or ten times inside the same fortnight, on top of whatever a lean HR and payroll function was already carrying.

The person who feels this first is usually whoever was already running HR and payroll before the spike started, often alone or nearly so. Their steady-state workload does not pause while the hiring push runs. What changes is that a task they used to do once, correctly, for one new joiner every month or two, now needs doing correctly five times in a fortnight, on top of everything else on their desk.

Onboarding volume and Key Employment Terms

Key Employment Terms (KETs) must be issued in writing within 14 days of an employee’s first day of work, for staff covered under the Employment Act. That deadline runs from each employee’s own start date, not from the day the hiring push began or the day the whole cohort is meant to be settled in. Five people starting in the same week create five separate 14-day clocks, not one.

MOM’s stated approach to a first lapse is to engage and guide the employer to compliance within a month, and it can go on to impose an administrative penalty of up to S$400 for each repeated infringement. That is a lenient starting position for a one-off miss, and a considerably less comfortable one once a hiring spike has turned “we will get to it” into a pattern across several new hires at once. Our guide to itemised pay slips and KETs covers both obligations and the penalty regime behind them in full.

The same clock problem shows up in itemised pay slips, which must be given together with payment or, if that is not possible, within three working days of it. A payroll run built for a stable headcount produces this correctly every month without much thought. A payroll run absorbing several new joiners mid-cycle, each needing a first pay slip calculated from a partial month, is exactly the kind of month this deadline gets missed in.

Every new file created in that fortnight also has to be kept, not just issued. MOM requires an employer to keep the latest two years of employment records for a current employee, and the last two years of records for a former employee, for one year after they leave. A hiring spike does not shorten that clock either; it just creates several new files that need to be right from day one, because a record fixed months later is a record fixed under scrutiny rather than as routine filing.

Payroll headcount jumping mid-cycle

CPF contributions are still due on the last day of the calendar month, for every employee on the books that month, however late in the month they joined. A wave of new joiners does not create a new deadline; it adds more rows to the same one, each needing the correct entry: age band, citizenship, and for a Permanent Resident in their first two years, the right PR year and rate type. Get one wrong and it is rarely one error, it is the same error repeated across everyone hired in the same batch. Our guide to submitting CPF contributions covers the monthly mechanics, and the CPF contribution rates page carries the current age-band table.

Two obligations tend to arrive quietly with volume rather than with any single hire. The Skills Development Levy is payable for every employee working in Singapore, foreign hires included, and CPF EZPay will not calculate it for them automatically the way it does for Citizens and Permanent Residents, so someone has to key it in by hand for each one. And the Auto-Inclusion Scheme becomes compulsory the moment an employer reaches five employees in the year, counted across the whole calendar year rather than at one point in it. A small employer that was never close to that threshold before the spike can cross it mid-year without anyone deciding to, and stays inside the scheme even if headcount later eases back down.

The payment side of payroll is sized for a stable headcount too, not just the calculation side. A bank file that has run the same names for a year suddenly needs several new sets of account details keyed correctly, and a bank’s own daily transfer limit was set with the old headcount in mind, not the new one. Neither of those is a CPF or IRAS rule, but both sit on the same critical path as the ones that are, and a payment that fails at the bank on payday is no less late for being the bank’s limit rather than a statutory one.

Work-pass timelines that gate the start date

If any part of the spike is a foreign hire, the pass, not the offer letter, sets the start date. MOM processes online Employment Pass and S Pass applications from Singapore-registered employers, or gives an update, within 10 business days, though some cases take longer. Employers without a Singapore registration wait considerably longer: around six weeks for an Employment Pass, eight weeks for an S Pass, a timeline that applies to a company registering its Singapore presence, not a route around needing one: the pass still has to be sponsored by a Singapore-based employer. Where the Fair Consideration Framework applies to the role, it also has to be advertised on MyCareersFuture for at least 14 consecutive days before an offer can be made, which has to be planned into the timeline rather than discovered at the end of it.

None of this compresses because five roles need filling instead of one. Assessing likely eligibility before an offer goes out, so it is not built on a pass that was never realistic, is worth doing for the first foreign hire in a spike and every one after it.

What gets skipped under pressure

The obligations above rarely fail because someone decides to ignore them. They fail because a lean team runs out of hours in the same weeks that several of them land together. In practice, the same handful of things come under strain first:

• Key Employment Terms issued late, because several contracts are being drafted at once instead of one at a time.
• Itemised pay slips slipping past the three-working-day mark for a new joiner’s first, partial-month pay.
• CPF entries carrying the wrong age band or PR year, copied in a hurry from a template that fitted the last hire rather than this one.
• The Skills Development Levy left unkeyed for a foreign hire, because CPF EZPay never prompts for it the way it does for local staff.
• A start date promised before a work pass has actually been issued, because the offer moved faster than the application.

None of these is difficult on its own. Running the full sequence correctly, for every hire, in the same weeks the roles themselves are being filled, is the part that takes capacity a lean team rarely has spare. Running that sequence is the part of the work we take on.

Where Skillsforce fits

Filling the roles is one half of a hiring spike. The other half is keeping everything the roles touch, onboarding, contracts, payroll and work-pass timelines, running correctly while it happens. We handle HR operations and payroll processing for Singapore employers going through exactly this, including the parts above that fail quietly rather than loudly. If you would rather run it yourself, the deadlines and thresholds above are the ones worth putting on a calendar before the offers go out. Missing one rarely shows up in the week it happens. It shows up months later, in a filing that does not reconcile.