Phone: 0 (552) 380 25 25  |  Weekdays 10:00–18:00 · Technical support 24/7

🇹🇷 TR

Digital Bridge Blog

Industry 4.0

Production Work Order Tracking: Seeing Where Every Job Is, Who Has It and How Far It Has Got

What production work order tracking is, why it beats paper travellers and spreadsheets, and seven steps to set it up with shop-floor terminals and ERP links.

9 min read  · Digital Bridge Engineering Team
Production Work Order Tracking: Seeing Where Every Job Is, Who Has It and How Far It Has Got

Production work order tracking is software that shows, in real time, which operation, machine and operator each work order is at and how much of it is finished. Unlike paper travellers and spreadsheets, it captures data on the shop floor as work happens, so planning and sales can answer "where is that order?" from a screen, not a phone call.

What actually happens in the production office

In the morning, planning prints a list of work orders and hands the travellers to the supervisors. By mid-morning sales rings: "The customer is chasing order 4521 – where is it?" The planner walks onto the floor, finds the supervisor and looks for the traveller. The answer is usually "cutting's done, it's going to bending next, probably finished tomorrow".

In the evening the travellers are collected and someone types the day's quantities into a spreadsheet. Scrap, stoppages and half-finished jobs are either left out or estimated. The next day's plan is built on yesterday's guess rather than yesterday's reality. It is the classic picture of a business that has hit the limits of running work on spreadsheets.

The problem is not the work order itself; it is that the data about it arrives late and incomplete. The ERP knows the order and the bill of materials, but not which machine the job is sitting on right now. The layer that fills this gap is covered in our article on the difference between MES and ERP: the shop-floor execution layer.

What untracked work orders cost you

An invisible work order costs you in three places: missed due dates, unnoticed stoppages and decisions made on bad numbers. Stoppages are the most expensive:

According to Siemens' "The True Cost of Downtime 2024", an hour of unplanned downtime costs $2.3 million in a large automotive plant and $36,000 in fast-moving consumer goods plants. (Siemens, The True Cost of Downtime 2024)

The same report found that large plants now average 25 unplanned downtime incidents a month and lose 27 hours of production a month as a result. In a factory running on paper travellers, most of those stoppages are never recorded against the work order, so nobody can say why the job ran late.

In Türkiye, the root cause is often that there is no system at all. According to TurkStat's ICT Usage Survey in Enterprises 2025, only 23.6% of enterprises with 10–49 employees use ERP software, compared with 76.5% of those with 250 or more. In many small manufacturers without an ERP, work orders still live on paper or in a spreadsheet.

Deciding on bad data has its own price. Data quality expert Thomas C. Redman estimates the cost of bad data at 15% to 25% of revenue for most companies (MIT Sloan Management Review, 2017). A production sheet filled in from memory at the end of a shift is exactly where that bad data starts.

What production work order tracking should record

Good tracking follows a work order through its whole life. The table below compares paper and spreadsheets with a dedicated system:

ItemPaper traveller and spreadsheetWork order tracking software
Work order statusFound out by asking the supervisorWaiting, started, stopped, finished – live
Quantity producedWritten up at shift endEntered at the terminal when the operation ends
Stoppages and causesOften not recordedStart, end and reason code
ScrapEstimatedBy reason code, per operation
Time spentUnknown or guessed from timesheetsActual time per operation
Materials usedAssumed from the BOMLinked by scanning the lot or batch
Posting to ERPManual, delayedAutomatic, when the job completes

The last two rows are the bridge between work order tracking and production traceability. If you know which lot went into which work order, you can find the affected products within minutes when a complaint arrives. Link nonconformance records to work orders as well, and your quality management system software can search for root causes in records rather than memories. The same records are the basis for working out the actual cost of each work order: the gap between the standard time in the routing and the time actually taken shows which products need their pricing reviewed.

Seven steps to set up work order tracking

  1. Map the flow. Write down every operation and decision point a work order passes through from order to dispatch. Do not install software until it is clear who approves what and where jobs wait. The items to check from selection to go-live are gathered in our MES implementation checklist.
  2. Define statuses and reason codes. Keep a simple status list – waiting, set-up, running, stopped, finished – and no more than 10–15 stoppage and scrap reasons. Long lists slow operators down.
  3. Choose the data capture points. Decide where each operation will be started and finished. Machines with PLCs can send counts automatically; on older machines an operator terminal is enough. Our guide to collecting data from legacy machines covers that choice in detail.
  4. Bring in barcodes. Print a barcode or QR code on the traveller and let the operator scan it to start the job. Typing numbers by hand is the biggest single source of error, and a barcode-based production traceability set-up reuses the same label for lot tracking.
  5. Connect to the ERP both ways. Work orders should come from the ERP, and quantities and material consumption should flow back. Otherwise you end up with two versions of the truth. If customer orders arrive via EDI, automotive EDI integration automates the source of the work order too.
  6. Pilot on one line. Start with one line or product family, measure data accuracy for two to four weeks and refine the reason codes with feedback from the floor.
  7. Turn data into indicators. Put on-time delivery, variance per work order, stoppage causes and OEE on a screen managers actually look at. Our guide to building a BI dashboard around the right KPIs helps you decide what belongs there.

