Cost variance is one of the most valuable signals in your DELMIAWorks data and one of the most commonly overlooked ones. The gap between what a job was estimated to cost and what it actually cost tells you whether your pricing is accurate, your standards are current, and your processes are running the way they were designed to.
Left unexamined at mid-year, cost variance carries quietly into H2 quoting, job profitability, and year-end margin. A focused review now takes less time than most teams expect and prevents a category of surprise that shows up in Q4 when there is no longer time to correct course.
Here is how to run it.
Step 1: Pull the Job Cost Variance Report for All Closed H1 Work Orders
In DELMIAWorks, navigate to your job cost reporting and pull variance data for all work orders closed in Q1 and Q2. Filter to show estimated versus actual for material, labor, and machine time separately rather than as a single combined variance.
Sort the results by total variance, largest to smallest, in both directions. You are looking for two groups: jobs that came in significantly over standard cost, and jobs that came in significantly under. Both are worth understanding.
Over-standard jobs point to potential pricing and process problems. Under-standard jobs can indicate data entry issues, missing cost captures, or operations that completed faster than the routing assumes, which may mean the standard needs updating.
Set a threshold that is meaningful for your operation. For most manufacturers, a variance of five percent or more on a job warrants a closer look. Set that threshold and focus on the jobs that exceed it rather than trying to explain every small deviation.
Step 2: Break Down the Variance by Category
For each job that exceeds your threshold, break the variance into its components.
Material variance occurs when the actual material consumed differs from the BOM quantity at standard cost. Common causes include BOM inaccuracies, substitution of non-standard materials, scrap rates running higher than the standard assumes, or receiving discrepancies that were not resolved before material hit the floor.
Labor variance occurs when actual labor hours differ from the routing standard. Common causes include setup times that are longer than the standard reflects, operators with different efficiency profiles than the routing assumes, or jobs with rework that added hours not captured in the original estimate.
Machine variance occurs when actual machine time differs from the routing standard. This often indicates that cycle times in the routing are outdated, that machine downtime during the job was absorbed into run time, or that the routing does not accurately reflect the current production method.
Understanding which category is driving the variance tells you where to look for the root cause. A material variance and a labor variance require completely different responses.
Step 3: Identify Patterns Across the Variance Data
One job running over standard is an event. Five jobs of the same type running over standard is a pattern.
After reviewing individual jobs, step back and look at the variance data by job type, work center, customer, and item. Ask whether the variance is concentrated in specific areas:
📋 A specific work center appearing repeatedly in labor variances may indicate a routing that needs updating or a training gap with the operators assigned there.
📦 A specific material appearing repeatedly in material variances may indicate a supplier quality issue, a BOM that does not reflect current yields, or a handling process generating more scrap than the standard assumes.
🔧 A specific job type appearing repeatedly in over-standard results may indicate that the estimating assumptions for that type of work need to be revisited before more of it is quoted.
Patterns are the most actionable output of the variance review. They point to systemic issues that will repeat in H2 if not addressed.
Step 4: Update Standards Where the Data Supports It
If the variance review reveals that certain standards are consistently wrong in the same direction, update them before Q3 starts.
A routing that consistently underestimates setup time by 30 minutes should be corrected. A BOM that consistently underestimates material usage by eight percent should be updated. Running H2 on standards you know are inaccurate means your job cost data will continue to misrepresent profitability, your scheduling will continue to underallocate time, and your quotes will continue to underprice the affected work.
In DELMIAWorks, routing and BOM updates take effect on new work orders created after the change. Existing open work orders continue on the old standard. Make updates before Q3 work orders are released so the corrected standards are in place from the start of the new quarter.
Step 5: Flag the Findings for Quoting
The final step is making sure the variance review informs your Q3 quoting.
If a category of work has been consistently running over standard, the people building quotes for that work in Q3 need to know. Share the variance findings with whoever is responsible for estimating and pricing. This does not necessarily mean raising prices immediately, though it may. It means making sure quotes reflect what the work actually costs rather than what it was assumed to cost when the standard was last set.
A mid-year cost variance review that never reaches the quoting function has limited value. The connection between what the data shows and what gets quoted in Q3 is where the review pays off.
How Long This Takes
For most manufacturers, a focused mid-year cost variance review in DELMIAWorks takes three to four hours when the right reports are pulled and reviewed with the right people. Operations and finance should both be in the room. Quality should be available if material variance is significant.
The output is not a formal report. It is a short list: standards that need updating, patterns that need addressing, and findings that need to reach the quoting function before Q3 work orders start flowing.
DR Software Services helps DELMIAWorks users set up cost variance reporting and conduct structured reviews as part of our post-go-live support and application process assessment services. If your variance data is not giving you clear direction, reach out at info@drsoftwareservices.com or visit drsoftwareservices.com/our-services/application-process-assessment.





