Straight into the service manual page
WrenchQuarry
More

Overhead base: 3 rules that keep the allocation intact

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

To allocate overhead fairly across jobs, pick one base, keep it whole, include every item that belongs in it, and allocate by period.

Key takeaways

  • Write the base in one sentence. Could another team lead read it and reach the same answer?
  • Compare this period's base with last period's. Any element that has disappeared needs a written reason.
  • Look for costs you left out because they were awkward: rework, returns, idle time, difficult customers. Ask whether they used shared resources. If they did, they belong in the base.
  • Confirm that the overhead pool and the base cover the same period, and that each late cost sits in its correct period.
  • Record any change to the base, including when it took effect, why it changed, and who approved it.

Why the base decides who pays

When a business carries overhead, it carries costs that do not belong to any one job alone. Rent, supervision, software, insurance, and shared equipment all serve every project at once. None of them arrives with a job number attached. Someone has to decide how much of each cost lands on each job. The usual method is an overhead rate: a pool of overhead costs is divided by some measure of activity, and the result is applied to each job.

Most of the attention goes to the rate. Owners ask whether it is too high, whether it should be built on labor or machine time, and whether last year's figure still holds. Those are fair questions. For one way to calculate a rate, see Shop overhead rate: calculate it from 2 estimates. But the rate is only half of the allocation. The other half is the base, the measure the rate is multiplied against. A good rate on a bad base still produces unfair results. And a base that quietly changes partway through the year means the rate no longer means what it meant when it was set.

This post covers three rules that keep the allocation intact. They apply whether you run a shop, a field crew, a design studio, or a small maintenance team. The advice is general. It is not a substitute for guidance from an accountant who knows your books and your obligations.

One of the clearest published sources on this subject is the Federal Acquisition Regulation (FAR), the U.S. federal rulebook for government contracts. Its section 31.203 covers how indirect costs are allocated. You do not need to be a government contractor to learn from it, because its wording is precise about the logic any fair overhead system needs. Where the text is specific, this post quotes it and links to it. Where it does not reach your situation directly, the post says so.

Keep one goal in mind as you read. The goal is not to make every job look the same. The goal is for each job to carry a share that matches the shared resources it actually used, under a method you can explain to anyone who asks.

Rule 1: Choose a base, then do not fragment it

Start by choosing a base that reflects how your work uses shared resources. Businesses use different bases. No single choice is right for everyone. The right base is the one that tracks how jobs consume overhead in your operation, and you should be able to explain why you picked it.

Once a suitable base is in place, the first rule is to keep it whole. The federal text is direct on this point. Once an appropriate base has been accepted, the contractor "shall not fragment the base by removing individual elements." (FAR 31.203) The logic carries over to any shop, even though the regulation itself governs government work.

Fragmenting rarely looks like a big decision. It usually starts with a reasonable request. A large material purchase makes one job look expensive, so someone wants it removed from the base. An outside invoice seems odd, so it is set aside. Some time gets booked to an internal category that does not carry overhead. Each change looks harmless on its own. Together they shrink the base, and overhead that was meant to be shared gets pushed onto whatever jobs are still in it.

The deeper problem is that fragmenting changes the answer without changing the work. Suppose a job's materials are excluded from the base. That job now carries less overhead, and every other job carries more. Nothing about the shop, the trucks, or the office has changed. Only the accounting has, and the other jobs had no say in it.

Changing a base can be legitimate. Sometimes the work really has changed, or the base you picked turns out to measure the wrong thing. The difference is that a change is a decision, not a cleanup. Make it on purpose, write down the reason, apply it from a stated point forward, and tell the people whose jobs will move.

A simple test helps. Write the base in one sentence, such as "overhead follows direct labor hours on every job." Then, before you remove any item from the base, ask whether it fails the same test you used when you included everything else. If you cannot name a reason that would apply to every job, leave the item in.

Who decides matters as well. A base that one person can change on a whim is not really a base. Name the person or group who owns the base definition, and require that any change go through them. This can be a short written note that the owner signs off on, kept where the other leads can find it. The point is that a change is visible before it affects anyone's numbers.

Rule 2: Put every item that belongs in the base into the base

The second rule is the mirror image of the first. Keeping the base whole means you should not take items out of it. It also means that every item that belongs in the base must be included, and each included item should carry its share of the pool.

The federal text gives a concrete example. When a cost input base is used, the contractor "shall include in the base all items that would properly be part of the cost input base, whether allowable or unallowable." (FAR 31.203)

Two ideas in that sentence matter for any team. The first is that membership in the base depends on what the base measures, not on how an item looks on a particular day. If the base is meant to capture the cost of doing the work, then a cost that is part of doing the work belongs in it.

The second is that an item can belong in the base even when you would prefer it did not. Whether a customer will pay for a cost should not decide whether that cost counts in the base. A cost you cannot pass on still used the shop, the software, and the supervisor's time.

This matters most for costs that feel like mistakes. Rework, warranty repairs, wasted materials, and time spent on a job that went badly often get left out, because they seem like problems to hide rather than work to count. But if those costs used labor and shared space, they belong in the base and should carry their share of overhead. Leaving them out shifts that share onto jobs that ran cleanly, which is the opposite of fair.

Idle time is another common gap. When a crew waits for parts, a permit, or a customer decision, the shared resources are still supporting that crew. Whether idle time belongs in the base depends on the base you chose, so check it against the definition you wrote under the first rule. Do not decide case by case based on which result you like.

