Guide
Guide

Pre-calculation vs post-calculation: what each one can tell you

Subduxion · June 24, 2026

Pre-calculation and post-calculation answer two different questions — what should this cost, and what did this actually cost — and neither one is useful in isolation. Post-calculation without a pre-calculation to check against has nothing to measure. Pre-calculation without post-calculation never gets more accurate. This guide sets out what each step actually does, and why the comparison between them, not either number alone, is what an estimator can act on.

Pre-calculation: the estimate before production

Pre-calculation is the cost estimate produced before a part is made, built from the drawing, the material, the assumed route, and the estimator's judgement about setup, programming and cycle time. It is the basis for the quote sent to the customer, not the same thing as the eventual sales price. Its accuracy depends entirely on how much of the part's real manufacturing behaviour was actually visible at the time it was calculated — which is part of why the same nominal part can be quoted with different confidence at different points in a shop's experience with it.

Post-calculation: comparing actuals to the estimate

Post-calculation compares the booked hours, material used, scrap and any outside costs of a finished order against the original pre-calculation, broken down per operation rather than only at the order total. That per-operation granularity matters: comparing only the order total lets an overly generous estimate on one operation and an overly tight one on another cancel out invisibly, leaving a shop that looks "on budget" while actually understanding nothing about where its estimate was actually wrong.

Why the comparison is the actual value

Neither number is useful alone. A pre-calculation with no post-calculation to check it against is an assumption that repeats itself, unchallenged, order after order. A post-calculation with no pre-calculation to compare against is just a historical record with nothing to learn from. The comparison between them is what makes a time standard checkable rather than a permanent guess, and it is the only mechanism that reveals whether a difference sits in one specific operation or is spread across an entire routing — and whether it traces back to the time standard itself, the shop rate, or the material.

Why not every deviation is a modelling error

A post-calculation deviation is not automatically proof the pre-calculation was wrong. A recorded time can reflect a broken tool, an unplanned stoppage, an operator effect, or an unusually difficult one-off setup — none of which are necessarily representative of how the same job would normally run. Treating every recorded actual as ground truth, without first asking whether it was representative, produces a "correction" that actually makes future estimates worse, not better. Deciding whether a recorded time is representative is itself part of the work, not a step that can be skipped.

A worked example: where a blanket comparison hides the real story

Consider a three-operation part: turning, milling, and a final deburring pass. The pre-calculation estimated 40, 35 and 15 minutes respectively — 90 minutes total. Post-calculation records the actual times as 40, 52 and 8 minutes — 100 minutes total, about 11 percent over estimate.

Compared only at the order level, this looks like a single, moderate estimating miss: "we're running about 10 percent long, tighten the buffer next time." That conclusion would be wrong on both ends. The turning estimate was exactly right. The deburring estimate was too generous by nearly half. And the milling operation ran 49 percent over — the real problem, entirely hidden by the order-level average, which happened to land in an unremarkable-looking range only because the deburring surplus partially offset it.

Investigating the milling deviation specifically (not the order total) reveals the actual cause: representativeness has to be checked before the number is used. If this specific run hit an unusually hard patch of material or needed an unplanned tool change, the 52-minute reading is a real but non-representative data point, and correcting the milling time standard based on it would make the next estimate worse, not better. If, instead, three consecutive orders on this part show the same milling overrun, that is a genuine, representative signal that the original time standard for that operation was wrong — and only that operation's standard should be corrected, not the part's estimate as a whole, and not the deburring standard that was actually fine.

What this means in practice

A useful post-calculation practice checks representativeness first, then compares per operation, then feeds specific, targeted corrections back into the next estimate — not a blanket adjustment applied to every future job because one order ran long. Done this way, post-calculation is the mechanism by which a shop's estimating genuinely improves over time, closing the loop back into the next quote that goes out.

Related glossary terms

pre-calculation-vs-post-calculation

Read more

production-actuals

Read more

actual-cycle-time

Read more

Related guides

Cycle time, setup time and programming time: what is the difference?

"How long does this part take to make" sounds like a single question with a single answer. In practice, a manufacturing company tracks at least three distinct time components separately: setup time, programming time, and cycle time. Collapsing them into one generic "production time" number hides exactly the information that matters for pricing and planning correctly, especially because the relative weight of each one changes depending on whether the job is a one-off or a large series.

Read more

Related research

why-production-actuals-are-noisy-training-data

Read more