You hired someone promising.<\/p>\n\n\n\n
First week went great. They showed up to meetings, delivered on time, seemed excited about the work.<\/p>\n\n\n\n
Then the cracks started appearing.<\/p>\n\n\n\n
A missed Zoom call here. Radio silence on Slack there. “Sorry, internet problems” became the go-to excuse.<\/p>\n\n\n\n
Now you’re three weeks in and you’ve had four no-shows. You’re wondering if you made a hiring mistake. Or if this is just how remote work goes.<\/p>\n\n\n\n
Neither is true.<\/p>\n\n\n\n
Repeated no-shows aren’t a “bad VA” problem or a remote work problem. They’re a systems problem on your end.<\/p>\n\n\n\n
I know that’s hard to hear. But once you understand what’s actually happening, you can fix it.<\/p>\n\n\n\n
Most no-show situations follow the same script. Someone accepts a recurring meeting time. Maybe even confirms it in Slack. <\/p>\n\n\n\n
Then they just… don’t show up.<\/p>\n\n\n\n
No heads up. No explanation. Sometimes an apology hours later, sometimes nothing at all.<\/p>\n\n\n\n
The knee-jerk reaction is to blame the person. They’re unreliable. They’re not serious. They’re juggling too many clients.<\/p>\n\n\n\n
Sometimes that’s true.<\/p>\n\n\n\n
Over-commitment is huge.<\/strong> Many Filipino VAs work with multiple clients because one client alone doesn’t provide enough hours or income security. When you add a recurring meeting without asking about their other commitments, you might be creating an impossible calendar.<\/p>\n\n\n\n Time zone confusion is bigger than you think.<\/strong> You say “Tuesday at 10am” and they confirm, but you never explicitly stated which timezone. Or you did, but your calendar invite showed the wrong conversion. Now you think they no-showed and they think the meeting is in three hours.<\/p>\n\n\n\n Fear-avoidance spirals quickly.<\/strong> They realize they can’t make the meeting five minutes beforehand. Instead of sending a quick message (which feels mortifying), they freeze. Then they feel so bad about the no-show that they avoid you entirely. <\/p>\n\n\n\n Weak consequences train bad behavior.<\/strong> If someone misses a meeting and nothing happens \u2013 no documentation, no conversation, no acknowledgment that this matters \u2013 you’ve just taught them that attendance is optional.<\/p>\n\n\n\n This is the part nobody talks about.<\/p>\n\n\n\n You need more than a Slack channel and good vibes.<\/p>\n\n\n\n You need a written agreement that spells out the basics. Not a 47-page contract. Just clear terms about the stuff that actually causes friction.<\/p>\n\n\n\n Work hours and availability windows.<\/strong> Not “flexible hours” or “as needed.” Actual days and times when they need to be online or reachable. In Philippine time, clearly stated.<\/p>\n\n\n\n If the role is async, define what “available” means. Does it mean responding to Slack within 2 hours during their shift? Checking in by 9am Manila time daily? Submitting a standup by a certain time?<\/p>\n\n\n\n Meeting commitments.<\/strong> This should be its own clause. Something like: “If you confirm attendance at a meeting and fail to attend or cancel with less than 24 hours notice more than twice in any 30-day period, this is grounds for contract termination.”<\/p>\n\n\n\n Harsh? Maybe. But it’s clear. And clarity prevents resentment on both sides.<\/p>\n\n\n\n Communication expectations.<\/strong> What’s your primary channel? What’s the expected response time? What happens in an emergency or if they’re sick?<\/p>\n\n\n\n A lot of clients think this stuff is obvious. It’s not.<\/p>\n\n\n\n How to report absences.<\/strong> If they’re sick or have an emergency, how and by when should they notify you? Do you need documentation for absences longer than a certain period?<\/p>\n\n\n\n What happens when problems arise.<\/strong> A simple escalation path. If they’re struggling with the workload or schedule, who do they talk to? How do you handle disputes?<\/p>\n\n\n\n Here’s what happens without documentation.<\/p>\n\n\n\n Third no-show happens. You’re frustrated. You message them: “This isn’t working out.”<\/p>\n\n\n\n They respond: “What do you mean? I’ve been doing great work!”<\/p>\n\n\n\n And now you’re in a he-said-she-said situation with no facts to point to.<\/p>\n\n\n\n UK employment guidance through Acas stresses one thing above everything else: write it down. Specific incidents, dates, impact, and what needs to change.<\/p>\n\n\n\nWhat Should Have Been in Place From Day One<\/strong><\/h2>\n\n\n\n
The Documentation System Nobody Wants to Do (But Everyone Needs)<\/strong><\/h2>\n\n\n\n