Typhoon day protocol

How it works

PAGASA signals are not a vibe. Power and transport die before heroism helps. Paid time or SIL should be clear. Do not demand camera-on standup from a roof. For a U.S. company hiring one Filipino teammate, write this into the brief, the employment contract, and the peso payroll file before the start date. Slack habits do not override the Labor Code, BIR, or NPC. If the local employer of record holds the paper, they run the statutory step; you still owe a clean operating definition so the seat does not fail in week three. Put a number on the example when you budget loaded cost, because a nameless allowance always returns as a December surprise or a missed SLA.

Example: Signal No. 3 in their city: queue paused, message in Slack, resume when power and wind allow. No ‘make up the hours Saturday’ ambush.

How it differs

Brownout can happen without a typhoon. AWOL is what you call it only after you check the weather.

Common errors

Writing people up for a storm.

In practice

Treat Typhoon day protocol as a week-one operating object. Ask for a desk shot, a power plan, and a second network path. Geography is not personality. Write an owner - founder, local employer, or worker - and a date you will look at it again: first cutoff, first holiday, or first miss. If nobody can show a contract clause, a payslip line, a calendar block, or a checklist box, you do not have typhoon day protocol yet. You have a conversation. Convert the conversation before the person starts, while changing the deal still costs a paragraph rather than a resignation. Re-read the worked example above against the actual hire in front of you. If the numbers in that example cannot be swapped for this seat’s pesos, hours, and start date, the brief is still unfinished.