Free. Private. No account.
TimeCalculate is a calculation tool, not an unexplained answer box. This page documents the arithmetic, assumptions, testing boundaries and privacy choices behind the results so that a user can reproduce a total and recognise when an employer rule or real-world rota exception must be applied separately.
Published by: the TimeCalculate team · Last reviewed: 2 September 2026
Time is converted to whole minutes before totals are calculated. A clock reading such as 07:45 becomes 465 minutes after midnight. This avoids treating clock minutes as decimal hundredths and keeps additions, deductions and comparisons exact until the final display step.
For a same-day interval, finish minutes are reduced by start minutes. When the finish is earlier than the start, the calculator treats the finish as occurring on the next day and adds 1,440 minutes. A 22:00–06:00 shift is therefore 480 minutes, or 8 hours.
Break minutes are deducted only from the clock span entered by the user. The tool cannot decide whether a break is contractually paid, whether a break was actually taken, or whether an employer rounds punches. Those rules must be checked against the source record.
Decimal values are produced after exact minutes are known. Forty-five minutes is 45 ÷ 60 = 0.75 hour. A displayed value may be rounded, while the hours-and-minutes result remains the checkable source.
| Record | Clock span | Break | Exact result |
|---|---|---|---|
| Day duty | 07:15–16:00 | 45 minutes | 480 minutes · 8 hours |
| Night duty | 22:30–06:15 | 30 minutes | 435 minutes · 7 hours 15 minutes |
| Combined | 480 + 435 | 915 minutes · 15 hours 15 minutes · 15.25 hours | |
The final decimal is calculated once from the combined 915 minutes. Rounding each line first can create a different total, so TimeCalculate retains minutes until the display stage.
A repeating rota is stored as an ordered cycle of working and rest blocks anchored to a real date. The anchor is not merely a convenient start date: it identifies which cycle day applies on every projected date. If cycle day one is wrong, every future result is shifted.
For each worker, all working intervals from every job are combined. Overlaps are merged so they are not counted twice. Time is considered shared only when every worker is outside all of their working intervals for at least the selected minimum-break length. This is why an overnight shift ending at 07:00 can shorten a calendar rest day: the free interval begins at the actual finish, not at midnight.
Repeating patterns are planning models. Leave, training, court, overtime, changed duties and sickness can replace the expected cycle on particular dates. A result is reliable only when those exceptions are entered or the scanned rota is checked against the source. TimeCalculate does not infer an employer decision that is absent from the input.
The scanner is an input assistant. It recognises text in the browser and proposes editable blocks; it is not the calculation authority. Image quality, cropped dates, abbreviations, colours, handwritten notes and duties without times can all affect interpretation. Users see a review step before any detected pattern is applied.
Core calculations are regression-tested with same-day shifts, midnight crossings, breaks, repeating cycles, overlapping jobs and shared-free windows. Changes to presentation, analytics or advertising are kept separate from the calculation and scanner modules so a content or interface release does not silently alter rota arithmetic. Live releases are also checked for mobile reflow, keyboard access, encrypted-link restoration and protected Cloudflare bindings.
Known limitations are stated on the relevant page. TimeCalculate is suitable for checking arithmetic and planning, but it is not an official payroll, attendance, employment-law or emergency-resourcing system. Where a result affects pay, legal rights or operational cover, compare it with the employer’s authoritative record.
Ordinary calculations, saved local state and rota-image recognition run in the browser. A comparison link is created only when the user asks for one. Its rota payload is encrypted before storage; the decryption key remains in the URL fragment and is not sent with the server request. Sensitive comparison pages and encrypted share links do not load advertising or Google Analytics.
A useful correction report includes the page, exact inputs, result shown, expected result and the rule used to obtain that expectation. Do not email rota screenshots or personal employment information. See the Contact page for the safe reporting route.
Read the practical rota-comparison guide or open the Friends & Family Shift Calculator.