Tripartite Guidelines on Flexible Work Arrangement (FWA) Requests: Employer Compliance Guide

Last reviewed: 12 September 2026

What the Tripartite Guidelines on FWA Requests Actually Require

The Tripartite Guidelines on Flexible Work Arrangement Requests (TG-FWAR) are not a law giving employees a right to work from home, compressed hours, or a part-time arrangement. They are a mandatory process standard: every employer in Singapore must have a proper way of receiving, considering and responding to a formal FWA request, and must be able to show that a request was genuinely assessed rather than dismissed out of hand. The distinction matters. An employee cannot force an employer to grant flexible work. What the employee can force is a fair hearing — a decision made on business grounds, delivered in writing, within a set window of time.

This puts FWA requests in a different category from Singapore’s broader, informal conversation about flexible work. Plenty of companies already let staff work from home on an ad hoc basis without anyone invoking these guidelines at all. TG-FWAR only switches on when a request is formal — and understanding that trigger point, covered below, is the first thing employers tend to get wrong when building their process.

Timeline: From Advisory Guidelines to Mandatory Compliance

Singapore has actually had guidance on flexible work arrangements since 2014, refreshed in 2017 — but both versions were aspirational, encouraging employers to consider FWAs without requiring a formal process. That changed after a Tripartite Workgroup on Flexible Work Arrangements, convened in September 2023 by the Ministry of Manpower, NTUC and SNEF, concluded that voluntary encouragement wasn’t shifting employer behaviour fast enough. The Workgroup’s report and the new TG-FWAR were jointly launched on 16 April 2024, with a lead-in period before the guidelines became mandatory on 1 December 2024.

Ms Gan Siow Huang, then Minister of State for Manpower, framed the shift around competitiveness rather than compliance: flexible work “can be beneficial for both employees and employers,” giving employers “a competitive advantage in talent attraction and retention.” NTUC’s Ms Yeo Wan Ling was more pointed about who actually needs the guidelines to work in practice, noting that access to FWAs “is often the main consideration for caregivers, women workers and senior workers when it comes to deciding to stay or return to the workforce.” That framing is worth remembering: TG-FWAR was built as a retention and participation tool first, and a compliance obligation second.

Who Can Request an FWA, and What Counts as “Formal”

Any employee who has completed probation — the duration of which is set by the employer’s own contract terms, not a fixed statutory period — is entitled to submit a formal FWA request. There’s no minimum tenure beyond clearing probation, no restriction to parents or caregivers, and no cap on how often someone can ask, though repeated requests in short succession are one of the few situations where an employer’s earlier decision becomes relevant context for a new one.

For employees whose request is about caring for an ageing parent, ElderSG (a sister site) has a family care coordinator to plan caregiving duties across the family.

The guidelines group FWAs into three broad types: flexi-place (working from home, a satellite office, or a hybrid split), flexi-time (staggered start and end times, compressed work weeks, flexi-hours) and flexi-load (part-time work, job sharing, or reduced workload arrangements, usually paired with a pay adjustment). What actually triggers TG-FWAR, though, isn’t the type of arrangement — it’s whether the request was made formally. An employee messaging their manager “can I work from home tomorrow, my kid’s unwell” is an informal, one-off ask that sits entirely outside these guidelines and is handled however the team normally handles it. A written request for a standing hybrid arrangement, submitted through whatever channel the company has designated, is formal, and starts the clock described below.

The Formal Request Process, Step by Step

If an employer has not set up its own submission process, TG-FWAR sets a fallback: the employee submits a written request that states the date of the request; the type of FWA requested, including expected frequency and duration; the reason for the request; and, where applicable, the intended start and end dates. Employers are expected to have communicated any procedural requirements — a specific form, an HR system, a named point of contact — to staff in advance. If a company process exists, employees are expected to follow it rather than default to the bare minimum above.

In practice, this means the single highest-leverage thing an employer can do under TG-FWAR is publish a one-page internal FWA policy before anyone asks for one: who receives requests, what information is needed, how long a decision takes, and who signs off. Building that process reactively, after the first request lands on a line manager’s desk with no template to follow, is how companies end up with the exact compliance gap TAFEP has already had to step in on — covered in the real case below.

Employer Obligations: Consider Seriously, Not Rubber-Stamp

TG-FWAR is explicit that “considering” a request means more than reading it and saying no. Employers are expected to evaluate each request on its own facts and, where reasonably practical, explore ways to accommodate it — reviewing existing work processes, redistributing tasks among a team, or trialling an arrangement for a fixed period before making it permanent. A manager who rejects every FWA request using the same boilerplate reason, without engaging with what the specific employee is asking for, has not met this bar even if the final answer might have been justified with proper reasoning.

This is also where TG-FWAR quietly overlaps with the Workplace Fairness Act. A pattern of FWA rejections that consistently falls along one protected characteristic — for instance, systematically refusing caregiving-related requests from women returning from maternity leave while approving similar requests from other staff — risks becoming a discrimination complaint under WFA rather than a simple process complaint under TG-FWAR. See our Workplace Fairness Act employer guide for how the two regimes interact.

Valid vs Invalid Grounds for Rejection

Employers are not required to approve every request, and TG-FWAR does not pretend otherwise. The guidelines set out categories of legitimate business grounds for saying no, alongside grounds that TAFEP and MOM consider unacceptable on their own.

