Guides · job cost variance report
How to read a job cost variance report
A variance report is only useful if it ends in a decision. Here's how to read one quickly, spot real patterns, and decide what to change.
By the MarginGuard team · FactoryEdgeAI · Last reviewed
- Read dollars first, percent second
- Group before you judge
- Match each pattern to an owner and an action
The problem
Variance reports usually arrive as a long table of jobs with red numbers. Without a reading method, teams argue about individual jobs, explain each one away, and change nothing. The same overruns show up next month.
What to measure
Read in this order: total erosion for the period; the top ten jobs by dollars eroded; then group those jobs by category, customer, part family, and work center. A pattern is the same driver showing up across three or more jobs.
How MarginGuard helps
MarginGuard produces this view automatically from your ERP export: erosion ranked in dollars, category breakdown per job, and rollups by customer and part family, so the meeting starts at the pattern, not the spreadsheet.
Next step: sign up, load the demo, or compare plans.
How to get started
- Step 1Start with the total
How much margin did closed jobs lose against estimate this period? That number sets how much time the review deserves.
- Step 2Take the top ten by dollars
Ignore small-dollar jobs with big percentages for now. They rarely move the P&L.
- Step 3Group and look for repeats
Same category, same customer, same part family, or same work center across several jobs means a pattern worth fixing.
- Step 4Assign one action per pattern
Estimate standard, price or terms, or process fix, each with an owner and a check date.
What each overrun usually means
Labor overrun: run time or rework above standard; check routing and cycle times. Setup overrun: more setups or longer first-article than planned; check batch sizes and fixturing. Burden overrun: extra machine hours or a costlier machine; check routing and machine rates. Material overrun: price changes or yield loss; check quote validity and scrap. Outside processing overrun: vendor price changes or expedites; check PO pricing against the quote.
Noise vs signal
A single job 30% over is a story; three jobs for the same customer 10% over is a pattern. Act on patterns, and note stories only if they repeat.
| Pattern | Owner | Typical action |
|---|---|---|
| Same part family over on labor | Estimating | Update the routing standard |
| Same customer over across categories | Sales | Reprice, add change-order terms, or decline |
| Same work center over regardless of part | Operations | Fix the process, tooling, or staffing |
| Material over across many jobs | Purchasing / sales | Add escalation clauses; shorten quote validity |
FAQ
- What's the difference between variance and erosion?
- Variance is actual minus estimated cost. Erosion is the resulting drop in margin dollars. With fixed revenue they're the same number.
- Should we review every job?
- No. Review the top ten by dollars, then patterns. Reviewing every job turns into explaining every job.
- Who should attend the review?
- Whoever owns estimating, sales, and operations: the three owners of the possible fixes.
Related MarginGuard pages
Related FactoryEdgeAI products
MarginGuard is the profitability layer. Pair it with the rest of the FactoryEdgeAI family when you need alarms or machine monitoring too.
- MarginGuard
Job-level profitability intelligence: estimate vs actual, margin alerts, and opportunity tracking beside your ERP.
- FactoryEdgeAI
CNC alarm lookup, troubleshooting guides, and shop-floor knowledge for machinists and programmers.
- Machine Monitor
MTConnect machine monitoring for utilization and status — pair with MarginGuard when you want contribution, not just busy spindles.
Act on job cost variance report
Create a free account, import a job-cost CSV, and review margin leaks—or load the demo shop first.
Keep your ERP. CSV import today. Create an account or sign in.