Work schedules

FTE Workload Converter

Convert weekly hours into full-time-equivalent workload and annual capacity.

PrivacyRuns in your browser
OutputAnalytics dashboard
CostFree to use
Analytics dashboard

Enter your details

Adjust the planning assumptions below.

Enter Weekly hours in hours and keep that unit consistent with the other duration fields.

Use the Full-time weekly standard value stated in weeks; do not mix it with a differently scaled duration.

Use the Paid weeks per year value stated in weeks; do not mix it with a differently scaled duration.

Enter Unpaid weeks in weeks and keep that unit consistent with the other duration fields.

Calculations stay in this browser. Saved inputs and recent results use local browser storage until you clear them.

Your schedule will appear here

Results update after calculation and include a visual timeline, calendar, or dashboard.

Purpose

Frame the time problem correctly

Convert weekly hours into full-time-equivalent workload and annual capacity.

This page focuses on weekly workload expressed as a full-time-equivalent share. Its most useful role is to compare workloads using an explicit full-time weekly standard. Viewed in the context of FTE workload ratios, before entering live data, start by deciding which schedule, employee group, or reporting period the entries describe; mixing cases can produce a precise-looking answer that belongs to no real roster.

Keep the scope narrow: FTE is a ratio, not a headcount, contract status, or productivity score. At the outset, the result is strongest when Weekly hours and Unpaid weeks come from the same documented scenario and use the conventions stated on the page.

Input quality matters more than extra decimals

While checking the entries, the calculation depends on Weekly hours, Full-time weekly standard, Paid weeks per year, and 1 additional fields. With the FTE workload ratios source record in view, during data preparation, record the values before changing them so a later run can be compared with the same baseline. While preparing the FTE workload ratios entries, while checking the entries, dates and clock times should retain their local context; hour counts and percentages should retain their units.

  • Weekly hours: Enter Weekly hours in hours and keep that unit consistent with the other duration fields.
  • Full-time weekly standard: Use the Full-time weekly standard value stated in weeks; do not mix it with a differently scaled duration.
  • Paid weeks per year: Use the Paid weeks per year value stated in weeks; do not mix it with a differently scaled duration.
  • Unpaid weeks: Enter Unpaid weeks in weeks and keep that unit consistent with the other duration fields.

For the input record, review the relationship between Weekly hours and Unpaid weeks, not just each value in isolation. For this FTE workload ratios dataset, for a consistent scenario, a transposed boundary, a duration copied in the wrong unit, or a count taken from another period can change the meaning while leaving every field technically valid.

The rule used by this calculator

Weekly hours are divided by the full-time standard and multiplied by active paid weeks.

FTE = weekly hours ÷ full-time weekly standard; annual hours = weekly hours × active paid weeks.

In the arithmetic for FTE workload ratios, in the unrounded work, read the formula from left to right and attach each term to its field. For weekly workload expressed as a full-time-equivalent share, intermediate values should remain unrounded until the final display. As part of the FTE workload ratios method, while following the rule, where the output counts people, days, sessions, or shifts, confirm whether the operational decision requires rounding up, rounding down, or preserving a fractional planning value.

At the unit check, a second run with only Unpaid weeks changed is an effective sensitivity check. While recomputing FTE workload ratios, for the calculation path, it shows whether the result moves in the expected direction and helps distinguish a formula response from a data-entry mistake.

Independent checks for the schedule

In the independent FTE workload ratios check, at the audit step, a useful review is independent of the calculate button. While verifying FTE workload ratios, during verification, read the source schedule, estimate the broad direction and magnitude, and then compare that expectation with the displayed output.

  • State the full-time weekly standard.
  • Use paid or scheduled hours consistently.
  • Check whether the result is per person or for a group.

For the FTE workload ratios reconciliation, before publication, if a check fails, do not force the answer to match. Before accepting the result, save the entered case, identify which assumption differs from the source record, and rerun the FTE Workload Converter with the corrected value.

Interpretation

Understanding the output hierarchy

Interpretation FTE expresses workload relative to a standard and should not be read as a person count or performance measure. Verify Weekly hours, Full-time weekly standard, and Paid weeks per year beside the FTE Workload Converter headline; Unpaid weeks reveals rounding across the secondary measures.

The FTE Workload Converter dashboard places secondary measures beside Weekly hours, Full-time weekly standard, Paid weeks per year, and Unpaid weeks. Verify Unpaid weeks in its original unit before accepting the secondary measures or headline status.

When interpreting FTE workload ratios, when explaining the output, state the answer with its noun and time basis—for example, hours in the selected period, active teams on the generated date, or planned participants under the entered capacity. That wording helps prevent the result from being reused as FTE is a ratio, not a headcount, contract status, or productivity score.

Worked case

Work through the default scenario

