A unit of measurement that standardizes employee workloads by converting part-time, seasonal, and contract hours into the equivalent of a full-time worker, typically based on a 40-hour workweek or 2,080 annual hours.
Key Takeaways
FTE is how HR and finance translate a messy workforce of full-timers, part-timers, contractors, and seasonal staff into one clean number. It answers a simple question: how many full-time workers' worth of labor does this organization actually use? Think of it like converting currencies. You can't compare a team of 20 (half part-time) to a team of 15 (all full-time) without a common unit. FTE gives you that unit. It doesn't care about headcount. It cares about hours. A company with 100 employees on paper might only have 82 FTEs when the math is done. That distinction matters for budgeting, compliance, and staffing decisions. Every workforce planning model, cost-per-hire calculation, and revenue-per-employee benchmark depends on accurate FTE counts. Using headcount when you should be using FTE inflates your denominator and makes your ratios look worse than they actually are.
The core formula is straightforward, but real-world scenarios introduce complexity.
FTE = Total hours worked by the employee per week / Standard full-time hours per week. If your organization defines full-time as 40 hours per week, an employee working 40 hours is 1.0 FTE. Someone working 30 hours is 0.75 FTE. On an annual basis: FTE = Total annual hours worked / 2,080. A seasonal employee who works 6 months at 40 hours per week (1,040 hours) counts as 0.5 FTE for the year.
To calculate total FTE for a department or organization, add individual FTEs together. If you have 50 full-time employees (50.0 FTE) and 20 part-time employees each working 20 hours per week (10.0 FTE), your total is 60.0 FTE from a headcount of 70 people. For ACA purposes, the IRS requires a monthly FTE calculation: add up total employee hours for the month (capped at 130 per employee) and divide by 120. This method treats 30 hours per week, not 40, as the full-time threshold.
Don't include overtime hours in FTE calculations. An employee who works 50 hours per week is still 1.0 FTE, not 1.25. FTE caps at 1.0 per person for standard reporting. Also, be clear about whether you're calculating annual FTE or point-in-time FTE. A contractor who worked January through June at full-time hours has an annual FTE of 0.5, but during those months their point-in-time FTE was 1.0. Mixing these up skews planning and compliance data.
Both metrics matter, but they answer different questions. Using the wrong one leads to bad decisions.
| Dimension | FTE | Headcount |
|---|---|---|
| What it measures | Total labor capacity in full-time equivalents | Number of individual employees on payroll |
| Part-time treatment | Fractional (0.5, 0.75, etc.) | Counts as 1 regardless of hours |
| Best for | Budgeting, capacity planning, cost-per-employee metrics | Benefits administration, office space planning, DEI reporting |
| ACA compliance | Required for determining employer mandate threshold | Not sufficient for ACA calculations |
| Revenue benchmarking | Revenue per FTE is the standard benchmark | Revenue per headcount can be misleading with many part-timers |
| Seasonal workers | Prorated based on hours actually worked | Counted at 1 during active employment |
| Contractor inclusion | Sometimes included for capacity planning | Typically excluded from headcount reports |
Several federal and state regulations use FTE thresholds to determine employer obligations. Accurate FTE tracking isn't optional for these.
Employers with 50 or more FTEs (called Applicable Large Employers, or ALEs) must offer affordable minimum essential coverage to full-time employees. The IRS defines full-time as averaging 30 hours per week or 130 hours per month. The penalty for non-compliance is $2,970 per full-time employee per year (2024 amount) minus the first 30 employees. Miscounting FTEs can mean either paying unnecessary penalties or failing to offer required coverage.
The Family and Medical Leave Act applies to employers with 50 or more employees within 75 miles. This uses headcount, not FTE, but some states have lower thresholds and different counting methods. Understanding the distinction prevents compliance gaps.
During COVID-era Paycheck Protection Program loans, FTE was central to loan forgiveness calculations. Employers had to track FTE changes between reference periods. Those who couldn't produce accurate FTE records faced reduced forgiveness or repayment requirements. While PPP has ended, it demonstrated why maintaining clean FTE data matters: you never know when a program or regulation will require it.
FTE shows up in nearly every HR planning and analysis function. Here are the most common applications.
The baseline for 1.0 FTE varies globally because standard workweeks differ by country and industry.
| Country/Region | Standard Full-Time Hours/Week | Annual FTE Hours | Notes |
|---|---|---|---|
| United States | 40 | 2,080 | ACA uses 30 hours/week as full-time threshold |
| United Kingdom | 37.5 | 1,950 | Contractual hours vary widely by sector |
| Germany | 38-40 | 1,976-2,080 | Collective agreements often specify lower hours |
| France | 35 | 1,607 | Legal 35-hour workweek since 2000 |
| Netherlands | 36-40 | 1,872-2,080 | High part-time rate (nearly 50% of workforce) |
| Japan | 40 | 2,080 | Overtime isn't included in FTE count |
| Australia | 38 | 1,976 | National Employment Standards baseline |
| India | 48 | 2,496 | Factories Act standard; IT sector often uses 40 hours |
Data points that illustrate why FTE tracking matters more than ever as workforce composition shifts.
Keeping FTE data clean requires discipline, especially in organizations with high part-time usage or seasonal fluctuations.