top of page
Search

Your EoR platform has a beautiful dashboard. Has it ever sat across the table at a SEnA conciliation meeting?

Writer: Connie Barrientos-Carey
Connie Barrientos-Carey
Sep 27
2 min read


Because that's where PH labor disputes actually get decided — not in a compliance widget synced from a server in Singapore.

Here's the structural problem nobody puts in the pitch deck: global SaaS EoR platforms are built to manage employment remotely. But Philippine labor disputes are not remote events. They are physical, procedural, and local:

→ SEnA (RA 10396) mandatory conciliation-mediation requires an actual person in an actual room within 30 days of filing — not a support ticket.
 → NLRC proceedings run through regional arbitration branches (NCR, Region VII, Region XI, etc.), each with its own calendar, its own quirks, its own local counsel relationships.
 → DOLE compliance inspections under labor standards enforcement happen on-site, with physical documentation demanded on the spot — payslips, DTRs, contracts, remittance proof.
 → Twin-notice due process under Labor Code Arts. 294–299 has to be executed correctly and locally, or the whole termination unravels in arbitration.

A platform can automate contracts. It cannot automate showing up.
This is the gap the market doesn't talk about: providers sell compliance through narrative — clean UX, global branding, "compliance guaranteed" copy. But when DOLE or NLRC comes knocking, what actually gets produced is documentation, presence, and paper trail — not a login screen.

The market rewards the loudest provider. Inspections reward the most documented one.

Aleph doesn't run PH employment from abroad. We run it from Cebu, Manila, and Davao — the same regional jurisdictions where your disputes, if they ever happen, will actually be heard.

If your current EoR's answer to "what happens if this goes to NLRC" is a shrug or a support email, that's worth a conversation.




 
 
 

Comments

bottom of page