Straight into the service manual page
WrenchQuarry
More

2 cost figures to split an out-of-town job's fixed cost

WrenchQuarry Editorial Team · Published · 13 min read · How these guides are written

Two cost figures let dispatchers split fixed overhead on out-of-town jobs: your fixed cost figure from a cost equation built on your own recent activity data, plus published GSA travel benchmarks for estimating lodging and meals while the technician is away. Put them together and every out-of-town job carries its share of overhead, priced in before the quote goes out.

  • Plot pairs of activity and total cost from recent periods, find the variable rate for each unit of activity, multiply it by that period's activity, subtract that variable portion from the period's total cost, and the remainder is your fixed cost figure
  • Use published travel benchmark rates for the destination as a starting point for lodging and meals, then check actual hotel prices before locking the bid
  • Choose a split base that matches what you are splitting — technician hours for shop-level overhead, days away for road-specific overhead
  • The tax-home test decides whether a job is travel at all: work inside your main place of business's general area is local work
  • Re-plot your cost data when fixed lines like insurance, rent, or subscriptions change, and confirm current travel benchmark rates before quoting

Why fixed cost is the number that gets lost on a road job

You send a technician out of town for three days. The customer gets a line-item bill: parts, labor hours, mileage. What never appears is the cost of the truck, the phone plan, the insurance, the shop rent — the fixed pile that keeps running whether the truck sits or rolls. That pile has to land somewhere. Split it across the wrong base and you either lose money quietly or price yourself out of the next bid.

Two figures fix this. The first is your fixed cost figure itself, pulled out of a cost equation you build from your own recent activity.

This guide walks through both figures for dispatchers and owners who book technicians on multi-day jobs away from the shop. It uses IRS guidance on what counts as deductible travel, GSA travel benchmark rules for estimating away-from-shop costs, and a cost-estimating method you can run on your own numbers.

The first figure: pulling fixed cost out of your own activity data

A cost equation has two parts. The variable part moves with every hour the truck rolls — fuel, consumables, hourly labor burden. The fixed part does not move. It is the same this month as next, whether you run one job or ten. Estimating a variable and fixed cost equation and predicting future costs is exactly the skill you need here, and the OpenStax Principles of Managerial Accounting chapter on cost equations walks through the mechanics.

The method is simple. You plot pairs of data from recent periods: activity on one axis, total cost on the other. One point on that graph represents 21,000 hours and $84,000 in costs. The next point represents 23,000 hours and $90,000 in costs, and so on, until all the pairs have been plotted.

From those points you find the variable rate for each unit of activity. In the worked example in that chapter, the variable rate for each flight-hour comes out at $1.96. Once you have that rate, you subtract the variable portion from any period's total cost. The remainder is fixed cost. The chapter shows the check: choosing a different data point gives the same fixed cost of $44,920, calculated as $64,520 minus 10,000 hours times $1.96.

Do this with your own numbers. Pull six or twelve months of shop totals — total cost, total technician hours — and plot them. Find your variable rate per hour. Subtract that variable portion — rate times hours — from a month's total and you have your fixed cost figure. That number is the first of the two you need. It is the pile that has to be split across jobs.

Why the split matters more when the truck is away

Back at the shop, splitting fixed cost across jobs is almost invisible. Every job shares the same building, the same phone system, the same dispatcher. The allocation is a bookkeeping formality. Out of town it stops being a formality. The technician is eating hotel rooms and restaurant meals the shop would not otherwise pay. The truck is racking up hours far from the nearest service point. The job is consuming a scarce resource — a trained person willing to be away from home — and the price has to reflect that.

Two mistakes show up repeatedly. The first is charging only the visible variable costs on a road job, letting the fixed pile get absorbed by whoever happens to be looking at the P&L at year end. The second is splitting fixed cost evenly across jobs regardless of duration or distance, so a two-hour tune-up down the street carries the same overhead load as a five-day install two states over. Both mistakes are cured by the same move: establish your fixed figure from real activity data, then choose a split base that reflects how the job actually draws on the shop.

A split base is the measure you divide by. Hours worked is the most common. Days away from the shop is another, and it is the better base for the fixed costs that only appear on the road. Miles driven is a third, though mileage often behaves more like a variable cost than a fixed one. Pick the base that matches what you are splitting, and be consistent across bids so your numbers stay comparable.

