What Is Slack Time in Forward vs Backward Scheduling?
User Solutions TeamSlack time is the spare time between when a job finishes and when it is due, and forward and backward scheduling place that slack at opposite ends of the work. It is the cushion before a deadline bites, like handing in an assignment two days early and holding two days of slack. Schedule a job forward and the slack piles up after the work; schedule it backward and the same slack sits in front of the work. EDGEBIC supports both, so you choose where the cushion lives.
This entry is part of the EDGEBIC by User Solutions glossary series; for the broader vocabulary of planning, see the manufacturing glossary.
How Slack Time Works
Slack is the difference between a job's completion and its deadline. If a job could finish Wednesday but is not due until Friday, it carries two days of slack. That spare time is what makes a schedule resilient. When a machine hiccups or an operation runs long, slack absorbs the delay so the due date still holds. A job scheduled with no slack is fragile: the smallest disruption makes it late.
The amount of slack depends on how much time exists between the earliest the work can start and the moment it is due. What forward and backward scheduling change is not the amount but the placement. Both directions can produce the same total slack for the same job; they differ in whether that cushion lands before or after the work.
Forward scheduling starts every step as early as possible from the order's start time. The job therefore finishes as soon as the routing allows, and any gap to the due date is left over at the end. The slack accumulates after the work. Backward scheduling does the reverse: it right-aligns the whole order so the last step ends at or before the due date, which forces the earlier steps to start as late as safely possible. The slack ends up in front of the work, before anything begins.
A Concrete Example
Take a job that needs 16 working hours and is due Friday end of shift, with the earliest it could start being Monday morning. The week holds 40 working hours, so there is 24 hours of slack to place somewhere.
Scheduled forward, the job starts Monday morning and finishes by Tuesday midday. From Tuesday midday to Friday, 24 hours of slack sits at the end. If Monday's operation runs three hours long, the job still finishes comfortably before Friday, because the cushion is after the work.
Scheduled backward, the same job is right-aligned to end Friday. Working back 16 hours from Friday's finish, it starts Thursday. The 24 hours of slack now sits in front, Monday through Wednesday, and the parts are not touched until Thursday. The finish is just in time, so less time is spent holding work in process, but there is no cushion after: a three-hour overrun on Thursday now threatens Friday.
Same job, same 24 hours of slack, opposite placement, and a real trade-off between inventory holding and schedule safety.
How EDGEBIC Uses It
EDGEBIC lets you set a scheduling direction per order, and the direction decides where slack lands. Forward is the default: the order starts as early as possible from its start time and slack accumulates after the work, which gives the safest buffer against delay. Backward right-aligns the order so its last step ends at or before the due date, minus any end-item lead time reserved in front, and slack sits deliberately before the work for a just-in-time finish.
Backward scheduling also carries a safety net. If the backward pass cannot fit the whole order between its earliest start and the due date, there is no room to place slack in front, so EDGEBIC rolls the entire order back and forward-schedules it from the earliest start instead. It records the job as backward-infeasible and surfaces it, so you get the earliest-possible plan plus a clear signal that the requested due date could not be met. That guarantee means backward never fails where forward would have succeeded. See the direction mechanics in the backward scheduling guide and the forward default in the forward scheduling guide.
Related Reading
Slack placement is the practical difference between the two directions covered in forward versus backward scheduling. For the deeper mechanics, see the backward scheduling guide, and for the generic term, the slack time glossary.
Expert Q&A: Deep Dive
Q: I scheduled backward to hit a due date and now the job starts much later than I expected. Is that right?
A: Yes, that is backward scheduling working as intended. It right-aligns the job so the last step ends at or before the due date, which pushes the start as late as safely possible and parks the slack in front of the work. The benefit is a just-in-time finish with less time spent holding parts. The cost is no cushion after the work, so if anything runs long the deadline is exposed. If you want the safety margin at the end instead, schedule forward.
Q: A backward job did not fit before its due date. What does EDGEBIC do with the slack then?
A: When the backward pass cannot fit the whole order between its earliest start and the due date, there is no slack to place in front, so EDGEBIC rolls the whole order back and forward-schedules it from the earliest start instead. It records the job as backward-infeasible and surfaces it to you. The result is the earliest-possible plan with any slack after the work, and a clear signal that the due date could not be met as requested.
Frequently Asked Questions
Ready to Transform Your Production Scheduling?
User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.
User Solutions Team
Manufacturing Software Experts
User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.
Share this article
Related Articles
The EDGEBIC Scheduling Glossary Index
A themed index to the EDGEBIC glossary: scheduling engine, capacity and calendars, materials and planning, shop floor, reporting, quoting, and data import terms, defined in plain language.
What Is the Critical Chain in Manufacturing Scheduling?
The critical chain is the longest dependent path through a plan once shared machine contention is counted, not just step precedence. Here is how it differs from the critical path.
What Does Finite Capacity Mean in EDGEBIC?
Finite capacity means the scheduler refuses to book more hours on a machine than that machine actually has. See exactly how EDGEBIC enforces it, day by day and shift by shift.