Calculate Your Weekly Time Card
Enter clock-in and clock-out times for each workday.
| Day | Clock In | Clock Out | Break (min) | Daily Total |
|---|---|---|---|---|
| Monday | 0.00 | |||
| Tuesday | 0.00 | |||
| Wednesday | 0.00 | |||
| Thursday | 0.00 | |||
| Friday | 0.00 | |||
| Saturday | 0.00 | |||
| Sunday | 0.00 |
How Time Card Calculation Works
Four simple steps to compute your weekly time card.
Enter Clock-In Times
Type the start time for each day you worked. Use the time picker for quick entry in HH:MM format.
Enter Clock-Out Times
Enter your end time for each day. The calculator handles both standard and overnight shifts.
Add Break Times
Enter break duration in minutes for each day. Lunch breaks and rest periods are subtracted from daily totals.
View Weekly Total
Get your weekly total in HH:MM and decimal hours, plus overtime hours and average daily hours.
What Is a Time Card Calculation?
Understanding how employee time tracking works.
Time card basics
A time card (also called a timesheet) is a record of an employee's work hours for a given pay period. Each day shows a clock-in time, a clock-out time, and any break deductions. The daily hours are summed to produce the weekly total.
The formula is: Daily Hours = Clock Out − Clock In − Breaks. For example, clocking in at 9:00 AM and out at 5:30 PM with a 30-minute lunch gives you 8 hours net.
Decimal hours for payroll
Payroll systems require decimal hours — not HH:MM. 8 hours 30 minutes becomes 8.50 decimal hours. This format allows direct multiplication with hourly rates for pay computation.
Overtime on time cards
When total weekly hours exceed 40 (the FLSA standard), the excess is overtime. Some employers track daily overtime too — any day exceeding 8 hours generates OT. This calculator flags both scenarios. For a quick single clock-in and clock-out, use the time card calculator.
When to Use Time Card Calculation
Common scenarios for time card tracking.
Office Workers
Track daily work hours for standard 9-to-5 shifts. Ensure accurate payroll reporting by recording exact clock-in and clock-out times every day.
Hourly Employees
Hourly workers need precise time card calculations for every pay period. Track regular hours and flag overtime when weekly totals exceed 40.
Small Business Owners
Calculate employee hours without expensive payroll software. This free tool gives you weekly totals and decimal hours ready for payroll processing.
Remote Workers
Track flexible work hours when working from home. Log your actual productive hours and breaks to maintain transparency with employers.
Restaurant & Retail
Service workers with variable shifts need accurate time cards. Track split shifts, weekend hours, and holiday overtime with ease.
Freelancers
Bill clients accurately by tracking your work hours per project. Convert to decimal hours and multiply by your rate for invoicing.
Time Card Calculation Examples
Real-world time card scenarios and their results.
Standard 5-day workweek
Clock in 9:00 AM, out 5:30 PM, 30-min lunch daily = 8.0 hours/day × 5 = 40.0 hours/week. No overtime triggered.
Overtime workweek
Same schedule plus Saturday 8:00 AM – 2:00 PM (6 hours) = 46.0 total hours = 6.0 hours overtime.
Variable shift week
Mon 10h, Tue 8h, Wed 6h, Thu 9h, Fri 8h = 41.0 total hours = 1.0 hour overtime.
Step-by-Step Walkthrough
The same weekly data read four different ways — and what each figure is actually good for.
A technician records six days: 7.75, 8.25, 8.00, 9.50, 7.50 and 5.00 hours. The overtime threshold is 40 hours for the week.
Total the week
7.75 + 8.25 + 8.00 + 9.50 + 7.50 + 5.00 = 46.00The headline number, and the only one that the overtime rule is tested against. On its own it says nothing about how the week was distributed.
Running total46.00 decimal hours
Count the days worked
6 days with a non-zero entryDays worked is a separate quantity from hours, and it matters for rest-day rules, attendance and per-day allowances. Two weeks with identical hours can differ here.
Running total6 days worked
Derive the daily average
46.00 ÷ 6 = 7.67 hours per dayThe average is a validation tool more than a metric. For a nominal 8-hour shift, 7.67 is plausible; a figure of 11.5 or 3.2 would point straight at a mistyped entry.
Running total7.67 hours per day
Split at the threshold
Regular = 40.00 Overtime = 46.00 − 40.00 = 6.00Six overtime hours, produced mostly by working a sixth day at all. Note that the 9.50-hour Thursday is not what drives this under a weekly rule.
Running total40.00 + 6.00 overtime
Sanity-check against the average
6 days × 7.67 ≈ 46.0 ✓Multiplying the average back by the day count should reproduce the total. When it does not, the day count and the hours have drifted apart — usually because a blank day was skipped or double-counted.
Running totalConsistent
Six days totalling 46.00 hours gives 6.00 overtime hours and a 7.67-hour daily average. The average is the fastest check that no row was mistyped.
Common Mistakes and Pro Tips
Mistakes that quietly corrupt your numbers
Dividing total hours by seven to get the daily average.
Divide by days actually worked — here 46.00 ÷ 6 = 7.67, not 6.57.
Why it matters: Including rest days drags the average below every real shift, which destroys its usefulness as a validation check. An average that no individual day resembles cannot flag anything.
Reading a high daily average as evidence of overtime.
Test the weekly total against the threshold; the average is diagnostic, not contractual.
Why it matters: A four-day week averaging 10 hours a day totals only 40 and owes nothing. The average describes shape, the total decides pay, and confusing the two produces overtime claims that the contract does not support.
Counting a zero-hour day in the days-worked figure because the row exists.
Count only days with actual hours recorded against them.
Why it matters: An inflated day count deflates the average and quietly breaks the cross-check. Worse, days worked often drives rest-day and allowance rules, so the error propagates beyond the arithmetic.
Entering a day as 7.45 when the shift was 7 hours 45 minutes.
Convert first: 45 ÷ 60 = 0.75, so the entry is 7.75.
Why it matters: The two differ by 0.30 hours per occurrence, and the mistake is self-consistent enough to survive a glance at the column. Across six days it can shift a week by nearly two hours and change the overtime band.
Pro tips
Use the average as a tripwire
Before accepting a week, ask whether the daily average is close to the expected shift length. It is the single fastest check on a column of numbers, and it catches most transcription errors.
Enter decimals, not clock readings
This card takes decimal hours. Seven hours forty-five minutes is 7.75, never 7.45 — convert the minutes before typing.
Distinguish zero days from blank days
A day off and a day whose punch is missing look identical in a total. Marking them differently is what makes days-worked trustworthy.
Track the spread, not just the mean
A 7.67 average built from 5.0 and 9.5 days is a very different week from six flat 7.67s. For fatigue and scheduling, the range matters more than the average.
Compare weeks, not days
Week-on-week totals reveal genuine workload trends. Day-on-day variation is mostly noise and reading into it produces conclusions that will not replicate.
Note why a sixth day happened
Working six days is the usual driver of a large overtime figure. A one-line reason attached to the week makes the cost explainable when it is reviewed.
Weekly Totals, Averages and Overtime
How days worked and total hours combine — with the daily average that should be used to sanity-check each row.
| Days worked | Total hours | Average per day | Regular | Overtime |
|---|---|---|---|---|
| 4 | 32.00 | 8.00 | 32.00 | 0.00 |
| 4 | 40.00 | 10.00 | 40.00 | 0.00 |
| 4 | 44.00 | 11.00 | 40.00 | 4.00 |
| 5 | 37.50 | 7.50 | 37.50 | 0.00 |
| 5 | 40.00 | 8.00 | 40.00 | 0.00 |
| 5 | 42.50 | 8.50 | 40.00 | 2.50 |
| 5 | 45.00 | 9.00 | 40.00 | 5.00 |
| 6 | 46.00 | 7.67 | 40.00 | 6.00 |
| 6 | 48.00 | 8.00 | 40.00 | 8.00 |
| 7 | 52.50 | 7.50 | 40.00 | 12.50 |
No rows match that filter.
The second row is the instructive one: a 10-hour daily average with no overtime at all, because a weekly threshold cares only about the total. For the underlying clock readings, use the time card calculator.
Reading a Weekly Time Card Properly
Four numbers, four different jobs — and the ways they get confused.
What each summary figure is for
The four outputs answer genuinely different questions:
- Decimal hours — the pay figure, and the only one the overtime threshold tests.
- Days worked — drives rest-day entitlements, attendance and per-day allowances.
- Average per day — a validation check on the individual rows.
- Overtime hours — the premium band, derived from the total alone.
Problems begin when one is used to answer another's question, most often when the average is treated as if it decided overtime.
Why the average is a validation tool
A daily average has little value as a performance measure — it flattens exactly the variation that makes a week interesting. Its real use is arithmetic quality control.
For a workforce on nominal 8-hour shifts, any weekly average outside roughly 6.5 to 9.5 deserves a second look before the card is accepted. That single range catches most decimal-entry errors, missing punches and duplicated rows.
Because it is cheap to compute and easy to explain, it belongs in the review step of any manual time card process.
The 7.45 problem
Entering 7 hours 45 minutes as 7.45 instead of 7.75 is the defining error of decimal time cards. It is subtle because the number looks entirely reasonable in a column of similar values.
Two properties make it dangerous: it always understates, and it recurs on every row where minutes exceed 30. A week of such entries can lose two hours without producing a single implausible-looking figure.
The reliable defence is the halfway rule: minutes above 30 must give a decimal above .50. Any entry with a fraction between .31 and .59 is worth checking, since those values cannot arise from a clean minute conversion.
Six-day weeks and rest-day rules
Days worked is not a decorative statistic. Many jurisdictions and agreements guarantee a minimum rest period each week, and some require a premium for a seventh consecutive day regardless of hours.
A week of six short days can therefore be more contractually significant than a week of five long ones, even though the second may have more hours in it.
Where those rules apply, read days worked alongside the hours total rather than treating it as a by-product of it.
Frequently Asked Questions
Common questions about the Time Card Calculation.
How do I calculate time card hours?
Enter your clock-in and clock-out times for each day of the week. The calculator subtracts clock-in from clock-out for each day, then sums all daily totals to give you the weekly total in both HH:MM and decimal hours format.
Does it account for lunch breaks?
Yes. Enter your break duration in minutes for each day. The calculator subtracts break time from the daily total automatically. A 30-minute lunch break on an 8-hour shift gives you 7.5 net hours.
How is overtime calculated on a time card?
The calculator sums all daily hours for the week. If the total exceeds 40 hours (or your custom threshold), the excess is flagged as overtime hours and highlighted separately.
What format should I use for clock-in/out?
Use the time picker (HH:MM format). The calculator works with both 12-hour and 24-hour formats. Enter times like 09:00, 17:30, etc.
Can I calculate bi-weekly time card hours?
This calculator covers one week (7 days). For bi-weekly calculations, calculate each week separately and add the totals. The weekly total and overtime are shown independently.
Is this time card calculator free?
Yes, completely free. No sign-up or download needed. All calculations happen in your browser — your time card data stays private.
How is the daily average calculated?
Total hours divided by days actually worked, not by seven. A 46-hour week over six days averages 7.67 hours per day. Dividing by calendar days would give 6.57, which resembles no real shift and is useless as a validation check.
Does a high daily average mean overtime is owed?
Not under a weekly threshold. A four-day week averaging 10 hours a day still totals only 40 and owes nothing. The average describes how the week was shaped; the weekly total is what decides the overtime band.
How do I enter 7 hours 45 minutes?
As 7.75. Divide the minutes by 60 first — 45 ÷ 60 = 0.75. Entering 7.45 understates the day by 0.30 hours and is hard to spot, because the value looks plausible next to other entries in the column.
Should a day off count towards days worked?
No — count only days with hours recorded. Including zero-hour days inflates the day count, deflates the average and breaks the cross-check, and days worked often drives rest-day and allowance rules independently of hours.
What is a quick way to check a week is correct?
Multiply the daily average back by days worked and confirm it reproduces the total, then check the average is close to your expected shift length. Together those two checks catch most mistyped rows, missing punches and duplicate entries.