Capacity Planning vs Resource Planning for Agencies

The agency owner asks a simple-sounding question on a Wednesday call: "Can we take this project?" Three people answer at once. The delivery lead says yes, the people are technically in the team. The finance lead says yes, the margin works. The resource manager says maybe, because the senior designer is at 105 percent next month. All three are using the word "capacity." None of them mean the same thing. The agency keeps mixing capacity planning with resource planning, and then wonders why the staffing answer disagrees with itself. This article separates the two for an agency operations audience and shows which question each one actually answers.

The distinction matters because the two views feed different decisions. Capacity planning answers "do we have room?" Resource planning answers "do we have the right people in the right roles?" Agencies that conflate them either oversell their own bench or understaff a delivery they could have taken comfortably.

The short definition difference

Capacity planning is a hour-and-week question. It asks how many productive hours the agency has available across people, roles, and weeks, after PTO, public holidays, retainers, and existing project load. The answer is a number with a date range attached.

Resource planning is a role-and-skill question. It asks which people can do which work, at which level, for which clients, and at what cost. The answer is a list of named assignments tied to specific deliverables. A team can have plenty of capacity in total hours and still have no resource match for a particular project.

A simple test: if the answer is "we have 240 hours free in March," that is capacity. If the answer is "Lina is the only senior strategist for healthcare clients and she is already on two retainers," that is resource planning.

Side by side, in one table

The table is the comparison. The rest of the article unpacks the rows that agency owners get wrong most often.

Where capacity planning helps

Capacity planning is the right view when the question is volume. A new retainer just landed. A pitch wants four months of effort. Two team members put in vacation for the same week. A client is asking whether the agency can absorb a scope change. Each of these is a "how many hours" question.

For capacity to be honest, the inputs cannot be optimistic. The base hours per person must account for FTE, not assume everyone is full time. PTO must come from approved leave, not a Slack message. Public holidays must follow each employee's country, not a single national calendar. Retainer hours must be deducted before the new work is added, not after. And the logged-hour delta from ClickUp has to be part of the picture, because a person who has been under-logging is not really free.

For the product flow that feeds this view, see project capacity planning and the agency-focused capacity planning template.

Where resource planning helps

Resource planning is the right view when the question is fit. The pitch needs a senior creative director with healthcare experience. The retainer expects two named developers because the client bought them in the pitch. The hypercare phase needs a QA lead who has already shipped similar work. None of these are answered by free hours alone.

Resource planning treats role demand as a first-class object. For a given engagement, the agency lists the roles, the hours per role per week, the seniority required, and the period. Then assignments are made against named people, freelance slots, or planned hires. FTE is a property of the person, not the engagement, which is why mixed full-time and freelance teams need a resource view rather than a capacity view to staff cleanly.

For the product side, see agency resource planning and the resource planning template for roles, FTE, PTO, and planned slots.

How agencies confuse the two

Most confusion comes from two patterns. Both look harmless and both produce bad staffing decisions.

Pattern one: capacity used as a hiring signal. The agency sees the team at 95 percent utilization and assumes it needs to hire. But utilization at the pod level can hide that the same two seniors are at 130 percent while three juniors sit at 60. The hiring decision belongs to resource planning, not capacity. Hire to close a role gap, not to lower an average number.

Pattern two: resource planning used to estimate volume.The agency lists the people on a pitch ("we have a team of eight") and treats that as proof of capacity. But "eight people on the team" says nothing about how many of their hours are unsold for the relevant weeks. Volume is a capacity answer, not a resource one.

When both views are kept distinct, the agency owner can ask the right question at the right moment. "Do we have room?" before sales. "Who specifically?" before kickoff. "Where are we short?" before hiring.

A worked example for an agency owner

Imagine a 25-person agency reviewing two opportunities at once. The first is a six-week brand sprint that needs roughly 240 hours total. The second is a six-month retainer that needs 60 hours per month from a specific senior developer who has shipped two similar platforms.

The brand sprint is a capacity question. Open the capacity view, check free hours across the design pod for the six weeks, subtract PTO and the public holidays in those weeks, and answer. The retainer is a resource question. Open the resource view, find the named senior developer, look at her current allocations, retainers, and approved vacation, and decide whether her 60 hours per month exist on top of her existing commitments. If she is already at 40 hours of retainer load, the answer is "not without rebalancing," even if the wider team has 400 free hours.

Two opportunities, two questions, two views. Treating both as "capacity" would have produced one wrong answer.

The split also clears up a frequent argument between sales and delivery. Sales tends to think in roles ("we sold a senior strategist for healthcare"). Delivery tends to think in hours ("we have 240 free hours next month"). Both are right inside their own frame. Naming the frame, before the disagreement starts, removes most of the friction. Sales is doing resource planning. Delivery is doing capacity planning. Once that is acknowledged, the two views can be checked against each other instead of competing.

When the two views must overlap

The views are distinct but not independent. Resource planning needs the same PTO, public holiday, FTE, and retainer data that capacity uses. Otherwise the named assignment looks fine but collapses the moment vacation is approved or the retainer hits its monthly hours.

In BreezeLeave, the overlap is intentional. Approved leave, country holidays, and FTE feed both the capacity forecast and the resource assignment grid. Planned slots live in the same project planner that capacity reads. Retainer hours are part of the same client and project structure. The two views are different lenses on shared operating data, not separate tools.

For the underlying logged-hours signal that both views need, see workload capacity planning with PTO and logged hours.

Assumptions to state when you publish numbers

Either view is only as honest as its assumptions. Before sharing utilization or assignment numbers outside the delivery team, write down:

• Working week length per country.
• Buffer applied per role (for internal reviews, client calls, learning time).
• How sick leave is treated relative to capacity.
• Whether freelance FTE includes a guaranteed minimum.
• Whether retainer hours are reported monthly or weekly.

Without those notes, the same 95 percent utilization can mean "we are at the edge" or "we are quietly overcommitted." The owner needs to know which one.

Pick the view, then act

Agencies do not need a debate about definitions every week. They need a habit: when the question is volume, open the capacity view; when the question is fit, open the resource view; when the answer looks too easy, check the other one.

Ready to put PTO, holidays, retainers, and logged hours into a capacity view that already knows the difference? Plan capacity around PTO, holidays, and logged hours in BreezeLeave, or read the agency resource planning page for the role-and-FTE side.