A clean record of hours worked, billed correctly
A timesheet is the evidence behind every hourly payment — it shows what was worked, on which project, on which day, and what it adds up to. A vague “about 40 hours” invites disputes; a per-day, per-task breakdown does not. This builder produces a weekly timesheet that totals hours by row and by day, splits standard from overtime hours against a threshold you choose, and prices the week at your hourly rate.
How it works
Hours are entered per task across the seven days of the week. The tool sums them, then applies an overtime split:
Row hours = Mon + Tue + Wed + Thu + Fri + Sat + Sun
Total hours = Σ row hours
Standard hrs = min(Total hours, threshold)
Overtime hrs = max(0, Total hours − threshold)
Pay = standard hrs × rate
+ overtime hrs × rate × overtime multiplier
The threshold (often 40 hours) and the overtime multiplier (often 1.5×) are both configurable, so the timesheet matches your contract or local labour rules. Each day is also totalled across all tasks, so you can spot a day that ran long. The output is a printable text timesheet ready to submit to a client or payroll.
Worked example
For example, a contractor working three projects in one week enters:
| Project | Mon | Tue | Wed | Thu | Fri | Sat | Sun | Total |
|---|---|---|---|---|---|---|---|---|
| API redesign | 6 | 7 | 8 | 0 | 6 | 0 | 0 | 27 |
| Documentation | 2 | 0 | 0 | 8 | 2 | 0 | 0 | 12 |
| Bug fixes | 0 | 0 | 0 | 0 | 0 | 5 | 0 | 5 |
| Total | 8 | 7 | 8 | 8 | 8 | 5 | 0 | 44 |
With a rate of £50/hour, a 40-hour threshold, and a 1.5× overtime multiplier:
- Standard pay: 40 × £50 = £2,000
- Overtime pay: 4 × £50 × 1.5 = £300
- Total billable: £2,300
The Saturday hours push the week into overtime, which is captured correctly without manual calculation.
What contractors and agencies need to know
Decimal hours are essential. Enter 7.5 rather than “7h30” — fractions are billed correctly and sum accurately. “7 hours 30 minutes” is easy to misread; 7.5 is not.
The week-ending date prevents disputes. Each weekly submission should carry a unique date — typically the Friday or Sunday that closes the week — so payroll can match it to the correct pay period without ambiguity. Missing or inconsistent week-end dates are the most common reason timesheets get bounced back.
Project codes matter for clients. A client with five cost centres needs to know which one your time hit. Even a short code like PRJ-412 makes reconciliation fast. Without it, approval stalls while someone emails you for clarification.
Overtime rules vary by jurisdiction. UK workers under the Working Time Regulations have different rules than US workers under FLSA. This tool lets you set your own threshold and multiplier, so it adapts to any contract or local law — it does not assume a specific jurisdiction’s defaults.
Pairing this with an invoice
This timesheet produces the hours-and-rate breakdown; pair it with a separate invoice builder to add VAT, payment terms, and your company details. The timesheet is the evidence; the invoice is the demand for payment. Attaching a clear timesheet to an invoice reduces the chance of it being queried and speeds up payment cycles.