You hired someone promising.
First week went great. They showed up to meetings, delivered on time, seemed excited about the work.
Then the cracks started appearing.
A missed Zoom call here. Radio silence on Slack there. “Sorry, internet problems” became the go-to excuse.
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.
Neither is true.
Repeated no-shows aren’t a “bad VA” problem or a remote work problem. They’re a systems problem on your end.
I know that’s hard to hear. But once you understand what’s actually happening, you can fix it.
What’s Really Behind the No-Shows
Most no-show situations follow the same script. Someone accepts a recurring meeting time. Maybe even confirms it in Slack.
Then they just… don’t show up.
No heads up. No explanation. Sometimes an apology hours later, sometimes nothing at all.
The knee-jerk reaction is to blame the person. They’re unreliable. They’re not serious. They’re juggling too many clients.
Sometimes that’s true.
The Real Culprits
Over-commitment is huge. 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.
Time zone confusion is bigger than you think. 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.
Fear-avoidance spirals quickly. 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.
Weak consequences train bad behavior. If someone misses a meeting and nothing happens – no documentation, no conversation, no acknowledgment that this matters – you’ve just taught them that attendance is optional.
What Should Have Been in Place From Day One
This is the part nobody talks about.
You need more than a Slack channel and good vibes.
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.
Work hours and availability windows. Not “flexible hours” or “as needed.” Actual days and times when they need to be online or reachable. In Philippine time, clearly stated.
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?
Meeting commitments. 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.”
Harsh? Maybe. But it’s clear. And clarity prevents resentment on both sides.
Communication expectations. What’s your primary channel? What’s the expected response time? What happens in an emergency or if they’re sick?
A lot of clients think this stuff is obvious. It’s not.
How to report absences. 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?
What happens when problems arise. A simple escalation path. If they’re struggling with the workload or schedule, who do they talk to? How do you handle disputes?
The Documentation System Nobody Wants to Do (But Everyone Needs)
Here’s what happens without documentation.
Third no-show happens. You’re frustrated. You message them: “This isn’t working out.”
They respond: “What do you mean? I’ve been doing great work!”
And now you’re in a he-said-she-said situation with no facts to point to.
UK employment guidance through Acas stresses one thing above everything else: write it down. Specific incidents, dates, impact, and what needs to change.
Start a simple log. It takes 30 seconds per incident.
- Date
- What happened (or didn’t happen)
- Any explanation they provided
- Impact on your business or team
“Dec 10 – Missed 10am strategy call, no advance notice, replied 4 hours later saying internet was down. Client asked for status update that was due in that call, team was blocked for rest of day.”
That’s it.
You’re not building a legal case. You’re creating a factual record so that when you need to have a difficult conversation, you have specifics instead of vague feelings.
The Conversation You Should Have After the First No-Show
Don’t wait for a pattern to form.
One no-show with no explanation is your signal to reset expectations immediately.
Schedule a video call. Not a Slack message. Not an email. A face-to-face conversation where tone and context matter.
Fair Work’s framework suggests describing the specific behavior, its impact, and what improvement looks like.
That translates directly to remote contractor relationships.
“Hey, you missed our Tuesday meeting without letting me know in advance.
I was waiting with the client, and they were frustrated because we needed your input to move forward.
I need to be able to count on you for scheduled meetings, or know as soon as possible if something comes up.
Can we talk about what happened and how to make sure it doesn’t happen again?”
Then listen.
Maybe their kid was sick. Maybe they genuinely didn’t understand the meeting was mandatory. Maybe they’re overwhelmed with other commitments.
All of that is solvable.
But you have to surface it first.
End the conversation with a written summary sent via email. Restate what you discussed, what you both agreed to, and what happens if the problem continues.
This isn’t being a jerk. It’s being clear.
When One Conversation Isn’t Enough
Sometimes you have the reset conversation and the no-shows continue.
Now you need what the employment world calls a performance improvement plan. For contractors, think of it as an attendance improvement plan.
It should cover four things:
What needs to be improved. “You must attend all confirmed meetings or provide at least 12 hours advance notice of inability to attend, with valid reason, for the next 30 days.”
What support you’ll provide. “I’ll send calendar invites for all meetings with timezone clearly marked. I’ll check in with you weekly to make sure workload is manageable.”
Timeline for improvement. Usually 30 days for attendance issues.
What happens if improvement doesn’t occur. “If you have more than one unexcused absence in the next 30 days, we will terminate the contract.”
Both parties acknowledge this by email. You’re creating a paper trail, yes. But you’re also giving someone a genuine chance to fix the problem.
When to Cut Your Losses
Sometimes you do everything right and it still doesn’t work.
You have the written agreement. You documented incidents. You had the reset conversation. You offered an improvement plan. And they still no-show.
At that point, you’re not being unfair by ending the contract. You’re protecting your business.
The termination message should be brief and factual.
Building Systems So This Doesn’t Keep Happening
No-shows are frustrating.
But they’re almost always fixable if you catch them early and address them directly.
Written expectations. Quick documentation. Reset conversations. Clear consequences. Positive incentives.
That’s the playbook.
Most people skip straight to firing someone and feeling burned out on remote work.
Don’t do that.
Fix the system first. Then, if someone still can’t show up after you’ve made everything clear, you can let them go knowing you did everything right.