Quick guide
How to use this calculator
- Choose the exact calendar, clock, recurrence, time-zone, working-day, or endpoint convention before entering values.
- Add one structured row for each participant, interval, stage, closure, target, or period that belongs in the scenario.
- Check the component ledger before using the headline result: it exposes skipped dates, offsets, transitions, overlaps, stage boundaries, and the convention driving the answer.
Calculation method
Explicit date and time workflow
Period boundaries follow the selected cadence; pay date is period end plus processing days, then adjusted under the entered working-calendar rule.
The calculator keeps civil dates, elapsed durations, local clock readings, UTC instants, work calendars, and recurring rules distinct rather than silently treating them as interchangeable.
Worked example
Worked example
A biweekly period beginning Monday spans 14 inclusive calendar dates before an entered pay-date lag is applied.
Period boundaries follow the selected cadence; pay date is period end plus processing days, then adjusted under the entered working-calendar rule.
Supported inputs
Precision and limits
Calendar and time-zone conventions
Gregorian dates and IANA named zones are modeled explicitly. Holiday, school, legal, payroll, contractual, and operating calendars are never inferred from a country name.
DST and civil-time limits
Repeated or nonexistent local clock readings are identified where they matter. Future government time-zone changes cannot be predicted beyond the time-zone data available to the runtime.
Planning support, not authority
Results organize entered assumptions. They do not determine legal notice, payroll compliance, staffing safety, entitlement, service credits, travel feasibility, or institutional policy.
Calculator-specific boundary
This is a date schedule, not payroll advice. Pay-frequency law, cutoff policy, holidays, direct-deposit timing, wages, tax, and compliance remain employer- and jurisdiction-specific.
Continue calculating