Contract work from a Mac: keeping a record without monitoring software
· 6 min read
You can keep a credible record of contract hours on a Mac without installing anything that watches your screen. Three parts do it: a daily receipt of hours by app, a one-line note per day of what was done, and the artifacts themselves (commits, files, sent mail) as proof. That record satisfies most clients, and unlike a monitoring tool, it belongs to you.
Why monitoring software is the wrong tool for a contractor
Monitoring tools exist to let someone else watch. They take screenshots on a schedule, log keystrokes or activity levels, read window titles, and send all of it to a server the client controls. For a contractor, that is the wrong shape in three ways.
It records the wrong thing. Screenshots prove you were at a screen; they do not prove the work was good or that the hours were efficient, and a client who needs screenshots to trust you has a trust problem the screenshots will not fix.
It puts your data on their server. Everything on your screen, including the other client’s work in the next tab, your bank, your messages, goes into their record. You cannot take it with you when the contract ends, and you cannot delete it.
It changes how you work. Knowing each screen is captured makes people perform work rather than do it. The post on what employee monitoring software sees and what a personal tracker should not lays out the full list of what these tools collect.
None of this means you should refuse a client who requires one; that is a contract decision and sometimes the contract is worth it. It means that if the question is simply “keep a record of your hours,” monitoring software is not the answer to it.
What a credible record actually needs
A client who asks for a record of hours needs to be able to answer three questions, and a good record answers them in order.
How long? The hours per day, recorded as they happened, not written down on Friday. This needs to be automatic, because a record that depends on remembering to start a timer has gaps exactly where it is most needed.
Doing what? A line per day in plain language. “Wired up the export endpoint, fixed two failing tests, reviewed the PR from their side.” Written at the end of the day, while it is fresh, in under a minute.
Can I check? The artifacts. A commit log with dates, files with modification times, sent messages, delivered documents. These exist anyway; the record just points at them.
Together, these are stronger than screenshots, because the client can verify the artifacts without trusting you and can read the notes without interpreting pictures of your screen.
Set it up in ten minutes
- Install an app-level recorder that asks for no permissions. Punchcard sits in the menu bar and notices which app is in front during the day. It needs no Accessibility, Screen Recording or Full Disk Access permission, records app names only (never window titles, document names, URLs, keystrokes or screen contents), and has no networking code, so nothing leaves the Mac. At your closing time it prints a receipt of the day: one line per app with its time, a total at the bottom, a stamp. See how to set up Punchcard in ninety seconds.
- Set the closing time to the end of your contracted day. If a day runs past it, the receipt prints late, headed SORRY WE MISSED YOU, with the real total. That is the overtime record.
- Create a plain text file called worklog.txt in the project folder. One line per day: date, client, what was done. Thirty seconds at closing time. If you work for more than one client, this line is where the split lives, because the receipt does not know clients.
- Once a week, export. Copy the week’s receipts as plain text into the log, or export the CSV from Punchcard and keep it beside the log. The weekly roll on Sunday gives you the totals in one print.
- Keep the artifacts where they are. Do not copy commits or files into the record; reference them. “See commits from 12 to 16 August” is enough.
From here on, the record keeps itself. The only manual step is the one line per day, and it is the line that makes the rest readable.
What the record shows and what it does not
Be honest with yourself and the client about what this is.
It shows the length of each working day, the share of the day in each app, and a note of what was done. Over a month, it shows a pattern: how many days, how long, how much was in the editor versus the meeting app versus the browser. A client can see the shape of the engagement without seeing a single document name.
It does not show what was on the screen, which sites were visited, which files were open, or which of two clients an editor hour belonged to. Punchcard will not provide any of that, by design, and if a client needs it, they need a different tool and you need to decide whether to accept it. The record also does not see work away from the Mac: calls, site visits, thinking. Add those to the daily line.
It is also a personal record, not a shared one. There is no dashboard the client can log into, no team view, no integration with their systems. You produce the summary; they read it.
Presenting the record when asked
A client who asks to see the record is best served by a one-page summary per invoice period, not by the raw data.
- A table of dates, hours (from the receipt totals), and the daily line.
- A total at the bottom that matches the invoice.
- A sentence pointing at the artifacts: where the commits, files or deliverables live.
If they want more, the receipts themselves are designed to be shareable: each exports as a 1080 by 1350 PNG with the app breakdown and total, and nothing else. How to show a client where the time went without a timesheet covers the summary format in more detail.
If the client insists on their tool
Sometimes a contract requires the client’s monitoring software, and the work is worth it. In that case, run both. Their tool gives them what they asked for; your own record gives you a copy of your hours that survives the contract, lives on your Mac, and shows nothing but app names. When the contract ends and their server is no longer yours to query, the receipts still are.
Check what their tool collects before installing it, and put it on a separate user account or a separate Mac if the contract allows. The post on privacy-first time tracking on a Mac lists the questions to ask about any tool that watches a screen.
Questions
Is an app-level record enough for a client audit?
For most contracts, yes, when paired with the daily note and the artifacts. An auditor wants dates, hours, descriptions and evidence, and this record provides all four. What it cannot provide is screen content, and a contract that requires that will say so explicitly.
Can the client tell I am not running monitoring software?
If they asked for it and you did not install it, yes, and you should tell them rather than let them find out. If they asked for a record of hours, a record of hours is what they get, and how you kept it is your business.
What about time on a second Mac?
Punchcard’s license covers two Macs, and each keeps its own record. How to track time across two Macs explains how to combine them; in short, export both and add the days.
Does the record hold up if I have multiple clients in a day?
The receipt gives the day total; the daily line gives the split. A client sees “Tuesday: 4 hours, API work” and the total receipt is there if they ask why the day printed at nine. It holds up as long as the daily line is written the same day.