The second figure: travel benchmarks for estimating away costs

The second figure is what you will actually spend on the technician while they are away. Lodging and meals are the two biggest lines, and both are easier to estimate if you have a published benchmark to start from. That is what a GSA travel benchmark is: a published benchmark for CONUS locations that agencies use for reimbursing travel costs.

GSA publishes the CONUS travel benchmarks the bulletin covers. The GSA Travel Benchmark Bulletin FTR 27-01 effectuates the travel reimbursement rates prescribed by GSA's Office of Government-wide Policy for CONUS locations. In plain terms: this bulletin carries the official rates for lodging and meals across the continental United States, set by the office that owns government-wide policy.

Those rates are not static. Other than changes posted on the GSA website, notices published periodically in the Federal Register now constitute the only notification of revisions to CONUS travel reimbursement rates to agencies. If you build a bid on last season's lodging figure, check whether the rate moved before you send the quote.

There is a second rule worth knowing from that same bulletin, because it affects how generous an estimate you can make. If travel reimbursement rates are insufficient to meet expenses, the FTR permits actual expense reimbursement up to 300% of the applicable maximum benchmark rate, pursuant to FTR § 301-11.17. That ceiling applies to federal reimbursement. For your own shop it is a useful signal: in expensive destinations, published rates can undershoot reality, and a bid built purely on the base rate may leave the technician short.

Your own policy does not have to mirror federal rules. But the GSA figures give you a defensible starting point for what a night away costs, and the 300% figure is a cap on federal actual-expense reimbursement when the published benchmark falls short of real expenses. Build your estimate from the published rate, then check the destination's real hotel prices before you lock the bid.

Using the two figures together

Here is the mechanics. You have your fixed cost figure from the cost equation. You have a GSA travel benchmark for lodging and meals. Now split.

Take the fixed figure and divide it across the jobs in the period using your chosen base. For an out-of-town job, add the away-specific costs — lodging, meals, incidentals — estimated from the benchmark rate for that destination and number of nights. Add the road-variable costs: fuel, tolls, wear. What remains to price is labor and parts, quoted as you always quote them.

The two figures do different work. The fixed cost figure tells you how much overhead each job must carry to keep the shop whole. Confusing them is how dispatchers end up quoting a road job at shop rates and wondering where the margin went.

What counts as travel, and what does not

Before you split anything, be clear about which costs are travel costs at all. The IRS Topic no. 511 on business travel expenses sets the boundary, and the boundary is your tax home.

Your tax home is the entire city or general area where your main place of business or work is located, regardless of where you maintain your family home. If you regularly work in more than one place, your tax home is the general area where your main place of business or work is located.

That definition matters because travel deductions only exist when you are away from your tax home. The IRS gives a blunt example: a taxpayer may not deduct any of the travel expenses, including meals and lodging, in Milwaukee because that is their tax home. Work done in your own city is local work. It carries no travel deduction, however late it runs.

For a technician based in one shop and sent to a job two hours away but within the same general area, the trip sits on the local side of the line. For the same technician sent to a destination outside that general area, the trip sits on the travel side of the line. The IRS points readers to Publication 463, Travel, Gift, and Car Expenses for the full detail on these and other travel expenses.

The tax-home test decides which jobs count as travel for costing purposes. But the tax-home test tells you which jobs are genuinely "away" jobs for costing purposes. A job inside your general area should be costed like local work. A job outside it is the kind this post is about.

Here is a small comparison of the two figures and where each one comes from:

FigureWhat it measuresWhere it comes from
Fixed cost each periodOverhead that does not move with hoursYour own plotted activity and cost data
GSA travel lodging and meals benchmarkExpected daily cost of a technician awayPublished destination benchmark rates

Building the split for a specific out-of-town job

Work a job end to end so the two figures land in the right places.

Start with duration. A three-day job away from the shop draws three nights of lodging and three days of meals. Pull the benchmark rate for that destination and multiply. Check the destination's actual hotel prices against the lodging figure, because the bulletin's 300% actual-expense ceiling exists precisely for cases where the base rate runs short. If actual prices sit well above the published rate, your estimate should reflect that before the bid goes out, not after the invoice arrives.

