Headcount and FTE Calculator

Headcount and FTE

{{ formatFte(totals.fte) }} FTE

{{ formatHeadcount(totals.headcount) }} headcount {{ formatHours(totals.weeklyHours) }} weekly hours {{ formatFte(totals.ftePerHead) }} FTE/head {{ capacityGapBadge }} {{ formatPercent(totals.partTimeShare) }} part-time share {{ contractorBadge }}

Standard full-time hours:

Enter weekly hours for one full-time equivalent, such as 40 or 37.5.

hrs/week

Entry mode:

Pick employee rows for people, aggregate rows for roles, or department rows for team totals.

Include contractors:

Turn on only when contractor capacity belongs in the same headcount and FTE total.

Workforce rows:

{{ rowLabelHeader }}	Department	Contract	Hours/person	Count	Remove

{{ warning }}

Group totals by:

Choose the column used for the grouped rollup tab; overall FTE remains unchanged.

FTE cap:

Use No cap for capacity math; cap each person at 1.0 for policy-style reports.

Decimal places:

Select 1-3 decimals for displayed FTE values in summaries, tables, CSV, and JSON.

Paste rows:

Paste one row per line: label, department, contract type, weekly hours, count.

Export label:

Use a short staffing snapshot label for downloaded CSV and JSON files.

Group	Rows	Headcount	Weekly hours	FTE	FTE/head	Gap	Part-time share	Copy
{{ row.label }}	{{ row.rows }}	{{ formatHeadcount(row.headcount) }}	{{ formatHours(row.weeklyHours) }}	{{ formatFte(row.fte) }}	{{ formatFte(row.ftePerHead) }}	{{ formatFte(row.capacityGap) }}	{{ formatPercent(row.partTimeShare) }}

Enter included workforce rows with positive FTE to render the headcount vs FTE chart.

Row	Department	Contract	Status	Count	Hours/person	Weekly hours	FTE/head	FTE	Gap	Copy
{{ row.label }} {{ row.included ? row.formula : row.exclusionReason }}	{{ row.department }}	{{ contractLabel(row.contractType) }}	{{ row.classificationLabel }}	{{ formatHeadcount(row.count) }}	{{ formatHours(row.weeklyHoursPerPerson) }}	{{ formatHours(row.totalWeeklyHours) }}	{{ row.included ? formatFte(row.ftePerPerson) : 'Excluded' }}	{{ row.included ? formatFte(row.fte) : 'Excluded' }}	{{ row.included ? formatFte(row.capacityGap) : 'Excluded' }}

Check	Value	Note	Copy
{{ row.label }}	{{ row.value }}	{{ row.note }}

Export to PDF Fullscreen

Include query parameters

Embed:

Customize embed code

Include query parameters

Wrap embed in collapsible toggle

Collapse panel by default

Hide card frame (bare iframe)

Loading behavior

Width

Height

Aspect ratio (width : height)

Max height (optional)

Collapsible heading

Collapsible description (optional)

Allow fullscreen

Referrer policy

Sandbox tokens

Headcount is a count of people. Full-time equivalent, usually shortened to FTE, is a count of work capacity measured against a full-time schedule. A team with four people can still have only three FTE if some schedules are part time, and one person can show more than 1.0 FTE in a pure capacity view when weekly hours exceed the chosen full-time standard.

That difference matters whenever staffing, budget, or workload planning depends on capacity rather than names on a roster. Headcount is useful for span of control, access lists, seats, and onboarding. FTE is more useful when a finance team, HR partner, or operations manager needs to compare available weekly hours across departments, roles, contractors, temporary staff, and part-time schedules.

Diagram comparing four people counted as four headcount with eighty weekly hours converted to two FTE

A standard full-time week is a policy choice, not a universal constant. Many organizations use 40 hours, some use 37.5 or 35, and some legal or statistical programs use their own thresholds. The important step is to choose the standard that matches the report you are preparing before comparing departments or periods.

FTE is planning arithmetic. It does not prove whether someone is eligible for benefits, whether a contractor should be counted as an employee, or whether a workforce count meets a formal rule. For those questions, the FTE number should be checked against the organization policy, contract terms, or program-specific definition that controls the decision.

Technical Details:

FTE is built from a ratio. Scheduled weekly hours are divided by the standard full-time weekly hours, then multiplied by the number of people represented by the row. This keeps the math consistent across individual employee rows, aggregate role rows, and department totals as long as each row uses hours per person and the same full-time standard.

The ratio also explains why headcount and FTE can move in different directions. Two people working half of the standard week produce 2 headcount and 1.0 FTE. A single included person working 48 hours against a 40-hour standard produces 1 headcount and 1.2 FTE unless the reporting rule caps each person at 1.0 FTE.

Formula Core

The calculation starts per person, then scales to the row count. When the cap is active, the per-person ratio is limited before multiplying by count.

\begin{array}{lcl} FTE per head & = & \frac{weekly hours per person}{standard full-time hours} \\ Row FTE & = & FTE per head \times row count \\ Capped FTE per head & = & min (1, \frac{weekly hours per person}{standard full-time hours}) \\ Headcount minus FTE & = & included headcount - included FTE \end{array}

