You hired three Filipino VAs to handle customer support.
On paper, that’s 120 hours of work per week.
But in reality? You’re getting maybe 90 hours of productive output, tickets are piling up during PTO requests, and you’re constantly wondering if you need to hire another person or if something else is broken.
The problem isn’t your team. It’s that you’re planning headcount when you should be planning capacity.
This guide breaks down the difference, shows you how to plan VA pods the right way.
What Is a VA Pod
A VA pod is a stable group of virtual assistants who share workflows, follow the same SOPs, and work toward common KPIs.
Think of it like a small delivery team, not a bunch of isolated generalists.
Example pods:
- A 4-person customer support pod handling tickets in shifts
- A 3-person SEO operations pod managing content calendars and link building
- A 2-person admin pod processing invoices and scheduling
Pods work because they create coverage, enable backup, and let people specialize instead of trying to do everything.
Headcount Ignores Reality
When you count heads, you assume everyone works their full contracted hours at 100% productivity.
A VA on a 40-hour-per-week contract looks like 40 hours of capacity.
But actual productive time is closer to 25-30 hours after you subtract meetings, breaks, training, PTO, and rework.
Not all work is equal.
Processing routine tickets is different from handling escalations.
Writing blog posts is different from editing them.
If you plan headcount without understanding what kind of work your pod actually does, you’ll constantly be surprised when things take longer than expected.
What Capacity Planning Actually Measures
Capacity planning starts with units of work, not hours.
You define what your team delivers and measure how much they can realistically complete over time.
Common units for VA pods:
- Tickets closed per day
- Leads processed per week
- Posts published per month
- Invoices reconciled per cycle
- Calls handled per shift
You track historical throughput to see what your pod actually completes, then use that as the baseline for future planning.
The formula is simple:
Demonstrated capacity x utilization target = planned workload
If your support pod averages 300 tickets per week and you plan at 75% utilization, you allocate 225 tickets per week and leave the rest as buffer.
That buffer absorbs spikes, covers training, handles incidents, and gives your team breathing room to maintain quality.
How to Build a Capacity Model for Your Pod
Define Your Units and Work Types
Pick the unit that matters most for your pod’s output.
For customer support, it might be tickets per day. For content operations, it might be tasks completed per week or words edited per day.
Then break work into categories:
- BAU work (business as usual, the recurring stuff)
- Project work (one-time initiatives, launches, migrations)
- Internal work (training, meetings, documentation)
Many teams underestimate how much time internal work consumes. Track it separately so you don’t accidentally plan like it doesn’t exist.
Calculate Effective Hours Per Person
Start with contracted hours.
If someone is hired for 40 hours per week, write that down.
Now subtract everything that isn’t direct productive work:
- Meetings and standups (usually 3-5 hours per week)
- Breaks (30-60 minutes per day)
- Administrative tasks (timesheets, expense reports, tool updates)
- Training and coaching (varies by seniority)
What’s left is effective hours. For most VA pods, that’s 5-6 hours per day, not 8.
Multiply effective hours by the number of people in your pod. That’s your pod’s weekly capacity in hours.
Measure Historical Throughput
Look back at the last 4-8 weeks.
How many units of work did your pod actually complete per week?
If your pod closed an average of 280 tickets per week over the last two months, that’s your baseline capacity.
This number already accounts for meetings, breaks, rework, and all the hidden friction. It’s what your team can realistically deliver under normal conditions.
When you track time properly with accurate clock-in and clock-out records, you can see exactly where productive hours go and what your true capacity is.
Apply a Utilization Cap
Don’t plan at 100% of demonstrated capacity.
Target 70-85% utilization for most pods.
If your baseline is 280 tickets per week, plan for 210-240 tickets. The remaining 15-30% is buffer.
Teams that consistently run above 90% utilization burn out faster, make more mistakes, and quit more often.
Adjust for Known Events
Capacity isn’t static.
It drops during Philippine public holidays, PTO requests, client-side holidays, onboarding new team members, and system migrations.
Build a calendar that flags these events and reduce planned capacity for those weeks. Having a clear PTO management system makes this much easier because you can see upcoming time off at a glance and plan accordingly.
If someone is taking PTO, reduce that week’s planned work proportionally. If you’re onboarding a new VA, assume that person contributes 25-50% of normal capacity for the first month.
Map Capacity Back to Headcount
Now you can answer the headcount question properly.
If projected demand is 400 tickets per week and your current pod’s planned capacity (at 75% utilization) is 240 tickets per week, you have a gap of 160 tickets.
Work backward from throughput per person. If the average VA closes 70 tickets per week at 75% utilization, you need roughly 2-3 more people.
This is how you justify hiring decisions with data instead of guessing.
Practical Framework You Can Use Right Now
Step 1: Measure baseline throughput
Track your pod’s output per week for each work type over 4-8 weeks. Use actual completed work, not theoretical estimates.
Step 2: Adjust for holidays and PTO
Mark Philippine public holidays, client-country holidays, and planned PTO on a calendar. Reduce planned capacity for those weeks proportionally.
Step 3: Apply utilization cap
Plan at 70-85% of average demonstrated capacity. Reserve the remaining 15-30% as buffer for training, incidents, and quality work.
Step 4: Compare to projected demand
If demand exceeds planned capacity at your utilization target, you need more headcount. If demand is under planned capacity, you’re overstaffed or you have room to take on more work.
Step 5: Iterate monthly
Revisit throughput and utilization every month. Adjust targets as your team improves processes, adds tools, or shifts focus.
The Bottom Line
Headcount tells you how many people you’re paying. Capacity tells you how much work those people can actually deliver.
Most employers plan headcount and wonder why work piles up, quality suffers, or people burn out.
The fix is planning capacity first.
Measure what your team actually completes. Apply a utilization cap. Adjust for holidays and known events. Then map that capacity back to headcount when you need to hire.
Start with one pod. Track throughput for a month. Compare planned vs actual capacity. Adjust from there.
You’ll know exactly when to hire, when to hold steady, and when the problem is process, not people.