The Customer Call You Can't Answer Yet
The customer asks a simple question: where's my job. You put them on hold, walk out to the floor, and start checking machines. The part isn't at the mill it was scheduled for — it moved to deburr two shifts ago, or it's sitting behind three other jobs waiting on a work center that's backed up, or it's actually done and sitting in a bin nobody logged. By the time you get back to the phone, four minutes have passed and you're guessing at an answer instead of stating one.
This isn't a communication problem. It's a records problem. The only record of where a job stands is a paper traveler physically attached to the part, and a traveler on a machine tells you where the job was when someone last wrote on it — not where it is right now, and not how long it's been sitting there. Multiply that one phone call by every open job on the floor and you get the real cost: a supervisor who spends part of every day walking the floor just to answer questions the paperwork should already answer.
Live WIP tracking replaces the walk with a screen. This article covers what work-in-progress actually means at the operation level, how a work-center queue view gets built from the same clock-in data you're probably already collecting badly, and what it takes to keep that view honest once it's live.
What WIP Means at the Operation Level, Not Just the Job Level
"Work in progress" sounds like a single number — how many jobs are open — but that's not the useful version of it. The useful version is where in the routing each open job currently sits, and how long it's been there.
A job isn't a single blob moving through the shop. It's a routing: a sequence of operations, each assigned to a work center, each with a standard time. WIP tracking that matters answers three questions per job, continuously:
- Which operation is this job on right now?
- Which work center is it queued at or running at?
- How long has it been in that queue or that run, compared to what the routing expected?
A dashboard that only shows "12 jobs open" is a job list. A dashboard that shows "Job 4471, operation 30 (deburr), queued 6 hours, standard queue time 1 hour" is a WIP tool. The difference is the operation-level detail, and that detail only exists if something is logging transitions between operations as they happen — not at end of day, not from memory.
From Paper Traveler to Work-Center Queue: The Mechanism
The mechanism underneath any accurate work-in-progress dashboard for manufacturing is the same one underneath actual-vs-quoted labor tracking: a clock-in event tied to a specific operation on a specific job.
Here's the chain. A routing defines the operations a part travels through — say, saw, mill, deburr, inspect, ship — each assigned to a work center. A traveler is generated from that routing, either as a printed document with a barcode or QR code, or as a digital view on a tablet at the work center. An operator starts the job by clocking in at that operation — a one-tap action at a kiosk or on a mobile device — and the system now knows, in real time, that Job 4471 is running at Mill 3. When the operator clocks out, or logs a downtime reason (setup, run, waiting, rework), the system knows the job has stopped, and why.
Roll that same event stream up across every work center and you get a live work-center queue view: which jobs are queued at each station, which are running, and how long each has been there. That's the dashboard. It isn't a separate system layered on top of clock events — it's the same clock-in data, aggregated by work center instead of by job.
This is also why a paper traveler alone can't produce this view. A traveler carries the routing and the operator sign-offs as the job moves — that's its job, and it does it well as a physical record. But nobody's typing those sign-offs into a queue view in real time, so the paper record and the live floor state drift apart within a shift. Digital clock-in data closes that gap because the event that updates the dashboard is the event that starts and stops the work — there's no separate re-entry step for someone to skip.
Building a Dashboard That Defaults to the Question You Actually Ask
Most shop-floor visibility tools get one interface decision wrong: they default to a list of jobs sorted by due date. That's a scheduling view, and it answers "what's overdue," which matters, but it isn't what a supervisor reaches for twenty times a day. The question asked twenty times a day is "where is job X," and the second most common question is "what's backed up at work center Y."
A work-center queue view answers both directly. Default the dashboard to work centers, not jobs: each work center shows what's running, what's queued behind it, and how long each item has been waiting. A search by job number, part number, or customer name resolves instantly to a work center and an operation, without a floor walk. That's the "where is my job" answer delivered in seconds instead of minutes, and it's the same underlying data whether the question came from a customer on the phone or a supervisor planning tomorrow's shift.
The tools worth trusting here are the ones built around this default, not a scheduling board retrofitted with a search box. WorkTickets builds its live WIP dashboard as a work-center queue by default for exactly this reason — the routing → traveler → clock-in → WIP chain feeds one view, and searching by job, part, or customer resolves against it directly. It's worth being precise about scope here: this is visibility into where work stands and how long it's been there, not finite-capacity scheduling or a dispatch board that sequences work for you — that's a different layer, deliberately outside what this kind of tool does.
Using the Queue View to Find the Bottleneck Before It Costs a Customer
Once WIP is visible by work center, a pattern usually shows up fast: one station is consistently the one with the longest queue. That's not an accident and it's rarely random — it's the bottleneck, and it's costing you in a specific way. Every job that queues longer than its routing's standard queue time is a job whose actual cycle time is quietly diverging from what was quoted, and a customer promise date that's now at risk.
A work-center queue view turns "we always seem to be behind at deburr" from a hunch into a measurable pattern: queue times at that station, compared across weeks, show whether it's a capacity problem (not enough hands or machine time) or a sequencing problem (jobs arriving in the wrong order because upstream operations ran long). That distinction matters because the fix is different — more capacity solves one, better routing or scheduling discipline solves the other — and you can't tell which one you have without the queue data.
Rework logging feeds the same view. A job that bounces back to an earlier operation shows up in the queue as an unexpected re-entry, and industry research on shop-floor quality puts scrap and rework costs as high as 2.2% of annual revenue for the average manufacturer — a real number worth tracking down to the operation that's causing it, not just absorbing at the end of the quarter. A queue view that shows a job cycling back through the same work center repeatedly is often the fastest way to spot which operation is generating that cost before it compounds across the next ten jobs that follow the same routing.
What It Takes to Keep the Data Honest
None of this works if clock-in compliance is inconsistent. A dashboard is only as accurate as the events feeding it, and the two failure modes are predictable: operators forgetting to clock out at shift change, and jobs sitting "in progress" on the screen long after they physically moved. Both are adoption problems, not software problems, and they're worth naming plainly rather than glossing over — a one-tap kiosk lowers the friction of clocking in and out, and a supervisor approval step on manual entries catches most of the drift, but neither replaces the discipline of clocking out when the job stops. Shops that get clean WIP data are the ones that treat the clock-in step as part of the job, not paperwork bolted on afterward.
The payoff for that discipline is a floor where "where's my job" gets answered from a screen in seconds, where a backed-up work center shows up as a pattern instead of a rumor, and where the next customer call doesn't require a walk. If you want to see how the routing-to-queue chain looks on your own job mix, WorkTickets runs a 14-day trial with no card required to start, across all four tiers — start a trial and bring a real routing to test against.
For a broader look at how WIP visibility fits into execution and costing as a whole, see the work-in-progress dashboard breakdown, the mechanics of answering "where is my job" from the floor, and how to read a queue for bottlenecks. Shops running a mostly paper-based process today can also review the work-center queue tracking primer or the full execution-and-costing guide before moving to a live system. A printable work-center WIP board is also available for shops that want a physical queue reference on the floor alongside the digital dashboard.
