Month in review: what a month roll shows you
· 6 min read
A monthly work review answers three questions that no single day can: how many days you actually worked, how long a typical day was, and which apps took the month. The way to do it without a spreadsheet is a month roll: one printed summary at the end of the month, built from every day’s record, that you read once for ten minutes and then act on. This post covers what to look for on it, how to run the review, and what the roll cannot tell you.
Why the month is the right unit for some questions
Daily receipts are good at “where did today go”. Weekly rolls are good at “was this a normal week”. Some questions only show up at a month.
Drift is one. A day that runs thirty minutes long is noise. A month where the typical day runs thirty minutes longer than last month is a trend, and you will not see it in any single receipt.
Days worked is another. Most people believe they work about twenty-two days a month. The month roll counts them, and the count includes the Saturday you “just checked in” and the public holiday you opened the laptop on. Counting the days: what a month of receipts teaches you is about that number alone.
Share is the third. Whether the editor or the chat app took more of your month is not visible day to day, because some days are all one and some days all the other. Over a month the split settles, and it is often not what you would have guessed.
What to look for on a month roll
A month roll has the same shape as a daily receipt: lines, a total, a stamp. Read it for these five things, in this order.
Days on the roll. How many days printed. Compare with the number of working days in the month. A gap means days off, or days you forgot to open the Mac, or days the tracker missed; a surplus means weekends that became workdays.
Total hours. The number at the bottom. Divide it by the days on the roll and you have the length of the typical day. That is the number to watch month over month. If it creeps up and you did not decide it should, you have found something.
The top line. Which app had the most time. For most desk work this should be the app you think of as “where I work”. If it is the browser or the chat app, the month is telling you what the days could not.
The top three lines as a share of the total. Add them. If the top three are eighty percent of the month, your work is concentrated. If they are half, the month was fragmented, and the real cost of switching apps all day explains why that matters more than the raw hours.
The longest day. Not for pride. A month with one fourteen-hour day is a month where something went wrong once; a month with five of them is a pattern.
How to run a month in review
This takes about ten minutes. Do it on the first working day of the new month, before the new month has a shape.
- Get the month roll in front of you. In Punchcard, it prints automatically at month end and sits under Past receipts; if you keep daily receipts by hand, lay out the month’s worth and add the totals.
- Write down the five numbers above: days, total, typical day, top app, longest day. One line each.
- Put them next to last month’s five. If this is your first month, put them next to what you would have guessed, and be honest about the guess.
- Circle the one number that moved the most, or surprised you the most. Only one.
- Decide one change for the coming month that addresses that number. Not a list of resolutions; one change you can check on the next roll.
- Write the change on the back of the roll, or in the same note as the numbers, so that next month’s review starts by checking whether it happened.
That last step is what makes the review stick. A review with no follow-up check is a reading exercise. How to tell if a productivity change actually worked is the long version of step six.
Where the month roll comes from
Punchcard prints three kinds of paper: a daily receipt at your closing time, a week roll on Sunday, and a month roll at the end of the month. All three are built from the same record, a single SQLite file on your Mac, and all three show app names only, never window titles, documents or URLs. The month roll needs no setup; if the app was running during the month, the roll prints.
If you want more than the roll shows, the CSV export in Settings (“Export my data”) gives you every day with every app and its time, which opens in Numbers or any spreadsheet. That is the route for questions the roll does not answer directly, like “how did Tuesdays compare with Thursdays” or “what was the first hour of each day”. For most people the roll is enough and the spreadsheet is a once-a-year curiosity.
What the roll cannot give you: a per-project or per-client split (there are no projects), billable totals (there are no rates), or any record of days the Mac was closed. It is a record of which apps were in front on this Mac, summed by month. It is a better record than memory by a wide margin, and a worse one than a timesheet you actually filled in, which nobody does.
Turning the review into one change
The reviews that work produce one sentence. Some examples of the kind of sentence that comes out of a month roll:
- “Twenty-four days on the roll in a month with twenty-one working days. Three weekend days. Next month: the Mac stays shut on Saturdays.”
- “Typical day up from 7h 50m to 8h 35m with no change in output. Next month: a closing time, set in the app, and stick to it.” How to set a closing time for your workday and keep it is the method.
- “Chat app is the top line for the second month running. Next month: chat closed until 11 am.”
Each of those is checkable on the next roll. That is the whole test of a good monthly change: could the next month’s paper prove you did it.
What a month roll cannot tell you
It cannot tell you whether the month was good. A high total can be a month of great work or a month of treading water, and the roll cannot see the difference. Pair it with one line about what shipped.
It cannot see time away from the Mac. Meetings in a room, reading on paper, thinking on a walk: none of it is on the roll, and if a large share of your work is like that, the roll is a floor rather than a total.
And it cannot tell you what to change. It can only make the pattern visible enough that you stop being able to ignore it, which in practice is most of the job.
Questions
How is a month roll different from the Sunday week roll?
Same format, different question. The week roll tells you whether the week was normal; the month roll tells you what normal has become. The Sunday roll: a weekly review you will not skip covers the weekly one.
I missed some days. Is the roll still useful?
Yes, as long as you know which days are missing. A month roll with eighteen days on it in a month you worked twenty-two is a record of eighteen days, and the typical-day number is still right for those. The days-worked count is the one number that becomes unreliable.
Can I get the month roll as a spreadsheet instead?
Not as a roll, but the CSV export contains everything the roll is built from, by day and by app. The roll is the summary; the CSV is the source.