Multi-Country Project Capacity Planning for Agencies

Multi-country agencies usually discover the capacity problem one missed deadline at a time. A campaign plan looks healthy in the project tool. The client has signed off on the timeline. The team looks fully staffed on paper. Then the Stockholm creative lead is out for Midsommar, the Zagreb developer has a bridge day after a public holiday, and the London account manager is on approved annual leave.

Nobody did anything wrong. The plan was just built from the wrong version of capacity. It counted people, not working days. For agencies delivering client work across borders, that distinction matters more than most resource plans admit.

Multi-country capacity planning is not only about who is assigned to a project. It is about who is actually available, in their country, during the delivery window.

The agency version of the problem

Say you run a 45-person digital agency with people in Croatia, Sweden, Serbia, Germany, and the UK. Your client work is split across strategy, design, development, QA, account management, and production support. A typical project needs six or seven people, but rarely from one country.

That makes the planning conversation messy fast. The designer in Stockholm may have more statutory vacation than the developer in Belgrade. The Croatian team may have a public holiday in the middle of a sprint that nobody in London recognizes. The German freelancer may be in a state with a different holiday calendar than the Berlin employee you planned around last year.

If your project plan only says "Mia is 80% allocated in June," it is missing the detail that decides whether the work can actually ship. Which days is Mia working? Which country holidays apply? Is she also covering another client? Has she already booked PTO around a local holiday? Those are operational questions, not HR trivia.

Public holidays are capacity events

Agencies tend to treat public holidays as calendar notes. They should be treated as capacity events. A public holiday removes available work without anyone submitting a vacation request, and that makes it easy to miss in project planning.

Late June is a good example. Sweden has Midsommar. Croatia has Anti-Fascist Struggle Day on June 22. Serbia has Vidovdan on June 28. Depending on the year, those dates can sit close enough together to make a two-week delivery window feel strangely thin. Your Swedish creative direction may be unavailable just when the Croatian production team is trying to finish assets, and the Serbian QA team may have less room for final checks than the project plan suggests.

The same thing happens around May holidays, Easter, national days, and year-end shutdown periods. One country loses a day. Another country loses two. A third country is technically working, but half the team has taken PTO to create a longer break. The client only sees the date on the statement of work.

For the leave side of that foundation, start with multi-country leave management. For the project side, connect that absence data to the way you plan delivery work.

PTO changes the shape of delivery

Approved PTO is easier to see than public holidays, but it still gets underestimated. The mistake is treating vacation as a simple subtraction from total team hours. In client work, the person who is out often matters as much as the number of hours missing.

If a junior developer is away for three days, the team may be able to rebalance the work. If the only person who knows the client's analytics setup is away for the same three days, a small absence becomes a delivery risk. If the account manager is out during stakeholder review, approvals can stall even when the production team is fully staffed.

This is where agencies need a different lens than internal product teams. Agency capacity is not just engineering capacity or design capacity. It is client-facing capacity, approval capacity, specialist capacity, and handoff capacity. A project can be blocked because the wrong person is unavailable for half a day.

This is also why leave approval and project planning should not live in separate worlds. Managers need to know when a PTO request affects an active launch, a client workshop, a support rota, or a time-sensitive handoff. That does not mean rejecting vacation by default. It means approving time off with enough context to protect both the employee and the client commitment.

Logged hours are useful, but they are not enough

Many agencies already track logged hours. That helps with utilization, billing, and margin analysis. But logged hours look backward. Capacity planning needs to look forward.

If last month shows a developer logging 32 billable hours per week, that does not mean you can safely assign 32 billable hours next week. Next week may include a national holiday, two approved PTO days, a client escalation, and a handoff from another team. Historical utilization is useful context, but it cannot replace an availability forecast.

A stronger review combines three views:

