Budgeted FTE describes the full-time-equivalent capacity included in a plan. Actual FTE describes an observed quantity calculated from actual staffing or hours, using a defined method. The difference is a variance, but the interpretation depends on what “actual” means. Actual contracted hours, paid hours and worked hours can produce different results for the same team.
Before investigating a gap, write down the numerator, denominator, period and population used in each measure. Comparing a monthly budget based on scheduled hours with an actual figure based on productive hours mixes two definitions. A difference between those numbers may reflect measurement choices rather than a staffing problem. The FTE calculator can verify the arithmetic once the inputs are aligned.
Set a common basis for comparison
Suppose the planning baseline is 40 scheduled hours per week for one FTE. A budget of eight FTE therefore represents 320 scheduled hours per week. To compare actual scheduled capacity, sum the included weekly schedules and divide by the same 40-hour baseline. Keep overtime or other exceptions separate unless the measure explicitly includes them.
If the reporting period is a month, decide whether both measures use a fixed annualized convention or the actual scheduled calendar. Mixing those approaches can create a recurring variance simply because months have different numbers of weekdays. State the method so readers do not interpret a calendar effect as an unexpected staffing change.
The monthly work hours guide explains that distinction. Use a shared definition for comparisons across months or teams, and retain a separate actual-hours view where it answers a different operational question. Consistency is more useful than a number that looks precise but changes meaning between reports.
Calculate the variance in hours and FTE
Imagine a weekly budget of 320 scheduled hours and actual scheduled capacity of 292 hours. The hours variance is 292 − 320 = −28 hours. Dividing each by the 40-hour baseline gives 7.3 actual FTE against 8.0 budgeted FTE, a variance of −0.7 FTE.
The relative variance is −28 ÷ 320 = −8.75%. Include the sign convention in the report. In this example, a negative value means actual scheduled capacity is below budget. Another organization might label the same gap as a positive vacancy requirement, so an unlabeled sign can create confusion.
Show hours alongside FTE because hours make the operational scale easier to understand. A gap of 0.7 FTE could mean 28 hours under the example's baseline, but a different denominator would imply a different hour total. Keeping both values visible also makes the calculation easier to audit.
Separate vacancies from reduced schedules
Suppose the 28-hour gap contains a vacant 20-hour role and an eight-hour reduction in another employee's weekly schedule. Those causes add to the same total gap but require different actions. Filling the vacancy would restore 20 hours. Reversing the schedule reduction would restore the remaining eight, if that change were appropriate and feasible.
Build a bridge from budget to actual using specific causes. Start with budgeted hours, subtract unfilled planned hours, add approved capacity above plan, and show schedule changes separately. The categories should be mutually understandable and should reconcile to the total, without counting one missing hour in two causes.
Avoid using a broad label such as “absence” for every difference. A vacant role, a planned leave period and a data delay are not equivalent. Their expected duration, ownership and operational response differ. A useful variance report supports action by identifying what changed and who can resolve it.
Distinguish paid, worked and productive hours
An employee may remain on a full contracted schedule while some hours are allocated to paid leave or training. A contracted-FTE report may show no change. A worked-hours report may show fewer hours, and a productive-service report may show a different reduction again. None of those views is automatically wrong; they answer different questions.
For example, 320 scheduled hours less 24 hours of leave and 16 hours of training leaves 280 hours for the measured service under those assumptions. That is 7.0 productive-hour equivalents on a 40-hour reference, but it does not necessarily mean only seven contracted FTE are employed.
The productive versus scheduled hours guide helps keep the layers clear. If management needs both budget accountability and service capacity, present both measures with their definitions. Trying to make one number perform both jobs can conceal the reason a fully staffed team still struggles to cover demand.
Account for joiners, leavers and timing
A month-end snapshot counts the staffing position at one point in time. A period-average or hours-based measure describes the interval. A person who joins near the end of the month may count in the final snapshot while contributing relatively little capacity during that month. This is a timing difference, not necessarily a data error.
Choose a method appropriate to the decision. A snapshot can help describe the current organization. Period hours can help explain delivered capacity. If you compare them, explicitly identify the mismatch and avoid treating every difference as a missing employee or an incorrect payroll record.
Keep start dates, end dates and effective dates for schedule changes in the supporting data. An approved change may be reflected in the budget before it becomes effective in the actual staffing record. A short timing bridge can explain that variance more clearly than repeatedly revising the historical figures to make them match.
Check whether extra hours conceal a structural gap
Actual worked hours can meet the budget even when planned positions remain vacant. Suppose a team is short 20 scheduled hours but supplies 20 additional hours through temporary arrangements or extra work. The total hours may match the plan, while the staffing arrangement, cost and sustainability differ.
Show those hours separately rather than allowing a matched grand total to end the review. Ask whether the additional capacity occurs at the required times and has the necessary skills. A total of 320 hours does not prove that every service interval is covered. The coverage gaps guide explains that limitation.
Do not infer cost directly from FTE variance. Two arrangements with equal hours can have different rates, premiums and other costs. Keep a parallel cost view when the decision involves spending, and make its assumptions explicit. The FTE calculation is a capacity comparison, not a complete labor-cost model.
Turn the variance into a practical action plan
For each material cause, record the hours affected, the expected duration, the owner and the proposed response. A temporary gap may call for rescheduling or a short-term arrangement. A continuing gap may require a revised hiring plan, changed demand assumptions or a review of the budget itself.
Prioritize by service impact as well as size. A small gap in a uniquely skilled role can matter more than a larger gap that falls during low demand. Use the shift coverage calculator where interval coverage is the issue, and the staffing capacity gap guide for a broader workload comparison.
At the next review, compare the expected resolution with what actually happened. Keep explanations specific enough to learn from repeated variance. If the same gap appears every month, investigate whether the plan assumes hiring or productive availability that the operation consistently cannot achieve, rather than treating each month as an isolated surprise.
Frequently asked questions
Is actual FTE the same as headcount?
No. Headcount counts people according to a defined population. FTE expresses included hours relative to a full-time baseline. A team can increase headcount while adding less than one FTE if the new schedules are part-time. See the FTE versus headcount guide.
Does being under budget mean the team is efficient?
Not necessarily. Lower hours or cost may accompany unmet demand, vacancies or deferred work. Compare the staffing result with service, workload and quality measures before interpreting it as an improvement.
How much variance is acceptable?
There is no universal percentage for every team. Set a review threshold based on operational risk, data reliability and the decisions the report supports. Explain significant causes even when a favorable-looking total hides a problem in a critical role or time interval.