FTE Planning for Mixed Full-Time and Freelance Teams

The resource manager at a 22-person agency is trying to answer a question that sounds simple: do we have enough design capacity for the next six weeks? The internal headcount says four designers. The reality is messier. One designer is part-time at four days a week. A second is on parental leave returning at 60 percent. A third is a contractor who confirmed availability for two of the six weeks. A fourth is full-time but holds a retainer that already eats half her calendar. Adding the headcount gives four. Adding the actual capacity gives something closer to 2.4 FTE during the weeks that matter. This article is for the resource manager and agency owner who want a capacity number that survives mixed contracts.

FTE planning works as a translation layer. Hours, contracts, and leave records get converted into one comparable unit: how much of a person is available, this week, for this work. Done well, FTE turns "we have four designers" into "we have 2.4 FTE of senior design and 1.1 FTE of production design between now and 27 June." Done badly, it produces a clean-looking number that hides the same gaps the spreadsheet did.

What FTE means in an agency

FTE is a unit. One FTE represents one person working a full standard week, before vacation, holidays, internal time, and meetings reduce the count. Most agencies set their standard week at 40 hours, although a 37.5 or 35 hour week is common in some European countries. The choice is less important than the consistency. If the rest of the plan assumes a 40 hour week, every other figure has to assume the same.

BreezeLeave models the three contract types that show up in mixed teams:

• Full-time employees count as 1.0 FTE before PTO and holidays are removed.
• Part-time employees count as a fractional FTE based on their contracted weekly hours. Four days a week against a 40 hour standard is 0.8 FTE.
• Freelancers and contractors are variable. They count as an FTE equivalent based on the hours they actually committed to, not their nominal weekly schedule. A freelancer offering 12 hours this week is 0.3 FTE, even if they call themselves full-time when asked.

That third bucket is where most agency plans go wrong. A freelancer who is "available" is not 1.0 FTE. They are whatever fraction of a week they will actually deliver against the agency's projects, after their other clients are accounted for.

The assumptions behind any FTE number

Any FTE figure depends on three assumptions. Naming them on the same page as the number is the difference between a defensible plan and a wish.

1. The standard week. 40, 37.5, or 35 hours. Stick to one across the company so capacity numbers compare.
2. What counts as available time. Subtract approved leave and public holidays before computing FTE. Decide whether internal time, meetings, and admin should be subtracted too, and apply the same rule to every contract type. A common starting point is 80 percent billable target, which gives 32 billable hours per 1.0 FTE per week on a 40 hour standard.
3. The horizon. FTE for the next two weeks is a planning number. FTE for the next quarter is a forecasting number. They are not the same kind of claim, and they should not be averaged together.

Without those three labels, a "2.4 FTE of design" number can mean anything. With them, the resource manager and the agency owner can argue about the assumption rather than the spreadsheet.

A worked example: design capacity for a six-week window

Take the agency from the opening paragraph. Four designers on the org chart. The next six weeks need to cover a brand sprint, two web builds, and the regular retainer load. Plain headcount says four. The FTE math says something different.

Standard week: 40 hours. Billable target: 75 percent, which is 30 billable hours per 1.0 FTE per week. Horizon: 28 April to 8 June. Approved leave: subtracted in advance.

The plain headcount of four converts into roughly 1.43 FTE of new design capacity per week on average, with a peak of 1.73 FTE during Iva's two confirmed weeks and a trough below 1.0 FTE during Maya's leave. The brand sprint that was sold as "the design team can absorb it" now needs an honest conversation. Either the retainer load reduces, freelance hours get extended, the brand sprint moves, or one of the three deliveries slips.

That conversation is uncomfortable to have on Monday. It is much more uncomfortable on the day the project misses its first milestone.

Freelancers need their own planning rules

Freelancers are the most flexible part of an agency team and the easiest to overcount. A few habits keep the plan honest.

