Calendars, Batching and Rest Days
The schedule that wins is the one still running next year. Here's how to build it without grinding yourself down.
The weekly scramble
Here's the pattern we see most: nothing planned on Monday, a panic on Thursday, a rushed upload on Friday night, and a weekend spent recovering. Each week starts from zero, so every decision — topic, title, thumbnail — gets made under pressure. That pressure is where the hours go.
A rhythm replaces decisions with defaults. You already know what Tuesday is for. You already know which piece goes out next. The energy goes into the work, not into deciding what the work is.
Choose a cadence you could keep through a bad month
Pick your publishing frequency by asking a blunt question: could I keep this up during a cold, a family visit and a deadline at my other job? If the honest answer is no, halve it. Weekly is fine. Fortnightly is fine. Monthly with real depth is fine. Audiences adapt to a predictable rhythm far better than to bursts and silences.
Write the cadence down as a sentence and stick it near your desk: "One long video every second Thursday, two short clips in between."
Batch by setup, not by piece
Every setup has a start-up cost: lights on, mic positioned, camera framed, scenes loaded. Batching means paying that cost once and recording two or three pieces in a row. Do the same for writing — draft several scripts in one session — and for packaging, designing a month of thumbnails from your master file in one sitting.
A simple batch week for a fortnightly video creator might look like this:
- Monday: shape two outlines
- Tuesday: record both
- Wednesday and Thursday: edit one each day
- Friday: package both and schedule them
- Following week: lighter admin, ideas, rest
Keep a buffer
A buffer is finished work waiting to publish. Two pieces is enough to absorb most disruptions. Build it slowly: during one batch week, make one extra piece. Once the buffer exists, a missed week becomes a non-event rather than a crisis.
Plan on one calendar
Use whichever calendar you already open daily. Google Calendar works for time-blocking; Trello boards or a Notion database work for tracking each piece through the pipeline stations. Don't run both for the same job. The planning tool should take minutes a week, not an afternoon.
Focus blocks and rest days
Francesco Cirillo's Pomodoro Technique — 25 minutes of focused work, then a short break — is a gentle way into editing sessions that otherwise sprawl. Cal Newport's Deep Work argues for longer protected blocks for demanding tasks; editing and scripting fit that description. Try a 90-minute block in the morning with notifications off.
Then schedule rest. Put at least one no-production day on the calendar each week, and a lighter week every couple of months. Austin Kleon's Show Your Work! reminds creators that a long body of work is built from small, regular contributions — which only happens if you're still around to make them.
Cadence options compared
| Cadence | Batch rhythm | Buffer target | Suits |
|---|---|---|---|
| Weekly | Record 2 every fortnight | 2 pieces | Podcasts, short tutorials |
| Fortnightly | Record 2 every month | 1–2 pieces | Longer video, essays |
| Monthly | One production week per month | 1 piece | Deep research, documentaries |