A manager's week: how much time is left for your own work

24 September 2026 · 7 min read

Most managers who measure their week find that their own work gets whatever is left after meetings, reviews and chat, and that the leftovers arrive in pieces too short to use. To see the real figure, record a normal week by app, total the coordination apps (calendar, calls, mail, chat) and the tools of your own craft separately, and read both on Sunday. Then protect one realistic block, not a heroic one, and check the following week whether it survived.

Why a manager’s own work disappears

An individual contributor’s week has meetings in it. A manager’s week is made of them, plus everything around them: preparing for a one-to-one, writing up the decision afterward, reading the document someone wants feedback on by Thursday, answering the question in chat that unblocks two people. All of that is the job. None of it is the work you are still expected to produce yourself: the plan, the budget, the hiring case, the code or design you still own, the strategy document due at the end of the quarter.

The trouble is not that craft work gets no time. It gets the gaps, and the gaps between meetings are twenty or forty minutes long. Your own work usually needs longer than that to get going, so the gaps fill with the next easiest thing, which is usually more chat.

That is why the calendar is a poor guide. It shows the meetings and leaves everything else looking free. The white space on a manager’s calendar is rarely free; it is where the reviews, the messages and the follow-ups live.

Sorting the week into three piles

Decide which apps belong where before you record anything. Deciding afterward lets you nudge the answer toward the one you wanted.

1. Coordination. Calendar, your video calling app (FaceTime or whatever your company uses), Mail, and the team chat app. Time in the Calendar app itself deserves a mention: it is scheduling, not meeting, and managers who move a lot of meetings around often find a surprisingly long Calendar line.
2. Craft. The tools of your own work. For an engineering manager, perhaps the code editor and Terminal. For a design lead, the design tool. For a finance or operations lead, Numbers or another spreadsheet app. For almost every manager, a word processor or Keynote for the documents only you can write.
3. Everything else. The browser, Finder, Preview, the HR system.

Reviews are the awkward case. Reading someone’s draft in the word processor looks exactly like writing your own draft in the word processor. An app-level record cannot tell them apart, and nothing short of reading your screen could. Accept that and note review-heavy days by hand; “Thu: two performance reviews, all afternoon” is enough.

The general version of this measurement (calling app against making apps, one week, a guess written down first) is in Meetings versus making. What follows is the manager-specific part: what the numbers mean when coordination is the job, and how to get some craft time back.

Reading the week roll

Punchcard prints a receipt at the closing time you set, one line per app with its time and a day total, and on Sunday a week roll that totals the seven days. It notices which app is in front, by name only, so there is nothing to start or stop between meetings. On Sunday, with the roll and the daily receipts in front of you:

1. Add up the coordination lines. Calendar, calling app, Mail, chat. Write the total down.
2. Add up the craft lines. Write that down too.
3. Compare the craft total with the craft work you owe. If this quarter’s plan needs something like ten hours of writing and the week produced three hours in the word processor, the plan will be written at night or not at all. This comparison matters more than any ratio.
4. Look at the craft line on each daily receipt. Three hours spread as thirty-six minutes a day is a very different week from one three-hour morning. The first rarely finishes anything.
5. Find the biggest coordination line. If it is chat rather than calls, meetings are not your main problem, and cutting them will not give you the time back.

Step four is where managers usually learn the most. The weekly total is often less bad than feared; the daily shape is often worse.

One caveat matters more for managers than most people. Calls taken in a browser tab land in the browser line, and calls taken on a phone or in a room with the laptop shut appear nowhere. If much of your week is spent in rooms, the receipt shows only the Mac part of it.

What a realistic protected block looks like

The standard advice is to block whole mornings for deep work. For a manager it tends to fail by the second week, because a manager who is unreachable every morning is not doing the job. A block you can keep beats a block you cannot, and a keepable one tends to look like this:

• Ninety minutes, not four hours. Long enough to get past the warm-up, short enough that nobody is blocked for long.
• Two or three a week, not five. Put them on the days your meetings already thin out. The daily receipts show which days those are.
• At an edge of the day. The first ninety minutes, before the team’s questions have piled up, or the last hour, once the meetings have run out. The middle of the day belongs to other people’s schedules.
• With a named output. “Draft section two of the plan”, not “strategy time”. A block with no named output gets given away to the first person who asks, because nothing visible is lost.
• With notifications held. A Focus mode, set up in System Settings under Focus, that holds mail and chat notifications for the block does more than a closed door, because most interruptions now arrive on screen.

Then check it. On block days, the craft line on that day’s receipt should come to at least roughly the length of the block. If the block was on the calendar and the craft line reads twenty minutes, the block was eaten, and the rest of the receipt usually says by what.

Do not expect the number to rise every week. A manager’s craft time is squeezed by things you do not control: hiring, a reorganization, a launch. The aim is a floor you defend, not a figure you keep growing.

A personal record, not a team one

Punchcard is built for one person looking at their own day. It has no team features, no view of other people and no way to collect anyone’s receipts, and it should not be used to see what your reports are doing. Asking a team to run a tracker and send you the output turns a tool for self-knowledge into monitoring, whatever the intention, and it changes how people work in ways that make the numbers meaningless anyway. If you want to know where your team’s week goes, ask them, and share your own receipt first if that makes the conversation easier. What employee monitoring software sees sets out the difference.

It also cannot sort apps into piles for you. There are no tags, projects or categories; you do the sorting by reading the lines, which on a week roll takes about a minute. It records app names only, never window titles, meeting names, document names or URLs, and it asks for no macOS permissions. On a work laptop that is the point: it knows less about your day than your calendar does.

Questions

How much craft time should a manager have?

There is no standard figure. It depends on how much individual work the role still carries. The useful comparison is against your own commitments, not other managers: if you owe ten hours of writing and the roll shows three, that gap is the finding.

Should one-to-ones count as coordination?

For this measurement, yes. They are among the most valuable meetings a manager has, but they are not your own craft work, and counting them as craft hides the squeeze you are trying to see.

My reviews happen in the same app as my own writing. Can the receipt separate them?

No. It sees the app, not the document. Keep a one-line note on review-heavy days, or read drafts as PDFs in Preview so reviewing gets a line of its own.