Methodology & Reference

Forecasted Overhead Allocation — the Workday Model

How FreightMath allocates forecasted overhead by effective workday instead of spreading it evenly across the calendar.

Overhead allocationForecast → actualsCurrent production release

Each month, FreightMath calculates a forecasted overhead allocation using a workday-based approach instead of spreading costs evenly across the calendar. We start with the prior month's total overhead from the general ledger and divide it by the number of effective workdays in the current month. That produces a daily overhead rate that:

  • Respects how your operation actually runs across weekdays, weekends, and holidays; and
  • Creates a consistent “overhead per available workday” metric that can be compared month to month.

As the month progresses, FreightMath accrues forecasted overhead by the effective workday. At month-end, that accumulated amount is allocated down to freight based on hours on delivered loads. Loads that consume more driver or asset time carry a proportionally larger share of overhead, while light-touch loads carry less.

Once actual monthly financials are available, FreightMath recasts these forecasted allocations to actuals for all cost categories (overhead, variable, and other operating costs). This ensures that reported OR, margins, and profitability by lane or customer tie back to the general ledger while preserving the operational insight provided by the Workday Model.

Why the Workday Model?

A simple calendar-day method treats every day the same, whether it is a Tuesday linehaul day or a holiday Sunday. That approach distorts month-to-month performance, especially in months with major holidays or unusual day patterns. The Workday Model corrects this by weighting each day type based on its relative activity and then allocating overhead in line with the number of effective workdays that have actually occurred.

Weight 1.0

Weekdays

Represent normal activity and typically carry full weight.

Weight ≈ 0.50

Saturdays

Usually count as partial days to reflect reduced staffing and volume.

Weight ≈ 0.25 or 0

Sundays & holidays

May count as very light days, or zero when the network is closed.

Practical example: November 2025 compression — fewer workdays, faster overhead accrual

November is a good illustration of why the Workday Model matters. Even though it has 30 calendar days, its pattern of weekends and holidays creates fewer effective workdays than a typical month:

  • The month starts on a Saturday and ends on a Sunday.
  • Thanksgiving counts as roughly a 0.25 day and the day after as a 0.50 day.
  • Saturdays count as 0.50 days and Sundays as 0.25 days.
September
24.5
effective workdays
October
≈ 26
effective workdays
November
≈ 22.5
effective workdays
December
≈ 24.25
with Christmas downtime

As of November 8, roughly 6.25 of 22.5 effective workdays have already elapsed — about 28% of the month. Under the Workday Model, that means about 28% of monthly overhead has already been allocated. If the first week's volume or revenue is soft, that front-loaded overhead will temporarily worsen your Operating Ratio (OR), even though the full month may still perform to plan.

Looking ahead, if you expect higher utilization, stronger volume, or better rates through the remaining workdays, this timing effect will naturally normalize by month-end. The model simply makes that compression visible, so you can explain short-term OR pressure without overreacting to a few slow days.

How it works

  1. 1

    Start from the GL

    Use the prior month's total overhead from the General Ledger (Total_OH_GL).

  2. 2

    Weight the calendar

    Calculate weighted working days in the month based on day type.

  3. 3

    Measure progress

    Determine the share of weighted days completed (pct_workdays = weighted_days_elapsed ÷ weighted_days_in_month).

  4. 4

    Allocate month-to-date

    Apply that percentage to allocate MTD overhead: OH_MTD = Total_OH_GL × pct_workdays.

Default weights

Day typeWeightExample
Monday–Friday1.0Full activity
Saturday0.5Reduced activity
Sunday0.25Minimal activity
HolidayVariableVeterans Day 1.0; Christmas 0.0

Formulas

OH_per_weighted_day = Total_OH_GL ÷ weighted_days_in_month
OH_MTD = Total_OH_GL × (weighted_days_elapsed ÷ weighted_days_in_month)
OH_per_load = OH_MTD × (load_hours ÷ Σ all_delivered_load_hours_MTD)

Examples

Example 1

Short vs. long month

