Calculate Weekly Hours and Overtime Accurately

Weekly hours arithmetic looks trivial until you notice that the threshold, the multiplier and even the definition of a week are set by law and differ substantially by jurisdiction.

In the United States, the Fair Labor Standards Act requires non-exempt employees to be paid at least 1.5× the regular rate for hours worked beyond 40 in a workweek. The FLSA workweek is a fixed, recurring period of 168 consecutive hours — seven consecutive 24-hour periods — which the employer designates and which does not have to start on Monday or at midnight. Crucially, the FLSA has no daily overtime requirement; a 12-hour day is not overtime federally if the week stays at or under 40 hours.

Several states impose more. California requires 1.5× beyond 8 hours in a day and beyond 40 in a week, 2× beyond 12 hours in a day, and additional rules for a seventh consecutive day worked.

In India, the Factories Act 1948 sets 9 hours a day and 48 hours a week, with overtime at twice the ordinary rate. Shops and establishments legislation varies by state.

In the EU, the Working Time Directive caps the average working week at 48 hours including overtime, averaged over a reference period, but leaves premium rates to member states and collective agreements.

Two consequences follow for anyone building or using a calculator: the weekly threshold must be configurable, and daily and weekly rules can both apply at once, with the daily calculation performed first so the same hour is not counted twice.

The most expensive error in overtime calculation is multiplying the base hourly wage instead of the regular rate of pay.

Under the FLSA the regular rate includes nearly all remuneration for employment, not just the stated hourly figure. Non-discretionary bonuses, shift differentials, commissions and production bonuses must be included; the regular rate is total straight-time compensation divided by total hours worked in the week.

A worked example makes the difference concrete. An employee earns £12/hour, works 45 hours, and receives a £50 attendance bonus:

• Straight-time pay: 45 × £12 = £540
• Plus the bonus: £540 + £50 = £590
• Regular rate: £590 ÷ 45 = £13.11/hour
• Overtime premium owed: 5 hours × £13.11 × 0.5 = £32.78

Calculating on the £12 base instead gives £30.00 — an underpayment on a single week, repeated across a workforce and a year.

What is excluded from the regular rate: genuinely discretionary bonuses, gifts, reimbursed expenses, and payments for time not worked such as holiday or sick pay. The line between a discretionary and a non-discretionary bonus is narrower than employers usually assume — a bonus announced in advance to encourage performance is non-discretionary.

Disputes are more often about which minutes count than about the arithmetic applied to them.

Unpaid meal breaks must be genuine. Under FLSA guidance a break of 30 minutes or more can be unpaid only if the employee is completely relieved of duty. Eating at a desk while covering the phone is compensable working time. Short breaks of roughly 5–20 minutes are counted as hours worked and must be paid.

Travel between job sites during the workday is working time. The ordinary commute from home to the first site and back from the last is not.

Preparatory and concluding activities that are integral to the job — setting up equipment, mandatory security screening in some rulings, shift handover — generally count.

Rounding is permitted but must be neutral. Rounding to the nearest quarter hour is lawful only if it does not systematically favour the employer over time. A system that always rounds clock-in up and clock-out down is unlawful even if each individual adjustment is small.

On-call time depends on constraint. An employee required to remain on premises is working; one free to use the time for their own purposes, subject to being reachable, generally is not.

Record-keeping is a legal obligation in itself. Under the FLSA employers must keep payroll records for three years and the time records underlying wage computations for two.

Three mechanical mistakes account for most incorrect timesheets.

Decimal hours versus hours and minutes. 7 hours 30 minutes is 7.5 hours, not 7.30. Adding times in the h.mm form silently understates every entry containing more than 30 minutes. Convert to decimal once, at entry: hours + minutes / 60.

Overnight shifts. A shift from 22:00 to 06:00 subtracts to negative eight hours if handled naively. The end time must be recognised as falling on the next day. Any calculator that cannot express a shift crossing midnight will be wrong for a large proportion of shift workers.

Rounding at the wrong point. Round once, at the end of the week, not per day. Rounding each day to two decimals and summing compounds the error across seven entries.

A reliable order of operations:

1. Convert every clock entry to minutes since midnight, handling day rollover.
2. Subtract unpaid break minutes per shift.
3. Sum to weekly minutes; convert to decimal hours once.
4. Apply daily overtime rules first, where the jurisdiction has them.
5. Apply the weekly threshold to the remaining straight-time hours.
6. Compute the regular rate including qualifying additional pay.
7. Apply multipliers and round the currency amount once, at the end.

A timesheet is personal data about identifiable workers: names, shift patterns, and by inference their location and availability. Under the UK GDPR and the EU GDPR it is personal data, and payroll information attracts particular care.

Uploading a staff timesheet to an online calculator is a transfer of that personal data to a third party. For an employer it may be a processing activity requiring a lawful basis and a data processing agreement. For a contractor submitting their own hours, it discloses a working pattern to a service with no relationship to the engagement.

The arithmetic needs no server. The OpenTools timesheet calculator runs in the page, so entries, names and rates stay on the device.

Whatever tool you use, two habits matter: keep the source records — the raw clock entries, not only the computed totals, since those are what a wage claim turns on — and check the calculator's assumptions against your jurisdiction before relying on it. A calculator that hard-codes a 40-hour threshold is wrong in India, wrong in California for daily overtime, and wrong under many collective agreements. This article describes common statutory positions and is not legal advice.