Timesheet Template

About this template

When to use it

A month of work for anyone who must allocate hours to projects. Three sheets — Work log, Weekly & monthly summary, How to fill in — with the first titled “Timesheet Template — June 2026”. Enter clock in, clock out and break; work hours and overtime calculate themselves.

Filling order

1. Rows 6–35 are 1–30 June; column D fills its weekday from =IF(C6=””,””,CHOOSE(WEEKDAY(C6,2),”Mon”,”Tue”,”Wed”,”Thu”,”Fri”,”Sat”,”Sun”)) — Monday through Sunday.
2. Column E takes one of four exact strings — Design, Development, Meetings, Reporting — because the summary sheet groups them with SUMIF. Days off are marked Day off, which no SUMIF picks up.
3. Enter clock in (F), clock out (G) and break in hours (H). Columns I and J are formulas.
4. Column K holds the project code that justifies billing; internal work is coded INT-000, per rule 4.
5. The only cell for you on the summary sheet is the 160-hour monthly standard (C15).

How the formulas calculate

• Work hours =IF(OR(F6=””,G6=””),””,ROUND((G6-F6)*24-N(H6),1)); overtime =IF(I6=””,””,ROUND(MAX(0,I6-8),1)), counting only what passes eight hours a day.
• Row 36 totals with =SUM(I6:I35), =SUM(J6:J35) and =COUNT(I6:I35)&” days worked”, which prints as “N days worked”.
• Weekly rows use =SUM(‘Work log’!I6:I12), and the limit check is =IF(E7>12,”Over limit”,”Within limit”) against the 12-hour weekly overtime cap in the rules.
• Hours by task type is =SUMIF(‘Work log’!$E$6:$E$35,”Design”,’Work log’!$I$6:$I$35) — the wording is baked in, so rename a task type in B24:B27 and in the formula together.
• The daily average is =IFERROR(C16/C19,0) and the variance =C16-C15 against the monthly standard.

Know this first

Rule 1 on the How to fill in sheet says “work hours (column H) and overtime (column I)”, but work hours are in column I and overtime in column J; H is the break. Table 4 on the summary sheet is titled “Monthly trend (reference)” yet its rows are Design, Development, Meetings, Reporting (34, 62, 18, 26) — task types, not months, and hand-typed, so this month’s entries never move them. Retitle it or replace it with real monthly totals. Nothing aggregates the project code; for hours per project add =SUMIF(‘Work log’!$K$6:$K$35,”PRJ-101″,’Work log’!$I$6:$I$35) yourself.

Examples

• 2 June · Design · 09:00 · 19:30 · break 1 · PRJ-101 → 9.5 hours, 1.5 overtime.
• 10 June · Development · 09:00 · 21:00 · break 1 · INT-000 → 11.0 hours, 3.0 overtime.
• Once a week’s overtime passes 12 hours, that week’s check cell reads “Over limit”.

Common mistakes

• Inventing task type names such as “Development 2”, which SUMIF then ignores.
• Writing “1 hour” instead of the number 1 in the break column.
• Submitting with the project code blank, leaving no basis for billing.
• Reusing the file for a 31-day month without extending row 36 and the weekly ranges.