Let me show you what could happen when nobody teaches you how to properly end a working relationship with a Filipino VA.
That VA knows a lot about your business.
Maybe the VA who left was the only one who knew how to handle a particular client or what the vendor renewal date was.
Nobody documented anything. Nobody did a handoff.
Now you’re scrambling to piece together how things worked. Clients aren’t getting responses. Projects stall.
You’re spending hours reconstructing knowledge that should have been transferred.
All of this is preventable.
You just need a system.
Your offboarding checklist is longer than you think
Track every system access point in one dashboard so nothing gets missed when someone leaves.
How to Actually Revoke Access Without Missing Anything
Here’s what needs to happen on offboarding day. And I mean the actual day. Not three days later when you remember.
Kill the main account first
Your VA probably has one primary account. Google Workspace. Microsoft 365. Whatever your main system is.
Disable it immediately. Reset the password. Kill all active sessions.
This prevents them from logging back in even if they saved credentials somewhere.
Strip permissions systematically
Don’t just disable the account and call it done.
Move the user to a disabled status that removes all permissions and license assignments. You’re not deleting the account. You’re making it unable to do anything.
Handle their email properly
Here’s what most people get wrong.
They just delete the email account. All that project history disappears. Clients email addresses that bounce.
Bad move.
Convert the email mailbox to a shared mailbox instead.
Keep it accessible for a limited time. Forward new mail to their manager or a team inbox so nothing goes unanswered.
Let your team access past email threads for project continuity.
Transfer file ownership before removing access
If you remove someone’s Google Drive or OneDrive license before transferring file ownership, those files can become inaccessible.
Delegate file ownership first. Then remove access. Never the reverse.
Handle the systems your SSO doesn’t cover
Your main system might cover the big applications.
But what about that analytics platform with a separate login? The social media scheduler? The client CRM? Those three vendor portals?
These don’t automatically get disabled when you turn off their main account.
You need to manually revoke each one.
This is where most people fail. They handle the obvious stuff and forget about the less-used applications.
Rotate any shared credentials
If the VA knows certain passwords, those need to change.
Shared Gmail accounts. Social media logins. API keys. Client portal passwords.
If they had access to your password manager, you need to rotate everything they could see.
Remove from collaboration tools
Slack. Teams. Asana. Trello. Whatever you use. Remove them from every workspace and channel.
Why Knowledge Transfer Can’t Wait Until Someone’s Last Day
Let me show you what usually happens.
Someone gives notice or you tell them you’re ending the engagement.
You think “okay, we’ll do a handoff in their last week.”
Then their last week arrives.
You’re both busy. They’re trying to wrap things up. You’re trying to find a replacement. The handoff happens in one rushed conversation where everyone’s distracted.
Half the important stuff doesn’t get covered. You don’t realize what you missed until two weeks later when you need to know something and can’t figure it out.
The person’s gone. The knowledge is gone.
This is why the best offboarding practices actually start at onboarding.
Make documentation part of normal work. Not something you scramble to do at the end.
Require VAs to maintain current documentation as a condition of working with you.
Standard operating procedures for recurring tasks. Project notes that explain context. Client preferences and history.
Keep credentials documented in a password manager you control.
Daily and monthly recap submissions create ongoing documentation naturally.
When someone leaves, you’re not starting from scratch. You have weeks or months of written updates about what they worked on, what challenges they faced, and what’s pending.
When you do this, handoffs don’t depend on someone’s memory or goodwill during their last week.
The documentation already exists.
For non-urgent separations, offer a paid transition period. One to two weeks where the person trains replacement staff or internal team members.
They record Loom sessions showing how to do key tasks. They write up explanations of how processes work. They flag upcoming deadlines and renewals.
They answer questions from whoever is taking over.
This isn’t them doing you a favor. You’re paying them for this time. It’s part of the job.
For VAs who had direct client contact, plan the transition carefully.
How to Handle Final Payment Without Creating Problems
Pay all approved invoices for work completed. Pay any bonuses or commissions that were contractually agreed, not discretionary.
Document the computation of final payment.
List hours worked or project milestones completed. The agreed rate. Any bonuses or reimbursements. The total.
When you have centralized time tracking and invoice systems, this calculation becomes straightforward.
You can see exactly what hours were approved, what invoices were submitted, and what’s already been paid.
For payment methods, continue using whatever system you established during the engagement.
Stop calculating final payments by hand.
See exactly what hours were approved, what invoices are pending, and what’s already been paid.
Why This Actually Protects Your Business
Systematic offboarding creates specific protection.
Security vulnerabilities disappear when access gets revoked completely and promptly.
No lingering credentials. No former workers with keys to your systems.
Operational continuity continues when knowledge transfers properly and clients don’t experience service gaps.
The Filipino VA community is interconnected. How you handle departures affects whether qualified people want to work with you later.
The alternative is chaos.