How long a newsletter issue really takes to write each week

25 September 2026 · 7 min read

It depends on the kind of newsletter, but not in the way most estimates assume. A curated issue is mostly reading, an essay issue is mostly drafting, and both carry a fixed production cost (formatting, images, links, a test send) that is easy to forget. The figure worth trusting is your own, measured across four issues and split into those parts, because that is what tells you whether your schedule can last.

Where newsletter time actually goes

Four kinds of work go into an issue, and they happen in different places at different times.

Reading and collecting. Articles, notes, links saved for later, replies from readers. For a curated newsletter this is most of the job, and it happens all week in short sessions, which is why it rarely gets counted.
Drafting. Writing the issue itself, usually in one or two sittings, in a writing app or in the sending platform’s editor.
Production. Pasting the draft into the platform, fixing the formatting, finding or making images, checking every link, sending a test to yourself, fixing what the test revealed.
After sending. Reading replies, answering them, and checking the numbers. Checking the numbers can quietly become a daily visit that adds up.

An estimate made from memory tends to count the drafting and little else. The other three parts are where the gap between the estimate and the real week comes from.

How to measure four issues

Why four: the first issue you measure tends to be unusual, because you are paying attention to it. By the fourth, the numbers settle into what a normal week looks like.

Punchcard does the recording. It sits in the menu bar, notices which app is in front through the day (app names only, never document names, URLs or window titles), and at the closing time you set it prints a receipt: each app with its time, and a day total.

Draft in one place. If you write the newsletter in a writing app you use for nothing else, its line on the receipt is your drafting time, clean. If the same app holds your other writing, the line mixes both.
Give production its own line. Sending platforms live in the browser, so production time disappears into the browser line with everything else. One practical trick: use a second browser only for the newsletter platform. Punchcard lists apps by name, so that browser gets its own line.
Note reading sessions. Reading scattered through the week is the hardest part to separate. A one-line note per day (“about forty minutes of newsletter reading”) is enough.
Tag send day. On the day an issue goes out, write down the week’s drafting line, production line and your reading estimate.
Repeat for four issues. The Sunday week roll gives you the week total alongside, so you can see the newsletter as a share of your whole week.

For a weekly newsletter, that is four weeks. For one that goes out every other week, eight. How long a podcast episode takes to edit uses the same approach for audio, if you publish both.

Reading the result

Add the three parts for each issue, then take the typical figure across the four. Three questions are worth asking.

Is production larger than you expected? If formatting and fixing take as long as writing, a fixed template with your usual sections, a standard image size and a checklist for the test send will pay for themselves within a few issues.

Is reading open-ended? A curated newsletter can absorb any amount of reading. If that estimate is growing, cap the sources you check, or give reading a fixed session each day and stop when it ends.

Is after-send checking a daily habit? If your newsletter browser shows up on every receipt of the week, not just on send day, choose one day to look at the numbers and leave it at that.

Then compare the typical figure with the guess you would have given before measuring. The size of that gap is useful on its own: it tells you how much to trust your other estimates for the newsletter, such as how long a special issue or a redesign will take.

Set a schedule you can keep

Now compare the typical issue with the time you actually have. If you write the newsletter around a job, the question is how many evening and weekend hours it takes, and whether you are willing to give it those hours every week for a year.

If it fits, keep the schedule and protect the drafting session: same day, same time, every issue.
If it does not fit, change the format before the frequency. A shorter essay, fewer links, or one fewer fixed section can take real time out of every issue.
If it still does not fit, go to every other week. A newsletter that arrives reliably every two weeks serves readers better than a weekly one that keeps skipping.
Keep a buffer issue. Write one issue ahead when you can. It turns a busy week into a non-event.

How to track time for a side project without it feeling like a job has more on keeping the measuring light enough that it does not become another chore.

What the receipt misses

Punchcard records the app in front on this Mac. Reading on your phone, thinking on a walk and notes written by hand do not appear. It has no projects or tags, so it cannot tell newsletter drafting from other writing in the same app; that is why the separate-app habits above help. And it cannot see what you wrote: it never records window titles, document names, URLs or keystrokes, and it contains no networking code at all.

It also has no timers, reminders or deadlines. It will not tell you when to write; it tells you, once a day, how long you did.

Questions

Is there a typical time per issue? Not one that means much. Issues range from a paragraph and five links to a long essay with research behind it. Your own four-issue figure is the only one worth planning around. Time tracking for writers explains why hours tell you more than word counts.

Should reading time count? If you would not have done the reading without the newsletter, yes. For a curated issue it is the core of the work, and leaving it out is how a newsletter comes to feel far heavier than its estimate.

What does it cost? Tracking never expires and the first seven receipts are free. Measuring four weekly issues needs the $9 license, paid once and good for two Macs.