• Availability: working days after country holidays, approved PTO, sick leave, and other absences are accounted for.
• Demand: planned project work, retainers, support commitments, client meetings, and internal obligations are visible in the same period.
• Reality: logged hours and recent delivery patterns show whether the team is consistently overcommitted or carrying hidden work.

When those three views disagree, believe the conflict. That is where the planning work is. Maybe the scope needs to move. Maybe a handoff needs to happen before leave starts. Maybe the team needs a backup reviewer in another country. Maybe the deadline is fine, but only if the client signs off by Wednesday instead of Friday.

A practical planning rhythm

The best agencies do not wait until a project is already late to check availability. They make capacity review part of the normal delivery rhythm. It does not need to be heavy. It just needs to be consistent.

Monthly: scan the next 8 to 12 weeks

Once a month, look ahead across all active client work. Mark country-specific public holidays, known PTO, major client milestones, and any weeks where several people in the same discipline are unavailable. This is where you catch the obvious problems early: three designers out during brand concept week, no senior developer available for a technical discovery, or a client launch sitting inside a holiday cluster.

Weekly: review delivery risk by role

In the weekly resourcing meeting, do not only ask whether the team has enough total hours. Ask whether each project has the right roles available. Strategy, design, development, QA, account management, and approval ownership all need coverage. If one role has no backup, that is the risk to solve first.

Before approval: check overlap

When a new leave request comes in, check it against current project commitments before approving. For most requests, the answer will still be yes. The difference is that you can approve with a plan: move a review earlier, assign a cover person, or tell the client that a decision window needs to shift.

This is the same principle behind team capacity planning: absence visibility should be part of the approval process, not a discovery after the calendar is already broken.

What to check before committing to a client deadline

Before a multi-country agency commits to a launch date, sprint plan, workshop schedule, or retainer capacity, run the deadline through a simple checklist.

• Which countries are represented on the project team? List the actual working countries, not only office locations or contract entities.
• Which public holidays fall inside the delivery window? Include floating holidays and regional variations where they apply.
• Who already has approved PTO? Look for overlap by role, not just by headcount.
• Which roles are single points of failure? Account lead, technical lead, QA owner, analytics specialist, copy reviewer, and client approver are common ones.
• What work must happen before someone leaves? Handovers, code reviews, asset approvals, access setup, and client notes should be scheduled before the absence.
• What work can safely wait? Not everything needs a backup. Separate deadline-critical work from nice-to-have progress.
• Where is the buffer? If the plan has no buffer and crosses multiple countries, the first holiday or sick day will consume it.

This checklist is intentionally boring. That is the point. The failure mode in agency planning is usually not a lack of sophisticated tooling. It is forgetting to ask plain questions early enough.

How BreezeLeave fits into the planning stack

BreezeLeave handles the leave foundation: employees can be assigned to countries, country-specific public holidays are visible, and approved absences are tracked in one place. That gives agencies a cleaner source of truth for who is available before they make project commitments.

It does not replace the project plan, the client brief, or the resourcing judgement of a delivery lead. It makes those conversations better by removing the basic uncertainty: who is off, which holidays apply, and where leave overlaps with delivery work.

Once that information is clear, agencies can connect it to project capacity planning, weekly resourcing reviews, and the client-facing timelines they already manage. The result is not a perfect forecast. It is a more honest one.

The planning habit that pays off

Multi-country agencies do not need to become more rigid to plan better. They need to stop treating availability as a single number. A team of six people is not six equal units of capacity when those people work under different holiday calendars, PTO patterns, client responsibilities, and specialist roles.

The planning habit that pays off is simple: before promising work, check actual working time. Before approving leave, check project impact. Before moving a deadline, check which country calendars are quietly shaping the week.

For more detail on the PTO side, read our guide to managing PTO across countries. For an agency-specific leave example, see how a 50-person agency manages PTO across three countries. The same lesson runs through all of it: when leave, holidays, and project work are planned together, distributed agencies make calmer promises and keep more of them.