How to show a client where the time went without a timesheet
· 6 min read
Give the client a dated account of the work in plain language, one short entry per working day, with the artifacts that prove each entry (files, messages, a daily receipt) rather than a grid of quarter hours. A timesheet was only ever a summary of evidence; when you have the evidence, you can skip the summary and show the thing itself.
What the client is actually asking
“Can you show me where the time went?” is rarely a request for a spreadsheet. It is one of three things: the invoice was bigger than expected and they want to understand why; the project took longer than promised and they want to know it was not idle; or someone above them asked and they need something to forward. All three are answered by the same document, and none of them is answered well by a table of 0.25-hour rows.
What the client needs is to be able to read, in two minutes, what happened on which days and why it took the shape it did. If you can give them that, the number stops being the subject.
Build a dated account from what already exists
You do not need to have tracked anything. You need to reconstruct the sequence of days, which your Mac has been recording on your behalf in several places.
- Open the project folder in Finder, list view, sorted by Date Modified. Every cluster of modified files is a working day. Note the dates and what kinds of files changed: drafts, exports, revisions.
- Search Mail and your messaging app for the client. Sort sent messages by date. Each one is a dated record of what you were doing and, usually, what you were waiting for. Copy the dates into a list.
- Scroll Calendar back over the project. Calls, reviews, and any blocks you put in for yourself. Add the dates.
- If you have daily receipts or any kind of log, line them up against the dates. Even a bare day total per date makes the account far more convincing, because it shows weight, not just presence.
- Merge everything into one list of dates. Against each date, write what happened in one line. Where you were waiting on the client, write that too, plainly and without blame: “Waiting on copy from your team” is a fact, not an accusation.
You will end up with something like twenty lines. That is the account. Everything else is formatting.
Make it readable: one entry per day, three parts each
For each day, write three short things:
- What was done. “Built the first full draft of the pricing page.”
- How heavy the day was. “Most of the day” or “about two hours” or “a full day.” Round honestly. If you have a receipt, use its total.
- What was produced or sent. “Sent draft v1 for review at 4 pm.”
Then group the days into phases with a one-line heading each: Discovery, First draft, Revisions, Handover. A client reading this sees a shape. They see that revisions took nine days because feedback came in three batches, and they can see the batches because the waiting days are listed too.
Keep the whole thing to a page. The goal is a document the client can read in the time it takes to decide whether to argue about the invoice, and that leaves them with no argument to make.
Back it with evidence, not hours
Here is the part that replaces the timesheet. For each phase, attach or link the artifacts: the draft you sent on the 4th, the revision on the 11th, the message thread where the scope changed. The client does not need to audit these. They need to see that they exist and match the dates.
Evidence does something a timesheet cannot: it is checkable by the client without trusting you. A timesheet says “3.5 hours, Tuesday.” A sent file says “here is the thing that existed on Tuesday that did not exist on Monday.” The second one ends the conversation.
If you have a daily record of hours, include the totals per day as a column in the account, but do not lead with them.
A daily receipt as the backbone
All of the above is easier if each day already has a record you did not have to write. Punchcard prints one: at your closing time, a paper receipt feeds out of the menu bar with the day itemized by app, a total at the bottom, and a stamp. Seven days make a week roll on Sunday. Each receipt exports as a 1080 by 1350 PNG, or copies as plain text, so a day’s total and its shape can be dropped into the account or attached to it directly.
For a client, a receipt does two things well. The day total is an honest measure of weight, not a reconstruction. And the itemization shows the nature of the day: eight hours in a design app reads differently from eight hours split between mail, a browser and a spreadsheet, and a client can see the difference without any explanation from you.
What it will not do is name the client. Punchcard records app names only, never window titles, document names or URLs, and it has no project or client field. A receipt proves that Tuesday was 6 hours 10 minutes, mostly in your editor; it does not prove those hours were for this client rather than another. If you work on one client at a time, that is implied by the dates. If you do not, your account needs a line saying which part of which day was theirs, and the receipt supplies the total you are splitting. There is more on using receipts as a shareable record in a time log you can post: the receipt format.
What not to send
Three things make these conversations worse.
Do not send raw data. A CSV export, an app-by-app breakdown for every day, or screenshots of a dashboard give the client more than they asked for and invite line-by-line questions about the 40 minutes in a browser on the 9th. Send the account; keep the data for yourself in case it is needed.
Do not explain time you are not billing. If you spent an evening reading around the problem and chose not to charge for it, leave it out. Mentioning unbilled time sounds like an attempt to make the billed time look reasonable by comparison, even when it is simply true.
Do not apologize for the days that were waiting. List them. “Waiting on feedback” appears on almost every project account, and clients who see it laid out next to the dates of their own messages tend to understand the timeline without a word from you.
Questions
What if the client insists on a timesheet format?
Give them the dated account with a column of hours per day added, and a total. That is a timesheet in every way that matters. If they want quarter-hour task rows and you do not have them, say so: “I kept a daily record, not a task-level one; here is the day-level detail.” Most clients accept that because it is clearly real.
Can a daily receipt be edited before sending?
A Punchcard receipt is what the day was; there is no editing. If a day includes hours that belong to another client, say so in the account rather than altering the record. An obviously unedited record is worth more to you than a tidy one.
How far back can I reconstruct?
File dates and sent mail go back as far as you keep them, so years. Daily receipts only exist from the day you started printing them. For an old project, use the first method; for every project after this one, let the receipts do the work.
Should I do this for every invoice, or only when asked?
A one-page account with every invoice over a certain size is a habit that prevents the question from being asked at all. It takes about fifteen minutes when the receipts and sent folder are already there.