The weekly schedule for running three newsletters at once

Sunday night arrives, and the operator who added a second or third town realizes each property needs a fresh issue. There is still one person coordinating the work, three sets of local details to verify, and three audiences expecting their newsletter on time. A single weekly production calendar with batched workdays solves the coordination problem by giving every issue the same visible path from planning to publication while protecting the reporting that must stay local.

What the shared calendar does

The calendar is one working view of all three properties. Each issue needs a send day, a named owner, a drafting deadline, a local-reporting deadline and a final-check deadline. Staggering those send days lets the same person finish one issue while the others are still being reported or assembled.

Batching means grouping similar tasks into one work block. An operator can gather links and reports for all three newsletters on Monday, draft repeatable sections in another block, and reserve separate sessions for local reporting and editing. This reduces the repeated setup that comes from treating every issue as a completely independent project.

The calendar also exposes collisions early. If two final checks land in the same hour, or all three properties need local interviews on the same afternoon, the operator can move work before a send is at risk. Its main result is a smaller number of production decisions during the week.

Decide what stays local and what can be shared

Use one test: does the item depend on town-specific reporting to be accurate or useful? If it does, it stays local. That includes the reporting itself, interviews, local context, the consequences for readers and the final editorial check. A shared draft can supply structure, but a person responsible for that property must verify the local version.

Work can be shared when the same verified material serves each audience without changing its meaning. Production checklists, section structures, research routines and repeatable drafting work belong in this category. Shared treatment should remove duplicated effort, then leave enough time for each property's local lead and supporting details.

• Keep local Town-specific reporting, source calls, reader impact, context, corrections and final approval.
• Share deliberately Research collection, production templates, repeatable sections, checklists and material verified for every market.
• Reuse with verification Start from common reporting where it applies, then confirm the facts and reader relevance separately for each property.

Reusing reporting is different from sending identical issues. Gather common material once, record what has been verified, and give each property its own local editing block. When the answer to the local-versus-shared test is unclear, give the item local treatment and share only the underlying production work.

Who this schedule fits

This approach fits a solo operator or small team running two or three properties with a repeatable weekly cadence. It is especially useful when the same people handle research, drafting, assembly and final checks across the newsletters. One owner should still be responsible for each issue's local accuracy and release.

It is a poor fit when every property depends on continuous breaking coverage, or when nobody has authority to make the final local decision. It also cannot solve a reporting-capacity shortage. Batching organizes the available hours; three newsletters still require three issues worth of local judgment.

A three-newsletter week you can adapt

The schedule below is a template, with the three properties labeled A, B and C. Tuesday, Wednesday and Thursday are staggered send days so final production never stacks up on one morning. Move the days to fit your markets, but preserve the order: plan together, gather together, finish locally and review the whole system.

Keep local reporting blocks close enough to each send that details can still be checked. Use the shared drafting blocks for work that survives until publication without fresh reporting. If a draft depends on an unconfirmed local detail, mark that dependency on the calendar rather than hiding it inside a general drafting task.

Collection can have its own fixed workflow. One publisher interviewed on the Local Media HQ Podcast described using an RSS-to-Slack-to-ChatGPT setup to sort incoming links and reports while producing two newsletters around other work commitments. RSS, short for Really Simple Syndication, is a feed that collects new items from websites. The transferable idea is to gather and sort material in a batch, then reserve human time for verification and writing.

Start with one week and measure the pressure points

Put next week's three issues on the calendar before changing anything else. Assign every issue one owner, stagger the sends, and label each task as shared, local or shared with local verification. Then run the week as written and record where work had to be rescued outside its assigned block.

At Friday's reset, distinguish coordination problems from capacity problems. Duplicated gathering, unclear ownership and overlapping final checks call for calendar changes. Repeatedly unfinished local reporting calls for fewer commitments, more reporting time or additional help. The calendar gives the operator a concrete record for making that decision.