Priority Dispatching Rules for Job Shop Scheduling

Priority dispatching rules are the foundation of job shop scheduling. Every time a machine finishes a job and becomes available, someone — or something — must decide which job runs next. That decision, multiplied across every machine and every shift, determines whether your shop meets due dates, minimizes waste, and keeps customers happy.

In this guide, we break down the most widely used priority rules, explain when each works best, and show how to implement them effectively in your job shop scheduling software. Based on 35+ years of manufacturing scheduling experience at User Solutions, these are the rules that consistently deliver results on real shop floors.

Why Priority Rules Matter

In a typical job shop with 100+ active jobs and 20+ machines, each machine might have 5 to 15 jobs waiting in its queue at any given time. The order in which those jobs run has massive consequences:

• On-time delivery swings by 20 to 40 percentage points depending on which rules are applied
• Average lead time varies by 15 to 30 percent based on sequencing logic
• Setup time waste can be cut by 20 to 50 percent when similar jobs are grouped
• WIP inventory levels depend directly on flow rate, which depends on sequencing

Manual priority decisions — the scheduler's gut, the loudest customer, the easiest setup — are inconsistent and suboptimal. Formal dispatching rules enforce consistent logic that can be measured and improved.

The Core Dispatching Rules Explained

1. First In, First Out (FIFO)

Logic: Run jobs in the order they arrived at the machine queue.

Strengths:

• Simple and perceived as fair
• Easy for operators to follow
• No calculation required

Weaknesses:

• Ignores due date urgency — a job due tomorrow waits behind a job due next month
• Results in poor on-time delivery performance
• Does not optimize for any meaningful scheduling objective

When to use: Only as a tiebreaker when other criteria are equal, or for non-bottleneck work centers where queue time is minimal.

2. Earliest Due Date (EDD)

Logic: Run the job with the closest due date first.

Strengths:

• Directly targets the most common scheduling objective: meeting due dates
• Minimizes maximum lateness across all jobs
• Intuitive for operators and managers to understand

Weaknesses:

• Does not consider how much work remains on a job — a job due tomorrow with 8 hours of remaining work gets the same priority as a job due tomorrow with 30 minutes remaining
• Ignores setup time implications

When to use: As the primary rule for most work centers. EDD is the single most effective rule for improving on-time delivery and is the default recommendation for most job shops.

3. Shortest Processing Time (SPT)

Logic: Run the job with the shortest operation time first.

Strengths:

• Minimizes average flow time (time jobs spend in the system)
• Maximizes the number of jobs completed per time period
• Reduces average WIP levels

Weaknesses:

• Large jobs get perpetually delayed — they keep getting pushed back by shorter jobs
• Does not consider due dates at all
• Can lead to very late delivery for complex, multi-operation jobs

When to use: When reducing average lead time or WIP is the primary objective. Often combined with due date rules to prevent large-job starvation.

4. Longest Processing Time (LPT)

Logic: Run the job with the longest operation time first.

Strengths:

• Good for load balancing when assigning jobs to parallel machines
• Prevents large jobs from getting stuck at the end when all machines are nearly full

Weaknesses:

• Increases average flow time
• Not useful as a general sequencing rule

When to use: Primarily for load balancing scenarios, not general dispatching.

5. Critical Ratio (CR)

Logic: Calculate (time remaining until due date) / (total remaining processing time). The lowest ratio is the most urgent.

• CR < 1.0 means the job is already behind schedule
• CR = 1.0 means the job is exactly on schedule
• CR > 1.0 means the job has slack

Strengths:

• Dynamic — re-calculates as time passes and work is completed
• Considers both urgency (due date) and workload (remaining processing time)
• Automatically escalates jobs that are falling behind
• Better than EDD in dynamic, high-variability environments

Weaknesses:

• Requires accurate remaining processing time data
• More complex to calculate and explain to operators

When to use: As the primary rule in shops with high variability and frequent schedule disruptions. This is the most sophisticated single rule and works well in most job shop environments.

6. Least Slack (LS)

Logic: Slack = due date - current time - total remaining processing time. Run the job with the least slack first.

Strengths:

• Similar benefits to Critical Ratio
• Focuses on jobs with the least buffer time

Weaknesses:

• Can produce erratic priorities when slack values are very close
• Does not account for queue time at downstream machines

When to use: As an alternative to Critical Ratio in shops where the absolute time buffer matters more than the ratio.

7. Setup-Dependent Rules

Logic: Consider setup time between the current job and each waiting job. Favor jobs that minimize changeover time.

Strengths:

• Can reduce setup time waste by 20 to 50 percent
• Increases effective machine capacity at bottleneck work centers
• Grouping similar jobs is operationally efficient

Weaknesses:

• May conflict with due date priorities — the lowest-setup job might not be the most urgent
• Requires a setup matrix defining changeover times between job families

When to use: At bottleneck machines where setup time is a significant percentage of available time. Combine with EDD or CR — group similar jobs, but only when their due dates are close enough that reordering does not cause late deliveries.

Comparison Table: When to Use Each Rule

Combining Rules: A Practical Approach

The most effective scheduling strategies combine multiple rules rather than relying on a single one:

1. Use Critical Ratio or EDD as the primary rule for most work centers
2. Add setup-dependent logic at bottleneck machines — group similar jobs within a due-date window
3. Apply SPT as a secondary rule when multiple jobs have similar urgency
4. Set customer priority overrides for key accounts that require guaranteed delivery

RMDB supports this multi-rule approach, allowing different rules per work center and combining priority factors with configurable weights. The visual Gantt chart in EDGEBI shows the resulting schedule, and planners can override specific decisions using drag-and-drop.

Implementing Priority Rules on the Shop Floor

Choosing the right rules is only half the battle. The other half is execution — getting operators to follow the priority sequence.

Best practices for shop floor implementation:

• Display dispatch lists on monitors at each work center showing jobs in priority order
• Keep it simple — operators should see job number, part number, quantity, and position in the queue
• Update lists in real time as jobs complete and conditions change
• Track adherence — measure what percentage of the time operators follow the priority list
• Explain the why — operators follow rules better when they understand the logic behind them

Measuring Priority Rule Effectiveness

Track these metrics to evaluate whether your priority rules are working:

• On-time delivery percentage — the ultimate measure of scheduling effectiveness
• Average lateness — the average number of days late across all jobs
• Maximum lateness — the worst-case late delivery
• Average flow time — how long jobs spend in the shop
• Schedule adherence — how closely the shop floor follows the scheduled sequence
• Setup time as a percentage of available time — for setup-dependent rules

Review these metrics monthly and adjust rules as needed. For more on tracking scheduling performance, see our guide to job shop scheduling ROI.

---

---

Want to see how the right priority rules transform your shop's performance? Contact User Solutions to see RMDB and EDGEBI in action with your data. We configure priority rules based on 35+ years of job shop scheduling experience — implemented in just 5 days.