At a forty-person fabrication shop, the customer service coordinator gets the same kind of call several times a day. Where's order 4471? Will it ship Friday? She checks the ERP, which says the job was released two weeks ago and nothing since, because operators don't record operations as they finish them. So she walks out to the floor, finds the job traveler on a cart near the welding bay, asks the supervisor, and comes back with an answer that's half information and half hope. On Friday, the job is still waiting for powder coating, and the customer hears about it when they call again.
Most small manufacturers know what's happening on their floor, collectively. The supervisors know, the operators know, and the traveler on the cart knows. What's missing is a way for that knowledge to reach the office, and the customer, without someone walking out to find it. The fix is a lightweight way of recording progress and a view that turns it into answers.
This article covers what to set up on the floor and in your ERP first, and what a live job tracking system does once progress is being recorded.
What not knowing costs
The direct cost is time: customer service walking the floor, supervisors interrupted to answer questions, and production meetings spent establishing where jobs are before anyone can decide anything.
The indirect costs are larger. Promises made without real information get broken, and customers lose confidence. Late jobs are discovered late, when the only fix is expediting, which pushes other jobs back and creates the next round of late jobs. Without reliable data, nobody can see where work is actually getting stuck, so the bottleneck stays a matter of opinion.
Set up progress recording first
Pick the stages that matter
You don't need to track every operation to answer most questions. Choose the stages that matter for visibility and planning, such as material received, cutting, machining or forming, welding, finishing or outside processing, inspection, packing and shipped. Customers mostly want to know how far along a job is and whether the date will hold.
Make recording effortless
Operators won't fill in forms between jobs. A barcode on the traveler scanned at a tablet or scanner at each work center, once when a job starts and once when it finishes, takes seconds. Place scanners where the work happens. If scanning isn't practical somewhere, a supervisor updating stages at set times of day is better than nothing.
Make the routing realistic
Check that the routings in your ERP match how jobs actually flow through the shop. A job that the ERP thinks goes through five operations but actually goes through seven will always look further along than it is.
Track outside processing
Jobs sent out for plating, heat treatment or coating disappear from view in many shops. Record the date sent, the vendor's promised return date and the actual return date for every outside operation.
Decide who can promise dates
Agree who may give customers a ship date and on what basis. Dates promised from a live view of the job and the schedule hold up far better than dates promised to end a phone call.
What live job tracking does
- Records progress as it happens. Each scan updates the job's stage in the tracking system and, where your ERP allows it, writes back the operation completion.
- Shows every job on one screen. A board shows every open job with its customer, due date, current stage and time in that stage, filterable by customer, work center or due week.
- Predicts completion. Using the remaining operations and typical time per operation and queue, measured from your own scan history, the system estimates when each job will finish and ship.
- Flags risk early. Jobs whose predicted ship date has slipped past the promised date, jobs sitting at a stage for longer than usual, and outside processing that's overdue back are flagged to the production manager and customer service, while there's still time to act.
- Answers status questions. When a customer emails asking about an order, the system drafts a reply from live data, such as "Order 4471: welding is complete, the parts are at the powder coater and due back Wednesday, and we expect to ship Friday," for customer service to check and send. Regular customers can be given a simple portal view of their own open orders.
- Sends proactive updates. Customers can be told automatically when key milestones are reached, and customer service is prompted to contact customers whose jobs are at risk before the customer finds out the hard way.
- Reports on delivery performance. A weekly report shows on-time delivery, the jobs that were late, and where they lost time, so the conversation about bottlenecks is based on evidence.
The AI part is in the communication: reading customer emails, finding the right orders, drafting accurate status replies, and summarizing why jobs are late from supervisors' notes. The tracking and predictions come from your own scan data, which keeps them grounded.
That's the job our live job tracker does, and the manufacturing page shows how it connects with quoting, job costing and inventory.
A worked example
Take the fabrication shop from the opening. It defines eight stages, from material received to shipped, and puts barcode scanners at the saw, the laser, the press brakes, the welding bays, the outside processing dispatch point and the packing bench. Operators scan the traveler at the start and finish of each operation, which adds a few seconds per job. Within weeks, the job board shows every open order's stage. When the customer emails about order 4471, the coordinator sees that welding finished on Monday, the parts went to the powder coater on Tuesday, and the coater's promised return date is Wednesday. The system drafts a reply saying the order is expected to ship Friday. On Wednesday afternoon the parts haven't come back, so the job is flagged as at risk. The coordinator calls the coater, learns it'll be Thursday, and tells the customer the same day, before the customer has to ask.
What to watch out for
- Burden on operators. If recording progress takes more than a few seconds, it won't happen consistently. Keep it to scans, and fix anything that makes scanning awkward.
- Using the data against people. If scan data is used to criticize individual operators, the scanning will become unreliable. Use it to find process bottlenecks, and say so.
- Predictions without history. Early predictions will be rough until the system has a few months of scan data. Treat them as guides at first, and let the dates firm up as history builds.
- What customers can see. Decide carefully what a customer portal shows. Customers need the stage and expected date, while internal notes and other customers' jobs on the same machine should stay private.
- Another screen nobody looks at. A board is useful only if it's used in daily production meetings and by customer service. Build it into those routines from day one.
How to tell whether it's working
Count status calls and emails and how long each takes to answer, before and after. Track on-time delivery against promised dates, and how many at-risk jobs were flagged early enough to recover. Measure scan compliance at each work center, since gaps in scanning will show up as jobs that seem stuck. And watch where jobs spend their time between operations, because the queue times the board reveals are often the most useful information it produces.
Where to start this week
Take ten open jobs and trace each one: where is it physically, what stage does the ERP say it's at, and when is it promised? The gap between the two answers shows how much your current system can be trusted. Then define your tracking stages and set up scanning at the two work centers where jobs most often wait, often welding or finishing, or the dispatch point for outside processing.
Once progress is recorded at even a few key points, answering customer questions from data becomes possible, and adding the remaining stages and the prediction layer is a natural next step. Customer service stops walking the floor, and customers start hearing about delays before they have to ask.
For a quick read on where job tracking sits among the other jobs worth automating in your plant, run the free PATH report on your website. If you'd rather talk it through, book a call.