FTE stands for full-time equivalent. One FTE equals one person working full time for the period you are measuring. A person working half time on a project is 0.5 FTE. Three people each contributing one day a week are 0.6 FTE combined.
Project managers and PMOs use FTE instead of headcount because headcount doesn't tell you how much work the team can actually do. A developer nominally assigned to three projects contributes fractional capacity to each one, not full capacity to all three. FTE makes that fraction explicit.
Why FTE matters more than headcount in IT planning
IT projects almost always involve people who are shared across multiple assignments. A developer might be 50% on a new platform build, 30% on a maintenance contract, and 20% on a backlog of enhancements. Their headcount contribution to the platform project is 1. Their FTE contribution is 0.5.
When you plan at the headcount level, this disappears. Projects get resourced based on who's assigned, not on how much of their capacity is actually available. That is how schedules slip without anyone being able to explain why. The estimate wasn't wrong. The available effort was never accurately measured.
How to calculate FTE demand for a project
Start with the estimated hours of work the project requires. Then divide by the net available hours per FTE in your planning period.
In a standard 40-hour week environment, one person working for a full quarter generates:
- 13 weeks x 40 hours = 520 gross hours per FTE per quarter
But gross hours are not net project hours. IT professionals typically spend 20 to 30% of their time on non-project work: team meetings, training, operational tasks, support tickets, and administrative overhead. Subtract that and you get net project hours:
- At 75% availability: 520 x 0.75 = 390 net hours per FTE per quarter
- At 85% availability: 520 x 0.85 = 442 net hours per FTE per quarter
To calculate FTE demand for a project:
FTE demand = Total project hours required ÷ Net hours per FTE per period
A project requiring 880 hours of development work in Q3, using a 75% availability assumption, needs 880 ÷ 390 = 2.26 FTEs. Round up to 2.5 FTEs to build in a small buffer.
Accounting for skill type
FTE demand must be broken out by skill area, not just totalled. Two FTEs of generalist developer capacity does not substitute for one FTE of security architecture. The demand calculation needs to specify:
- Development FTE demand
- QA/testing FTE demand
- Architecture FTE demand
- Project management FTE demand
- Business analysis FTE demand
A project that looks well-resourced in total FTE terms may be critically short in one specific skill. That shortage will show up as a bottleneck halfway through delivery.
Building a portfolio-level FTE picture
The real value of FTE planning is at the portfolio level. Once you have calculated FTE demand for each approved project, you can aggregate across the portfolio by skill area and compare against available supply:
| Skill area | Available FTE | Portfolio demand (FTE) | Gap |
|---|---|---|---|
| Development | 9.0 | 12.5 | +3.5 |
| QA / Testing | 3.5 | 2.8 | -0.7 |
| Architecture | 1.5 | 3.2 | +1.7 |
| Project management | 2.0 | 2.4 | +0.4 |
This view shows that QA has surplus capacity while development and architecture are materially constrained. Approving more projects without addressing those constraints will slow everything already in flight.
FTE vs headcount: when to use each
Use FTE when sizing project demand, comparing work volume across periods, or planning for people who are shared across multiple projects. FTE is the right unit for portfolio capacity planning because it reflects how much productive time is actually available, not just how many people show up.
Use headcount when making hiring decisions, reporting team size for budget purposes, or when a role requires 100% dedication to a single project. If a project needs a dedicated program manager from start to finish, that is a headcount decision, not an FTE calculation.
The planning mistakes that make every schedule optimistic
Planning at the role level only. "We need a PM, two developers, and a QA engineer" describes a team composition but not how much of each person's time the project actually requires. Always convert role assignments to FTE fractions before committing to a schedule.
Ignoring non-project time. IT teams typically spend 20 to 30% of their time on work outside the project portfolio: operational support, routine maintenance, internal meetings, and administrative tasks. Capacity plans that ignore this are structurally optimistic before a single project scope changes.
Treating FTE demand as fixed. Project scope changes. A two-month delay in a dependency changes the demand profile for the next quarter. FTE demand estimates should be reviewed when scope changes significantly, not left in place from the original approval.
Aggregating without separating by skill. A combined surplus of 2 FTEs at the portfolio level provides no comfort if development is short 3 FTEs and QA has 5 FTEs of surplus. The skill-level breakdown matters more than the total.
How often to update FTE plans
Most IT PMOs run capacity reviews quarterly. That cadence aligns with the planning cycle and gives enough time to act on what the numbers show. Some organizations run monthly reviews when the portfolio is changing quickly or when demand is volatile.
The right cadence is whatever keeps the capacity picture accurate enough to make real decisions. A quarterly FTE plan that is never revisited becomes fiction by month two.
For a broader look at how FTE demand fits into portfolio decision-making, see our guide on capacity vs demand gap analysis in IT portfolio management. For how FTE planning connects to agile delivery teams, the sprint capacity vs portfolio capacity planning article covers how these two levels relate.
Frequently Asked Questions
What is an FTE in IT project planning?
FTE stands for full-time equivalent. One FTE equals one person working full time for the period being measured. A person allocated at 50% to a project contributes 0.5 FTE. FTE is used instead of headcount because headcount does not account for part-time allocations or people shared across multiple projects.
How do you calculate FTE demand for an IT project?
Estimate the total hours of work required. Divide by the net available hours per FTE in your planning period, typically 390 to 440 hours per quarter after deducting overhead. A project requiring 880 hours of work in a quarter needs approximately 2.0 to 2.3 FTEs depending on your availability assumption.
What is the difference between FTE and headcount?
Headcount is the number of people on a team regardless of allocation. FTE is a normalized measure of working time. A team of ten people, half of whom are allocated at 20% to a project, has a headcount of ten but contributes only 1.0 FTE to that project. FTE is more useful for sizing project demand; headcount is more useful for hiring decisions.
Why do IT projects use FTE instead of hours?
FTE makes it easier to compare demand across planning periods and to aggregate across a portfolio. Saying a project needs 2 FTEs for Q3 is easier to communicate and compare than 880 hours, especially when combining estimates across multiple projects with different durations and team compositions.