Headcount and FTE calculation rules
Rule area	Supported behavior	What to verify
Standard full-time hours	Any positive weekly standard, with a warning when the value is below 20 or above 60	Use the same standard across departments when totals need to compare fairly.
Entry mode	Employee rows force count to 1; aggregate and department rows use the entered count	Use hours per person, not total group hours, when count is greater than 1.
Contract type	Employee, temporary, and intern rows are included; contractor rows are excluded unless the contractor toggle is on	Confirm whether the report needs workforce capacity, employee-only capacity, or a contractor-inclusive view.
FTE cap	No cap allows overtime rows above 1.0 FTE per head; the cap option limits each person to 1.0	Choose the cap rule that matches the reporting policy, not the rule that makes the total look cleaner.
Grouping	Rollups can group by department, contract type, or row label without changing the row math	Use grouping for review and presentation; do not treat it as a different calculation.

Classification labels come from each row's included status and weekly schedule. A row below the standard is part time. A row equal to the standard is full time. A row above the standard is overtime unless it is excluded by the contractor setting. A row with zero weekly hours stays visible but contributes no capacity.

Main output fields for headcount and FTE results
Output	Meaning	Typical use
Headcount	Included row counts added together	People count, seat planning, roster size, and staffing conversations.
FTE	Included weekly hours converted to full-time-equivalent capacity	Budget capacity, workload coverage, and department comparisons.
Weekly hours	Included count multiplied by weekly hours per person	Checking whether the FTE total agrees with the raw capacity behind it.
FTE/head	Total FTE divided by included headcount	Quick read on how full-time or part-time the included roster is on average.
Gap	Headcount minus FTE	Spotting part-time mix, overtime, and the effect of a cap rule.
Part-time share	Included heads with positive weekly hours below the standard, divided by included headcount	Explaining why FTE may be much lower than the people count.

Formal programs may define full-time and full-time equivalent counts differently. The U.S. Bureau of Labor Statistics uses 35 hours for its Current Population Survey full-time classification, while IRS employer shared responsibility rules use a 30-hour or 130-hour monthly full-time test and a separate monthly FTE method for certain employer-size determinations. Those examples are useful reminders that a general weekly FTE worksheet should not be used as a compliance ruling.

Everyday Use & Decision Guide:

Set Standard full-time hours before entering rows. Use 40 only when that is the standard for the report. If the organization reports a full week as 37.5 or 35 hours, that value should drive the FTE total so part-time and full-time rows compare against the right denominator.

Choose Entry mode from the source data you have. Employee rows work well when each row is one person or an anonymous person-level record. Aggregate rows fit role summaries such as three analysts at 30 hours each. Department rows fit a higher-level planning view when each row represents a team with one average schedule.

The contractor toggle is worth checking before reading any headline number. With Include contractors off, contractor rows still appear in the row table but do not add to headcount, FTE, group totals, or the chart. With it on, contractor capacity is included alongside employee, temporary, and intern rows.

Roster Rollup is the best first tab for department, contract type, or row-label totals.
Headcount vs FTE shows where people count and capacity diverge by group.
Row Math is the audit view for count, hours per person, FTE/head, row FTE, and row gap.
FTE Checks gives quick tie-outs for the formula, half-time example, grouped totals, capacity gap, and contractor setting.
JSON keeps the settings, summary, groups, rows, checks, and warnings together for review.

The pasted row box is useful for spreadsheet notes. Paste rows as label, department, contract type, weekly hours, and count. Rows that do not have enough fields are skipped, so scan Row Math after pasting to make sure the expected roles or departments appeared.

Use the result as a staffing snapshot, then match it to the decision at hand. A high headcount with low FTE can be normal for a part-time-heavy roster. A negative gap can be a sign of overtime or an uncapped rule. A contractor-inclusive result may be right for capacity planning and wrong for employee-only reporting.

Step-by-Step Guide:

Work from the reporting rule to the rows, then use the tabs to check both the headline and the row math.

Enter Standard full-time hours. The summary line should later repeat that standard, such as a 40.00 hr full-time standard.
Choose Entry mode. If you choose employee rows, the Count field is fixed at 1 for each row.
Fill Workforce rows with a row label, department, contract type, hours per person, and count. Use Add row for manual entry or Apply pasted rows for CSV or tab-separated text.
Open Advanced if you need to change Group totals by, turn on Cap each person at 1.0 FTE, adjust Decimal places, or add an export label.
Set Include contractors to match the report. The contractor badge should tell you how many contractor heads are included or excluded.
Read the summary badges for total headcount, weekly hours, FTE/head, capacity gap, part-time share, and contractor treatment.
Clear any warning before relying on the result. Common fixes are setting standard hours above zero, checking unusual standards, correcting zero-hour rows, or deciding whether an overtime row should be capped.
Use Roster Rollup, Row Math, and FTE Checks for review before copying CSV, exporting DOCX, saving the chart, or copying the JSON payload.

