How to use this topic center
Date and time errors often come from mixing different concepts: a date without a time zone, a duration measured in seconds, a calendar month, a business-day policy, and an instant are not interchangeable.
The tools make endpoint, weekend, month-end, and time-zone choices explicit. They do not infer public holidays or promise future government time-zone rules.
Classify the temporal question
Choose calendar age for complete components, elapsed days for date boundaries, time duration for clock arithmetic, and a UTC instant for cross-zone coordination.
- Do not divide days into calendar years.
- Do not attach a time zone to a date-only question.
- Do not treat a month as fixed seconds.
State endpoint and month-end policies
Inclusive counts and end-of-month clamping change valid outputs. Display the selected policy beside the result.
- Name start/end inclusion.
- Document leap-day handling.
- Apply components in a stable order.
Keep business calendars honest
A weekend-only model is deterministic. Public holidays require a maintained jurisdictional dataset or explicit user exclusions.
- State the weekend convention.
- Accept explicit closure dates.
- Never guess holidays from locale.
Use named zones for meetings
IANA zone names carry date-dependent rules. Convert one source local time to an instant, then render that instant for each participant.
- Avoid ambiguous abbreviations.
- Resolve transition gaps and overlaps.
- Recheck future events after rule updates.
Worked journey: schedule a ten-business-day review
A team wants a ten-weekday review window and a final meeting across New York and Berlin.
- Use the business-day guide with an explicit inclusive policy and manually entered company closures.
- Use calendar addition for any separate month-based milestone instead of converting it to 30 days.
- Anchor the final meeting to one instant and render it in both named zones.
Outcome: The schedule separates date policy, closure data, and time-zone conversion, so a hidden assumption cannot silently shift the deadline or meeting.
Date and time workflow checklist
- Use unambiguous dates.
- Choose calendar or elapsed output.
- State endpoint and month-end rules.
- Enter closures explicitly.
- Anchor cross-zone meetings to an instant.
Limits of this collection
- The tools do not infer holidays, legal deadline rules, payroll calendars, shift schedules, or future time-zone legislation.
- Historical non-Gregorian calendars and jurisdiction-specific legal age rules are outside the general civil-date model.
Primary references for this topic
- ISO 8601 — Date and time formatInternational Organization for Standardization
- Time Zone DatabaseInternet Assigned Numbers Authority
- The International System of Units (SI Brochure), 9th editionBureau International des Poids et Mesures
Practical guides in this topic
Distinguish calendar age from elapsed days
Calculate complete years, months, and days using civil dates while keeping endpoint and leap-day policies visible.
7 min read · Reviewed 2026-08-22Add calendar durations with an end-of-month rule
Keep years, months, weeks, and days distinct and inspect how invalid target dates are resolved.
7 min read · Reviewed 2026-08-22Count business days without inventing holidays
Apply a weekday and endpoint policy, keep excluded dates user-supplied, and avoid claiming a jurisdictional holiday calendar.
7 min read · Reviewed 2026-08-22Schedule time-zone meetings from one instant
Anchor a meeting to a UTC instant, use named zones for display, and verify daylight-saving offsets for the meeting date.
8 min read · Reviewed 2026-08-22