Record complete endpoints
Record calendar date, clock time, and applicable time zone for start and end. Dates remove overnight ambiguity. In 12-hour notation, 12:00 AM is midnight and 12:00 PM is noon.
Elapsed duration equals end timestamp−start timestamp. A negative result usually indicates reversed entries or a missing next-day date. Do not add 24 hours automatically unless the actual schedule establishes a following-day end.
Subtract unpaid breaks once
Gross duration includes every minute between punches. Net worked duration=gross duration−unpaid breaks. Paid breaks stay included. Record multiple unpaid breaks independently, add them, then subtract their total once.
Do not subtract a scheduled break that was not taken unless controlling rules permit it. Meal requirements, pay, rounding, overtime, and records vary by employer and jurisdiction. This guide explains arithmetic, not legal entitlement.
Three complete work examples
Input: 9:00 AM to 5:30 PM, 30-minute unpaid break. Formula: net=gross−break. Calculation: 8 h 30 min−30 min=8 h. Result: 8.00 hours. Interpretation: the break is excluded once.
Input: October 6 at 10:15 PM to October 7 at 6:45 AM. Formula: end−start. Calculation: 1 h 45 min to midnight+6 h 45 min=8 h 30 min. Result: 8.50 hours. Interpretation: dates prevent negative subtraction.
Input: 7:40 AM to 4:25 PM, breaks 20 and 25 minutes. Formula: gross−sum(breaks). Calculation: 8 h 45 min−45 min=8 h. Result: 8.00 hours. Interpretation: add breaks before subtracting.
Convert minutes to decimal hours
Decimal hours are not clock notation. Divide minutes by 60: 15 minutes=0.25, 30=0.50, and 45=0.75 hour. Thus 7 hours 20 minutes is 7+20/60=7.333… hours, not 7.20.
Keep exact seconds or minutes through calculations and round only at the authorized final stage. Rounding every segment can differ from rounding a weekly total. Preserve the unrounded duration alongside any payroll display.
Handle overnight and clock changes
A shift crossing midnight requires different start and end dates. Shifts crossing daylight-saving transitions may have actual durations different from simple wall-clock subtraction because the local offset changes.
Confirm time zone and offset when staff travel, systems store UTC, or a clock transition occurs. NumUtility uses the device's local date-time environment. A scheduled wall-clock duration and actual elapsed duration can differ.
Separate arithmetic from policy
Apply only a documented rounding rule and identify whether it affects punches, shifts, or pay-period totals. Billing rules may round, truncate, or round up in fixed increments; these methods are not interchangeable.
Overtime is not determined by elapsed time alone. Daily or weekly thresholds, paid leave, split shifts, contracts, and local law may apply. Calculate exact net durations first, then use the controlling policy or qualified payroll guidance.
For five shifts of 7 hours 36 minutes, each is 456 minutes and the total is 2,280 minutes, exactly 38 hours. Adding clock-style values as 7.36 would be wrong because 0.36 hour is only 21.6 minutes.
Seconds may matter in system logs even when a timesheet displays minutes. A display rounded from 7:59:40 to 8:00 does not change the timestamp difference. Retain precision consistent with source records and policy.
If a break crosses midnight, store its own start and end timestamps or its verified duration. Do not infer break length from labels such as lunch. Missing punches need an authorized correction process rather than a guessed arithmetic value.
Split shifts should be calculated as separate intervals. If someone works 8:00–11:30 and 2:00–6:15, the first interval is 3 hours 30 minutes and the second is 4 hours 15 minutes, totaling 7 hours 45 minutes or 7.75 hours. Treating 8:00–6:15 as one interval would incorrectly count the gap.
A shift longer than 24 hours must keep its full dates. Reducing a duration to the clock remainder can discard complete days. For example, 27 hours is 1 day 3 hours, not merely 3 hours. Decide whether a reporting system wants total hours, 27, or a day-hour breakdown, then label the result clearly.
Travel can create local end times earlier than local start times even when elapsed time is positive. Convert both timestamps with their correct offsets to a common time basis such as UTC before subtraction. Simply comparing displayed clock faces in different zones can add or remove several hours incorrectly.
Timesheets often distinguish worked time from paid time. Paid leave, training, on-call periods, travel, premiums, and meal periods may be categorized by policy even when timestamps are known. Keep arithmetic duration separate from classification so a neutral elapsed-time result is not presented as a legal payroll conclusion.
To audit a discrepancy, compare source punches, time zones, break entries, corrections, rounding stage, and pay-period boundaries in that order. Recalculate from unrounded timestamps. A difference of a few minutes may come from rounding, while an exact hour near a clock transition may indicate a time-zone issue.
Use the Time Duration Calculator
Enter full local start and end date-times. The calculator reports signed days, hours, minutes, and seconds. Subtract unpaid breaks separately and divide final remainder minutes by 60 when decimal hours are required.
For weekly totals, convert verified shifts to a common exact unit such as minutes, add them, then convert once. The tool does not store timecards, identify paid work, calculate wages, or decide overtime and legal compliance.
A timesheet correction should preserve the original entry, corrected value, reason, approver, and timestamp when the system supports it. Overwriting a punch without history makes later arithmetic difficult to verify. The calculation may be simple, but trustworthy payroll records also depend on provenance and authorization.
When comparing a schedule with actual work, calculate them independently. A scheduled 9:00–5:00 shift with a 30-minute unpaid break is 7.5 scheduled hours; actual punches of 8:53–5:12 with a 27-minute break produce a different exact duration. Do not substitute scheduled values for missing actual records without the approved correction process.
For invoice narratives, pair decimal hours with a readable duration when useful: 7.75 hours (7 hours 45 minutes). This prevents clients from reading .75 as 75 minutes and makes the conversion reviewable. Keep dates and time zones on supporting records, particularly when remote work crosses regions.
A final reconciliation can use totals in minutes. Convert each endpoint difference to seconds or minutes, subtract verified unpaid breaks in the same unit, sum the net intervals, and only then convert to hours. Compare that exact total with the timesheet display and document any permitted rounding adjustment separately. For example, 467 minutes is 7 hours 47 minutes or 7.7833… decimal hours before rounding. It is not 7.47 hours. If two systems disagree, export their raw timestamps and offsets rather than comparing formatted totals alone. This workflow distinguishes arithmetic differences from missing punches, different break classifications, time-zone conversion, and policy-driven rounding.
Keep the calculation neutral when facts are incomplete. Mark a missing punch, disputed break, or uncertain time zone as unresolved instead of filling it with an assumed value. Once an authorized correction is supplied, rerun the same documented method. This prevents a polished decimal result from hiding uncertain source data and makes later review easier for the worker, manager, client, or payroll specialist.