Proof of work for yourself, not your boss: keeping a record
· 6 min read
Proof of work for yourself is a record of what the day actually contained, kept for the person who lived it. It is the answer to the evening feeling that you did nothing, and to the opposite feeling that you can keep this pace forever. To do its job it has to be private, automatic, and honest, which is a different design from anything built to report to a manager.
The two lies the evening tells you
At the end of a working day, memory hands you one of two stories, and both are wrong.
The first is that you did nothing. You were at the desk for nine hours, you are tired, and you cannot name what you produced. The meeting ran long, the thing you meant to finish is not finished, and the day feels like a loss. This story is common on days that were actually full of work, because the work was in pieces too short to remember.
The second is that the day was fine and you can do it again tomorrow. This one shows up on the days that ran to 7:30, because the overrun was absorbed a few minutes at a time and never registered as a whole.
A record made during the day, without your help, answers both. It says the editor had three hours and twelve minutes on the day you thought you did nothing, and it says the day total was nine hours forty on the day you thought was fine. Why you feel busy all day and still got nothing done is about the first lie.
What a personal record needs to be
A record that serves you, rather than someone above you, has four properties, and each rules out most of what gets sold as time tracking.
It has to be private. Not “private to your team”, not “private until you share it”: stored on your Mac, readable by you, sent nowhere. The moment a record can be seen by someone with authority over you, you start shaping the day for the record, and it stops being true.
It has to be automatic. A record you have to produce is one you will stop producing by Wednesday, and the days you skip are the ones you most needed. The day has to write itself down.
It has to be honest. It records what happened, including the two hours in the browser, with no way to tidy it afterward. A record you can edit is a diary. A diary is fine, but it is not proof.
And it has to be yours. Stored in a file you can find, in a format you can read without the app, with a way to delete all of it that actually deletes all of it.
Why monitoring software is the wrong model
Anything built to report time to an employer is built backward for this purpose.
Monitoring tools are designed around the needs of the person reading the report, not the person generating it. So they capture as much as possible: window titles, document names, URLs, screenshots at intervals, keystroke counts. Every one of those makes the report more useful to a manager and less honest as a personal record, because you know it is watching and you behave for it. What employee monitoring software sees and what a personal tracker should not goes through the list.
The design question for a personal record is the opposite: what is the least that needs to be seen for the record to be useful to me. The answer is the name of the app in front, and how long. Not what was in it, not which document, not which website. App names are enough to tell you that the day was three hours of editor, two of browser, and one of chat, and that answers both evening lies. Anything more is surveillance with your own name on the account.
Keeping the record
Punchcard is built to the four properties above and nothing else. It sits in the menu bar and notices which app is in front during the day. App names only: it never sees window titles, document names, URLs, keystrokes, or screen contents, and it asks for zero macOS permissions, so it could not see them if it wanted to. At the closing time you set, it prints a receipt of the day: one line per app with the time, a day total, a stamp. That receipt is the proof.
Private: it contains no networking code at all. There is no account, no cloud, no analytics, no crash reports; the release build fails if a networking symbol appears. Nothing leaves the Mac because nothing can.
Automatic: there are no timers to start, no projects to pick, no tags. It is on, and at closing time the receipt prints.
Honest: the receipt is what it is. There is no editing a line after the fact.
Yours: the record is one SQLite file at ~/Library/Application Support/Punchcard/punchcard.sqlite. You can export it as CSV and keep it as long as you like, and “Burn the roll” deletes everything, which means everything.
What it does not do is also part of the design. There is no team view, no sharing to a manager, and no integrations. If your employer requires a time report, Punchcard is not that tool. It answers one question, “where did my day go”, for the person asking it.
What to do with the proof
A record nobody looks at is not proof of anything. Three uses, in order of effort.
Read it at closing time. Total, top three lines, the one that surprises you. That takes a minute and it is the whole answer to the evening lies. The end-of-day receipt: a two-minute review that sticks lays out the routine.
Keep it where you can see it. Receipts export as a 1080 by 1350 PNG or as plain text. Some people keep a folder of days; some put the day’s receipt on the fridge so the people they live with can see that the day existed. Letting someone at home see it is your choice, made on your terms, which is the opposite of a report.
Plan from it. A week of receipts, or the Sunday week roll, tells you what a normal week actually holds, and that is the only honest basis for deciding what next week should hold. People who plan from memory plan for the week they wish they had.
What a record is not
A per-app record is proof that the day happened and where it went. It is not proof of output. Three hours in the editor is three hours in the editor; it does not say the code was good, or that it shipped.
It is not a defense. If you find yourself wanting to show the receipt to a manager to prove you were working, something has gone wrong upstream of the receipt, and the receipt will not fix it. The record loses its honesty the moment it is kept for anyone else’s questions.
And it is not a score. A long editor line is not a good day and a long chat line is not a bad one. The record is evidence. What it means is up to you, which is the point of keeping it for yourself.
Questions
Is a private record really worth keeping if nobody checks it?
That is the only kind worth keeping. A record that someone checks is shaped for them. A record only you read is the one that tells you the truth.
What does Punchcard actually store?
App names, the time each was in front, and the date, in one SQLite file on your Mac. Nothing else. You can open the CSV export and see every field.
Can my employer read it?
Not through Punchcard. It has no sharing, no sync, and no network code. Someone with administrator access to your Mac could find the file, as they could any file, but nothing about the app sends it anywhere.
I want to show my work to a client or team. Can I?
You can export a receipt as a PNG or copy it as text and send it yourself. That is a choice you make each time, not a feature that does it for you, and the record stays yours either way.