A Work-In-Progress Dashboard for Manufacturing That Supervisors Use

The Dashboard Nobody Opens

Every shop that's bought software in the last five years has a dashboard somewhere. A screen with tiles, maybe a bar chart, maybe a gauge that says "Utilization: 78%." It was in the demo. Somebody was excited about it. Eight months later it's open on a monitor in the office that nobody's office is next to, and the supervisor still walks the floor to find out what's late.

That's not a failure of dashboards as a category. It's a failure of the specific dashboard, because it answered a question nobody on the floor was asking. Supervisors don't want a KPI. They want to know, in the next four seconds, what's sitting where, how long it's been sitting there, and which of those things is about to become a customer phone call. A work-in-progress dashboard for manufacturing earns its screen real estate by answering exactly that — nothing more abstract, and nothing that takes a second click to interpret.

This article is about what that dashboard actually needs to contain, why the default view should be a work-center queue and not a job list, and how the same screen that answers "where is my job" also does quiet duty as a bottleneck finder — without pretending to be a finite-capacity scheduler it isn't.

Why Most Work-In-Progress Dashboards Sit Unused

The pattern is consistent across shops that have tried and abandoned a WIP screen: the dashboard was built around what the software could report, not around what the supervisor needed to decide. Total jobs open. Average cycle time. A pie chart of job status. All true, none of it actionable at 7:15 in the morning when the question is "what do I put on machine 4 next."

WIP tracking on the shop floor only gets used when it's organized around the unit the supervisor actually manages — the work center, not the job number. A job list sorted by due date tells you what's late. It doesn't tell you where the late job currently sits, who's supposed to be working it, or what's stacked up in front of it. That's a different question, and it's the one that gets asked out loud on the floor.

What a Work Center Queue View Actually Answers

Flip the default view from "jobs" to "work centers," and the dashboard changes shape. Instead of one row per job, it's one column per work center — saw, mill 1, mill 2, deburr, weld cell, final inspection — with cards for whatever's queued, running, or waiting at each one. The supervisor looks at the mill column, sees three jobs stacked, and knows in one glance that mill 2 is the constraint this morning without opening a report.

Underneath that queue view, the useful dashboard tracks three things per job, per operation:

• Status — waiting, running, or flagged (a downtime reason code like setup, waiting on material, or rework attached to whatever's stalled).
• Age — how long the job has sat at this operation, not just how long it's been open overall. A job that's been in the shop three days but only waiting at deburr for twenty minutes is not the same problem as one that's been sitting at deburr for two days.
• Actual vs. quoted so far — not a full profitability report, just a quick signal at the operation level: is this running long against what the routing called for.

That third point matters because a WIP screen that only shows location is half the picture. A job can be exactly where it should be and still be quietly eating margin because the operation is running two, three times over its standard. The queue view earns credibility with a supervisor the first time it shows them that before the job crosses their desk as a problem.

Turning "Where Is My Job" Into a Search, Not a Walk

The second most common question on a shop floor, after "what's next," is "where is my job" — asked by a customer on the phone, a salesperson standing in the doorway, or an owner who wants an answer before lunch. Historically that question means someone puts down what they're doing and walks the floor.

The value of a WIP dashboard isn't that it replaces the floor walk for the supervisor. It's that it replaces the floor walk for everyone else who used to interrupt the supervisor to ask.

A dashboard built for this searches by job number, part number, or customer name and returns the current work center, the current status, and how long it's been there — the same three data points from the queue view, just filtered to one job instead of shown across all of them. That's the whole feature. It doesn't need to be more sophisticated than that, and adding more to it usually makes it slower to answer the one question it exists for.

Bottleneck Identification Without Pretending to Schedule

Job shop bottleneck identification gets sold, in a lot of software categories, as a finite-capacity scheduling problem — an algorithm that tells you which work center will be the constraint next Thursday. That's a real capability, and it's also a different tool than a WIP dashboard, built on a different set of assumptions about how reliably a shop's routings and lead times hold up in practice. A WIP dashboard doesn't schedule anything. What it does is show you, honestly, where things are stacking up right now — which is enough to answer the bottleneck question the way most small shops actually need it answered: not "what will be the constraint," but "what is the constraint, today, and has it been the constraint for the last three days running."

That distinction is worth being explicit about, because a supervisor who's been burned by an ERP deployment that promised scheduling and delivered a stalled rollout is rightly suspicious of anything that claims to predict the floor. A queue view that just shows aging, honestly, across every work center does something more modest and more trustworthy: it makes the pattern visible without claiming to have solved it. If mill 2 has had a three-job queue every morning for two weeks, that's not a forecast — that's an observation anyone can act on, whether the action is cross-training an operator, moving a machine's priority, or finally admitting the quote times for that operation are wrong.

What Belongs on the Screen — and What Doesn't

The failure mode on the other side of "too abstract" is "too much." A dashboard that tries to show scrap trends, labor cost rollups, on-time percentage, and a live Gantt chart all on one screen ends up being read by nobody, because reading it takes longer than walking over and asking. The queue view earns its keep by staying disciplined about what's on it:

• Work centers as columns, jobs as cards — always the default view, never buried behind a click.
• Age and status color-coded, so a stalled job is visually obvious before anyone reads a number.
• A search bar for the "where is my job" question, separate from the queue view but one click away.
• A drill-down, not a wall of numbers — click a card to see the actual-vs-quoted detail; don't put it on the board by default.

Everything else — scrap causes, labor cost, profitability by job — belongs in a report the supervisor pulls when they want it, not competing for attention with the one screen they check forty times a shift.

Getting to a Dashboard Your Supervisor Actually Opens

Most shops running QuickBooks and a stack of paper travelers don't lack the discipline to track work in progress — they lack a screen that reflects the floor back to them in the shape they already think in. WorkTickets builds its live WIP dashboard around exactly the work-center queue view described above: jobs shown by where they're sitting, age visible at a glance, and a "where is job X" search by job, part, or customer number for anyone who needs the answer without walking the floor. Actual-vs-quoted labor is attached at the operation level on every tier, so the queue view isn't just a location map — it's an early flag on jobs that are quietly running long before they show up as a margin problem at quarter close.

If you're building this for the first time or replacing a dashboard nobody opens, it's worth reading through our guides on WIP tracking on the shop floor, work-center queue tracking, and job shop bottleneck identification for the mechanics behind each piece, or the broader execution and costing guide for small job shops for how WIP visibility fits with routing, traveler, and scrap-logging work. If your floor still needs a physical reference alongside the screen, our Work-Center WIP Board & Queue Tracker gives supervisors a printable version of the same queue-by-work-center layout for stations without a monitor.

WorkTickets runs a 14-day trial across all self-serve tiers ($199, $349, and $599 per month for Essentials, Professional, and Business), so you can put the queue view in front of your actual supervisor on your actual jobs before deciding anything. If you'd rather see it walked through first, book a demo and bring a work center you're currently tracking on paper.