Why the operator experience decides the outcome

The operator is the data source. The terminal has to work with dirty hands, gloves and noise, and no transaction should take more than three taps. Linking tracking to an andon system lets operators call for help the moment a job stops, so the problem becomes visible within minutes. When the stop is a breakdown, opening and closing the maintenance work order is the job of CMMS maintenance management software.

Three common mistakes

Trying to measure everything on day one. A forty-field screen teaches operators to skip fields. Start with status, quantity and stoppage reason, then add material and quality data once the basics are flowing.

Not splitting the work order into operations. A single-line work order shows as "in production", but nobody knows whether it is in cutting, welding or painting. The value appears once the order is broken into operation steps. For a sector example of a flow split into cutting, edge banding, drilling and packing, see furniture manufacturing software.

Collecting data nobody uses. If stoppage reasons are never discussed in the weekly meeting, operators soon start picking any reason just to move on. Management that asks for the data has to show it is being used.

How we do it at Digital Bridge

We do not sell off-the-shelf packages. Every factory's work order flow, product structure and floor conditions differ, so we start with a needs analysis and finish with a written proposal setting out scope, phases and cost. A typical project looks like this:

  • Discovery and flow analysis. We follow the real journey of your work orders on site and document where jobs wait and where data is lost. For Industry 4.0 projects the site assessment is free of charge.
  • Shop-floor data capture. We place industrial data terminals at each operation; the operator scans the barcode to start the job, selects a stoppage reason and enters the quantity. Because hardware and software come from the same team, the enclosure, screen and interface are designed for your floor.
  • The MES layer. Our MES production management solution processes that data by work order, operation and machine. It integrates with Logo, SAP, Mikro and bespoke ERP systems.
  • Feedback into the plan. Actual output flows into our production planning and scheduling (APS) solution, so a late work order shows up on the schedule immediately and the sequence can be rebuilt.
  • Pilot, then roll out. We run one line first, measure data accuracy with you and then extend to the rest of the plant.
  • Management view. On-time delivery and stoppage causes are brought onto a BI dashboard for sales and management.

If you want to compare labour time with attendance, data from SmartPass, which records attendance on a card read and calculates timesheets from the shift plan, can feed into the same analysis. To see where work order tracking sits in a wider programme, read our Industry 4.0 roadmap for SMEs; to see how work order load is balanced against available hours, read our manufacturing capacity planning guide.

Articles on traceability, maintenance and quality are collected on our Industry 4.0 topic page.

Your next step

Pick 20 work orders from last month at random and write down the planned and actual finish date for each. If you can tell from your records why the late ones were late, you are in good shape; if you cannot, work order tracking should be your first investment. Get in touch and we will look at your flow together.

Let us look at your case

Tell us about your process; after a needs analysis we send a written proposal with scope, phases and cost.

Request a Quote +90 552 380 25 25
Questions we hear most often

Frequently Asked Questions

What is the difference between work order tracking software and an ERP?

The ERP manages orders, stock, bills of materials and costs, and it opens and closes work orders. Work order tracking follows the job on the shop floor: which operation it is at, who is working on it, how long it takes and how much scrap it produces, all in real time. One does not replace the other; the best results come when tracking data posts automatically back to the ERP.

Does a small workshop need work order tracking?

In a workshop with a handful of jobs a day, where everyone can see every job, paper may be enough. Once you have dozens of work orders in progress, more than one shift or subcontracted operations, tracking becomes hard and delays are spotted late. Starting with a simple operator terminal on one line is the easiest way to see the benefit without committing to a large system.

What if operators don't keep up with data entry?

Usually the interface is the problem, not the operator. Scanning a barcode to start a job, large touch buttons and short reason lists bring each transaction down to a few seconds. Machines with PLCs can also send counts automatically, which reduces manual entry. Adjusting screens with operator feedback during the pilot makes a clear difference to adoption.

Will it work with our existing ERP?

It should, otherwise you end up with two separate records. Work orders need to come from the ERP, and actual quantities and material use need to be written back. Digital Bridge's MES integrates with Logo, SAP, Mikro and bespoke ERP systems; the scope of the integration is agreed during the needs analysis and set out in the written proposal.

Which indicators does work order tracking let us measure?

The core indicators are on-time delivery, planned versus actual time, stoppage duration and causes, scrap rate and actual cost per work order. As data builds up you can calculate OEE, identify bottleneck machines and base capacity plans on real cycle times. Your plan then rests on measurement from the floor rather than on estimates.

How much does production work order tracking cost?

Cost depends mainly on the number of operations and terminals where data is captured, whether machine counts are collected automatically, the scope of the ERP integration and the reporting you need. Digital Bridge does not sell off-the-shelf packages: it starts with a needs analysis and then provides a written proposal setting out scope, phases and cost. For Industry 4.0 projects the site assessment is free.

Have a different question? Ask Us

Talk to an Engineer

Tell us what you need to solve. We'll come back with a written proposal.