Work center overhead: 3 steps to cost each item

Key takeaways

Gather setup minutes, run minutes, the rate and the item count.
Match the count to the items covered by the setup and run time.
Check the allocated total and document your inputs.

When a shop runs a batch of finished items through a work center, pooled overhead can be allocated to those items. It sits in a pool: the cost of the machines, the supervision, the power, the tooling, and the rest of what it takes to keep the work center open. An estimator decides how much of that pool belongs to each piece in the run and puts a number on it.

That number is only useful if someone else can check it. A manager may ask why one run costs more for each piece than the last. A customer may ask how a quoted price was built. An auditor may ask for the trail behind a standard cost. In each case, start from the overhead share and show how you got there. If the answer is "I divided the total by about ten," the share is not traceable. If the answer is "here are the setup minutes, the run minutes, the rate, and the item count, and here is the arithmetic," it is.

Traceable also means repeatable. The same inputs should give the same share, and a similar run should follow the same steps.

This post walks through three steps: define the run and gather its inputs, spread the work center cost across the items, and tie out and document the result. The arithmetic follows the worked examples in Microsoft's documentation on calculating standard cost in Business Central, which show how setup time, run time, and rates combine into a cost for each item. The method is general. Your shop's rate rules, cost pools, and allocation policy decide which inputs you use, so confirm those choices with whoever owns your cost accounting.

Step 1: Define the run and gather the inputs

Start by writing down exactly what the run is. A run is the group of finished items that share one setup at one work center. Name the finished item, state how many items are in the run, and name the work center. Write the run as one line at the top of your worksheet, so every number below it has an obvious owner.

Keep runs separate. If the same work center makes two products, each run needs its own setup and item count.

Next, gather four inputs:

Setup minutes for the run. The time the work center spends preparing before the first item is made. This is a fixed amount for the whole run.
Run minutes for each item. The time the work center spends on each piece.
Rate for each minute. The overhead rate you charge for each minute of work center time.
Items in the run. The number of finished items the setup and run time will cover.

Record a source next to each input. A setup time should point to a routing, a time study, or logged history. A rate should point to the calculation that produced it. If you cannot name a source, label the input as an assumption. Assumptions are normal in an estimate, but they must be visible, because a hidden assumption is the first thing a reviewer will question. For a broader bid review, use the construction estimate audit guide.

Decide how setup time is treated before you calculate. Some shops use setup time to schedule work but do not charge it into each item's cost in the same way. Write the decision on the worksheet and keep it the same across comparable runs. You will need it again in Step 3.

Check units before going further. If a rate is quoted per hour, convert it to a rate for each minute before you multiply. A unit mismatch can throw a share off by a large factor while the final number still looks plausible. Estimate the answer roughly before the full calculation. If the rough figure and the result are far apart, check the units first.

Choose the item count with care

The item count is where many shares go wrong. It should be the number of items the setup and run time actually cover, not the quantity sold on the order, the monthly shop volume, or a larger job that happens to share a product code.

If the run includes items that will be scrapped or rejected, decide whether the share covers good pieces only or every piece started, and write the decision down. The denominator must match the costing basis and scrap treatment; dividing by all pieces started does not by itself give overhead for each good finished item.

If one setup covers several batches, the item count for a single batch is not the right divisor for the setup. State the number of pieces the setup covers and show how you arrived at it. A reviewer who sees a clear count will trust the share far more than one who has to guess.

Step 2: Spread the work center cost across the run

With the inputs in hand, the overhead share for one finished item is calculated as (setup minutes + run minutes for each item × number of items) × rate for each minute ÷ number of items.

Read it from left to right. The parentheses add every minute the work center spends on the run: one setup plus the run time for each item. Multiplying by the rate turns those minutes into a total work center cost. Dividing by the number of items spreads that total across the pieces, and the result is the overhead share for one finished item.

The standard cost guidance in Microsoft's Business Central documentation uses this same structure. Its work center 200 example contributes 4 for each item: (10 setup minutes + 1 run minute × 10 items) × 2 for each minute ÷ 10 items. Every term has a source you can point to, which is what makes the result checkable.

Keep the expression in your worksheet with each term in its own cell or column. Do not replace it with a single typed-in figure. A collapsed number cannot be checked, and a reviewer has to take your word for it. A reviewer who sees the four inputs can recompute the answer quickly and find any mistake.

Two features of this formula explain most of the variation from run to run.

First, setup time is divided by the item count, so its effect shrinks as the run grows. A long setup on a short run is expensive for each piece. The same setup spread over a long run barely moves the number. This is why one product can carry very different overhead for each item depending on how it is batched, even when the machine work is identical. When a customer asks why a small order costs more for each piece, setup allocation is a possible explanation, and the worksheet should show it.