Plan freelancers in committed hours, not roles. "Iva, design, two weeks" is too vague. "Iva, 12 confirmed hours per week from 12 May to 23 May, on project X" is plannable. Convert the committed hours into FTE using the same standard week as the rest of the plan, so the number compares.

Treat freelance FTE as time-windowed. Most freelancers cannot commit to the same volume every week. The plan should show their FTE only for the weeks they have confirmed, and revert to zero outside that window. A single average FTE across a six-week horizon hides the weeks where they are not booked.

Track logged freelance hours against committed hours weekly. A freelancer who agreed to 12 hours and delivered 8 is not a bad freelancer. They are a 0.2 FTE this week. The plan needs to reflect that before next week's commitments are made.

Demand expressed in FTE makes the math comparable

FTE is not only a supply unit. Project demand can be expressed in FTE as well, and that is what makes a mixed team plan readable. Instead of "we need a senior designer for six weeks," the demand becomes "we need 0.6 FTE of senior design and 0.4 FTE of production design across weeks 19 to 24." That number can be compared directly to the supply FTE table without translation.

Three demand inputs help the conversion stay honest:

• Estimated hours. Divide by the standard week to get FTE. 60 hours of design across two weeks on a 40 hour standard is 0.75 FTE.
• Role mix. Senior and production design are not interchangeable. Split the demand by role before comparing it to supply, even if the total looks balanced at a single number.
• Distribution. A project that needs 80 design hours across six weeks averages around 0.33 FTE. If the design phase has to finish in the first two weeks, the same project peaks at 1.0 FTE. The plan should show both shapes.

BreezeLeave keeps demand and supply on the same FTE basis so the comparison does not require a separate sheet. For the planning side of the same workflow, see resource planning for agency projects.

Where FTE planning quietly breaks

Four failure patterns repeat across mixed teams. Naming them helps the resource manager catch them before they hit a delivery.

• Averaged horizons. A monthly average FTE that looks healthy hides a week where every senior designer is on leave at the same time. Plan in weeks before averaging into months.
• Counting unconfirmed freelancers. A freelancer who said "yes in principle" is 0.0 FTE until the hours are confirmed in writing.
• Forgetting internal time. If 25 percent of every full-time week goes to meetings, onboarding, and internal work, subtract that before computing capacity for client projects. Pick a number, even if it is approximate, and apply it consistently.
• Stale leave data. If approved leave is recorded in one tool and capacity is planned in another, somebody will plan a project sprint over a vacation that was approved three weeks ago. Connect approved leave to the FTE view so it is subtracted automatically.

A weekly FTE habit the agency will keep

FTE planning works as a 30 minute Monday habit, not a quarterly ritual. The questions stay the same:

1. Which approved leave landed in the next six weeks since last Monday? Update the FTE supply table to reflect it.
2. Which freelance hours got confirmed or fell through? Adjust the variable FTE rows for the weeks in question.
3. Which retainers shifted load? A retainer that quietly grew from 0.3 FTE to 0.5 FTE for one person changes how much capacity that person can offer to other projects.
4. For each project starting in the window, compare demand FTE to supply FTE by role. Where the gap is more than 0.2 FTE, escalate before the project commits dates.

Three weeks of this habit usually changes how the agency talks about capacity. The conversation shifts from "do we have enough designers" to "we have 1.4 FTE of senior design free in week 21 and 0.6 FTE in week 22, so the brand sprint either starts a week earlier or moves Iva's confirmed hours forward." That is a useful disagreement to have. The general one is not.

Make the plan the conversation

The point of FTE planning is not the number. It is the conversation the number forces. A mixed team works only when full-time, part-time, and freelance contributions get compared on the same basis. Name the standard week, subtract leave, treat freelancers as windowed FTE, and review the plan weekly.

Ready to plan agency resources around PTO, FTE, and confirmed freelance hours instead of headcount? Plan agency resources around PTO and FTE in BreezeLeave, or start with the project capacity planning page for the demand side of the same view.