Subcontracted work raises a similar question. Teams often want to keep an outside firm's cost out of the base because it is "not our labor." Ask a different question instead. Did the work use your scheduling, your supervision, your coordination, or your shared tools? If it did, the cost of managing that work is part of the overhead story. Shared tools and vehicles that sit in a yard between jobs work the same way. Their cost does not disappear because a particular crew borrowed them.

A useful question to ask about any cost left out of the base is this: if the same cost came from a normal job, would it be included? If the answer is yes, then the reason for excluding it should be the same reason that applies to every other job. If you cannot find that reason, include the cost.

Rule 3: Allocate within the period the costs were incurred

The third rule is about time, and it is the one most often broken without anyone noticing. The federal text defines the base period this way: a base period is "the cost accounting period during which such costs are incurred and accumulated for allocation to work performed in that period." (FAR 31.203)

The key idea is alignment. The overhead costs, the base, and the work they are spread across should all belong to the same period. When costs from one period land on work done in another, the rate stops describing the work and starts describing the bookkeeping.

This goes wrong in predictable ways. A late bill for last period's utilities arrives this period and gets spread across this period's jobs. A stretch of work finishes in the next period, but its overhead was booked in the earlier one. A quiet period carries high fixed costs, and those costs get pushed forward onto jobs that happened to start later. Each case feels like a small timing issue. Over a year, the pattern can move a meaningful amount of overhead from one job to another.

Late-arriving costs need a deliberate rule. Some teams hold a short window after the period closes, during which bills for the closed period can still be recorded there. Either approach can work. What does not work is an unwritten habit that changes from month to month depending on who is doing the books. Whichever you choose, write it down, apply it the same way every time, and make sure the people reviewing job results can see when a late cost has been moved. To compare results across periods, see Job-cost comparisons: 3 checks across periods.

A few habits keep time aligned:

  • Set a cutoff for each period, and state when costs for that period stop being accepted into it.
  • Record overhead when it is incurred, not when someone remembers to book it.
  • When a late cost belongs to an earlier period, record it in that period and note the late arrival. Do not fold it into whatever period happens to be open.
  • Make sure the pool and the base cover the same span of time. If one covers a month and the other covers a quarter, the rate is comparing unlike things.

Watch for long gaps between rate reviews, too. A rate set at one point and used for a long stretch can drift as the work changes. Pick a review schedule that suits your work, write it down, and treat a large change in the base as a reason to look at the rate again sooner.

The principle underneath all of this is simple. Costs should follow the work in the period when the work happens. That is a general accounting idea, and it applies to your team even if no government contract is involved.

Illustrative example: fragmentation and timing in one small team

Imagine a small team that spreads overhead across its jobs using total direct cost as the base, with a period pool of 200. Two jobs run side by side, each with 100 of direct cost. One is material-heavy. The other is labor-heavy.

Partway through the period, the team lead notices that the material-heavy job looks expensive on the overhead report. The lead removes that job's materials from the base. The job's overhead share drops, and the labor-heavy job's share rises. This is fragmentation, the thing the first rule warns against, and it moves overhead onto a job that did nothing differently.

Later, a supplier invoice arrives for materials used in the prior period. The lead spreads it across the current period's jobs, because that is where the bookkeeping happens to be open. This is a timing break, the thing the third rule warns against.

Explaining the allocation to a job lead

Sooner or later, a lead will ask why their job carries the overhead it does. How you answer tells them whether the system is trustworthy. The best answer is short and points to the written base. Something like: "Overhead follows direct labor hours on every job, this is the pool for the period, and your job used this share of the shared hours." If the lead can see the same base, the same pool, and the same period, the conversation usually ends there.

If the lead disagrees, treat the disagreement as information. Maybe the base does not measure what it should for their kind of work. Maybe a cost was left out, or a late bill landed in the wrong period. Those are fair concerns to check. What you should avoid is adjusting one job's numbers to make the conversation go away. A single exception makes every other job's number less reliable, because no one can tell whether it was treated the same way.

Keep the explanation consistent across the team. Give every lead the same one-page description of the base and the period, and update that page whenever the base changes.

Where the federal text fits

The Federal Acquisition Regulation text quoted in this post applies to government contracts. If your business holds such contracts, the specific requirements are a matter for your contracting and accounting advisors. The same section notes that "For contracts subject to full CAS coverage, allocation of indirect costs shall be based on the applicable provisions." (FAR 31.203) This post does not summarize those provisions, because they reach well beyond the scope of a general guide.

For everyone else, the value of the text is its logic. Keep the base whole. Include everything that properly belongs in it. Let each item carry its share. Match costs to the period when the work happened. A team that follows those three ideas can defend its overhead allocation to anyone who asks, and it can change the allocation on purpose when the work truly changes.

Start with the base. Write it in one sentence today, check whether last period's base matches it, and bring any gaps to the next review. That single habit will do more for fairness than arguing about the rate.

Related guides: Overhead line checks: 8 items before dispatch · Overhead rate for labor-hour bids: 2 totals.

Frequently asked questions

What is an overhead base?

The overhead base is the measure the overhead rate is multiplied against, such as labor or machine time.

Can I remove items from the base?

Only as a deliberate change: write down the reason, apply it from a stated point forward, and tell the affected jobs.

Does the federal rule apply to my business?

Only if your business holds government contracts; otherwise, use its logic as a general guide.

Sources

More field guides