---
title: "How to Calculate Your Total Work Hours for a Week"
description: "Add daily work periods accurately to calculate a weekly total, including breaks and partial hours, with an easy step-by-step method."
canonical: "https://freeaigeneration.com/en/guides/how-to-calculate-your-total-work-hours-for-a-week/"
robots: "noindex"
lang: "en"
---

# How to Calculate Your Total Work Hours for a Week

To calculate weekly work hours you do seven small calculations and a sum, not one big one. The unit that makes it reliable is the minute: get each day into whole minutes, add those minutes, and convert to decimal hours once at the end. Do it in the other order and the two columns of the result stop matching.

## Seven rows, one running total

The work hours calculator gives you Monday through Sunday, each row with an include switch, a start, an end and an unpaid break in minutes. Only switched-on rows are validated and counted. A row you leave off contributes nothing even if times are still typed into it, which is the point of the switch and also the easiest way to lose a day by accident.

The per-day figures and the weekly total are derived from the same integer minutes, so with a single row enabled the two lines agree exactly. Nothing about a standard week, a contract or a legal maximum is baked in — the grid adds what you tell it to add.

## Why the sum happens in minutes

Minutes are the exact unit; decimal hours are a presentation of minutes. Add five days of 420 minutes and you have 2,100 minutes, which converts once to 35:00 and 35 decimal hours. Round each day to 7.00 first and you get the same answer, because those days happened to be exact.

The difference shows up when the days are not exact. Five days of 7 hours 40 minutes is 5 × 460 = 2,300 minutes = 38:20, and the decimal column reads 38.33. Adding five separately rounded values of 7.67 gives 38.35, a total that matches neither the minutes nor the h:mm display. The gap is small, and it is the kind of gap somebody else notices.

## A worked week

Monday 480 minutes, Tuesday 450, Wednesday 180, Thursday off, Friday 480. The enabled rows sum to 480 + 450 + 180 + 480 = 1,590 minutes = 26:30, or 26.5 decimal hours. A half day and a day off are both ordinary inputs; the calculator has no opinion about what a week should look like.

## The optional target

The "Weekly target" field is optional. If you use it, it takes decimal hours from 0 to 168 with up to two decimal places, and either a dot or a comma as the separator, so 37.5 and 37,5 mean the same thing: 37 hours 30 minutes.

The line below reports the difference as plain arithmetic — actual minus target — worded as more than, less than, or exactly the target. It is never called overtime, and the distinction is deliberate: a total above a number you typed says nothing about what a rule, a contract or a payroll system would do with the extra hours.

## The ceiling, and what a total is not

A week is 168 hours, which is why the target field stops there. The grid itself cannot reach that figure from valid entries, because each row holds one shift shorter than 24 hours; seven of them top out at 167 hours 53 minutes.

The total describes the rows you entered. It is not a standard working week, not an overtime calculation, and not a record that survives the tab — nothing is saved, stored or exported, and there is no way to reload yesterday's grid. The record-keeping side is covered in [how to fill in a timesheet without calculation errors](/en/guides/how-to-fill-in-a-timesheet-without-calculation-errors/), and a single row is worked through in [how to calculate work hours in a day](/en/guides/how-to-calculate-work-hours-in-a-day/).

The [Work Hours Calculator](/en/utilities/date-time/work-hours-calculator/) does the summing and the conversion in one pass. It runs in your browser, no FreeAIGeneration account required. The [guides hub](/en/guides/) collects the neighbouring walkthroughs.