Working the graveyard shift, and working alongside AI

Two realities reshaping the Philippines' BPO and healthcare workforce — what the law guarantees night-shift workers, and what it requires before a role can be automated away

Few industries test Philippine labor law the way BPO and healthcare do. Both run around the clock, both depend on people working hours the rest of the country sleeps through, and both are now facing a second disruption on top of the first: artificial intelligence quietly taking over tasks that used to require a full shift of human hands. This article covers two questions we hear constantly from workers in these sectors — what am I legally owed for working nights, and can I legally be let go because a machine can now do my job?

Night differential and health rights for night-shift workers

The mandatory 10% premium

Article 86 of the Labor Code entitles every covered private-sector employee to night shift differential (NSD) of at least 10% of their regular hourly wage for every hour worked between 10:00 PM and 6:00 AM. This applies to rank-and-file BPO agents, call center representatives, and healthcare staff working graveyard shifts, regardless of whether they're paid hourly, salaried, or on a compressed workweek. Work performed from 6:00 PM to 9:59 PM does not count as night shift for this purpose — the Labor Code's definition specifically begins at 10:00 PM.

NSD is a statutory benefit, not a bonus, which means it cannot be waived, reduced, or bargained away, even in a signed contract. Any clause attempting to eliminate or reduce it below the 10% minimum is void. Many BPO companies voluntarily pay 15% to 25% or more to attract talent for night shifts — and once a higher rate becomes established company practice, it generally cannot be unilaterally withdrawn under the non-diminution-of-benefits rule. NSD also stacks with other premiums: an employee working overtime, a holiday, or a rest day during night hours is entitled to those premiums calculated separately, then added on top of the night differential.

Employees generally excluded from NSD coverage are managerial employees and field personnel — the same categories excluded from overtime pay under the Labor Code.

Health rights, not just pay

The rationale for NSD itself acknowledges a health reality: night work disrupts sleep cycles, and the law intends the premium to help offset the associated health costs. But Philippine law doesn't stop at compensation — Republic Act No. 11058, the Occupational Safety and Health Standards Law, and its implementing rules impose concrete health and safety obligations on employers, with requirements that scale based on headcount at a single site:

• On-site medical personnel. A facility with more than 50 employees must have a registered nurse on site; facilities exceeding 200 employees must also retain a workplace physician and dentist.
• Safety officers and an approved OSH program. Covered workplaces must have a documented safety and health program, prepared in consultation with workers, and submitted to DOLE for approval.
• Health hazard policies. The required OSH program must include specific policies on HIV/AIDS, tuberculosis, and hepatitis prevention, alongside general workplace safety.
• Mandatory annual training. Employers must provide the required eight-hour annual OSH training under RA 11058.
• The right to refuse unsafe work. Workers are entitled to refuse work that presents an imminent danger to their life or health, without being penalized for the refusal.

DOLE inspectors actively check BPO sites for compliance with these standards, along with facility-level requirements like adequate restroom fixtures and rest areas scaled to a site's night-shift headcount. Non-compliance exposes employers to corrective orders, fines, and potential closure of the affected work area.

What this means in practice

For a night-shift worker, this combination of rules means two things run in parallel: your payslip should show NSD as a distinct line item on top of your base rate for every hour between 10 PM and 6 AM, and your workplace should have real, documented health infrastructure — not just a compensation policy, but an actual nurse, safety officer, and OSH program appropriate to the size of your site. If either is missing, both DOLE and the NLRC are available avenues: unpaid NSD is a straightforward money claim, while unsafe working conditions can be reported directly to DOLE for inspection.

Redundancy in the age of AI

Automation is a recognized, but regulated, ground for termination

Article 298 of the Labor Code lists redundancy and the installation of labor-saving devices as authorized causes for termination — meaning Philippine law has always contemplated that technology would eventually replace certain roles. Employers are legally permitted to restructure around AI. What the law does not permit is treating that right as a shortcut around proof and process.

The Supreme Court has been clear that redundancy doesn't require a company to be in financial distress; a role can be legitimately eliminated purely for efficiency, as the Court held in Asian Alcohol Corporation v. National Labor Relations Commission (G.R. No. 131108, March 25, 1999). But that same body of jurisprudence places the burden squarely on the employer to prove the redundancy is real. In Wiltshire File Co., Inc. v. National Labor Relations Commission (G.R. No. 82249, February 7, 1991), the Court held that a redundant position is one that has become superfluous — the services of an employee in excess of what is reasonably demanded by the actual requirements of the enterprise. And in Mejila v. Wrigley Philippines, Inc. (G.R. Nos. 199469 & 199505, September 11, 2019), the Court emphasized that a company must produce actual evidence, such as a new staffing pattern, feasibility studies, or a management-approved restructuring plan, rather than simply asserting the position is no longer needed.

The procedural requirements employers must follow

Whether a company is automating five roles or fifty, the same non-negotiable steps apply before AI can lawfully replace a position:

• 30-day written notice to both the affected employee and DOLE, before the intended termination date.
• Separation pay of at least one month's salary, or one month's pay per year of service, whichever is higher.
• Good faith in abolishing the position — the redundancy must genuinely eliminate the role, not simply relabel it to remove a particular individual.
• Fair and reasonable criteria for selecting which positions are declared redundant, applied consistently rather than arbitrarily.

What actually happens when the notice requirement is skipped

