Two Directions, One Goal
Every production scheduler faces the same question: When should each operation start? There are exactly two ways to answer it — start from today and push forward, or start from the due date and work backward. Each approach makes different trade-offs, and the best operations use both strategically.
If you've worked in aerospace, defense, or any high-mix environment (Lockheed, Boeing, Raytheon), you've seen this decision play out at scale. A single F-35 has over 300,000 parts flowing through hundreds of work centers. Scheduling direction isn't academic — it determines whether you deliver on time or burn overtime trying to catch up.
Forward Scheduling: Start Now, Finish When Ready
Forward scheduling begins at the earliest available date (today, or when materials arrive) and sequences operations in order, assigning each to the first available time slot. The finish date is the output — you calculate when the job will complete.
How it works
When to use forward scheduling
- Make-to-stock (MTS) — No specific due date; goal is to replenish inventory as efficiently as possible
- Job shops with long lead times — When you need to know the earliest possible completion date
- Quoting and promising — "When can we deliver?" requires forward scheduling from today
- Bottleneck-first scheduling — TOC/DBR schedules the constraint forward, then works outward
Backward Scheduling: Start from the Due Date
Backward scheduling starts at the customer due date and works backward through each operation, determining the latest possible start date for each. The result is a schedule that produces just-in-time — minimizing WIP, carrying costs, and risk of obsolescence.
How it works
When to use backward scheduling
- Make-to-order (MTO) — Specific due dates; goal is to minimize WIP while meeting delivery
- MRP logic — Classic MRP uses backward scheduling: explode the BOM, offset lead times from the due date
- Just-in-time environments — Start as late as possible to minimize inventory holding
- Aerospace/defense programs — Milestone-driven schedules work backward from contract delivery dates
Side-by-Side Comparison
| Factor | Forward Scheduling | Backward Scheduling |
|---|---|---|
| Anchor point | Start date (today or material available) | Due date (customer requirement) |
| Question answered | "When will this finish?" | "When must this start?" |
| WIP level | Higher — starts everything ASAP | Lower — starts as late as possible |
| On-time risk | Lower (more slack) | Higher (no slack built in) |
| Carrying cost | Higher — cash tied up longer | Lower — JIT production |
| Best for | MTS, quoting, bottleneck focus | MTO, MRP, contract milestones |
| ERP default | Used for available-to-promise | Used for planned orders (MRP) |
Adding Constraints: Where It Gets Real
Pure forward or backward scheduling assumes infinite capacity — that every work center is always available. That's never true. The real world has constraints:
- Finite capacity — Machine X can only run one job at a time. If two jobs need it Tuesday, one waits.
- Material availability — You can't start machining if the casting hasn't arrived from the supplier.
- Tooling and fixtures — Special tooling shared across programs creates contention.
- Labor skills — Only 3 certified welders for Class A joints. Schedule accordingly.
- Setup/changeover — Sequence-dependent setups mean the order jobs run matters enormously.
Finite capacity scheduling
Finite capacity scheduling loads jobs onto resources respecting actual capacity limits. When a conflict occurs, it uses priority rules to decide who goes first:
Common priority/dispatch rules
| Rule | Logic | Best when |
|---|---|---|
| EDD (Earliest Due Date) | Job with soonest due date goes first | Minimizing max lateness |
| SPT (Shortest Processing Time) | Shortest job goes first | Minimizing average flow time |
| CR (Critical Ratio) | (Due date - Now) / Remaining work | Dynamic; balances urgency vs. work left |
| Bottleneck first | Schedule the constraint; subordinate everything else | TOC environments |
| Setup minimization | Group similar jobs to reduce changeover | High changeover time environments |
The Hybrid Approach: How the Best Plants Do It
World-class operations don't pick one method — they combine them:
- Backward schedule from due dates — Establish ideal start/finish dates for every operation
- Forward schedule from constraints — Identify the bottleneck and schedule it forward to maximize utilization
- Buffer critical path — Add time buffers before the constraint and before the due date (per TOC)
- Level the load — Use heijunka principles to smooth demand peaks across the horizon
- Re-plan daily — The schedule is a living document. Actual performance drives re-planning.
Real-World Example: Defense Contractor Program
A major defense program has 18-month assembly flow with 4,000+ operations across 200 work centers.
Approach: Backward schedule from contract milestones → identify critical path → forward schedule the 3 bottleneck work centers → buffer merge points → release materials 2 weeks before needed (not 2 months).
Result: 40% WIP reduction, 15% lead time compression, 97% on-time delivery to milestones.
How ERP Systems Handle This
Understanding scheduling direction is critical because your ERP system uses both:
- MRP run (backward) — Explodes the BOM from the demand date, offsets lead times backward to calculate planned order release dates
- CRP / capacity planning (forward) — Takes MRP planned orders and loads them onto work centers forward to check capacity feasibility
- APS (Advanced Planning & Scheduling) — Simultaneously considers forward and backward with finite capacity, materials, and multiple constraints
- Available-to-Promise (forward) — "When can I deliver?" schedules forward from available material/capacity
Key Takeaway
Remember This
Forward scheduling answers "When will it finish?" — backward scheduling answers "When must it start?" Most real-world scheduling combines both: backward from due dates to establish targets, forward from constraints to ensure feasibility, with buffers to absorb variability. The art is knowing which direction to use, when, and how your ERP/MES systems automate the heavy lifting.
Interactive Demo
Toggle between forward and backward scheduling. See how slack and buffer time shift on the timeline.
Stop reading, start doing
Model your process flow, optimize staffing with Theory of Constraints, and track every shift — all in one platform. Set up in under 5 minutes.