Work order variances should be recorded during execution, at the operation where they occur, rather than only when the order is closed. This shows whether the difference was caused by material, time used, output quantity, scrap, or a change in operations. Such records turn the gap between plan and actual execution into decision-ready information and a basis for production cost control.
A work order connects the production plan with actual execution: the item, quantity, bill of materials, operations, work centres, planned time, and expected consumption. A variance occurs when an actual value differs from its planned value.
A total difference at the end of an order is rarely enough. For example, higher material consumption may result from scrap, a material substitution, different packaging, poor yield, or an inaccurate bill of materials. Longer time may result from machine downtime, setup, waiting for material, additional inspection, or an incorrectly set standard.
Without a cause, a variance remains an accounting difference. With a cause, it becomes operating information: should the plan change, should an issue at the workplace be resolved, should procurement be checked, or should capacity be scheduled differently?
For a production manager, the key question is not only, "How much did we deviate?" A more useful question is, "At which operation, at what point, and why did the plan stop matching the actual work?"
A material variance compares planned and actual consumption of raw material, semi-finished goods, packaging, or auxiliary material. In practice, it should be viewed both in quantity and value.
A quantity variance may arise from:
A value variance may also arise when the actual purchase price differs from the planned price, even if the quantity consumed is unchanged. These two causes should not be merged into one unexplained line item. Production may affect the consumption quantity, while procurement and price calculation may explain the value component of the difference.
Time on a work order usually includes setup, machine time, manual work, inspection, and, depending on company rules, certain types of downtime. Planned time supports capacity planning, delivery dates, and the calculation of labour or machine cost.
Record actual time by operation and by time type whenever the process permits it. A useful record distinguishes, for example:
Not every longer duration indicates poor execution. The first batch of a new product, a small batch with frequent tool changes, or additional incoming inspection may have a justified impact. Still, without a recorded reason code, it is impossible to distinguish a justified variance from a recurring loss.
A quantity variance concerns the difference between planned and actually reported output. It includes good quantity, work in progress, scrap, rework, and possible overproduction.
For production tracking, it is useful to report output as it occurs or at clearly defined short intervals. If all quantities are reported only at the end of a shift or order, it is harder to connect a shortfall with a specific material batch, machine, shift, or process event.
Overproduction also requires an explanation. It may result from a minimum technical batch, packaging requirements, a planning error, or a deliberate decision to cover expected demand. Without a record, excess output can conceal an inaccurate plan or create unwanted inventory.
Scrap is not merely a smaller finished quantity. It may consume material, labour time, machine capacity, and energy, and it may sometimes require additional disposal. It should therefore be reported with the quantity, operation, and reason.
Scrap reasons should be limited to a short, understandable list suited to the process. Examples may include a material defect, incorrect settings, handling damage, dimensional deviation, or an assembly error. An overly broad category such as "other" reduces the value of data, especially when it becomes a frequent selection.
Keep rework separate from scrap. A repairable item is not the same as an irreversible loss, but it creates additional cost and uses capacity. If rework is reported as normal output, the actual time and actual product cost can remain hidden.
An operation variance occurs when work is performed differently from the defined routing. It may include skipping an operation, adding an operation, changing the work centre, changing the sequence, using external processing, or repeating an operation.
Such variances are not necessarily errors. Available capacity, machine failure, or a quality requirement may justify them. The approved change and its reason need to be recorded. Otherwise, the plan appears to have been executed even though the actual workflow indicates different resource needs.
Late work order closing often relies on memory, estimates, or a shift-level total. This approach may close the order administratively, but it does not provide a reliable basis for process improvement.
A sound recording process follows several simple rules:
Timeliness does not necessarily mean entering every data point instantly. It means establishing a rhythm that preserves the connection between an event and its cause: by unit, batch, pallet, operation, shift, or another natural process control point.
Production cost control does not begin only when accounting calculates the finished product. It begins when more material is consumed, work takes longer, scrap occurs, or an operation changes.
A practical analysis sequence can look like this:
Example: a work order consumes more material than planned, while reported time is normal. The total material cost alone does not explain enough. If the record shows scrap at the first operation after a material roll change, the review can focus on incoming material, machine settings, and the setup method. If the record shows regular excess consumption without scrap across multiple orders, an outdated standard or incorrectly defined technical requirement is more likely.
Another example: an order is late because of additional time at final inspection. If quality records recurring rework from the preceding operation, the issue is not only inspection capacity. The cost is created earlier, while final inspection merely detects it.
An overly detailed form slows work and encourages skipped entries. Too little detail produces data that cannot support action. The appropriate level of detail depends on variance frequency, material value, capacity bottlenecks, and quality risk.
As a starting point, it is often more useful to track a limited number of reasons with the greatest impact than to collect many categories that are rarely used. After several analysis cycles, the reason list can be adjusted to actual problems.
Interpretation also has limits. A variance does not prove its cause by itself. It indicates where the process should be checked. A reason entered without verification may be incomplete, and one order may not represent a trend. A decision to change a standard should therefore rely on repeated records, expert review, and confirmation of actual operating conditions.
An ERP system can connect the work order, material issue, labour reporting, output, scrap, inventory, and cost calculation. The presence of data alone is not enough. Clear events, responsibilities, and recording rules are required.
In manufacturing processes, three questions are especially useful:
In manufacturing projects, ORKA approaches these questions through process, data, and responsibilities, rather than only by configuring fields in a system. Learn more at ORKA for manufacturing .
Choose a work order with frequent differences between plan and actual execution. Follow it from material issue through reporting the finished quantity. For every variance, record the operation, time of occurrence, quantity, reason, and the person or function responsible for verification.
This short review often shows whether data is missing, reporting is late, or the plan no longer reflects the actual process. Where a broader review of processes, data, and ERP support criteria is needed, ERP and process screening can structure the next decisions.