It's a common misconception that a missed 30-day notice automatically turns a redundancy into an illegal dismissal. It doesn't — not on its own. Philippine jurisprudence draws a sharper line between the substantive ground for the dismissal and the procedural steps taken to carry it out, and the two are not weighed the same way.

If the redundancy itself is genuine — backed by real evidence like a staffing plan or feasibility study — but the employer fails to give proper written notice to the employee and DOLE, the dismissal is not rendered illegal. The employee is not entitled to reinstatement or backwages on that basis alone. What the employer owes instead is nominal damages for violating the employee's right to procedural due process, on top of the separation pay already due for the redundancy itself.

Where the dismissal is for an authorized cause, the lack of statutory due process should not nullify the dismissal, or render it illegal, or ineffectual. However, the employer should indemnify the employee for the violation of his right to statutory due process.

This is the doctrine the Supreme Court set out in Jaka Food Processing Corporation v. Pacot (G.R. No. 151378, March 28, 2005), which specifically distinguished authorized-cause dismissals from just-cause dismissals for purposes of computing this indemnity — setting a higher nominal damage benchmark for authorized-cause procedural lapses (commonly ₱50,000) than for just-cause lapses, reasoning that an authorized cause originates from the employer's own initiative, not the employee's fault.

Mejila v. Wrigley Philippines, Inc., cited above, is a direct illustration of exactly this outcome. Wrigley's redundancy program — part of a headcount optimization and outsourcing initiative — was found genuine and well-supported. But the company's notice to DOLE had been sent to the wrong field office and never actually received. The Supreme Court upheld the redundancy as valid, and Mejila's dismissal was not declared illegal; she was instead awarded nominal damages and attorney's fees for the procedural defect alone.

The substantive ground still carries real weight, however. Where the employer cannot produce genuine evidence that the position was actually redundant — no staffing plan, no feasibility study, nothing beyond an assertion that "AI can now do this" — that failure goes to the substance of the dismissal itself, not merely its procedure, and can support a finding of illegal dismissal with the full remedies of reinstatement and backwages. The distinction that matters is this: a real redundancy with a missed notice costs the employer nominal damages; a fabricated or unsubstantiated redundancy, notice or no notice, costs the employer the case.

Building a redundancy file that actually holds up

Waiting for dedicated AI legislation misses the point: the bar an AI-driven redundancy has to clear already exists, and it's the same one Wiltshire and Mejila set decades before anyone was automating a BPO seat. What survives NLRC scrutiny today is a file built before the notice ever goes out — not after a complaint is filed. In practice, that means a documented "before automation vs. after automation" comparison of the specific role (not a department-wide assumption), a staffing study or cost-benefit analysis showing the tasks were actually absorbed by the system rather than quietly redistributed to remaining staff, and a paper trail showing the company at least considered redeployment or retraining before defaulting to termination. None of this is legally required by name — the Labor Code doesn't yet use the word "AI" — but it's precisely the kind of evidence that has always separated a genuine redundancy from a dressed-up one, and it happens to be exactly what pending legislation would soon require outright.

The industry is already leaning into "augmentation," not replacement

That last point matters because the BPO/IT-BPM sector isn't waiting for Congress either. Industry body IBPAP has publicly framed AI adoption around augmenting agents rather than displacing them, pairing that message with reskilling pipelines like Project UNLAD, a joint upskilling initiative between the industry, DICT, and TESDA aimed at moving workers into AI-assisted roles instead of out the door. There's real tension underneath that messaging — competitive pressure to cut costs runs directly against the reputational and regulatory cost of visible, unexplained layoffs — but the practical result is that companies who can point to a retraining or redeployment attempt before a redundancy tend to fare better on both fronts: legally, because it reinforces the good-faith requirement courts already look for, and reputationally, in an industry where "we automated and retrained" reads very differently from "we automated and fired." The direction of travel, whether driven by legislation, industry self-interest, or both, points the same way: retraining first is quickly becoming the default expectation, not the exception.

Practical guidance

For employers: Document the business case before you act — a staffing plan, cost analysis, or feasibility study showing the position is genuinely redundant, not just a memo. Apply your selection criteria consistently across similarly situated roles, and give the full 30-day notice to both the employee and DOLE regardless of how solid the substantive case is — a missed notice is a real, avoidable cost even when it isn't a fatal one. Where feasible, retraining and redeployment carry far less legal and reputational risk than abrupt displacement, and align with where both government policy and pending legislation are heading.

For employees: Redundancy due to automation is legal, but only when it's genuine. Keep your employment contract, performance reviews, and any communications about restructuring. A missed or defective DOLE notice is worth raising and can entitle you to nominal damages, but the stronger claim is challenging whether the redundancy was real at all — ask what evidence, if any, your employer can produce that your position was actually eliminated.

The bigger picture

Both issues covered here point to the same underlying principle: technology and business necessity don't suspend the Labor Code, they operate within it. A night shift doesn't just come with a pay premium — it comes with a legal obligation to protect the health of the people working it. And a company's right to automate doesn't come with a right to skip the proof the law requires before someone loses their job because of it — even if, as the jurisprudence shows, a paperwork misstep alone won't undo an otherwise genuine redundancy.

This article was prepared with the assistance of artificial intelligence and, while carefully reviewed, may contain inaccuracies; it does not constitute formal legal advice, and readers should consult a qualified attorney regarding their specific circumstances. Read our full firm caveat at the top of this hub.