The Dispatch
How to Run Five Blogs From One Desk (Without Losing Weekends)
Five blogs is a strange number. It is too many to run by mood — the way a single passion blog survives — and too few to justify hiring anyone. Most portfolios die exactly here, one quiet Tuesday at a time. After three years of running mine (and watching desk customers run theirs), the operators who make it share a system, not a talent. This is that system.
1. Put every property in a cadence tier
Not all blogs deserve the same week. The mistake is treating five properties as five equal obligations; the fix is tiers. Tier one is your earner — the site with traffic or revenue attached — and it publishes twice a week, no debate. Tier two properties publish weekly. Tier three, the experiments and long bets, publish twice a month and are not allowed to feel guilty about it.
The tier decides everything downstream: how many calendar slots the desk plans, how much editing attention a draft gets, and which property wins when a week goes sideways. When you are sick or traveling, tier three pauses first and nobody notices, because you decided that in advance instead of at 11 p.m.
2. Plan all five calendars in one sitting
Context-switching is the real cost of a portfolio. Opening one site's analytics, remembering its audience, deciding what it should say this week — that warm-up is expensive, and doing it five separate times multiplies it. So planning happens once, on Monday morning, for everything: review each property's proposed week, swap the weak pitches, and accept the lot. Twenty to thirty minutes, five calendars, done.
What makes this possible is that the proposals already respect each property's niche and archive. You are curating, not inventing. Curating five weeks is a coffee's worth of work; inventing five weeks is a lost evening.
3. Batch the edit queue into two desk days
Drafting is no longer the bottleneck — reviewing is, and review quality collapses when it happens in scraps between other work. The fix is two edit blocks a week: Tuesday and Thursday, ninety minutes each, queue open, everything else closed. Work newest-property-first so no site consistently gets your tired last hour.
Inside the block, be a real editor: approve what is good, kick back what is not with one specific note, and reschedule what the week does not need. The note matters — "tighten the intro, the comparison table should come before the verdict" produces a usable redraft; "make it better" produces a coin flip.
4. Let voices do the remembering
The portfolio failure nobody warns you about is bleed: after a while, your gear site's reviews and your cooking blog's essays start sharing a bloodstream, and both audiences can tell. Saved property voices fix this mechanically. The gear site's voice bans superlatives and requires a spec table; the cooking blog's voice writes in first person and opens with a story. You stop carrying five personas in your head, because the desk carries them.
5. Read one report, not five dashboards
Finally, kill the morning tab-parade. One circulation report should tell you what published, what is waiting on you, and which property slipped. Attention is the scarcest resource in a portfolio; the report's job is to point it. My rule: whichever property the report flags gets my first edit block of the week, and everything else runs on the system.
The honest summary
Five blogs from one desk is not about working faster. It is about deciding things once — tiers, calendars, edit blocks, voices — so the week runs on rails you already laid. The desk automates the drafting and the shipping; the system above is how you stay the publisher instead of becoming the bottleneck.
Ready to put your own properties on a schedule? Open a free desk or try the Writing Desk first.