Worked scenario Example: Thirty-two weekly hours against a forty-hour standard equals 0.8 FTE before unpaid weeks reduce annual capacity. Reconcile Unpaid weeks with the FTE Workload Converter secondary measures before judging the Unpaid weeks headline scale or units.

In this FTE workload ratios example, for the demonstration values, recreate the sample before substituting live data. When reproducing the FTE workload ratios sample, during a sample run, note the starting values, the intermediate relationship described by the formula, and the final unit. For the illustrated FTE workload ratios case, for the demonstration values, change one assumption at a time; that approach makes it easier to explain why the result changed.

In practice, use the worked case to compare workloads using an explicit full-time weekly standard. In this FTE workload ratios example, while checking the default case, do not copy the sample answer into a schedule—the example demonstrates the method, while the live result must be rebuilt from the actual record.

Scope

Separate the calculation from the decision

This calculator answers a specific question about weekly workload expressed as a full-time-equivalent share. Fte is a ratio, not a headcount, contract status, or productivity score. When distinguishing FTE workload ratios from nearby calculations, for a different decision, similar totals may originate from the same work record while describing different concepts, so compare tools by the output noun and denominator rather than by the size of the number.

At the boundary of the FTE workload ratios model, for the adjacent question, before transferring the result, write a one-sentence interpretation that names the period and population. For the specific FTE workload ratios question, before transferring the number, if that sentence requires a different verb—such as approve, guarantee, diagnose, or determine eligibility—the decision has moved beyond the calculator's scope.

Recordkeeping

Make a later rerun possible

In the saved FTE workload ratios record, for the next reviewer, someone reviewing the result later should be able to recreate it without guessing. For a reproducible FTE workload ratios rerun, in the saved record, store the following items with the output:

  • weekly hours
  • full-time standard
  • period and population

Within the FTE workload ratios audit trail, at the reporting handoff, also retain the calculation date and the version of any schedule, policy, holiday list, or staffing assumption used. In the saved FTE workload ratios record, during documentation, label superseded runs instead of silently replacing them; that preserves the reason a past decision looked reasonable at the time.

Workflow

An operational use for the result

Practical use Confirm the organization's full-time standard and whether unpaid periods reduce the capacity being reported.

The practical decision is to compare workloads using an explicit full-time weekly standard. When applying the FTE workload ratios result, in the operational workflow, put the result beside the roster, timesheet, capacity plan, or approval record it informs. In the workflow built around FTE workload ratios, in the working plan, a detached number loses the dates, people, and operating assumptions that made it meaningful.

For the next FTE workload ratios decision, when the baseline changes, when the schedule changes, create a new run rather than editing the old result. During implementation, comparing the two cases shows whether the difference comes from Weekly hours, Unpaid weeks, or a broader policy or coverage change.

Handoff

Before the next reporting period

Before publishing a result from the FTE Workload Converter, ask who owns the source schedule, who can approve exceptions, and when the next source update will occur. Those questions matter because different full-time standards, seasonal schedules, job sharing, and unpaid time can change the appropriate denominator.

Keep the original Weekly hours and Unpaid weeks values beside any revised case. For FTE workload ratios, explain which field changed, why it changed, and whether the operational conclusion changed with it. In a FTE workload ratios review, this small reconciliation step prevents a later reader from treating two different scenarios as duplicate calculations.

Finally, compare the calculated weekly workload expressed as a full-time-equivalent share output with an observable schedule fact: a known shift boundary, a recent period total, an actual queue observation, or an approved capacity figure. Within the FTE workload ratios record, the comparison is not a replacement formula; it is a reasonableness test that can expose an incorrect unit or an outdated source record.

What still requires policy or human judgment

An FTE ratio measures scheduled workload, not productivity, headcount, or benefit eligibility. Alter Unpaid weeks in the FTE Workload Converter before reading the secondary measures or headline.

different full-time standards, seasonal schedules, job sharing, and unpaid time can change the appropriate denominator

For policy-controlled treatment, use the FTE Workload Converter as transparent arithmetic, not as a substitute for the controlling agreement, published schedule, payroll record, or responsible reviewer. At the practical limit of FTE workload ratios, where an outside rule applies, where consequences are material, resolve discrepancies before the result is distributed.

Common questions before using FTE Workload Converter

Does 0.8 FTE always mean four workdays per week?

No. The same ratio can be distributed across different days, shifts, or seasonal patterns.

Does Unpaid weeks alter every part of the fte workload converter result?

Store Weekly hours and Full-time weekly standard unchanged and alter Unpaid weeks once in the FTE Workload Converter. Reconcile the Unpaid weeks component with secondary measures to identify a proportional or threshold effect.

How does Unpaid weeks qualify the fte workload converter headline?

The FTE Workload Converter headline compresses Weekly hours and Full-time weekly standard, so reconcile it with Unpaid weeks and secondary measures. The Unpaid weeks denominator then exposes rounding in the FTE Workload Converter.