Manufacturing work-order labor variance software
Your ERP tells you a work order ran over after it closes. Takum reads the daily hours and flags the drift while the order is still open.
30-50%
McKinsey reports what happens when high-mix, low-volume manufacturers build real-time visibility, daily performance planning, and accountability into standard work: productivity typically improves 30 to 50 percent within eight to 12 weeks. This page walks through the problem those plants fixed, and how.
/ 01 · The problem
Variance found at close is history, not control.
Work-order labor variance is the gap between the hours a routing says a job should take and the hours your people actually charge to it. Every manufacturer that runs work orders has it. The question is when you find out.
Most plants find out at month-end close. By then the order is finished, the crew has moved on, and the variance report is a history lesson. You can argue about the standard. You can code the loss to a bucket. What you cannot do is change how the job was run, because the job is over.
The useful moment is earlier: day 2 or day 3 of an open order, when the hours are drifting past pace and a supervisor can still re-sequence the work, move people, or find out the standard was wrong before it burns through the rest of the schedule.
/ 02 · The root cause
The overrun is not sudden. It is unmeasured.
A job rarely blows through its standard in one bad shift. It drifts. A setup runs long, a part fights back, a crew works short one person. That drift shows up in the daily hours from the first day it starts.
The root cause of finding out late is measurement timing. In shops without shop-floor data capture, actual hours ride payroll's calendar and land weekly, sometimes biweekly. Variance gets computed at close, because that is when accounting needs it. And pace, the percent of hours consumed against the percent of work complete, is rarely computed at all.
That is still the norm in 2026, not a relic. IoT Analytics counts 54 percent of plants worldwide still running production on paper or spreadsheets, and Zebra's 2024 study of 1,200 manufacturing leaders found just 16 percent with real-time visibility into work in process. When something does go wrong, Accenture found, 78 percent of companies need at least a week to fully understand the impact. In a shop like that, the one number that would send a supervisor to walk the job today is not on any report anyone sees.
None of this is new. Harvard Business School's Robert Kaplan, with H. Thomas Johnson, put it on the first page of their 1987 book on management accounting:
"Today's management accounting information... is too late, too aggregated, and too distorted to be relevant for managers' planning and control decisions."
Johnson & Kaplan, Relevance Lost, Harvard Business School Press, 1987
That was written almost four decades ago. In most plants, the reporting cycle it describes has not changed. Stale standards make it worse: when a routing has not been updated since the process changed, the variance report reads as noise, and people stop trusting it. A number nobody trusts is a number nobody acts on.
Not every hour of drift is a crew running slow, either. Rework is labor variance wearing a disguise: the hours to fix a part land on the same work order as the hours that made it, and scrap burns hours that produce nothing at all. ASQ estimates quality-related costs run 15 to 20 percent of sales at many companies, and the labor share of that estimate sits inside work orders as rework hours nobody separated out. A month-end variance line cannot tell rework from a slow crew. A daily flag cannot either, but it points at the right order while the parts are still on the floor.
/ 03 · The solution
How labor variance software works in practice.
Feed
A daily file of hours
Each day, hours by employee and work order come over from your time charging. A flat file or an export from the ERP is enough. No new time clocks, no shop-floor rollout.
Compare
Hours against the standard
Hours to date get compared against the standard for that routing, at the point the order is in its life. An order at 40 percent of its hours with 20 percent of the work done is a different fact than the same total at 90 percent done.
Flag
While the order is open
Orders trending past standard get flagged. The supervisor sees which order, which day the drift started, and how far past pace it is running.
One honest caveat: a flag is a question, not a verdict. Sometimes the job is genuinely in trouble. Sometimes the standard is wrong. Both answers are worth having while there is time to use them.
One more honest note, about the other half of the ratio. The clean version of pace uses earned hours: units actually completed, times the standard hours per unit. When completion reporting is reliable, that is the comparison Takum runs. In many job shops it is not, because crews report finished quantities in batches, days after the work happened. The daily hours still carry the signal. A job burning a third past its expected pace is worth a walk no matter what the completion count says, and Takum flags when the completion data is too thin to lean on.
Built to catch it early, not explain it late.
Takum is cost-control software that identifies work-order labor overruns and unsupported vendor charges while there is still time to act.
For a manufacturer, that means Takum takes the daily hours feed described above, learns what normal pace looks like for each routing, and surfaces the orders that are drifting, in time for your team to step in. It sits beside your ERP rather than replacing it. Your standards, your work orders, and your time charging stay exactly where they are.
Takum does not promise that every flag saves money. People still make the call on the floor. What it removes is the excuse that nobody could have seen the overrun coming, because with a daily feed, someone can.
/ 04 · Illustrative example
What a catch on day 4 is worth.
The numbers below are invented round numbers chosen to show the math.
Caught on day 4, that order is a conversation: re-sequence the remaining operations, move people, or check whether the standard itself is wrong. Caught at close, it is a variance line and an awkward meeting.
An operator taught us the principle behind this page. Ben Burgess, P.E., who runs Burgess Civil in Tampa, put it plainly: what gets measured gets managed. Kaplan and Norton opened their 1992 Harvard Business Review article on measurement with the same idea: "What you measure is what you get." The day-4 flag is that principle applied to labor hours. Nothing about it is magic. It is a number someone sees in time to act on it.
The $65 loaded rate is an assumption, not a measurement. BLS puts total employer compensation for production workers in manufacturing at $38.86 per hour worked as of March 2026, wages plus benefits; loaded rates that add overhead and indirect costs run well higher, and $65 is our round working number. Swap in your own; the math is the point, not the rate.
/ 05 · Fit
Who this is for, and who it is not.
A good fit if
- You run work orders with routings and labor standards, and hours get charged to them by employee.
- You can produce a daily export of those hours, or your ERP already can.
- Labor variance shows up at month-end, and by then nobody can explain it or do anything about it.
Not a fit if
- Labor is not charged to work orders. With nothing to compare against a standard, there is nothing to flag.
- You only want job costing after close. Your ERP already does that, and Takum would not add much.
- You cannot produce a regular hours feed. Takum cannot flag what it cannot see.
See your variance while you can still act on it.
Request a demo and see how a daily hours feed turns into flags your supervisors can act on the same day.
/ Sources
- 01McKinsey & Company, Energizing industrial manufacturing through active performance management (2020). The 30 to 50 percent productivity figure for high-mix, low-volume manufacturers within eight to 12 weeks.
- 02IoT Analytics, MES Market Report 2025-2031 (December 2025). 54 percent of plants worldwide run production on pen, paper, or spreadsheets.
- 03Zebra Technologies, 2024 Manufacturing Vision Study. 16 percent of 1,200 surveyed manufacturing leaders report real-time visibility into work in process.
- 04Accenture, 2023 survey of 1,230 senior executives across engineering, production, supply chain, and operations. 11 percent had near real-time alerting for production and supply disruptions; 78 percent needed at least a week to fully understand the impact.
- 05H. Thomas Johnson & Robert S. Kaplan, Relevance Lost: The Rise and Fall of Management Accounting, Harvard Business School Press (1987). Quoted from page one.
- 06Robert S. Kaplan & David P. Norton, The Balanced Scorecard: Measures That Drive Performance, Harvard Business Review (January-February 1992).
- 07U.S. Bureau of Labor Statistics, Employer Costs for Employee Compensation, Table 4 (March 2026). Production occupations in manufacturing: $38.86 per hour worked, total compensation.
- 08ASQ, Cost of Quality. Quality-related costs of 15 to 20 percent of sales at many companies.
- 09Ben Burgess, P.E., Burgess Civil, LLC, Tampa. Quoted with written permission, July 2026.
Every figure above was verified against the publisher's own source on July 23, 2026. The example in section 04 uses invented round numbers and says so. If you find an error, write to imsulen@takum.ai and we will correct it.
