A practical newsletter production workflow for online newspapers

A newsletter is not merely a second list of stories from the website. It is a publication in which readers encounter the newsroom's priorities at a predictable time. On a website, people arrive through many routes. In an inbox, they often decide whether to continue from a subject line and the first screen. Selection, ordering, copy, links, and delivery therefore need their own workflow.

Small newsrooms often hold that workflow in one person's memory. A changed URL can then be missed at deadline, a test send can be skipped, and publication can stop when that person is away. Defining inputs, approval criteria, and checks makes consistent delivery possible with a small team. This guide describes a practical process for producing a weekly or other recurring editorial newsletter.

Define the reader promise before choosing stories

Write one sentence that identifies the audience, frequency, and value. For example: “Every Friday, we help local business owners understand the week's policy and community developments in five minutes.” This sentence becomes an editorial test for both inclusion and exclusion.

Avoid promising to include everything published on the site. The homepage and archive already serve that purpose. A newsletter is better suited to selecting developments readers should not miss, adding context to useful reporting, and directing readers toward a relevant next step. A breaking brief, weekly curation, and specialist industry update should each have a distinct promise.

Choose a cadence the newsroom can sustain. A reliable weekly edition generally builds more trust than a daily message that frequently disappears. Put drafting deadlines, delivery times, and holiday rules on the editorial calendar, and name at least one backup producer.

Give every edition a stable editorial structure

A recurring framework removes the need to begin with a blank page. An edition might contain a short editor's note, one lead story, three key stories, a short-items section, a reader action, and subscription information. The exact number matters less than having a clear purpose for each section.

The first screen should communicate the value of the edition. If a large logo and long greeting occupy all available space, readers cannot reach the lead story quickly. Put the principal headline and a concise explanation near the top, and move routine notices lower. Confirm that the same priority survives on a phone.

Keep the template as simple as the content permits. Decorative images and complex columns can behave differently across mail applications. Headlines, summaries, and links must remain understandable when images do not load. Keep section names and button language reasonably consistent between editions.

Collect candidates before the production deadline

Building the candidate list by scanning the site at the last minute creates omissions and bias. Ask the desk or reporting team to flag newsletter candidates when stories are published. A shared document or board only needs the story URL, headline, one-sentence value, intended audience, and publication status.

Instead of labeling a candidate merely “good,” identify the job it would perform. Is it the week's most consequential change, immediately useful information, or context that connects continuing coverage? When three similar stories compete, feature the most complete one and place the others in a related-links group.

Record anything likely to change after the candidate deadline. The producer should know when a headline or URL is provisional or a story is scheduled but not yet public. Also note access conditions and expiration dates for member-only reports, registrations, or events.

Use selection criteria the team can explain

Ordering stories only by page views repeatedly rewards coverage that is already popular. Consider public significance, timeliness, relevance to the promised audience, additional context, and variety. A numerical score is optional, but the team should be able to explain why a story leads the edition.

Check whether one institution, person, or story format dominates the issue without a clear editorial reason. Do not mechanically fill one slot from every desk. Seek a useful range of perspectives and formats within the newsletter's purpose, without inserting weak work merely for symmetry.

Sequence creates a reading path. A lead report may be followed by an explainer, while a concise service item can provide a change of pace after a demanding story. Read only the first sentence of each section and ask whether the progression of the edition is still visible.

Write the subject line and preheader together

The email subject is not simply a field for the lead article's headline. It should state the central value of the edition without promising information that is absent or manufacturing urgency. Rather than joining many topics with commas, choose one representative topic and only the supporting context needed to understand it.

The preheader is the short text commonly shown beside or below the subject in an inbox. It should extend the subject, perhaps with the second story or the scope of the edition, instead of repeating it. Configure it deliberately so the first sentence or unsubscribe notice is not pulled in automatically.

Draft two or three subject options and preview how they appear when space is limited. Put meaningful words early enough to survive truncation. Use emoji, brackets, and capitalization sparingly according to the publication's style, and favor a durable description over a phrase designed only to provoke a click.

Make each summary earn its link

