Status-before-bad-news

How it works

Template: what is down, since when, what you tried, what you need. Teach it in week one. Put it in the handoff. Praise ugly accuracy. 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: ‘Payment API 500 since 02:14 PHT. Retried twice. Need a U.S. owner by 07:00.’ That is the note. Not a 400-word apology.

How it differs

Follow-the-sun handoff is the vehicle. Indirect no is what the template prevents.

Common errors

Rewarding long apologies over short facts.

In practice

Treat Status-before-bad-news as a week-one operating object. Put the expected sentence in the brief: what they send, to whom, by when. Culture words do not replace a template. 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 status-before-bad-news 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.