Next, the fixed split. Take your period's fixed cost figure and divide it by your chosen base across all jobs in that period. If the base is technician hours, the out-of-town job picks up a share proportional to the hours worked on site. If the base is days away, it picks up a share proportional to the days spent off shop ground. Days-away works better when the overhead you are splitting is genuinely tied to being away — travel cost claims, phone plans, out-of-area insurance riders, trip administration. Hours work better when the overhead is shop capacity being consumed.

Most shops use both. Split shop-level overhead on hours. Split road-specific overhead on days or miles. Two bases, two allocations, one total that has to cover the period.

Then the road-variable costs: fuel, tolls, overnight truck parking if any, parts shipped to the site rather than carried out. Estimate these from the route and the job scope. They are not part of either of your two figures — they are their own line, quoted directly.

What comes back is a job price with four parts: labor and parts quoted as usual, road-variable costs estimated for the route, away costs estimated from the travel benchmark, and a share of fixed overhead from your cost equation. Nothing sits outside the price waiting to be absorbed.

Timing the check on rates

Travel benchmarks move with federal notices. Build a rate check into your bid process. Before quoting any multi-day job, confirm the benchmark rate for that destination and season against the current published figure, and confirm the destination's real hotel prices against the lodging line. A bid built on a stale rate is a bid built on a guess, and the guess is entirely avoidable.

The same check applies to your cost equation. Fixed cost drifts — insurance renewals, rent escalations, new subscriptions. Re-plot your activity and cost data periodically so the fixed figure you are splitting reflects current reality rather than last year's. The mechanics do not change: plot the pairs, find the variable rate, subtract, take the remainder. Only the inputs refresh.

Common mistakes when splitting fixed cost on the road

Splitting on the wrong base. Assigning road-job overhead on shop hours alone underweights the away-specific costs. Assigning everything on days away overweights short but intensive jobs. Match the base to what you are splitting, and say which base you used when the customer asks how the price was built.

Ignoring the tax home boundary. Costing a same-area job as if it were travel inflates the price and loses the bid. Costing a genuine multi-day away job as local work leaves the technician short on the road. The tax-home test settles it: your main place of business's city or general area is the line.

Letting the travel benchmark figure do double duty. The travel benchmark estimates lodging and meals. It is not an overhead allocation and it is not a substitute for your fixed cost figure. Using it as either one muddies the split.

Quoting before checking actual destination costs. The published lodging rate is a starting point. Actual prices in an expensive city can run well above it — which is exactly why federal rules allow actual expense reimbursement up to three times the base rate in hard cases. Check before you quote.

Never re-running the equation. A cost equation built once and filed away goes stale. The plot needs fresh pairs. The fixed figure needs to move when your real fixed costs move.

Related guides: Backing 5% VAT out of a £483 price before a job is billed · Job-cost comparisons: 3 checks across periods · Floor price for a one-off job: 3 cost parts.

FAQ

What if the technician is away for a week and lodging in the destination is far above the benchmark? Estimate from the benchmark, then check actual hotel prices for that city and week. Where actuals sit well above the published lodging line, price the job on the real figure. Federal rules allow actual expense reimbursement up to 300% of the applicable maximum benchmark rate. Your customer is paying for the job in that city, in that week.

How often should I rebuild the cost equation? Often enough that the fixed figure tracks your real overhead. Insurance renewals, rent changes, new software subscriptions all move it. Re-plot when any meaningful fixed line changes, and at least on your normal budgeting cycle. The method stays the same each time: plot activity and cost pairs, find the variable rate for each unit of activity, multiply it by that period's activity, subtract that variable portion from the period's total, take the remainder as fixed cost.

Does the tax-home test change how I price the job? It changes whether the job is priced as a road job at all. Work inside your main place of business's city or general area is local: no travel costs, no away benchmark in the split. Work outside that tax-home area is travel, and carries lodging, meals, and the road-specific overhead that comes with them. Set the boundary once, in writing, so dispatchers apply it the same way every time.

Which two numbers should a dispatcher check before sending a quote? Check the benchmark rate for the destination and the current fixed cost figure for the period. Those are your two figures. Everything else on the quote — labor, parts, route costs — follows your normal process. The two figures are what keep the overhead and the road from falling outside the price. For the full rules on what counts as travel, the IRS points to Publication 463, Travel, Gift, and Car Expenses.

Sources

More field guides