Do not paste the opening paragraph of an article into the newsletter by default. Write for the inbox reader: what happened, why it matters now, and what the linked story adds. Keep the summary to a few sentences and do not introduce a conclusion, number, or characterization unsupported by the reporting.

A page full of summaries ending with “learn more” becomes indistinct. Lead with concrete actors and actions. At the same time, do not conceal the essential fact to force a click; readers should receive a useful account even if they do not leave the email.

Link labels should explain the destination. “Review the eligibility rules” or “Read the field interview” is more useful than repeating “more.” Confirm that headline and button links point to the same intended page, and check that a post-publication headline change has not made the newsletter wording contradictory.

Keep subscription status separate from editorial production

Manage subscription state inside the delivery system rather than having editors download and combine personal address files. Keep signup source, newsletter choice, and opt-out state distinct. Do not automatically add addresses collected for another purpose. Review consent wording and retention practices against the publication's own policy and the requirements that apply to its service.

Create a process for handling undeliverable addresses and repeated bounces. Every edition should provide a readily discoverable way to change an address or stop receiving the message. Prefer the delivery platform's standard unsubscribe handling to a manual process that can lose requests.

Segment only when it creates a meaningful content difference. Dividing lists by location or interest without producing different editorial choices increases operational risk. When an edition varies by audience, record the segment conditions, exclusions, and expected recipient count before sending.

Test in the environments readers actually use

Once the draft is assembled, send a test to someone other than its writer. Start with the sender name, reply address, subject, and preheader, then open every link. A message that looks correct in a web preview can still contain a different button URL or added tracking parameters in the delivered copy.

Check text size, spacing, image proportions, and button separation on both a phone and desktop. Disable images and confirm that headlines and summaries still communicate the issue. Give informative images useful alternative text. In a representative dark-mode view, make sure the logo does not vanish and text retains readable contrast.

Publication status and timing matter as much as layout. A message must not arrive before its linked article becomes public or after a registration deadline has passed. If final copy changes just before scheduling, repeat a compact version of the full test rather than checking only the edited paragraph.

Separate preparation, review, and send authority

Even a small team can distinguish writing, checking, and final delivery. One person prepares the copy, another reviews facts and links, and an authorized producer confirms the scheduled send. When one person must fill every role, use a checklist after a short break rather than proofreading immediately after writing.

The approval record can be brief: final subject, scheduled time, target list, reviewer, and test status. Its purpose is not to create a long meeting note but to identify exactly which version was approved. Schedule with enough buffer to cancel when a late problem is found.

Define who decides how breaking news changes a regular edition. The team may replace the lead, add a short note, postpone, or send a separate alert. Even in urgent circumstances, do not skip recipient selection, publication-state checks, or link testing.

Review hypotheses, not isolated numbers

Immediately after delivery, first confirm that the message was accepted, links resolve, and reader reports are monitored. If an error appears, identify the affected audience and available correction route. Fix the web story promptly; for an incorrect email link, determine whether a redirect or correction notice is appropriate.

Open and click measurements can be limited by mail software and privacy settings. Do not declare a subject or story successful from one number alone. Record changes in timing, topic, and placement that might also explain the result. Replies, unsubscribes, and reporting tips may carry more editorial meaning than a single aggregate rate.

Use the review to choose one adjustment for the next edition: shorten the lead summary, remove a low-value section, or move the candidate deadline earlier. Changing many elements at once makes it difficult to learn what mattered.

Maintain a reusable production checklist

Divide the checklist by stage. Planning covers audience, central topic, candidate deadline, and owner. Editing covers publication status, factual agreement between story and summary, topic duplication, and descriptive link text. Delivery covers recipient list, sender, subject, preheader, test results, and scheduled time.

Do not stop at completion boxes. For common problems, name the person or role that receives the escalation. A changed article URL may go to site operations; an audience-state problem may go to subscription support. This makes deadline decisions faster. Review the checklist periodically, removing obsolete steps and adding safeguards for recurring errors.

To begin today, write the next edition's reader promise in one sentence, define its recurring sections, and create a candidate intake row. Finish the draft a day before delivery, test it in two real mail environments, and have a second person open every link. After sending, record one improvement for the following edition. This small loop turns newsletter production from individual habit into a sustainable newsroom publishing process.