Dates look simple and behave badly. Months change length, leap years appear on a three-tier rule, clocks jump twice a year, week numbering has competing standards, and payroll wants minutes expressed as decimal fractions of an hour. These calculators handle the arithmetic properly so that contract terms, timesheets, deadlines and log timestamps all come out right rather than nearly right.
11 calculators in this category
A 90-day payment term is not three months, and three months is not 90 days. A 122-day project window contains only about 87 working days once weekends come out. Each of these counts answers a different question, and quoting the wrong one is how schedules slip before work even starts. Contracts overwhelmingly define terms in days precisely because days are the only unit with a fixed length.
Months are elastic in both directions. Adding one month to 31 January either overflows into March or clamps to 28 February depending on the convention applied, and the two answers differ by several days. If an agreement is expressed in months, it should say which rule governs; if it cannot, express it in days instead.
Every calculator here works in UTC internally. That is deliberate: in a local time zone, two days each year are 23 or 25 hours long, and naive subtraction across a clock change lands a day out. Anchoring to UTC removes that failure mode entirely, at the cost of one caveat — a deadline expressed in a local zone can differ by a day at the boundary, so cross-border deadlines should always name their reference zone.
The same applies to log analysis. A timestamp of midnight UTC on 1 January is the evening of 31 December across the Americas. Incident timelines assembled from systems in different zones need every entry normalised before they can be compared, which is what epoch timestamps exist to make possible.
Payroll systems want hours as decimals, so 8 hours 20 minutes is 8.33 hours. Entering 8.20 loses eight minutes, and repeated daily across a workforce that becomes a material and legally exposed underpayment. The duration and time card calculators both output decimal hours for exactly this reason.
Overtime rules add another layer. The US federal standard is weekly above 40 hours at time and a half, but several states impose a daily threshold as well, and where both apply the more generous outcome governs. Non-discretionary bonuses and shift differentials usually have to be folded into the regular rate before the premium is applied, which raises the effective overtime rate above the base wage.
The date difference calculator measures the interval, so 1 January to 2 January is one day. The business days calculator is inclusive of both endpoints, matching how project schedules are normally stated.
Holiday calendars differ by country, region and industry, and several dates move each year or shift when they fall on a weekend. Manual entry is the only approach that stays accurate everywhere.
ISO 8601, where weeks start on Monday and week 1 contains the first Thursday of January. North American Sunday-start numbering can differ by one, so always state which system a week number belongs to.
Yes, using the full three-tier Gregorian rule. 2000 was a leap year and 2100 will not be, despite both being divisible by four.