A shop-floor job prioritization tool should answer one question without hesitation: what does this operator run next? If the answer still requires a supervisor huddle, a whiteboard check, or a gut call based on whoever is pushing hardest, the tool is not doing its job.
We work with high-mix, make-to-order discrete manufacturers who face this problem every single day. Operators are ready to work. Material is on hand. And yet the question of which job to pick up next triggers a conversation, a delay, or a wrong call that costs an hour of setup time and moves the wrong order closer to late. That is the problem we built Protected Flow Manufacturing (PFM)™ to solve – not with a better schedule, but with a continuously updated answer to that one question.
Why Dispatch Lists and ERP Priority Queues Fall Short on the Shop Floor
Most shops rely on some version of a dispatch list – a sorted queue of jobs pulled from the ERP. It looks like a prioritization tool. In practice, it ages the moment it is printed.
The core problem is timing. A dispatch list reflects the state of the shop when the data was last refreshed, which is often overnight. By the time an operator sees it, a machine may have gone down, a rush order may have arrived, a delivery may have come in short, and three jobs may have moved to a different work center. None of that is in the list.
ERP priority queues carry the same limitation. They are typically sorted by due date, which sounds reasonable until you realize that due date alone does not tell you how close a job is to actually being late. A job due in four days with six operations left is in far more danger than a job due tomorrow that only needs final inspection. A due-date queue cannot see that difference.
The result is predictable. Operators either follow the list blindly and run the wrong jobs, or they stop trusting the list entirely and fall back on their own judgment – which is inconsistent, hard to defend, and breaks down completely across a shift change.
What a Real Shop-Floor Job Prioritization Tool Should Actually Do
A shop-floor job prioritization tool has one job: give every operator, at every work center, a trustworthy answer to “what do I run next?” – and keep that answer current as conditions change.
For a high-mix discrete shop, that means the tool has to show live priorities at each work center rather than a snapshot from last night, reflect changes when something disrupts the plan, give every operator a consistent answer regardless of which supervisor is on the floor, and account for more than just due date when deciding what is most urgent.
That last point is where most tools fall short. At LillyWorks, the deciding factor is not due date. It is Threat Level.
Threat Level is how much each job is at risk of being late. Due date and customer are important inputs to that calculation, but they are not the driver. Due date is an important input, but it is not the driver. Threat Level is the default driver. Customer is a field that may override Threat Level if needed, so Threat Level is the default but can be overridden when your business rules require it.
Threat Levels are not manually assigned. They are calculated in real time for each operation at each resource area, based on approved data from ERP, machines, and other inputs. Every operation on every production order has a specific Threat Level. At each work center, PFM shows a live list of jobs sorted by Threat Level – or by a configured priority override where applicable. When conditions change, Threat Levels recalculate and the list updates. Operators do not need to ask a supervisor what to run. They look at the list and work the top job.
The Difference Between Scheduling and Real-Time Job Prioritization
This distinction matters more than most people expect.
A schedule is a plan built at a point in time. It sequences work based on the information available when it was created – due dates, routings, capacity estimates. Once it is set, it is fixed. When reality diverges from the plan, someone has to intervene, update the schedule, and get the change communicated. In a high-mix environment where conditions shift daily, that cycle breaks down fast. You spend more time maintaining the schedule than running the shop.
Real-time job prioritization works differently. It does not defend yesterday’s plan. It continuously reflects today’s conditions.
Think about the difference between printing directions before a long drive and using GPS. Printed directions may have been accurate when you made them, but they go stale the moment there is an accident on the highway or a road closure halfway through. PFM works like GPS. It watches actual conditions and continuously reroutes work so everything keeps moving toward on-time completion.
PFM is not a scheduling tool. It does not create a fixed schedule or a master production schedule. It is a dynamic, real-time prioritization system that directs resources based on current shop floor conditions – and that difference is significant for any shop running complex, variable work.
How Shop-Floor Job Prioritization Affects On-Time Delivery
Late deliveries rarely happen because people were not working hard. They happen because the wrong people were working on the wrong jobs, and nobody had a clear enough picture to catch it before the due date passed.
Effective shop-floor job prioritization changes that at the moment it matters most: when an operator picks up a job. When the highest Threat Level job is always visible and always current, the right work moves first. Lower-risk jobs wait. Bottlenecks surface before they turn into emergencies. Supervisors can redirect resources early in the day rather than scrambling at the end of the week.
Operators run the jobs that most need to move. Supervisors see which work centers are accumulating high Threat Level jobs and act before those jobs go late. Planners trust that the floor is working in an order that reflects actual risk.
When a customer calls and asks whether their order will ship on time, you do not need a floor walk to answer. You open the PFM view, check the job’s current Threat Level and operation, and give an answer you can stand behind.
Can a Shop-Floor Job Prioritization Tool Work Alongside Our Existing ERP?
Yes – and that is exactly how PFM is designed to work.
We are direct about this: PFM does not replace your ERP. Your ERP remains the system of record for orders, inventory, purchasing, and financials. It is where item masters live, where purchase orders are tracked, and where your business history is stored. We rely on it for all of that.
What ERP was not designed to do is continuously re-evaluate, in real time, which jobs are at risk and what needs to happen next on the shop floor. That is the gap PFM fills.
PFM reads the order, routing, and status data your ERP already holds, uses that information along with other approved data sources to calculate Threat Levels and real-time priorities, and optionally feeds information back so both systems stay aligned. Progress data for jobs can come from multiple sources – it can be captured in PFM, fed via real-time machine data collection tools, or it can also come from the ERP itself. PFM only optionally sends information back to the ERP.
ERP is the memory of the business. PFM is the real-time view that tells your team where to focus right now. Together, they give you something neither provides alone.
When Prioritization Becomes a Habit Instead of an Argument
One of the quieter costs of poor shop-floor job prioritization is the daily argument. The supervisor who insists job A goes first. The operator who ran job B because it was already set up. The planner who finds out Friday that the wrong work moved all week.
Those arguments are not a people problem. They are what happens when there is no single, trustworthy source of priority information. People fill that gap with judgment, habit, and whoever has the most authority in the room.
PFM replaces that dynamic with a shared, real-time view that every role can see and rely on. Operators know what to run. Supervisors know where to look for trouble. Leaders can answer customer questions with confidence. The question “what do we run next?” stops being a negotiation and becomes a straightforward lookup.
If you are ready to move beyond dispatch lists and give your shop floor a real-time prioritization system that keeps every operator aligned with what actually matters, contact LillyWorks and see Protected Flow Manufacturing (PFM)™ in action.
FAQs About Shop-Floor Job Prioritization and PFM
Does PFM replace the dispatch lists we currently pull from our ERP?
Not exactly – it replaces the need for them. PFM generates a live, continuously updated priority list at each work center based on Threat Level. That list is far more current and accurate than anything pulled from ERP on a batch cycle. Your ERP still holds the underlying order and routing data. PFM uses that data to calculate real-time priorities that reflect what is actually happening on the shop floor right now.
How is Threat Level different from sorting jobs by due date?
Due date tells you when a job needs to be done. Threat Level tells you how much danger a job is actually in of being late, given everything happening in your plant at this moment – remaining operations, routing, available capacity, current conditions. A job due in three days with four operations left may carry a much higher Threat Level than a job due tomorrow that only needs final inspection. Sorting by due date cannot make that distinction. Threat Level can.
Will operators actually follow a prioritization system, or default to old habits?
They will follow it if it makes their day more predictable. Most of the friction in a shop comes from uncertainty – operators are not sure which job truly matters most, so they make their best guess and sometimes get it wrong. When PFM gives them a clear, current, trusted answer at their work center, that uncertainty goes away. The shops that see the fastest adoption are the ones where the system visibly reduces the arguments and second-guessing that slow everyone down. Contact LillyWorks to talk through what that could look like in your environment.