Your Filipino remote worker misses standup. Again.<\/p>\n\n\n\n
No Slack message. No text. Radio silence.<\/p>\n\n\n\n
Is their internet down? Did they evacuate? Are they safe?<\/p>\n\n\n\n
Most managers don’t think about this until it happens. Then they’re scrambling, unsure if they should dock pay, how to track hours, or whether they’re even allowed to ask someone to work during a disaster.<\/p>\n\n\n\n
Let’s fix that.<\/p>\n\n\n\n
The Philippines gets hit with an average of 20 typhoons per year. That’s not counting earthquakes, volcanic activity, or the rotating blackouts that happen even on sunny days.<\/p>\n\n\n\n
Your remote team isn’t working from a cozy home office in the suburbs. They might be in:<\/p>\n\n\n\n
A coastal area that floods every monsoon season<\/p><\/li>
A province where internet goes out for days after a storm<\/p><\/li>
A neighborhood with scheduled power outages twice a week<\/p><\/li>
An apartment building that loses connection when it rains hard<\/p><\/li><\/ul>\n\n\n\n
This isn’t about being unprepared. It’s about living in one of the most disaster-prone countries on Earth.<\/p>\n\n\n\n
The National Disaster Risk Reduction and Management Council doesn’t issue warnings for fun. When PAGASA raises a typhoon signal, entire cities shut down. <\/p>\n\n\n\n
Roads flood. Cell towers go dark. Your “just check in when you can” policy falls apart fast.<\/p>\n\n\n\n
Here’s where it gets messy.<\/p>\n\n\n\n
The Department of Labor and Employment has clear rules about work suspension during calamities. But those rules were written for traditional employees, not remote contractors.<\/p>\n\n\n\n
If your remote worker is classified as an independent contractor (which most are), the standard “no work, no pay” principle technically applies. <\/p>\n\n\n\n
You’re not legally required to pay them if they can’t work due to a typhoon.<\/p>\n\n\n\n
When a typhoon knocks out power for three days, do you pay your remote team?<\/p>\n\n\n\n
Legally, if they’re contractors, probably not. Practically? It’s more complicated.<\/p>\n\n\n\n
Some managers I’ve talked to have a “disaster advance” policy. If someone loses work time due to a verified emergency, they can request an advance on future pay. <\/p>\n\n\n\n
Not a gift, not charity. An advance they work off later.<\/p>\n\n\n\n
Others build a “calamity buffer” into contracts. Think of it like paid sick days, but for disasters. Two or three paid emergency days per year, no questions asked.<\/p>\n\n\n\n
The Bangko Sentral ng Pilipinas keeps banking systems running even during emergencies, so payment processing through platforms like Wise usually works. <\/p>\n\n\n\n
But your remote worker might not be able to access an ATM if their area is flooded.<\/p>\n\n\n\n
This is where having multiple payment options matters. Not just bank transfers, but mobile wallets like GCash that work when traditional banking is down.<\/p>\n\n\n\n
Your emergency plan can’t be a PDF nobody reads.<\/p>\n\n\n\n
It needs to be simple enough that someone can follow it while their roof is leaking and their phone is at 12% battery.<\/p>\n\n\n\n
Before the Storm<\/strong><\/p>\n\n\n\n Get basic information now, not during the crisis. Where does your team live? What’s their backup internet situation? Do they have a secondary phone number?<\/p>\n\n\n\n You don’t need their life story. Just enough to know if they’re in a high-risk area.<\/p>\n\n\n\n Set up a communication hierarchy. If Slack is down, try SMS. If SMS doesn’t work, try WhatsApp or Telegram. Have at least three ways to reach each person.<\/p>\n\n\n\n Make it clear: Safety first, work second. Nobody should feel pressured to clock in while evacuating.<\/p>\n\n\n\n During the Emergency<\/strong><\/p>\n\n\n\n Suspend normal productivity expectations. If someone manages to get online from an evacuation center using mobile data, they’re not going to hit their usual numbers.<\/p>\n\n\n\n Your time tracking system needs flexibility built in. Grace periods for missed clock-ins. Manual time entry options. The ability to pause tracking without penalty.<\/p>\n\n\n\n Those daily standups and recap reports? Scale them back. A simple “I’m safe, internet is spotty, will update tomorrow” is enough.<\/p>\n\n\n\n Don’t go dark on your end either. A quick message saying “We know there’s a typhoon, stay safe, we’ll figure out the work stuff later” does more for team morale than you’d think.<\/p>\n\n\n\n After the Dust Settles<\/strong><\/p>\n\n\n\n This is when you assess actual damage.<\/p>\n\n\n\n Some people will be back online in a day. Others might need a week. A few might have lost their home workspace entirely and need time to relocate or rebuild.<\/p>\n\n\n\n Have a conversation about what they need. Sometimes it’s time off. Sometimes it’s a small advance to cover storm damage. Sometimes it’s just flexibility while they sort out their new normal.<\/p>\n\n\n\n Document everything. If someone can’t work for legitimate disaster reasons, note it. This protects both of you if there are questions later about hours or payment.<\/p>\n\n\n\n Let’s be honest about Philippine internet.<\/p>\n\n\n\n It’s gotten better. Fiber is expanding. Mobile data is faster than it used to be. But it’s still not bulletproof.<\/p>\n\n\n\n Power is even less reliable. Rotating blackouts happen in many provinces, sometimes on a schedule, sometimes not. <\/p>\n\n\n\n Your remote worker might know they’ll lose power from 2-4 PM every Tuesday, or they might get surprised by an outage that lasts six hours.<\/p>\n\n\n\n This isn’t a reason not to hire Filipino remote workers. It’s a reason to build realistic expectations into your workflow.<\/p>\n\n\n\n Your management platform needs to handle reality, not just the ideal scenario.<\/p>\n\n\n\n Time tracking that’s too rigid breaks during emergencies. If someone can’t clock in because the power is out, they shouldn’t be penalized. <\/p>\n\n\n\n Manual time entry and grace periods aren’t nice-to-haves. They’re essential.<\/p>\n\n\n\n Slack integration is useful until Slack requires internet that doesn’t exist. Have backup communication channels that work on minimal data.<\/p>\n\n\n\n Disasters are traumatic.<\/p>\n\n\n\n Your remote worker might be online and “working,” but they just watched their neighborhood flood. Their family might have lost their home. They might be dealing with things you can’t see through a screen.<\/p>\n\n\n\n This isn’t about being soft. It’s about being realistic.<\/p>\n\n\n\n Some managers check in with a simple “How are you actually doing?” during one-on-ones after a disaster. Not “how’s the work going?” Just “are you okay?”<\/p>\n\n\n\n Sometimes the answer is yes. Sometimes it’s not. Either way, you learn something important about your team.<\/p>\n","protected":false},"excerpt":{"rendered":" The Philippines averages 20 typhoons a year, and most foreign employers have no plan until their remote worker goes dark mid-week with no explanation. Here’s how to build a practical emergency plan that protects your team, keeps work moving where possible, and holds the relationship together when things get rough.<\/p>\n","protected":false},"author":2,"featured_media":49,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-965","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-for-employers"],"_links":{"self":[{"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/posts\/965","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/comments?post=965"}],"version-history":[{"count":1,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/posts\/965\/revisions"}],"predecessor-version":[{"id":967,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/posts\/965\/revisions\/967"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/media\/49"}],"wp:attachment":[{"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/media?parent=965"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/categories?post=965"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/tags?post=965"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}The Infrastructure Reality<\/h2>\n\n\n\n
What This Means for Your Tools<\/h2>\n\n\n\n
The Mental Health Part<\/h2>\n\n\n\n