Plan a publisher newsletter around a clear reader promise

Start with the sentence a reader could repeat

Before anyone designs a form, an editor should be able to finish one sentence: this newsletter helps a named reader know or do something they would otherwise miss. A local news digest might help residents follow the decisions that change their services. A specialist magazine might help practitioners find the few stories worth reading in a crowded week. “Stay up to date” does not finish the sentence, and a signup page that cannot finish it is inviting people to join an unspecified list.

Test the sentence on someone who does not work on the publication. If they cannot describe what a typical edition would contain, the promise is still too vague to support a signup page, a welcome message or a calendar. Rewrite it until a stranger can predict, roughly, what will arrive in the inbox.

Turn the sentence into a brief two people can use

A one-sentence promise becomes operational when it is written as a short brief. Keep it where both the editor and the person who maintains the signup page can see it, because the two must change together. If the product changes, the form, the welcome message and the calendar have to change with it.

The rhythm line deserves particular honesty. A publication that promises a weekly edition but sends irregularly risks drifting away from what readers were told, and that gap is awkward to explain later. A looser promise that the team can keep is easier to defend than an ambitious one it cannot.

• Reader: who the edition is for, described by what they need to decide or understand rather than by demographics.
• Promise: the one sentence above, in the words the signup page will use.
• Coverage boundary: the area and subjects included, and the subjects deliberately left to other products.
• Rhythm: how often readers should expect an edition, stated only if the team can sustain it.
• Typical edition: the usual sections and what a reader will find in them.
• Responsibility: the editor who approves each issue and the operator who checks destinations before sending.
• Review: where corrections, access problems and reader questions are recorded before the next issue is chosen.

Choose items by role, not by quota

A quota forces weak material into an issue because a slot has to be filled. Roles describe what an item does for the reader instead. An edition might lead with one important development, add a practical explainer and close with something the reader can use. A quieter week can have fewer items and still meet the brief, because the brief is about usefulness rather than volume.

For each candidate item, write down the underlying source, the question the reader would bring to it, the reason it belongs in this edition rather than the next, and the page it will link to. That record is useful when a link changes or a reader challenges a summary. The editorial-calendar guide turns these fields into a planning sheet, and the issue-layout guide is the place to look next for structuring the issue itself.

A filled selection record for one item

The record below is a filled example for a fictional digest, Harbour Notes. Harbour Notes, the council, the service and every detail are invented to show the shape of a working record; nothing here describes a real publication, decision or result. In the same fictional issue, a service-change explainer and a community-facility guide would each get a record of their own. Replace each line with your own material and keep the record beside the draft so the operator can check it before sending.

• Item: a council decision to change how a local service operates (fictional).
• Source: the council’s own published decision record for the meeting, plus the service’s notice page. The editor reads the decision record itself rather than relying on a second-hand summary, and notes the date it was opened.
• Reader question: Does this change when or how I can use the service, and is there anything I need to do?
• Role in the edition: lead, the one important development of this issue.
• Why now: the decision has just been published and affects residents who use the service.
• Destination: the specific decision record page, not the council homepage. The operator opens it from the finished email before sending.
• Limit to carry into the summary: if the record describes a change as proposed, or leaves the start date to a later notice, the summary says exactly that and does not state a date it cannot support.
• Editorial decision: include as the lead, with a summary of a few sentences, a link to the decision record and a pointer to the service notice for practical details. The editor approves the wording; the operator confirms the link.
• What would change the decision: if the record cannot be found or contradicts the notice, hold the item, or run it as a short note that official confirmation is awaited and name where the information came from.

Keep a commercial label separate from an ordinary source credit

Two different things are easy to run together. A commercial label tells the reader about a relationship: someone paid, supplied goods or services, or has an arrangement with the publication that the reader may want to weigh. A source credit tells the reader where information or an opinion came from. Quoting a report, linking to a council record or crediting a commentator is attribution. It does not turn the item into an advertisement, and treating it as one would blur a useful distinction.

In the fictional issue, the restaurant offer is the item that raises the question of a commercial label. Its record would read: source, the restaurant; reader question, none that the brief promises to answer; role, not an editorial item; decision, decline, or run as a labelled commercial placement considered separately. The edition is complete either way.

The sample lines below show the difference. They are illustrations, not templates that any law or platform rule requires. This guide does not state legal or regulatory obligations, so check the rules that apply to your own situation.

• Source credit, no commercial relationship: “Source: the council’s published decision record.” The reader learns where the summary came from and can follow the link.
• Source credit with an author: “Comment from a local historian, quoted from their published article.” The reader learns who is speaking; nothing is implied about payment.
• Commercial label: “Paid placement from a local restaurant.” The reader learns about the relationship before deciding what to make of the offer. Adapt the wording to say plainly who wrote the text.
• Unclear case: an organisation supplies free material that the editor then uses. The editor decides whether the arrangement is commercial; when unsure, state the relationship in plain words rather than saying nothing. The sponsorship guide is the place to work through such cases.

Make the signup page describe the same product

The signup page, the confirmation message and the first edition should describe one product. A recovered configuration associated with Port City Daily pointed to its own email-updates page, and another associated with Tygodnik Przegląd pointed to a newsletter confirmation page. These observations illustrate recurring-publication journeys; they do not show the wording or performance of any historical newsletter.

For a new publication, name the publisher and the purpose of the signup in plain words. Distinguish a submitted request from any further confirmation step your platform uses. Mailchimp’s help page on double opt-in, listed in this guide’s bibliography, is one example of a platform with such a step, though platform behaviour should be re-checked against current documentation. The confirmation-page guide explains how to make those states readable.

Run a short check before an edition leaves

Selection is only half the job. Before sending, a second reader, or the same person after a break, can work through a short list.

• Every link opens the page the surrounding sentence describes, not a homepage or an error.
• Each summary says no more than its destination supports, and any important limit in the source is carried into the summary.
• Each outside source or author is credited by name or link, as in the selection record.
• Any commercial relationship, such as payment, supplied goods or an arrangement the reader may want to weigh, is labelled in plain words next to the item and kept distinct from source credits.
• The reply route in the footer is read by a named person.
• The sender name and publication name match what the signup page promised.
• A named editor has approved the final text, not an earlier draft.

Review the product, not only the most-clicked story

After the send, ask whether the edition did what the brief promised. Was it complete? Did its links reach the intended pages? Could readers reply through the advertised route? Did anything need correcting? A large click count on one story cannot answer those questions alone.

Keep a short issue log recording what changed from the plan and why, and read it alongside click analysis and reader feedback. Make the next issue’s changes specific enough to evaluate. Mailchimp’s click-tracking help page is listed in this guide’s bibliography; consult it directly for what that service reports. Resist settling on an ideal newsletter length from a few editions. Base the length on the edition’s promise and the material worth including, with a selection process the editor can explain.