October: 26 weighted days → $2,400,000 ÷ 26 = $92,308/day

November: 22.75 weighted days → $2,400,000 ÷ 22.75 = $105,495/day

With fewer working days, overhead per day increases even though total OH is constant.

Example 2

Month-to-date allocation

Weighted days in November = 22.75; through Nov 10, 8.25 days elapsed → pct_workdays = 8.25 ÷ 22.75 = 0.3626

Allocated MTD OH = $2,400,000 × 0.3626 = $870,240

Interactive calculator — October vs. December

Enter your own overhead, revenue, and weighted workdays to see how compression moves the OR.

Interactive calculator

Compare a long workday month vs. a short workday month

This calculator compares October (higher weighted workdays) with December (lower weighted workdays) and shows overhead per weighted workday, overhead-only OR (Overhead ÷ Revenue), and full OR using a consistent variable-expense percentage.

Same overhead applied to October and December.

October — Long Workday Month

Example: 26 weighted days.
If left blank, FreightMath will back-solve variable expense to target a 97% OR for October.

December — Short Workday Month

Example: 21.5 weighted days.
Keeps the same variable-expense % of revenue as October.

Note: OR (Operating Ratio) = Total Operating Costs ÷ Revenue. For October, if variable expense is blank, the calculator backs into variable expense that produces a 97% OR. December then applies the same variable-expense percentage to its revenue, with revenue scaled to reflect fewer weighted workdays.

How do you fight back against overhead compression?

Overhead compression will occur whether you want it to or not, however there are proven ways to “fight back.” The Workday Model simply makes it visible sooner. The question for leadership is how to respond proactively so that a compressed month still lands at or above target OR.

Incentivize your driving teams

Use driver-choice productivity bonuses to encourage drivers to take additional freight when it makes sense for them.

  • Optional “stay out” or productivity bonuses tied to extra loads or miles during compressed weeks.
  • Premiums for weekend and holiday coverage where you know there is freight to support it.

All incentives will respect Hours-of-Service and home-time commitments. The goal is to reward drivers who choose to lean in when the network needs coverage, not to force additional work.

Run a monthly productivity planning meeting

One week before the start of each month, hold a cross-functional “productivity planning” session that:

  • Reviews the upcoming month's effective workday calendar and identifies compression risk.
  • Plans specific actions to fight back: targeted freight, driver incentives, and coverage strategies.
  • Sets a clear OR and contribution goal for the month tied to those actions.

Going into a compressed month with a plan and a numeric goal is far more effective than reacting mid-stream to a noisy first week.

Convert fixed overhead to more variable, where it truly saves money

Explore opportunities to shift cost structures from fully fixed to per-transaction, per-load, or other activity-based models, but only where there is a clear, measurable cost advantage. Examples include:

  • Certain support functions or services priced per load, per call, or per claim instead of flat retainers.
  • Maintenance, wash, or yard services with volume-based tiers instead of purely fixed monthly fees.

The objective is to make more of your overhead behave like variable cost without increasing total spend. Acknowledging this is easier said than done.

Offset compression with non-asset productivity

Include your non-asset team in the productivity planning conversation. Ask explicitly how they will:

  • Seek additional volume during the month to provide a legitimate contribution to overhead, not “negative margin” loads.
  • Use non-asset capacity to absorb swings in demand without adding fixed tractors or offices.

Non-asset growth and better contribution per non-asset load can offset some of the OR pressure created by compressed workdays on the asset side.

These actions do not change the fact that overhead is fixed for the month, but they directly influence how much productive revenue and contribution you generate from the remaining workdays to offset that overhead consumption. Combined with the Workday Model, they turn overhead compression from a surprise into a managed risk with a clear playbook.

Key takeaways

  • Shorter months naturally show higher daily OH because overhead is spread across fewer workdays.
  • This model improves comparability across months and better mirrors operational cadence.
  • It smooths costs during holiday weeks and avoids misleading dips or spikes.

© FreightMath · Workday-weighted Overhead Allocation · Reflects current production release