A customer calls to ask whether their order will ship on Friday. In many factories, answering means a supervisor walking the floor: counting parts at the press, checking the queue at welding and asking the paint shop what they have. By the time the answer reaches the office, it is already out of date.
Production tracking by stage replaces that walk with a record. This article explains what stage-level tracking means, what to record as work moves from pressing to dispatch, why tracking so often becomes unreliable, and how to set it up so the floor actually keeps it current.
What production tracking means
Production tracking is recording the progress of work through production as it happens. It can be done at three levels of detail, and each answers a different question:
| Level | The question it answers | What is recorded |
|---|---|---|
| Order level | Is this order done? | Quantity completed against the order, and the expected finish date |
| Stage level | Where is this order right now? | Quantity completed, waiting and rejected at each stage |
| Batch or unit level | Which parts went where, and when? | The identity of each batch, lot or part as it passes each stage |
Order-level tracking is what most spreadsheets manage. Stage-level tracking is where shop-floor visibility comes from, and it is the focus of this article. Batch or unit-level tracking adds traceability on top.
The building blocks: production orders, work orders and stages
Stage tracking needs a structure to hang records on. In most factories that structure has three parts:
- A production order says what to make, how many and by when.
- Work orders break the production order into units of work for the floor, often by stage, batch or machine.
- Stages are the steps the work actually passes through, in the order it passes through them.
The difference between the first two is a common source of confusion, so we cover it separately in production orders vs work orders. For tracking, what matters is that every record on the floor can be tied back to a work order, and every work order to a production order.
Tracking work through the stages
What progress means changes from stage to stage. Taking a typical sheet-metal fabrication flow as a general example:
| Stage | What to record | What tends to go wrong |
|---|---|---|
| Pressing (blanking, forming and similar operations) | Quantity pressed, rejects, die or setup used | Large runs go ahead of need, so counts drift from what later stages require |
| Bending | Quantity bent, rejects, machine | Half the order bent and half still waiting, recorded as a single status |
| Welding | Quantity completed at each welding stage, for multi-stage assemblies | Sub-assemblies waiting for a missing component disappear from view |
| Painting | Quantity painted, rework for finish | Parts wait for a full load or for curing, so done and moved differ |
| Quality checks | Result at each stage: passed, rejected or held | Results written up later in a separate register, so status looks better than it is |
| PDI | Order-level inspection result | Treated as a signature rather than a recorded step |
| Dispatch | Quantity dispatched against the order | Partial dispatches not recorded against the remaining balance |
Two points from this table apply everywhere. Record quantities, not only statuses: an order with 300 of its 500 parts bent is not bent. And record rejects and rework where they happen, or the quantities further down the line will never add up.
Why stage-level visibility matters
- Bottlenecks show up as queues. When you can see quantities waiting at each stage, a pile-up in front of welding is visible today, not when the delivery date slips.
- Delivery promises become estimates instead of guesses. Knowing that an order has cleared pressing and bending but not welding tells you how much work remains.
- Quality problems can be contained. If a defect is traced to a bending setup, stage records show which batches went through that setup and where they are now.
- Plans stay connected to reality. A plan built on yesterday's spreadsheet drifts from what is happening on the floor; live stage records keep it honest.
- Work in progress becomes measurable. Stage records are the raw material for knowing how much WIP sits where, which we cover in what is WIP in manufacturing.
Common reasons tracking breaks down
Most tracking systems fail quietly. Nobody decides to stop using them; the data simply stops being trusted. The usual causes:
- Updates happen at the end of the shift from memory, so the record is always hours behind and sometimes wrong.
- Recording takes too long. If logging a stage means filling in ten fields, operators will batch it up or skip it.
- Done and moved are treated as the same thing. A batch that is welded but still at the welding bay is not yet available to painting.
- Rework loops aren't recorded. A part sent back from painting to welding vanishes from the count and reappears later as a surprise.
- There are several sources of truth, such as a whiteboard, a register and a spreadsheet, and they disagree.
- The stages in the system don't match the stages on the floor, so people translate, and translation introduces errors.
How to set up stage tracking
- Map the stages as they really are, including sub-operations and multi-stage processes such as welding done across several stations.
- Define what complete means at each stage, and whether quality has to pass the work before it moves on.
- Choose the unit of tracking: the whole order, a batch or an individual part. Most factories track batches against work orders.
- Make recording fast at the point of work. A scan or a couple of taps on a phone gets done; a form at a desk across the floor does not.
- Record quantities in and out, plus rejects and rework, not just a status.
- Give every work order or batch a clear identity, such as a production ID, so records can't be attached to the wrong job.
- Review stage status daily with supervisors and planners, and fix the data whenever it disagrees with the floor.
How digital production systems help
Paper travellers and spreadsheets can track stages, but they depend on someone copying the data to where others can see it. A digital production system records progress once, at the stage, and makes it visible everywhere at the same time.
In practice that means a current view of every order by stage; quantities that add up because rejects and rework are recorded where they occur; identification by production ID, QR code or barcode so records attach to the right job; and dashboards and reports built from the same records rather than compiled by hand. Planning, production and quality look at the same numbers.
An example: Budve SmartFlow
Budve SmartFlow, a manufacturing production and quality management system Reinstate Labs designed and built, is organised around a stage-wise workflow. Its production capabilities include production orders, production planning, work orders, WIP, batch and lot tracking, machine utilisation and production IDs in a format such as PROD-2026-000001, along with a QR and barcode workflow capability.
The unit's manufacturing processes are modelled as they run on the floor: bending; pressing, which covers blanking, forming, pearling and restricting; welding, carried out in five stages; and painting. Quality management follows a stage-wise workflow, PDI and dispatch form their own module, and the system also has dashboard and reporting modules.
Conclusion
Shop-floor visibility comes from stage-level records that are kept at the point of work, count quantities rather than statuses, and tie every record to a work order and a production order. Get those foundations right and the questions that used to need a walk around the floor can be answered from a screen.
For how this fits into a wider production and quality system, see our manufacturing page. Turning stage records into dashboards that planners actually use is part of our data and analytics work.