Second, run time is not divided by the item count, because each item carries its own run minutes. Keeping the setup part and the run part on separate lines makes it easy to explain a change. The setup portion fell because the run got bigger, while the run portion stayed the same.

Some work centers carry overhead as a percentage of cost components plus a flat rate. The same Microsoft guidance shows this pattern: "Work center 100 contribution is calculated as (5 direct cost × 20% + 1 overhead rate) × 10 items ÷ 10 items." The shape of the formula changes, but the discipline does not. Write each component on its own line, state its basis, and add the parts at the end.

Keep full precision in the intermediate steps. Round only the figure you show the reader, and note in the worksheet how many decimal places you carry.

Tie out the totals first. If you spread a pool across several items, the shares should add back to the pool. Multiply the share for each item by the number of items and compare the result with the overhead allocated to this run using the same inputs and rate. If they differ, something was rounded, dropped, or counted twice. Find the cause before moving on.

The guidance also shows a production item whose overhead is "10% × (20 material + 12 noninventory material + 9 capacity + 7 subcontracting + 2 capacity overhead) + 3 overhead rate." Laying the components out this way lets a reader see the whole cost and confirm that each part is included once. The same example adds the cost shares together as "The sum of all cost shares, calculated as 20 + 12 + 9 + 7 + 2 + 8," so each share is visible on its own line.

Next, test the setup treatment. If your estimate charges setup to the run, calculate what the share would be if setup were used only for planning. The guidance gives a way to make this comparison in Business Central: "To compare the result when setup time is used only for planning, for the FINISHED item, set the Lot Size field to 1." The aim is not to choose the lower number. It is to show how much of the answer depends on the setup decision, so that decision is visible rather than buried. On small runs the difference can be large, because the setup is spread over fewer pieces.

Write the basis next to the number. Every overhead share should carry a short note with the work center, the run size, the date the inputs were taken, the rate source, and any assumption made. A list of labeled items is easier to audit than a paragraph of explanation.

Keep the worksheet versioned as well. When a rate or setup time changes, save the new version beside the old one so the earlier share can still be reproduced from its original inputs. When a manager asks why this quote differs from the last one, the honest answer is often that an input changed on a specific date.

Put the three steps together with one illustrative run.

Step 1, gather the inputs. Setup is 10 minutes for the run. Run time is 1 minute for each item. The rate is 2 for each minute. The item count is 10. Record the routing as the source for the minutes, the rate worksheet for the rate, and the count of items covered by the setup and run time.

Step 2, spread the cost. Total minutes for the run are 10 + (1 × 10), which is 20 minutes. Total work center cost is 20 × 2, which is 40. The share for each item is 40 ÷ 10, which is 4.

Step 3, tie out and document. Multiply 4 × 10 to recover 40, then record the setup treatment and input sources.

Check a percentage-based calculation

A second example uses the percentage-based pattern. Lay it out line by line. The direct cost line is 5. The percentage line is 5 × 20%, which is 1. The overhead rate line is 1. Adding the percentage line and the overhead rate line gives 2. The layout matters as much as the answer, because a reviewer can check each line against its source without rebuilding the formula.

Common mistakes to avoid

Mixing units. Hours and minutes get combined in the same formula, or a hour-by-hour rate is multiplied by a time measured in minutes. Write the unit next to every input and check that the units cancel to the unit you want.

Using the wrong divisor. Setup is spread over monthly volume or a product family count instead of the items in this run. Keep the item count tied to the run it describes.

Changing the setup treatment silently. A quote that looks cheaper may simply have used a different setup rule. Write the treatment on the worksheet every time.

Rounding early. Rounding each component before adding them can shift the total. Carry full precision and round only the displayed result.

Reusing an old rate. A rate that has changed should not quietly stay in the worksheet. Date every rate and point each estimate at the version it used.

A short checklist before you send the estimate

The run is named, with the product, the item count, and the work center.
Every input has a source, or is marked as an assumption.
Units match in every term, and the result has the unit you want.
The formula is in the worksheet, with one term in each cell or line.
The allocated shares add back to the pool they came from.
The setup treatment is written down, and the alternative has been compared.
Each share carries a basis note with the date and the rate source.
The share is labeled as one component of the item's cost, not the whole cost.

For the pricing stage, see the guide to markup and margin rates.

Closing thought

None of this requires special tools. It requires the discipline to write each term down and keep it where a reviewer can see it.

Check your shop's own cost rules before you rely on any figure, and treat the numbers in this post as an illustration of the method rather than values to copy. When the worksheet is clear, the share is easy to defend, and the next estimate for a similar run is faster to build because the steps are already in place.

Today, choose one run and record its setup minutes, run minutes, rate and covered item count before calculating its overhead share.

Questions about work center overhead

Which item count should I use?

Use the count covered by the setup and run time, with the treatment of scrap stated explicitly.

What total should the shares match?

The shares should match the overhead allocated to that run using the same inputs and rate.