{"id":337,"date":"2026-01-08T20:45:40","date_gmt":"2026-01-09T00:45:40","guid":{"rendered":"https:\/\/manageph.com\/blog\/?p=337"},"modified":"2026-01-08T20:45:40","modified_gmt":"2026-01-09T00:45:40","slug":"offboard-filipino-virtual-assistants","status":"publish","type":"post","link":"https:\/\/manageph.com\/blog\/offboard-filipino-virtual-assistants\/","title":{"rendered":"How to Properly Offboard Filipino Virtual Assistants"},"content":{"rendered":"\n

Let me show you what could happen when nobody teaches you how to properly end a working relationship with a Filipino VA.<\/p>\n\n\n\n

That VA knows a lot about your business.<\/p>\n\n\n\n

Maybe the VA who left was the only one who knew how to handle a particular client or what the vendor renewal date was.<\/p>\n\n\n\n

Nobody documented anything. Nobody did a handoff.<\/p>\n\n\n\n

Now you’re scrambling to piece together how things worked. Clients aren’t getting responses. Projects stall. <\/p>\n\n\n\n

You’re spending hours reconstructing knowledge that should have been transferred.<\/p>\n\n\n\n

All of this is preventable.<\/p>\n\n\n\n

You just need a system.<\/p>\n\n\n\n

\n
\n <\/svg> <\/div>\n
\n

Your offboarding checklist is longer than you think<\/h4>\n

Track every system access point in one dashboard so nothing gets missed when someone leaves.<\/p>\n <\/div>\n

\n \n Get Started <\/a>\n <\/div>\n<\/div>\n\n\n\n

How to Actually Revoke Access Without Missing Anything<\/strong><\/h2>\n\n\n\n

Here’s what needs to happen on offboarding day. And I mean the actual day. Not three days later when you remember.<\/p>\n\n\n\n

Kill the main account first<\/strong><\/h3>\n\n\n\n

Your VA probably has one primary account. Google Workspace. Microsoft 365. Whatever your main system is.<\/p>\n\n\n\n

Disable it immediately. Reset the password. Kill all active sessions.<\/p>\n\n\n\n

This prevents them from logging back in even if they saved credentials somewhere.<\/p>\n\n\n\n

Strip permissions systematically<\/strong><\/h3>\n\n\n\n

Don’t just disable the account and call it done.<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

Handle their email properly<\/strong><\/h3>\n\n\n\n

Here’s what most people get wrong.<\/p>\n\n\n\n

They just delete the email account. All that project history disappears. Clients email addresses that bounce.<\/p>\n\n\n\n

Bad move.<\/p>\n\n\n\n

Convert the email mailbox to a shared mailbox instead.<\/p>\n\n\n\n

Keep it accessible for a limited time. Forward new mail to their manager or a team inbox so nothing goes unanswered.<\/p>\n\n\n\n

Let your team access past email threads for project continuity.<\/p>\n\n\n\n

Transfer file ownership before removing access<\/strong><\/h3>\n\n\n\n

If you remove someone’s Google Drive or OneDrive license before transferring file ownership, those files can become inaccessible.<\/p>\n\n\n\n

Delegate file ownership first. Then remove access. Never the reverse.<\/p>\n\n\n\n

Handle the systems your SSO doesn’t cover<\/strong><\/h3>\n\n\n\n

Your main system might cover the big applications.<\/p>\n\n\n\n

But what about that analytics platform with a separate login? The social media scheduler? The client CRM? Those three vendor portals?<\/p>\n\n\n\n

These don’t automatically get disabled when you turn off their main account.<\/p>\n\n\n\n

You need to manually revoke each one.<\/p>\n\n\n\n

This is where most people fail. They handle the obvious stuff and forget about the less-used applications.<\/p>\n\n\n\n

Rotate any shared credentials<\/strong><\/h3>\n\n\n\n

If the VA knows certain passwords, those need to change.<\/p>\n\n\n\n

Shared Gmail accounts. Social media logins. API keys. Client portal passwords.<\/p>\n\n\n\n

If they had access to your password manager, you need to rotate everything they could see.<\/p>\n\n\n\n

Remove from collaboration tools<\/strong><\/h3>\n\n\n\n

Slack. Teams. Asana. Trello. Whatever you use. Remove them from every workspace and channel.<\/p>\n\n\n\n

Why Knowledge Transfer Can’t Wait Until Someone’s Last Day<\/strong><\/h2>\n\n\n\n

Let me show you what usually happens.<\/p>\n\n\n\n

Someone gives notice or you tell them you’re ending the engagement.<\/p>\n\n\n\n

You think “okay, we’ll do a handoff in their last week.”<\/p>\n\n\n\n

Then their last week arrives.<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

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.<\/p>\n\n\n\n

The person’s gone. The knowledge is gone.<\/p>\n\n\n\n

This is why the best offboarding practices actually start at onboarding.<\/p>\n\n\n\n

Make documentation part of normal work. Not something you scramble to do at the end.<\/p>\n\n\n\n

Require VAs to maintain current documentation as a condition of working with you. <\/p>\n\n\n\n

Standard operating procedures for recurring tasks. Project notes that explain context. Client preferences and history.<\/p>\n\n\n\n

Keep credentials documented in a password manager you control.<\/p>\n\n\n\n

Daily and monthly recap submissions<\/a> create ongoing documentation naturally. <\/p>\n\n\n\n

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.<\/p>\n\n\n\n

When you do this, handoffs don’t depend on someone’s memory or goodwill during their last week.<\/p>\n\n\n\n

The documentation already exists.<\/p>\n\n\n\n

For non-urgent separations, offer a paid transition period. One to two weeks where the person trains replacement staff or internal team members.<\/p>\n\n\n\n

They record Loom sessions showing how to do key tasks. They write up explanations of how processes work. They flag upcoming deadlines and renewals.<\/p>\n\n\n\n

They answer questions from whoever is taking over.<\/p>\n\n\n\n

This isn’t them doing you a favor. You’re paying them for this time. It’s part of the job.<\/p>\n\n\n\n

For VAs who had direct client contact, plan the transition carefully.<\/p>\n\n\n\n

How to Handle Final Payment Without Creating Problems<\/strong><\/h2>\n\n\n\n

Pay all approved invoices for work completed. Pay any bonuses or commissions that were contractually agreed, not discretionary.<\/p>\n\n\n\n

Document the computation of final payment.<\/p>\n\n\n\n

List hours worked or project milestones completed. The agreed rate. Any bonuses or reimbursements. The total.<\/p>\n\n\n\n

When you have centralized time tracking and invoice systems<\/a>, this calculation becomes straightforward. <\/p>\n\n\n\n

You can see exactly what hours were approved, what invoices were submitted, and what’s already been paid. <\/p>\n\n\n\n

For payment methods, continue using whatever system you established during the engagement. <\/p>\n\n\n\n

\n
\n <\/svg> <\/div>\n
\n

Stop calculating final payments by hand.<\/h4>\n

See exactly what hours were approved, what invoices are pending, and what’s already been paid.<\/p>\n <\/div>\n

\n \n Get Started <\/a>\n <\/div>\n<\/div>\n\n\n\n

Why This Actually Protects Your Business<\/strong><\/h2>\n\n\n\n

Systematic offboarding creates specific protection.<\/p>\n\n\n\n

Security vulnerabilities disappear when access gets revoked completely and promptly. <\/p>\n\n\n\n

No lingering credentials. No former workers with keys to your systems.<\/p>\n\n\n\n

Operational continuity continues when knowledge transfers properly and clients don’t experience service gaps. <\/p>\n\n\n\n

The Filipino VA community is interconnected. How you handle departures affects whether qualified people want to work with you later.<\/p>\n\n\n\n

The alternative is chaos.<\/p>\n","protected":false},"excerpt":{"rendered":"

Most employers don’t realize the security risks and operational chaos that happens when they improperly offboard Filipino VAs. This guide shows you exactly how to end working relationships properly<\/p>\n","protected":false},"author":2,"featured_media":273,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-337","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-for-employers"],"_links":{"self":[{"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/posts\/337","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/comments?post=337"}],"version-history":[{"count":2,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/posts\/337\/revisions"}],"predecessor-version":[{"id":677,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/posts\/337\/revisions\/677"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/media\/273"}],"wp:attachment":[{"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/media?parent=337"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/categories?post=337"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/tags?post=337"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}