The Job Shipped. When Should Management Review the Cost Variance?
Job-cost variance is most useful while its operational cause can still be understood. Epicor users should review material, labour, burden, subcontract and quantity variances close enough to execution to act on them.
The short answer
Management should review significant Epicor job-cost variance while the operational cause can still be reconstructed, not only after the job has disappeared into monthly reporting. Material, labour, burden, subcontract, scrap and quantity differences become more actionable when supervisors, planners and finance can connect the variance to a recent event.
The purpose is not to close the accounts early. It is to learn from execution while the evidence is still warm.
How this connects to the pillar
The broader plan-to-profit model is covered in Epicor Has the Orders. Can Management See Which Ones Will Actually Make Money?. Job-cost review converts operational execution into economic evidence.
Separate accounting completion from learning timing
A final job cost may require all transactions to be complete.
Operational learning does not always need to wait that long.
If material usage or labour is already materially above expectation, the business can investigate the cause even before the final accounting view is complete.
Use interim review for action and final review for confirmed economics.
Review variance by driver
One total cost variance hides too much.
Separate material, labour, burden, subcontract and other relevant components.
Then connect the variance to operational causes.
A labour overrun might come from:
- additional setup;
- low yield;
- rework;
- training;
- machine problems;
- underestimated routing time;
- waiting;
- small batch inefficiency.
Different causes require different action.
Use quantity and rate separately
Material cost can rise because more material was consumed or because the price was higher.
Labour cost can rise because more hours were used or because the effective rate changed.
Separating quantity and rate helps management distinguish execution from commercial or purchasing effects.
The exact analysis depends on the costing model, but the principle is useful across manufacturing environments.
Review scrap with the job, not only with quality
Scrap has a quality dimension and a profitability dimension.
When scrap rises, the job may consume more material, labour and capacity than expected.
Connect the physical cause to the economic result.
Repeated scrap on a product family may justify engineering, supplier, process or pricing action.
Treat rework as a second route through the factory
Rework consumes capacity that may not have been planned in the original job economics.
It can create additional labour, material, inspection and delay.
If rework is recorded only as a quality incident without connecting to job cost, management can underestimate its profitability effect.
Make the economic consequence visible where practical.
Review subcontract variance with timing and scope
Outside processing can vary because supplier price changed, quantity changed, expedited service was required or additional work was added.
Do not treat the subcontract invoice as one unexplained variance.
Connect the amount to the event that changed the job.
This makes supplier and commercial discussions more useful.
Compare actual to the right baseline
A job can differ from the original estimate because the customer changed the requirement after order acceptance.
If management compares actual only to the original quote, operational teams may appear inefficient even when the scope changed legitimately.
Preserve a clear view of the baseline and approved changes.
This helps distinguish execution variance from scope variance.
Use tolerance to focus attention
Not every small variance deserves review.
Set thresholds appropriate to value, percentage, strategic importance or recurring cause.
The objective is to focus management attention where the variance can teach the business something or materially affect margin.
A high-volume low-value product may need different thresholds from a low-volume engineered job.
Connect variance to future standards
A variance review creates value only if learning changes something.
Possible actions include:
- routing time update;
- material quantity update;
- supplier strategy;
- setup reduction;
- pricing assumption;
- quality action;
- training;
- tooling change;
- customer change-control discipline.
Do not update standards based on one unusual event.
Look for repeated evidence.
Share the review across finance and operations
Finance understands cost structure.
Operations understands what physically happened.
A useful review combines both perspectives.
If finance investigates alone, the cause may be unclear. If operations investigates alone, the economic significance may be missed.
The shared review should be concise and exception-based.
What management should measure
Useful indicators include:
- jobs with material variance above tolerance;
- labour-hour variance;
- scrap and rework cost;
- subcontract variance;
- jobs with scope change but no baseline update;
- time between job completion and variance review;
- repeated variance by product family;
- repeated variance by resource or operation;
- standards changed based on validated recurring evidence.
The objective is faster learning, not more reports.
ACC context
ACC supports Epicor manufacturing and financial process improvement. Job costing becomes more powerful when actual transactions are reviewed close enough to execution that the organization can understand and improve the underlying operational cause. Explore ACC’s Epicor capabilities.
Operational review point
Select five recently completed jobs with the largest meaningful variance.
For each, identify one operational cause and one economic driver.
Ask whether the cause was unusual, recurring or created by customer scope change.
Then decide whether any planning, costing, pricing or process assumption should change.
Use cost variance before quoting repeat work
When a similar job is likely to be quoted again, recent actual-cost evidence should be reviewed before the next commercial commitment.
If the last jobs consistently required more setup, material or specialist labour than expected, the estimate should not continue to rely on the old assumption without review.
This is one of the fastest ways for operational learning to improve future profitability.
Distinguish controllable and structural variance
Some variance comes from execution that can be improved.
Other variance reflects a structural change in the business: supplier prices, wage rates, energy, required subcontracting or a permanently changed process.
Management should not ask operations to “improve” a variance that actually requires a new planning or costing baseline.
Classifying the cause protects accountability.
Review favorable variance too
An unusually favorable result can also contain useful learning.
Perhaps setup was reduced, yield improved or a new method worked better than expected.
If the improvement is repeatable, standards and future plans may need updating.
Ignoring favorable variance means the business learns only from problems and may miss proven improvement.
Connect variance to throughput impact
An unfavorable job-cost variance may also have consumed capacity that could have produced other profitable work.
A long rework loop or excessive setup does not only add cost to one job; it may delay other jobs using the same constrained resource.
For significant cases, include the throughput consequence in the review.
This helps management prioritize improvements where a variance damages both job economics and delivery performance.
Avoid turning variance review into blame
If employees believe variance review exists to identify who made the mistake, the quality of explanations will deteriorate.
The review should focus on assumptions, process conditions and repeatable causes.
Individual accountability still matters where required, but the main purpose is to improve planning, standards and execution.
A learning-oriented review produces better operational evidence.
Review timing of transaction capture before trusting variance
A variance can look operational when the real issue is incomplete posting.
If labour, material or subcontract transactions are still missing, the interim cost view may be misleading.
Define a minimum completeness rule for meaningful review.
This keeps early variance analysis useful without pretending the job is financially final.
Connect variance review to ownership
Each material variance should end with one of three outcomes: accepted one-off event, corrective action, or baseline/standard review.
Assign the next action to a named owner.
Without that final step, variance meetings can become descriptive reporting with no effect on the next job.
Use repeat-job comparisons carefully
Comparing similar jobs can expose unusual cost quickly, but confirm that quantity, routing, scope and material assumptions are truly comparable before concluding that one job performed worse.
This protects the review from false conclusions and keeps improvement focused on genuine operational causes over time and across repeat jobs.
Frequently asked questions
Should cost variance be reviewed before the job is closed?
It can be useful for operational learning if the relevant transactions are sufficiently complete. Final accounting review can still happen later.
Is an unfavorable variance always an operations problem?
No. Purchase price, customer change, supplier cost, commercial assumptions and other factors may be responsible.
How should small variances be handled?
Use tolerance and recurrence to avoid spending management time on noise.
What is the biggest risk of reviewing variance too late?
The people involved may no longer remember the event, making the cost explainable financially but not actionable operationally.