Flexible Work Requests: Does Your Written Response Trail Hold Up in 2027?

Under the Tripartite Guidelines on Flexible Work Arrangement Requests, in force since 1 December 2024, a Singapore employer must give a written response to a formal flexible work arrangement (FWA) request within two months of receiving it, and if the answer is no, the reason must be a business reason. That is the entire obligation in one sentence: reply, in writing, inside 60 days, with a reason you can defend. You are never required to say yes. You are required to have a process and to be able to show it. For an SME heading into the last weeks of 2026, the real exposure is not refusal. It is a request that arrives in the third week of peak trading, gets answered verbally beside the packing table, and leaves no record that anyone asked at all.

What do the guidelines actually require an employer to do?

These are tripartite guidelines rather than legislation, but they apply to all employers and they are the standard MOM and TAFEP will measure you against. The practical requirements are short:

• An employee who has completed probation may submit a formal request for a flexible work arrangement.
• You should discuss the request properly, in good faith, rather than simply filing it.
• You must respond in writing within two months of receiving the request.
• If you decline, you must state the business ground for declining.

FWAs fall into three families, and it helps to use the same words your staff do. Flexi-time changes when someone works, such as staggered start hours or shift swaps. Flexi-place changes where, usually some days at home. Flexi-load changes how much, such as a four-day week or part-time hours with pay adjusted accordingly. Most requests an SME receives are flexi-time, and most of those are cheaper to grant than owners expect.

Which conversations count as a formal request, and which do not?

A chat in the pantry is not a formal request. A request should be in writing and should say which arrangement is wanted, when it would start, how long it would run, how often it would apply, and why. If one of those is missing, you are entitled to ask for it, but you should ask in writing and say what is outstanding.

This is where most SMEs quietly fail. The employee believes they asked in September. The supervisor remembers a casual conversation. Two months pass, nothing is answered, and now there is a disagreement about a date that nobody recorded. The fix costs almost nothing: one intake channel, usually a single email address or a one-page form, a date stamp on arrival, and an acknowledgement within two working days. Once the date of receipt is recorded by you rather than argued about later, the two-month clock is something you control.

What counts as a valid business reason to say no?

Grounds that stand up are grounds tied to the work itself:

• Cost: the arrangement needs coverage, equipment or overtime you would have to add.
• Output: productivity or quality would measurably drop.
• Feasibility: the job genuinely cannot be done off site or outside those hours, which covers most warehouse, retail floor, workshop and delivery roles.
• Service levels: customers or clients need someone reachable in that window.

Grounds that do not stand up are the ones owners reach for first: it is not our practice, there is nothing about it in the handbook, everyone else will ask for the same thing, or a preference for seeing people at their desks. None of those describe a business impact, and none of them read well if the matter is ever reviewed by someone outside your company.

There is also a middle answer that is often the right one and is frequently forgotten. You can approve in part, approve for a trial period with a review date, or approve with a peak-season carve-out written into the terms. A documented partial yes is a legitimate response and usually ends the conversation better than a flat no.

Why does the written trail matter more than the decision?

Because if an employee raises the matter with TAFEP or MOM, the decision is rarely the problem. The missing record is. An employer who declined a request for a defensible reason and wrote it down has a complete answer. An employer who approved the request but never documented it has nothing, and cannot show that the request was handled at all.

There is a second reason that has nothing to do with regulators. Two similar requests answered differently, with no record of why, is how an ordinary staffing decision turns into a fairness complaint. A simple log, showing who asked, what they asked for, what was decided and on what ground, is the difference between a decision you can explain in one minute and an argument that runs for a month. Larger customers and government-linked buyers are also asking more questions about employment practices during vendor checks, and a one-page policy plus a log is usually all the evidence they want to see.

How do you handle a request that lands in the middle of peak season?

The two-month clock does not pause for December. A request received on 20 November is due a written answer by 20 January, which is precisely when your attention is on shipping, year-end closing and leave cover. Three moves keep this from slipping:

1. Name a decision maker and a backup now. Most missed deadlines are one person's inbox during two weeks of leave.
2. Answer the simple ones immediately. A staggered start time for one person on a two-person shift is usually a five-minute decision, not a committee matter.
3. Use dated trials. If you cannot assess an arrangement fairly during peak, approve a trial starting in mid-January with a stated review date and a stated measure of success. That is a real answer inside the window, and it is honest.

What should be written down before January?

Six items, and an afternoon is enough for all of them. A one-page FWA policy naming the request channel and the response timeline. A single intake address or form. A log with six columns: name, arrangement requested, date received, decision, date answered, reason. A named decision maker and a backup. Four short response templates: approve, approve with changes, approve as a trial, and decline with reason. Finally, a ten-minute briefing for supervisors with one instruction: you may discuss a request, you may not decline it on the spot.

None of this adds headcount or software. It converts an unbounded people risk into a two-line administrative routine, and it means the first request of 2027 is handled the same way as the fiftieth.

Frequently asked questions

Do we have to approve a flexible work request?

No. You must consider it properly and give a written response within two months, and if you decline you must give a business-based reason. A well-reasoned refusal, documented, is fully compliant with the guidelines.

What happens if we simply never reply?

The employee can raise it with TAFEP or MOM. There is no fine attached to the guidelines, but employers who disregard them can be required to attend corrective workshops and will have the matter on record. The larger cost is the time it consumes and the damage to trust inside a small team.

Can we trial an arrangement instead of committing permanently?

Yes, and for most SMEs this is the best answer. Approve a defined trial with a start date, a review date and a clear measure of what success looks like, then put all three in writing. If it does not work, you have evidence rather than an opinion.