Valid grounds for rejection	Not valid on their own
Significant increase in operating cost that isn’t reasonably absorbable	Management philosophy or company “culture” opposed to flexible work
Detriment to output, quality or ability to meet business demand	Tradition — “we’ve never done this before”
Genuine feasibility constraints in job design (the role requires physical presence, fixed shift coverage, or client-facing hours)	A supervisor’s personal preference for in-person oversight, unrelated to measurable performance
Inability to reorganise workload or cover among the team without harming service levels	Unsubstantiated assumptions about productivity loss with no attempt to test the arrangement

The practical test TAFEP applies is whether the employer can point to a specific, job-related reason tied to this request, rather than a general aversion to flexible work as a category. A rejection letter that says “not compatible with our current operating model” without explaining which part of the model conflicts with which part of the request will not hold up if the decision is ever queried.

The Two-Month Clock and Written Decision Requirement

Employers have up to two months from the date a formal request is received to respond in writing — by letter, email, or an HR system record, but not a verbal conversation alone. Faster turnaround is always fine and, for most straightforward requests, expected; two months is a ceiling for complex cases, not a target. If the decision is a rejection, the employer must state the reason and is encouraged to discuss possible alternatives with the employee rather than simply closing the request. If circumstances mean an arrangement can only be granted temporarily or on a trial basis, saying so in writing up front avoids disputes later about what was actually agreed.

Skipping the “in writing” step is a more common failure than employers expect, because it feels like the smaller, less consequential half of the obligation compared to the substance of the decision. It is not. As the real case below shows, it is currently the only documented reason any Singapore employer has been formally engaged by TAFEP over TG-FWAR at all.

FWA Requests vs Return-to-Office Mandates

A question that comes up constantly as more Singapore employers push return-to-office policies: does a company-wide RTO mandate override an individual’s right to make a formal FWA request? MOM has answered this directly, in a written parliamentary reply dated 12 January 2026, confirming that TG-FWAR “also applies to employees in firms where the default work arrangement is to be on-site.” In other words, announcing that the whole company is going back to five days in office does not exempt that company from considering an individual employee’s formal request for an exception. The default policy sets the starting point; it doesn’t end the conversation for someone who formally asks for something different.

For employers currently tightening in-office requirements, the practical implication is to keep the FWA request channel open and genuinely functioning even while the general policy is moving in the opposite direction. An RTO announcement is not, by itself, a valid ground under the table above for automatically rejecting every individual request that follows it — each one still needs its own assessment against the specific role and the specific reason given.

Real Case: The Verbal-Rejection Complaint TAFEP Resolved

Two things are worth knowing about how TG-FWAR has actually played out since December 2024, both from MOM’s own written parliamentary answers. First, in a reply dated 3 March 2025, MOM confirmed that employers and employees are not required to report FWA outcomes to the Ministry at all, so there is no centralised data on how many requests are made, approved or rejected nationally — a genuine gap for anyone trying to benchmark “normal” approval rates. Second, in a reply dated 26 September 2025, MOM disclosed that TAFEP had received exactly one formal complaint under TG-FWAR since it took effect. The complaint: an employee reported that their employer had communicated the outcome of their FWA request verbally instead of in writing, as the guidelines require.

TAFEP’s response was not a fine or a public censure. According to MOM’s own account, TAFEP “worked with the company to revise its processes to be in line with the TG-FWAR.” That is the entire enforcement action on record for this set of guidelines, more than a year after they became mandatory. It’s a small dataset, but it’s an instructive one: the one documented compliance failure in Singapore wasn’t about an employer refusing a reasonable request — it was about an employer getting the paperwork wrong on a decision that, for all the public record shows, may well have been substantively fine.

How “Educational, Not Punitive” Enforcement Actually Works

Unlike the Workplace Fairness Act, which carries statutory civil penalties once fully in force, or the Workplace Safety and Health Act, which carries criminal liability for serious breaches, TG-FWAR has no fine, no court, and no regulator with prosecutorial power behind it. MOM has said plainly that if TAFEP finds an employer has not properly assessed an FWA request, TAFEP “will guide the employer to comply” — full stop. There is currently no published escalation path for a company that ignores that guidance.

That doesn’t make the guidelines toothless in practice. An employer with no FWA process, or one that habitually rejects requests without documentation, is building exactly the kind of paper trail — or absence of one — that turns into a much more serious Workplace Fairness Act complaint the moment a rejection pattern lines up with age, caregiving status, sex or another protected characteristic. TG-FWAR is best treated as the compliance floor that keeps a company from ever reaching that harder conversation, not as a box that can be safely left unticked because the guidelines themselves are unenforced.

Building a Compliant FWA Process: An Employer Checklist

Most Singapore employers can close their entire TG-FWAR gap with a short, one-time setup:

• Publish a one-page internal FWA policy stating how to submit a request, what information is required, and who reviews it — don’t wait for the first request to improvise one.
• Assign a named owner (usually HR) responsible for tracking the two-month response window on every request, with a simple log or ticket so nothing is answered late by accident.
• Require every decision, approval or rejection, to be issued in writing — even if a manager also delivers the news verbally as a courtesy. Verbal-only communication is the one failure mode already on TAFEP’s record.
• For any rejection, document the specific business reason against the categories above, rather than a generic line. Keep that documentation on file.
• Brief line managers on the difference between a valid business ground and an invalid preference-based one, since most rejections happen at manager level before HR ever sees them.
• Review requests individually even during a company-wide return-to-office push — the default arrangement doesn’t excuse skipping the individual assessment.

For the law now governing discrimination in how these requests (and every other employment decision) get handled, see our Workplace Fairness Act employer guide. For the broader statutory framework FWA requests sit inside, see our Employment Act overview.