Dispatch Cutoff Calendar Planner

How to use Dispatch Cutoff Calendar Planner

Enter order date-minutes and the ordered transport legs. For each leg find its next permitted dispatch cutoff, then count delivery-business dates strictly afterward. Its entered arrival clock becomes readiness for the next leg, so missed intermediate cutoffs remain visible.

1. Use the example as the schema; replace its labels and entered model assumptions.
2. Enter order date-minutes and the ordered transport legs. For each leg find its next permitted dispatch cutoff, then count delivery-business dates strictly afterward. Its entered arrival clock becomes readiness for the next leg, so missed intermediate cutoffs remain visible.
3. Calculate, inspect the complete witnesses and limitations, then copy or download the JSON report.

Good to know

• Up to 50 orders, 8 legs and 100 excluded dates per calendar per leg. Each transit is 1–90 business dates, with no zero-day service. At most 1,001 dispatch candidates or 1,000 delivery date scans in a leg, and 250,000 date scans overall.
• All clocks share one naive Gregorian calendar, dates 1900–9999. No time zones, DST, live holidays, actual carrier commitments, customs, capacity or variable processing times. All weekdays, cutoffs and arrival times are user assumptions.
• Local calculation with no upload, input persistence or outside lookup. Model JSON is limited to 30,000 characters and 10,000 values. Decimal quantities are strings with up to six places; count fields use plain JSON integers. Exact fractions are capped at 8,192 bits. The complete JSON output is limited to 1,000,000 characters; approximate numbers preserve their stored values. Unsupported states fail explicitly.