Why it matters for agencies
A timesheet is the source for billing, payroll checks, utilisation and retainer burn. If it is filled in from memory on Friday afternoon it is wrong, and every number built on it is wrong too.
How to do it or work it out
Record time as you go with a timer, or at the latest at the end of each day. For each entry, note the client, the project and a short description of the work.
Submit the timesheet at a fixed time each period and have someone other than the author review it. Add up the days and compare the total with the person's expected hours before you approve it.
Choose a period that suits how you bill. Weekly works for most agencies, and fortnightly or monthly suits teams that invoice on those cycles. The longer the period, the more people forget, so pair a longer period with daily timers.
A timesheet is not the same as a roster or a time card. A roster says when someone is planned to work, and the timesheet says what happened. A time card, or a clock-in and clock-out record, usually holds only start and finish times. A timesheet adds what the hours were spent on, which is the part an agency needs to bill a client.
What a useful timesheet holds: the person, the period, the date of each entry, the hours (or start and finish times), the client, the project or task, whether the time is billable, and a line of description. Add unpaid breaks if your payroll needs them, and leave and public holidays so a short week is explained. Who approved it and when is part of the record too.
It can live on paper, in a spreadsheet or in software. Paper and spreadsheets are fine for a handful of people. Once several people log time against many projects, they cost more in chasing and re-typing than they save, because totals have to be added up and checked by hand. Our weekly and agency timesheet templates cover the first two, and Jasper HQ covers the last.
If your hours feed payroll, the rules for what records you must keep and for how long come from your country and your award or agreement, not from this page. Ask your payroll provider or check the regulator's own pages.
A worked example
A developer logs 7.5 hours on each of Monday to Friday. The week totals 37.5 hours, against 38 expected, so the half hour gap is either unrecorded time or a short day. The approver asks about it before approving instead of finding out at invoicing. The following week the same developer logs 38 hours, but 12 of them fall on Wednesday. The total matches the expected hours and still hides an error, which is why approvers read the days and not only the total.
Common mistakes
- Filling it in on Friday afternoon. Memory drops the short tasks and rounds the rest, so the sheet drifts towards the contracted week instead of the real one.
- Vague descriptions such as work or meeting. A client who queries the invoice will ask what the hours were, and nobody can answer from that.
- Submitting without checking the total. A day with 3 hours or 14 hours is usually a mistake, and it is far easier to fix before approval than after invoicing. Keeping one sheet for pay and another for billing makes it worse, because the same hours then drift apart. Record once, with a billable flag, and report both ways.