{"id":247,"date":"2025-12-10T18:57:25","date_gmt":"2025-12-10T22:57:25","guid":{"rendered":"https:\/\/manageph.com\/blog\/?p=247"},"modified":"2025-12-10T18:57:25","modified_gmt":"2025-12-10T22:57:25","slug":"how-to-manage-filipino-vas-across-projects","status":"publish","type":"post","link":"https:\/\/manageph.com\/blog\/how-to-manage-filipino-vas-across-projects\/","title":{"rendered":"How to Manage Multiple Projects with Filipino Virtual Assistants"},"content":{"rendered":"\n

I hired my first Filipino VA in 2006. One person. One project. Easy.<\/p>\n\n\n\n

Then I hired another. Then three more. Then I had four clients and six VAs and I realized something.<\/p>\n\n\n\n

I had no idea what anyone was doing.<\/p>\n\n\n\n

Invoices were coming in at random times. I couldn’t remember who was working on what. One VA asked me a question about Project B and I gave them an answer meant for Project A.<\/p>\n\n\n\n

It was a mess.<\/p>\n\n\n\n

Here’s what I learned about actually managing multiple VAs across multiple projects without losing your mind.<\/p>\n\n\n\n

Get the Tax Forms Sorted<\/strong><\/h3>\n\n\n\n

US companies need Form W-8BEN from Filipino contractors. It says “I’m a foreign person, you don’t withhold US taxes from me.”<\/p>\n\n\n\n

It takes five minutes. Get it signed. Keep it on file.<\/p>\n\n\n\n

Your Filipino VAs should register with the BIR (Bureau of Internal Revenue) as self-employed. That’s their responsibility, not yours.<\/p>\n\n\n\n

Don’t tell them how to do their taxes. Don’t control that process. It makes you look like an employer.<\/p>\n\n\n\n

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

Store W-8BEN forms and Compliance Documents in One Place<\/h4>\n

Organize and manage your Filipino Virtual Assistant’s documents and stay compliant all in one simple platform.<\/p>\n <\/div>\n

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

Pick a Payment Method and Stick With It<\/strong><\/h3>\n\n\n\n

Wise works. PayPal works. Pick one.<\/p>\n\n\n\n

The main thing is you need records. Who got paid. For what project. When.<\/p>\n\n\n\n

When you’re paying multiple people for multiple projects, you need to know that the $500 you sent to Maria was for Client A’s content work, not Client B’s admin tasks.<\/p>\n\n\n\n

Here’s what I do now.<\/p>\n\n\n\n

Every VA submits an invoice. The invoice lists the project name, the dates, the hours or deliverables, and the rate. <\/p>\n\n\n\n

I approve it in my system (or just reply “approved” to the email). Then I pay on the same day every week.<\/p>\n\n\n\n

Everyone knows when to expect payment. I can batch all my Wise transfers at once. I have a record of everything.<\/p>\n\n\n\n

Make Invoice Templates <\/strong><\/h3>\n\n\n\n

Give your VAs an invoice template.<\/p>\n\n\n\n

Project name (required). Date range (required). What they did. How much.<\/p>\n\n\n\n

If they work hourly, they track hours per project. If they’re project-based, they invoice when deliverables are done.<\/p>\n\n\n\n

Route everything through the same place. Email usually works. <\/p>\n\n\n\n

This sounds basic. But when you have six invoices coming in at random times for projects you can barely remember, you’ll understand why this matters.<\/p>\n\n\n\n

Data Protection Is Not Optional<\/strong><\/h3>\n\n\n\n

Your VAs are accessing client information. Sometimes sensitive stuff.<\/p>\n\n\n\n

The Philippines has a Data Privacy Act known as Republic Act 10173. It’s actually pretty strict.<\/p>\n\n\n\n

If personal data is being processed in the Philippines (which it is, if your VAs are there), the law applies. Even if you’re a foreign company.<\/p>\n\n\n\n

You’re the “controller.” Your VA is the “processor.” You’re still responsible for everything.<\/p>\n\n\n\n

Your contract needs to say that. I used to skip this part. Seemed like overkill for a VA relationship.<\/p>\n\n\n\n

Then one of my VAs had their laptop stolen. With client data on it. Now my contracts cover it.<\/p>\n\n\n\n

Simple Security Measures<\/strong><\/h3>\n\n\n\n

Every VA gets their own login. No shared passwords ever.<\/p>\n\n\n\n

Give access only to what they need. If they’re working on Project A, they don’t need access to Project B’s files.<\/p>\n\n\n\n

Require password managers. Require two-factor authentication if possible.<\/p>\n\n\n\n

When a project ends or a VA leaves, cut access immediately. Check that they’ve deleted data from their devices. Verify they’re out of all your tools.<\/p>\n\n\n\n

I keep a checklist now. Takes two minutes to run through when someone’s wrapping up.<\/p>\n\n\n\n

Pick One Project Management Tool<\/strong><\/h3>\n\n\n\n

Asana. Trello. ClickUp. Monday. Doesn’t matter which one.<\/p>\n\n\n\n

Pick one. Make everyone use it. I use Asana. Every project gets its own board. Every task has an owner and a due date.<\/p>\n\n\n\n

Same status tags everywhere: To Do, In Progress, Review, Done.<\/p>\n\n\n\n

Track Time by Project<\/strong><\/h3>\n\n\n\n

Your VAs should track their time. Even if you’re not paying hourly. Why? Because you need to know where the hours are going.<\/p>\n\n\n\n

Project A is eating 30 hours a week and you thought it would be 10? That’s a problem. Either the scope is wrong or something’s inefficient.<\/p>\n\n\n\n

Use ManagePh. Use whatever’s built into your PM tool. Track time per project, per task if possible.<\/p>\n\n\n\n

This also makes invoices easy to verify. VA says they worked 25 hours on Project B? You can check.<\/p>\n\n\n\n

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

Get Real Time Visibility Across All Your Projects<\/h4>\n

Clock-in and clock-out tracking per project, automatic hour calculations, and invoice generation all in one place with ManagePh<\/p>\n <\/div>\n

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

Time Block Your Own Work<\/strong><\/h3>\n\n\n\n

You can’t manage multiple projects if your own time is chaotic.<\/p>\n\n\n\n

Block time by project. Monday morning is Project A. Tuesday afternoon is Project B coordination. Wednesday morning is Project C client calls.<\/p>\n\n\n\n

My VAs do the same thing. They know which project they’re working on during which blocks.<\/p>\n\n\n\n

Reduces context switching. Keeps things focused.<\/p>\n\n\n\n

Make One Virtual Assistant the Coordinator<\/strong><\/h3>\n\n\n\n

This was a game changer for me. One of my more experienced VAs became the project coordinator. <\/p>\n\n\n\n

She doesn’t do less work. She just also keeps track of what everyone else is doing.<\/p>\n\n\n\n

She collects daily standups. She chases people when tasks are blocked. She makes sure things are moving through the workflow. She tells me when something needs my attention.<\/p>\n\n\n\n

If you have multiple VAs, try this. Pick someone organized. <\/p>\n\n\n\n

Give them coordinator duties on top of their regular work. Pay them a bit more if you need to.<\/p>\n\n\n\n

Write One Master Agreement<\/strong><\/h3>\n\n\n\n

One master services agreement. Covers all the general stuff.<\/p>\n\n\n\n

You’re an independent contractor. Payment terms are bi-weekly. Everything you create is work-for-hire and belongs to me (or my client). <\/p>\n\n\n\n

You’ll keep information confidential. Here’s how we handle data. Here’s how either of us can end this.<\/p>\n\n\n\n

That’s your base document.<\/p>\n\n\n\n

Add Project-Specific SOWs<\/strong><\/h3>\n\n\n\n

Then every new project gets a Statement of Work.<\/p>\n\n\n\n

References the master agreement. Adds the specific details.<\/p>\n\n\n\n

Project name. Client (if applicable). What you’re delivering. Timeline. Rate or total cost. What data or tools you need access to.<\/p>\n\n\n\n

Both parties sign. Now everyone knows what this project is.<\/p>\n\n\n\n

VA finishes Project X and starts on Project Y? New SOW. Same master agreement.<\/p>\n\n\n\n

Cross-Train Everyone<\/strong><\/h3>\n\n\n\n

If one person knows how to do something, that’s a single point of failure.<\/p>\n\n\n\n

I learned this when my main VA got dengue fever. Out for three weeks. No one else knew how to do half her tasks.<\/p>\n\n\n\n

Now at least two people understand every major function.<\/p>\n\n\n\n

Document your processes. Rotate VAs through different types of tasks sometimes. <\/p>\n\n\n\n

Keep project documentation where anyone can access it (client contacts, credentials in a password manager, file locations, process notes).<\/p>\n\n\n\n

Knowledge can’t live in one person’s head.<\/p>\n\n\n\n

Plan Transitions Deliberately<\/strong><\/h3>\n\n\n\n

When someone’s leaving a project, bring the new person on early if you can.<\/p>\n\n\n\n

Two-week overlap. They work together. Knowledge transfers naturally.<\/p>\n\n\n\n

Way better than “here’s a Google Doc, good luck.”<\/p>\n\n\n\n

I have a transition checklist now. Knowledge transfer sessions. Documentation handoff.<\/p>\n\n\n\n

Run through it every time someone leaves. Nothing gets missed.<\/p>\n\n\n\n

Run a Weekly Review<\/strong><\/h3>\n\n\n\n

Check time logs against project budgets. Approve invoices. Make sure deliverables are moving through your workflow. Communicate any priority changes.<\/p>\n\n\n\n

Look for patterns.<\/p>\n\n\n\n

VA consistently working overtime on one project? Needs resources or client input.<\/p>\n\n\n\n

Tasks sitting in review forever? Your approval process is the bottleneck.<\/p>\n\n\n\n

This is when you make tactical calls.<\/p>\n\n\n\n

Document Everything<\/strong><\/h3>\n\n\n\n

Write down how you do things.<\/p>\n\n\n\n

How you use your Project Management tools. What reporting formats you expect. How payment cycles work. Security practices. How to escalate issues.<\/p>\n\n\n\n

This becomes your training material.<\/p>\n\n\n\n

New VA starts? Share the docs. They understand your processes without you explaining everything.<\/p>\n\n\n\n

This Actually Works<\/strong><\/h2>\n\n\n\n

I manage more projects now than I did ever. With less stress. Because I built systems.<\/p>\n\n\n\n

Clear contractor relationships. Consistent payments. Data protection that’s actually enforced. One place where all work lives. <\/p>\n\n\n\n

Contracts that scale. Risk management that catches problems early. Weekly reviews that keep everything on track.<\/p>\n\n\n\n

Most people add VAs without adding systems.<\/p>\n\n\n\n

That’s how you end up with chaos.<\/p>\n\n\n\n

Build the infrastructure first. Then scale.<\/p>\n\n\n\n

You can run multiple projects with multiple VAs without losing your mind. You just need these seven pieces in place.<\/p>\n\n\n\n

The tools will vary. Your specific processes will vary.<\/p>\n\n\n\n

But the pattern is the same: systematic attention to classification, payments, data protection, unified operations, good contracts, and active monitoring.<\/p>\n\n\n\n

Get those right and scaling becomes easy instead of overwhelming.<\/p>\n","protected":false},"excerpt":{"rendered":"

Scaling your Filipino VA team across multiple projects? This guide covers everything you need to know from payment workflows to weekly standoffs<\/p>\n","protected":false},"author":2,"featured_media":147,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[],"class_list":["post-247","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\/247","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=247"}],"version-history":[{"count":4,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/posts\/247\/revisions"}],"predecessor-version":[{"id":457,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/posts\/247\/revisions\/457"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/media\/147"}],"wp:attachment":[{"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/media?parent=247"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/categories?post=247"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/tags?post=247"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}