Why Weekends and Supplier Holidays Push Delivery Dates Past the Deadline
A "2-working-day" supplier lead time is not 2 calendar days when Saturday, Sunday, and a Monday factory holiday sit in the middle.
Interactive calculator loads automatically in modern browsers. All plain-English explanations, units, and tables are shown directly on this page.
How This Rule Works in Simple Steps
What We Want to Achieve: meet the fixed due date — A nonworking day changes the feasible availability date.
- Count weekdays after release; exclude Saturday Sunday and holiday.
- The release day is excluded from lead-time accumulation.
- A holiday already on a weekend must not be counted twice.
- Keep pure calculation code separate from storage and UI.
Three Simple Steps We Compare on This Page
- 1. Normal Day (Baseline Plan): Apply the baseline policy to the frozen input state.
- 2. Problem Day (When Something Goes Wrong): Mark the specified ordinal day as a supplier holiday.
- 3. Fixed Plan (How We Solve It): Release on the explicitly approved earlier ordinal day.
Important Things to Remember Before Using in Real Life
- Day one is Monday; one holiday; local cutoff excluded.
- Passing this model does not validate a complete real supply chain.
- A case must disclose every assumption used in the calculation.
7 Worked Examples of "Why Weekends and Supplier Holidays Push Delivery Dates Past the Deadline"
Click any of the 7 worked examples below to open its own separate page with step-by-step numbers and a visual bar chart:
- SCI-050: Three days means three working days — The supplier works Monday through Friday. (A weekend inside the interval extends the calendar result.)
- SCI-051: Holiday at the supplier — A supplier holiday interrupts the working-day count. (One local closure shifts the feasible ready date.)
- SCI-052: Release day is not day one — The policy starts counting after release. (A different counting convention can shift the promise date.)
- SCI-053: Receiving calendar differs — Receiving availability follows a separate calendar. (This fixture isolates one supplier stage before later integration.)
- SCI-054: Earlier release is a real action — A release can move earlier with confirmed artwork. (The repaired start is feasible only under the declared approval.)
- SCI-055: Month boundary and weekend — A planning period boundary falls over a weekend. (An ordinal-day toy exposes the boundary effect without timezone ambiguity.)
- SCI-056: Duplicate holiday record — The same closure appears in two imported calendars. (One physical day off must not remove two workdays.)