{"id":391,"date":"2026-01-13T17:43:52","date_gmt":"2026-01-13T21:43:52","guid":{"rendered":"https:\/\/manageph.com\/blog\/?p=391"},"modified":"2026-01-13T17:43:52","modified_gmt":"2026-01-13T21:43:52","slug":"estimate-weekly-hours-filipino-virtual-assistants","status":"publish","type":"post","link":"https:\/\/manageph.com\/blog\/estimate-weekly-hours-filipino-virtual-assistants\/","title":{"rendered":"How to Estimate Weekly Hours for Filipino Virtual Assistants"},"content":{"rendered":"\n

You hired a VA.<\/p>\n\n\n\n

You said “I need help about 20 hours a week.”<\/p>\n\n\n\n

That number came from nowhere. Maybe you saw it in a job post. Maybe it sounded reasonable.<\/p>\n\n\n\n

Three months later, your VA is either bored with not enough work or drowning in tasks that need 40 hours crammed into 20.<\/p>\n\n\n\n

Both situations suck. One wastes money. The other burns people out.<\/p>\n\n\n\n

Here’s how to actually figure out the right number of hours before you hire.<\/p>\n\n\n\n

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

Your VA Logs Time. You Approve It. Everyone’s Clear.<\/h4>\n <\/div>\n
\n \n Get Started <\/a>\n <\/div>\n<\/div>\n\n\n\n

Three Common Weekly Hour Ranges for Hiring Filipino VAs<\/strong><\/h2>\n\n\n\n

When you look at what founders actually do (not what they post in polished job descriptions), three patterns show up.<\/p>\n\n\n\n

5 to 10 Hours for Testing the Waters<\/strong><\/p>\n\n\n\n

You’re a solo founder. Side project. Early stage.<\/p>\n\n\n\n

You need inbox triage, calendar management, basic formatting, simple reporting.<\/p>\n\n\n\n

Not urgent. Not daily. Just stuff that needs doing but you don’t want to do it.<\/p>\n\n\n\n

5 to 10 hours per week handles that.<\/p>\n\n\n\n

You’re not building a partnership here. You’re offloading specific tasks with clear completion criteria.<\/p>\n\n\n\n

Founders start here to see ROI before scaling up.<\/p>\n\n\n\n

20 to 30 Hours for Your Core Operations Partner<\/strong><\/p>\n\n\n\n

This is the sweet spot for small growing businesses.<\/p>\n\n\n\n

You need someone who owns daily routines. Customer emails. Bookkeeping prep. Content publishing. Project coordination.<\/p>\n\n\n\n

20 to 30 hours gives them enough time to actually own these processes.<\/p>\n\n\n\n

They’re not stretched so thin they can only react. They can improve systems, catch problems early, and take real ownership.<\/p>\n\n\n\n

This range shows up constantly in small business communities as the zone where VAs deliver the most value without burning out.<\/p>\n\n\n\n

It’s also officially “part-time” in most labor frameworks, which means it’s real work with predictable patterns, not casual coverage.<\/p>\n\n\n\n

35 to 40 Hours for Full Operational Coverage<\/strong><\/p>\n\n\n\n

Someone running major parts of your day-to-day operations.<\/p>\n\n\n\n

This aligns with standard full-time in the Philippines and internationally.<\/p>\n\n\n\n

At this level, you’re inside normal working time expectations before overtime kicks in.<\/p>\n\n\n\n

When people in remote work forums talk about pushing past 40 hours, it’s almost always framed as temporary. A crunch period with extra pay or time off afterward.<\/p>\n\n\n\n

Not the default schedule.<\/p>\n\n\n\n

Going past 40 hours consistently is where you see burnout, errors, and people quietly checking out.<\/p>\n\n\n\n

How to Estimate Based on Actual Tasks <\/strong><\/h2>\n\n\n\n

Legal frameworks tell you the boundaries. They don’t tell you if answering customer emails should take 2 hours or 8 hours per week.<\/p>\n\n\n\n

Here’s how to figure that out.<\/p>\n\n\n\n

List Every Recurring Task<\/strong><\/p>\n\n\n\n

Write down everything you expect this person to do weekly.<\/p>\n\n\n\n

Be specific. “Handle customer service” is too vague.<\/p>\n\n\n\n

“Answer 15 customer emails per week, update 3 help docs, log issues in Notion” is specific.<\/p>\n\n\n\n

For each task, estimate low, mid, and high time per unit.<\/p>\n\n\n\n

One customer email might take 10 to 15 minutes including research and follow-up.<\/p>\n\n\n\n

15 emails times 12 minutes average equals 3 hours just for email.<\/p>\n\n\n\n

Do this for every task on the list. Add them up.<\/p>\n\n\n\n

That’s your baseline estimate.<\/p>\n\n\n\n

Add 20 to 30 Percent for New Roles<\/strong><\/p>\n\n\n\n

New VAs need time to learn your systems.<\/p>\n\n\n\n

They’ll ask questions. Need clarification. Make mistakes and fix them.<\/p>\n\n\n\n

If your task-based estimate says 25 hours, budget 30 to 33 hours during the first month.<\/p>\n\n\n\n

After they’re up to speed, you can adjust down if the work actually takes less time.<\/p>\n\n\n\n

Track Time for the First Few Weeks<\/strong><\/p>\n\n\n\n

Get a time tracker.<\/a> <\/p>\n\n\n\n

Have your VA log time by task for the first two weeks minimum.<\/p>\n\n\n\n

Then look at the data.<\/p>\n\n\n\n

Are certain tasks taking way longer than you thought? Cut them or simplify the process.<\/p>\n\n\n\n

Are other tasks faster than expected? Maybe you can add more to that area.<\/p>\n\n\n\n

Founders who actually do this report finding 5 to 10 hours per week of wasted effort. <\/p>\n\n\n\n

Tasks that don’t matter. Inefficient workflows. Stuff that can be batched or eliminated.<\/p>\n\n\n\n

Adjust your hour estimate based on what you learn.<\/p>\n\n\n\n

The Patterns That Tell You Your Estimate is Wrong<\/strong><\/h2>\n\n\n\n

Some red flags show up over and over when hours are off.<\/p>\n\n\n\n

You Expect Coverage Across Impossible Time Zones<\/strong><\/p>\n\n\n\n

I see this one a lot.<\/p>\n\n\n\n

“I need someone available 6am US time and also 10pm Australian time.”<\/p>\n\n\n\n

That’s not a schedule. That’s two different jobs.<\/p>\n\n\n\n

Even if you only “need” them for scattered tasks during those hours, you’re asking for always-on availability that spans way more than a normal work day.<\/p>\n\n\n\n

This violates basic rest requirements in most labor frameworks.<\/p>\n\n\n\n

You either need two people covering different shifts, or you need to pick one time zone and work within it.<\/p>\n\n\n\n

The Work Clearly Needs More Hours Than You’re Paying For<\/strong><\/p>\n\n\n\n

Your VA consistently works past their contracted hours to hit deadlines.<\/p>\n\n\n\n

Or they’re rushing through tasks and quality drops.<\/p>\n\n\n\n

Or they tell you “I can’t get to that this week” when the task list looks reasonable.<\/p>\n\n\n\n

These are all signs your hour estimate is wrong.<\/p>\n\n\n\n

Don’t fix this by adding aggressive monitoring to squeeze more output from the same hours.<\/p>\n\n\n\n

Fix it by either cutting scope or increasing paid time.<\/p>\n\n\n\n

Philippine guidance on telecommuting specifically says monitoring has to be “proportionate, transparent and purpose-bound.”<\/p>\n\n\n\n

Heavy surveillance layered on top of unrealistic hours just drives people away.<\/p>\n\n\n\n

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

Track the Hours That Actually Happen<\/h4>\n <\/div>\n
\n \n Get Started <\/a>\n <\/div>\n<\/div>\n\n\n\n

They’re Constantly “Busy” But Nothing Gets Done<\/strong><\/p>\n\n\n\n

Opposite problem.<\/p>\n\n\n\n

Your VA logs full hours but output is weak.<\/p>\n\n\n\n

This often means you over-estimated hours and they’re stretching tasks to fill time.<\/p>\n\n\n\n

Or the work doesn’t actually need someone full-time and they know it, so they disengage.<\/p>\n\n\n\n

Both waste money and create a weird dynamic where everyone knows the hours don’t match reality but nobody says it.<\/p>\n","protected":false},"excerpt":{"rendered":"

Calculate the right weekly hours for your Filipino VA based on actual tasks, not guesses. Avoid burnout and wasted money with this task-based estimation guide.<\/p>\n","protected":false},"author":2,"featured_media":198,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[32,38,9],"class_list":["post-391","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-for-employers","tag-management","tag-management-tips","tag-virtual-assistants"],"_links":{"self":[{"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/posts\/391","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=391"}],"version-history":[{"count":2,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/posts\/391\/revisions"}],"predecessor-version":[{"id":722,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/posts\/391\/revisions\/722"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/media\/198"}],"wp:attachment":[{"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/media?parent=391"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/categories?post=391"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/manageph.com\/blog\/wp-json\/wp\/v2\/tags?post=391"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}