Job risk prioritization should tell you, at any moment, which jobs are actually at risk of shipping late. So why does most of that risk assessment still happen once a day? It runs in a batch that finished hours before your shift even started. A job that looked safe at midnight can be in real trouble by 10 a.m. An overnight calculation has no way to catch that until the next run.
We see this constantly with operations teams running high-mix, make-to-order work. The MRP or scheduling batch runs overnight, and priorities get set. Everyone starts the day trusting a list that’s already behind. By the time a machine goes down or a rush order lands, the list your team is working from no longer reflects reality. That’s less a data problem than a timing problem, and it’s baked into how most systems calculate risk in the first place.
Why Job Risk Prioritization Traditionally Waits For Overnight Batch
Most ERP and MRP systems calculate priority once, usually overnight. Recalculating across an entire plant’s worth of orders used to be too heavy a lift to run continuously. That batch approach made sense when it was designed, but it also means the resulting priority list is a snapshot, accurate for the moment it was generated and steadily less accurate with every hour that passes.
In a high-mix, make-to-order shop, that gap shows up fast. Routings differ from job to job. Run times vary. New orders and rush requests land throughout the day, not on a predictable schedule. A batch run captures none of that until the next cycle, which for most shops means waiting until tomorrow.
The result is a familiar pattern:
The morning priority list looks clean and confident
By midday, half of it no longer matches what’s actually happening on the floor
Supervisors start making judgment calls to fill the gap, because the system can’t
None of that reflects poorly on the team making those calls. The system was only ever built to answer the question once a day.
What Real-Time Risk Recalculation Actually Means
Real-time risk assessment means the picture of lateness risk updates continuously as conditions change, not once at the start of the day. Instead of a single calculation that ages from the moment it’s generated, every job’s risk gets reevaluated as new information comes in. That could be a delay, a material shortage, or a rush order.
That distinction matters more than it sounds. A batch system can tell you what looked risky last night, but only a real-time system tells you what’s risky right now. That’s the only version of the answer that actually helps someone decide what to run next.
Why Job Lateness Risk Changes Faster Than Your MRP Run
Job lateness risk isn’t fixed. It moves with everything happening around a job: how much work remains, how busy the resources ahead of it are, whether material showed up on time, and how close the due date has gotten. An MRP run captures a single snapshot of all of that. The moment any one input changes, the snapshot is out of date.
A stable, low-variability plant might not feel that lag much, but a high-mix shop feels it within hours. A job with comfortable slack at last night’s batch run can lose that cushion by mid-morning if the resource ahead of it falls behind, or if a rush order jumps the queue. Waiting for tomorrow’s batch to catch that shift means your team is working from a version of reality that’s already wrong.
How Threat Level Recalculates Job Lateness Risk Continuously
Protected Flow Manufacturing (PFM)™ isn’t a scheduling tool but a dynamic, real-time prioritization system that directs work based on Threat Level.
Threat Level is how much each job is at risk of being late. Due date and customer are considered as inputs, but they are not the driver. Due date matters, but it does not determine what runs next. Threat Level is the default driver.
Instead of calculating risk once and letting it age, PFM recalculates Threat Level for every operation on every work order continuously. It uses the latest approved data from ERP, machines, and other sources. When something changes, whether a breakdown, a rush order, or a late shipment, Threat Levels shift right away. Priorities reshuffle across every work center in response. There’s no overnight cycle standing between a real change on the floor and an updated picture of risk.
Customer is a field that may and can override Threat Level if need be. Threat Level is the default, but can be overridden by customer or another critical priority defined by the manufacturer. That override handles the genuine exceptions. It isn’t the mechanism doing the everyday work of ranking risk, which stays grounded in what’s actually happening on the floor.
A useful way to picture the difference: an overnight batch run is like checking traffic once before you leave home. You trust that report for your entire drive. PFM works more like GPS, watching current conditions and rerouting continuously. You’re always working from what’s true right now, not what was true this morning.
What This Means For The Person Deciding What To Run Next
If your team starts the day with a list built overnight, and spends the rest of it patching that list by hand, the problem isn’t effort. It’s timing: job risk prioritization was never designed to update as fast as your floor actually changes. A batch run can only tell you what risk looked like at one point in time.
With continuous recalculation, that gap closes. Instead of asking whether this morning’s list still holds, your team asks which jobs carry the highest Threat Level right now. The answer is built from current conditions instead of last night’s snapshot. That matters most on the days when things go sideways early. A single breakdown or rush order can make an entire morning’s plan obsolete before the coffee’s done brewing.
None of this replaces your ERP or MRP. Those systems still hold your orders, inventory, and financial data, and they do that job well. PFM reads from that data and layers continuous, Threat Level based prioritization on top of it. It optionally sends information back so both systems stay aligned, with ERP holding the record and PFM tracking what’s actually true right now.
Closing The Gap Between Last Night’s Plan And Today’s Reality
An overnight batch run will always be describing a plant that existed a few hours ago. A stable, low-mix environment might absorb that gap without much cost. For a high-mix, make-to-order shop, it’s the difference between a priority list your team can trust and one they have to second-guess by mid-morning.
That’s the gap Protected Flow Manufacturing (PFM)™ was built to close. It uses Threat Level to keep priorities current instead of asking a single overnight calculation to hold up all day. If your team is still starting each morning with a list that’s already behind, we invite you to talk with us at LillyWorks. We can show you what continuous, real-time risk assessment could look like on your floor.
FAQs About Job Risk Prioritization And Real-Time Recalculation
Why Does Overnight MRP Make Job Priorities Stale By Mid-Shift?
MRP and traditional ERP scheduling typically calculate priority once, in a batch run, using the data available at that moment. As soon as a machine goes down, a job runs long, or a rush order arrives, that calculation no longer reflects reality. There’s no way to update it until the next batch run.
How Is Job Lateness Risk Calculated In Real Time?
With PFM, job lateness risk is expressed as Threat Level. It’s calculated continuously for every operation on every work order using the latest approved data. As conditions on the floor change, Threat Level updates automatically instead of waiting for a scheduled recalculation.
Can Job Risk Prioritization Update Automatically When A Job Falls Behind?
Yes. When a job’s progress, routing, or due date risk changes, PFM recalculates its Threat Level and adjusts its priority at every affected work center right away. No manual reschedule or wait for the next planning cycle is required.