How to run a weekly production routine for a one-person local newsletter

By the end of this guide you will have a weekly production routine you can run in one sitting: sources pulled, stories built, the whole issue checked, and a finished draft pushed to your email platform. Before starting you need three things: a set of local sources you check each week, a publication with its voice set, and a connected email platform. The routine below assumes a weekly deadline, the cadence most local newsletters run on.

The short version

One person can run a weekly issue in phases: check the sources, pick this week's stories, build each section, review the whole issue, preview it, then push the draft. Most of the work is deciding what goes in, not writing from scratch. The phases hold whether you assemble the issue by hand or with software that pulls your sources for you.

The point of fixing the phases in advance is that deadline day stops being a series of improvisations. You open the same feed, fill the same sections, run the same check, and hand off the same way every week. When a week goes badly, the routine is what carries the issue out the door.

Before deadline day

A weekly routine starts before the day itself. Set your voice once, so every story comes back sounding like your publication rather than like a wire report. Connect your email platform once, so the handoff is a push and not an import. Then let your sources accumulate. If your software checks sources every morning, opening it on deadline day means the week's stories are already waiting, and nothing gets discovered at the last hour.

Your source list should cover the beats a local reader cares about: news from the city, schools, county and police, shelter pets, new restaurants and businesses, home listings, community calendars, and local job boards. You do not need every one in every issue. You need them checked every week so you can pick.

The deadline-day routine

Two phases deserve their own note. The story pick is where a one-person publisher spends the most judgment: you are choosing what your town talks about this week, and no tool makes that call for you. The review is where the routine protects you from yourself: it happens after the sections are done and before the preview, so it never gets skipped when the clock is short.

Where one-person publishers get stuck

The first sticking point is checking facts on deadline. A local issue carries a lot of small numbers: a price on a listing, a date on an event, a pay range on a job post. One wrong number and readers notice, and hand-checking every one is the part that gets rushed when the clock is running. A review on a real local issue opened 31 links and fact-checked 18 stories in 27 seconds, which is the scale of checking a full issue actually requires. Build the check into the routine as its own phase rather than a thing you do if there's time.

The second is the handoff to the email platform. Keep the boundary clean: the publishing software builds the issue, and your email platform sends it. Subscribers, delivery history and list health stay where they are, so the handoff is a draft push, not a migration project. There is no week where the routine includes exporting a list.

The third is drift. A routine only works if it holds on the bad weeks, so pick a fixed slot, the same day and hour every week, and treat the deadline as real. The team behind lightbreak built their tool around exactly this pressure: every feature had to earn its place on a Thursday morning at 7am, with two hours to deadline and a part-time contributor on the keyboard. That is the shape of a one-person operation's worst week, and the routine has to survive it.

The fourth is the empty week, when the feed looks thin. This is what the standing sections solve. Pet of the Week, a Featured Home and a restaurant worth visiting do not depend on the news cycle, so the issue has a floor even when the news feed is quiet. A reader who opens a thin issue still finds a picture of the town this week.

What the routine looks like on lightbreak

lightbreak is newsletter publishing software for local media, and it maps onto this routine phase by phase. It checks a publication's sources every morning, so opening the app means the week's stories are already waiting. Drop a story in and it comes back written in your voice, with The Gist and Why It Matters. A listing becomes a Featured Home with its own GIF, Pet of the Week and Restaurant Radar get GIFs made automatically from the listing's or place's photos, and the review agent reads the whole issue against every source it came from before you push the draft to Beehiiv or ActiveCampaign. Moving over costs nothing, and a person always decides when an issue sends.

Most publications on lightbreak ship an issue in under 15 minutes from source to send, against a manual workflow that usually takes 2 to 3 hours. The difference is not faster writing. It is that the pulling, the GIF-making and the checking stop being your hours.

The app lives at app.lightbreak.ai, and pricing depends on how many publications you run, quoted on a call. Every plan includes unlimited issues, every source feed, stories in your voice, automatic GIFs, the review agent, API and MCP access, and templates set up for you. MCP is a way for an AI assistant such as Claude or ChatGPT to use the same tools as the app: build an issue, write sections, make GIFs, run the review and push a draft, with a key created in Settings under AI agents and API.

Questions