b2KIT

Work Hours Tracker

Log daily clock-in and clock-out times, track overtime, and calculate weekly totals.

Tested tool guide Tested browser tools Checked August 16, 2026

What Work Hours Tracker does, with a checked example

Work Hours Tracker keeps a running weekly timesheet: for each day you enter a clock-in time, a clock-out time, and any break minutes, and the tool adds a row and keeps a weekly running total as you go. It splits that total against an overtime threshold (40 hours by default) so you can see regular versus overtime hours before the week closes. The part people miss most often is that overnight shifts and jurisdiction-specific rules like daily overtime aren't handled automatically - the tool assumes one simple weekly cutoff.

Worked example

A concrete input and expected output from the current implementation.

Input

Mon 9:00-17:30 (30 min break); Tue 9:00-17:30 (30 min break); Wed 9:00-18:00 (30 min break); Thu 9:00-17:30 (30 min break); Fri 9:00-17:00 (30 min break); Sat 9:00-13:00 (no break)

Expected output

Daily net hours: Mon 8.0, Tue 8.0, Wed 8.5, Thu 8.0, Fri 7.5, Sat 4.0. Weekly total 44.0 hours = 40.0 regular + 4.0 overtime.

Each day's net hours is clock-out minus clock-in minus the break; the six days sum to 44.0 hours, which is 4.0 past the default 40-hour threshold, so the split is 40.0 regular and 4.0 overtime.

How the result is produced

1

Per-day rows build the week

Each entry becomes a row: clock-in, clock-out, and break minutes for that date. The tool converts the clock-in/out pair into elapsed time and subtracts the break to get net hours worked that day, then keeps the row in a running weekly log rather than discarding it once calculated, so any day can be reviewed or corrected before the week's totals are used.

2

Weekly split against a threshold

Net hours from every row in the week are summed into a single weekly total. That total is compared against an overtime threshold, 40 hours by default, and split into two figures: regular hours up to the threshold and overtime hours for anything beyond it. Changing the threshold recalculates the split without altering any of the logged times.

Good uses

  • reconstructing a week's timesheet from daily punch times before submitting it to payroll
  • a freelancer or contractor logging hours across several days to see how close the week is running to 40 hours
  • catching a data-entry mistake on one day by reviewing the weekly log before it skews the total

Limits and checks

  • The overtime threshold is a single weekly number; it won't apply daily-overtime rules some jurisdictions use (for example, hours worked beyond 8 in one day), so the overtime figure may not match what an employer actually owes there.
  • Shifts that cross midnight need extra care - depending on how the clock-out is entered, an overnight shift can be misread as a very short or negative span if the date isn't tracked along with the time.
  • Treat the log as session-based: navigating away or closing the tab without exporting or noting the totals can lose the days already entered.

Common questions

Does it apply California's daily overtime rule instead of the weekly 40-hour rule?

No. The tool computes overtime as anything past the weekly total exceeding your set threshold, not a daily rule. If your state requires daily overtime after 8 hours worked in a single day, you'd need to check each day against that separately.

Will my week of entries still be there if I come back tomorrow?

That's not something to assume - treat the log as tied to your current browser session and export or record the totals before closing the tab, rather than relying on it to persist automatically.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools