Date & Time
Recurring Event Business-Day Calculator
Apply a transparent weekend, holiday, and shutdown adjustment policy to a recurring event series, then identify shifted-date collisions and daily capacity breaches before publishing the calendar.
Business-day adjustment shuttle
Nominal dates transferred through weekend, holiday, and shutdown gates
Every event moves from a nominal lane to an adjusted business-day lane, with collisions and overloaded destinations called out explicitly.
Adjusted-date audit
Nominal recurrence and business-day movement ledger
Inspect every original day, weekday, adjustment reason, final business day, shift distance, destination load, and capacity status.
| Event | Nominal day | Nominal weekday | Adjustment | Final day | Shift | Day load | Capacity status |
|---|
Calendar-policy setup
State the movement rule before generating dates
- Enter occurrence count and nominal interval.
- Set the first event weekday.
- Choose next- or previous-business-day movement.
- Add recurring holiday and shutdown tests.
- Enter event hours and daily capacity.
Business-day logic
A valid date can still create an invalid daily load
Moving several events off excluded dates can make them collide on the same business day.
Capacity is tested after all movement rules, because the operational problem exists at the adjusted destination date.
Calculation method
Apply adjustment rules in sequence and test the final destination date
Weekend movement occurs first, followed by declared holiday and shutdown adjustments. Events landing on the same final day are combined before the daily-hour limit is tested.
Detailed calculation process and general formulas
d_i=(i−1)Id'_i=moveWeekend(d_i,r)d''_i=moveHoliday(d'_i)d*_i=moveShutdown(d''_i)Load(d)=count(d*_i=d)hSymbols, meanings, and units
- I
- nominal recurrence intervaldays
- r
- weekend movement rulepolicy code
- d*_i
- final adjusted event dayrelative day
- h
- hours per eventhours/event
- Load(d)
- combined event load on adjusted day dhours/day
Calendar integrity
Measure both date movement and workload concentration
The model keeps each cause of movement separate and then measures the combined impact.
Weekend policy
—Events moved because the nominal day is Saturday or Sunday.
Declared closures
—Holiday and shutdown movements.
Schedule compression
—Events sharing one adjusted business day.
Capacity exceptions
—Adjusted days above the entered hour limit.
Decision takeaway: Approve the adjusted series only after collision and daily-capacity tests, not merely after each date becomes a weekday.
Policy checks
Confirm how exclusions are actually handled
- Some holidays use modified rather than zero capacity.
- Previous-day movement can reverse event order.
- Local business calendars may differ.
- Shutdown rules should be date-specific in production.
Calendar evidence
Records needed before publication
- Official business-day calendar
- Weekend movement policy
- Holiday and shutdown notices
- Daily resource capacity
- Adjusted-date approval log
Practical applications
Decisions this calculator is designed to support
Recurring payroll review
A weekly review shifts off weekends and periodic company shutdowns.
What the result clarifies: The shuttle reveals when multiple reviews land on one limited-capacity day.
Regulatory sample collection
Collection dates must move to business days under a documented policy.
What the result clarifies: The ledger preserves the reason and shift distance for every adjusted date.
Worked example
Current-input substitution and reconciliation
Model limitations
Holiday and shutdown patterns are synthetic cadence inputs, not a real jurisdiction calendar. The model does not resolve time zones, partial closures, resource-specific calendars, or legal deadline rules.
Recurring Event Business-Day Calculator FAQ
Which adjustment is applied first?
Weekend movement, then the entered holiday and shutdown rules.
What is a collision?
Two or more events share the same final adjusted day.
Can previous-day movement create negative days?
The model floors adjusted relative days at zero.
Why test hours after moving dates?
Capacity is consumed on the final operational day.