Interpreting Results:

Start with total FTE and headcount together. FTE tells you the full-time-equivalent capacity in the included rows. Headcount tells you how many included people or row counts produced that capacity. Neither number replaces the other.

The capacity gap is often the fastest explanation. A positive gap means headcount is larger than FTE, usually because part-time rows are present. A gap near zero means the roster is close to the selected full-time standard. A negative gap means FTE is above headcount, usually because overtime rows are uncapped.

How to interpret headcount and FTE output cues
Cue	Read it this way	Do not overread it as
High headcount, lower FTE	The roster has part-time capacity or lower-hour rows.	A staffing problem by itself; it may match the intended model.
FTE/head below 1.0	The average included head is below the full-time standard.	Proof that every person is part time; the row table may include a mix.
FTE/head above 1.0	At least one included row exceeds the standard and the cap is not limiting it.	A benefits or employment-status decision.
Contractor heads excluded	Contractor rows are visible but left out of summary and group totals.	Evidence that contractors do not work hours; the toggle is a reporting choice.
Grouped totals tie out	The rollup rows add back to the overall included headcount and FTE.	A different calculation from the row-level formula.

Warnings deserve review even when the output looks tidy. A zero count, zero weekly hours, unusual standard week, fractional count, or overtime row can all be intentional, but each one changes how confidently the result can be used in a staffing or budget conversation.

Worked Examples:

Part-time mix with contractors excluded

With a 40-hour standard, two customer support associates at 20 hours each, one operations coordinator at 40 hours, and one finance analyst at 32 hours produce 4 headcount, 112 weekly hours, and 2.80 FTE. The FTE/head badge reads 0.70, and the capacity gap is 1.20 FTE below headcount. A 16-hour implementation contractor stays out of those totals when Include contractors is off.

Including contractors for a capacity view

Turn Include contractors on for the same rows and the contractor adds 0.40 FTE. The summary becomes 5 headcount, 128 weekly hours, and 3.20 FTE. In Roster Rollup, grouping by department can show Operations with the employee coordinator and the contractor together, which is useful for workload capacity but may not be appropriate for employee-only reporting.

Overtime row and the cap setting

A single specialist working 48 hours against a 40-hour standard appears as 1.20 FTE/head and 1.20 FTE when No cap is selected. Row Math labels the row as overtime and the summary gap becomes negative because FTE is above headcount. If the report must never count more than 1.0 FTE per person, switch FTE cap to Cap each person at 1.0 FTE and check that the row now reads 1.00 FTE.

Pasted rows that need review

A pasted line such as Support analyst,Customer Care,employee,20,2 creates an aggregate row with two heads at 20 hours per person. A shorter line without label, department, contract type, weekly hours, and count can be skipped. After using Apply pasted rows, scan Row Math for the expected labels and read the warning area before exporting.

FAQ:

What standard full-time hours should I enter?

Use the standard for the report you are preparing. Forty hours is common, but 37.5 or 35 may be correct for some organizations. The tool warns when the standard is below 20 or above 60 because those values are unusual for weekly FTE work.

Why does FTE not match headcount?

Headcount adds people or row counts. FTE converts weekly hours into full-time-equivalent capacity. Two people at half of the standard week are 2 headcount and 1.0 FTE.

Are contractors included in the totals?

Only when Include contractors is on. Contractor rows remain visible either way, but with the toggle off they are excluded from total headcount, FTE, group totals, and chart rows.

Why can one row show more than 1.0 FTE per head?

When No cap is selected, weekly hours above the standard produce more than 1.0 FTE per head. Use Cap each person at 1.0 FTE when your report treats overtime as extra hours without increasing the per-person FTE count.

Can I paste spreadsheet rows?

Yes. Paste comma-separated or tab-separated rows in this order: label, department, contract type, weekly hours, and count. After applying pasted rows, check Row Math because malformed lines can be skipped.

Are workforce rows sent to a server for calculation?

No server-side FTE calculation helper is part of this tool. The rows, tables, chart data, and exports are generated in the page. Use non-identifying labels when the output may be copied, downloaded, or shared.

Can this be used for ACA, benefits, or legal headcount rules?

Use it as a general staffing and capacity worksheet, not as a compliance calculator. Programs such as employer shared responsibility rules can define full-time employees, hours of service, and FTE counts differently from a weekly planning worksheet.

Glossary:

Capacity gap: Headcount minus FTE. Positive values usually reflect part-time rows, while negative values usually reflect uncapped overtime rows.
FTE: Full-time equivalent capacity, calculated by comparing weekly hours with the selected full-time standard.
FTE cap: A rule that limits each person's FTE contribution to 1.0 before multiplying by row count.
FTE/head: Total FTE divided by included headcount, used as an average capacity read per included head.
Headcount: The number of included people or row counts, before converting hours into FTE.
Part-time share: The share of included headcount with positive weekly hours below the selected standard full-time hours.
Standard full-time hours: The weekly hours that count as 1.0 FTE for the report being prepared.