Newsletter Standards

Shared publicly as a case study from the Polaris Pixels AI Playbook (polarispixels.com/ai-playbook). Use it as a model for your own documents, not a template to copy.

Document type: Binding standard
Version: 2.0
Last updated: September 29, 2026
Supersedes: newsletter-standards-v1.md (September 12, 2026)

Grissinger for Commissioner. Written for anyone (human or AI) drafting a newsletter issue. Built from analysis of the first fourteen issues, March through September 2026.

What this is

One weekly email to the campaign's subscriber list, published simultaneously as a blog post at ryangrissinger.com/blog. There is one list. Everyone on it is a supporter or an interested resident who opted in, not a persuadable stranger. Write to the supporter.

Because it publishes publicly, assume opponents, reporters, and the county read every issue. Nothing internal, nothing strategic, nothing from VAN, no turf details, no donor names or amounts.

Register. Because the audience is supporters, this is one of the places where the full case belongs: Ryan's yes vote on all four levies and his endorsement of the Democratic ticket (see candidate-briefing-context-v4.md). Because it also publishes publicly, write nothing you would not say at a forum.

The job of each issue

Three things, in this order of importance:

1. Get one specific action out of the reader this week.
2. Give the reader something worth forwarding to a neighbor.
3. Show that Ryan is already doing the work of the job.

If an issue does not do all three, it is not finished.

Cadence and length

Send Tuesday. Every Tuesday. Consistency matters more than the perfect send time.

Length: through Monday, October 5, 400 to 600 words. From Tuesday, October 6 (early voting) through Election Day, 300 to 450 words and more urgent.

Hero image: one real photo from the past week. A photo of the actual thing (signs in the garage, volunteers at a table, a meeting room) beats a graphic every time.

The section spine

Use these headers, in this order, every issue. Skip a section if there is genuinely nothing for it. Do not rename them, do not reorder them, do not invent topic-based headers. The repeating spine is what lets a reader who opens twenty of these jump straight to the part they care about.

Opening line. One or two sentences. Orient the reader and name the single most time-sensitive thing. Examples that worked: "Three things need you between now and September 1. Start with tonight." and "Quick one this week, and there is one thing I need from you at the bottom."

What I Did. Two to four short paragraphs on the past week. Meetings, events, doors, county business. Name real people and real places. This is the "show the work" section and it is the reason anyone believes the rest.

From the County. Required in every issue. 100 to 150 words on one thing happening in county government: a vote, a project, a number, a meeting Ryan attended. Explain what it means in plain language. Be honest about what is and is not a county decision. This is the most forwardable part of the newsletter and the only part that makes an argument for the candidacy. Logistics do not get forwarded. This does.

What's Coming. Dated list of public events. Day, date, event, place, time. Link to ryangrissinger.com/calendar at the end. Keep it to the next ten days plus anything major beyond that.

What I Need. The primary ask. See the ask rules below.

Bottom Line. Two or three sentences connecting the week back to growth. Then the countdown line, then the tagline, then the signature.

The one-ask rule

One primary ask per issue. State it in What I Need, and put it in the subject line whenever possible.

Every other ask drops to a single sentence with one link, placed lower. Four asks with equal weight produces zero actions. The September 2 issue carried four asks plus three events, and the only hard deadline in it (October 2 postcards) sat third.

Choose the primary ask by what the campaign actually needs that week, not by what is easiest to write.

How to write an ask

Copy this pattern. It is the best writing in the archive:

• Name the task in plain words.
• Say exactly how it works, step by step.
• Say how long it takes.
• Say what the reader does NOT have to do.
• Give one link or one phone number.

Model: "I hand you a bundle of 30. You write them out by hand, then either give them back to me or drop them in the mail. A bundle takes about 45 minutes. No script to memorize, no doors to knock, no phone calls. Forty five minutes at your kitchen table."

Never write an ask as a description of campaign activity. "We're organizing targeted canvassing in the precincts where these conversations matter most" is not an ask. "Email me and I will hand you a list of 40 doors and the literature to carry" is an ask.

Canonical links

One action, one link, every time. Mixed links create friction and break tracking.

Use the campaign's tracked short links for the primary ask so the issue's performance is measurable.

Direct contact, when the ask needs a human: ryan@ryangrissinger.com or text 614-203-9405.

The weekly meeting

The campaign holds a standing weekly meeting [day, time, and location redacted]. In each issue, state that week's specific date, and say plainly if it has moved or will move. A wrong time costs more trust than an inconsistent one.

Subject lines

Concrete and specific. A number, a place, or a thing that happened.

Good: "6,000 postcards out the door. And 15,000 more on the way." / "7 townships, 2 EMS/Fire stations, and a sheriff's office" / "Canvassing has started. I need you at a door."

Never use "Campaign update" as a subject line. Never use a generic three-noun subject ("New materials, new momentum, new asks").

If the primary ask can carry the subject line, let it.

Voice

First person, always. Ryan writes this and signs it. Never refer to Ryan in third person ("Ryan will be there," "text Ryan"). Write "I will be there," "text me."

Conversational, direct, like a neighbor who did his homework. Short paragraphs, two to four sentences. Vary sentence length. 8th grade reading level.

Section 1 of script-voice-constitution-v2.md applies to every issue: the banned devices, no em dashes, and the master banned-vocabulary list. The approved and retired campaign language in candidate-briefing-context-v4.md applies too.

Thank people by name: the volunteers who opened their home for an event, the ones who helped set it up. Naming volunteers is both a thank-you and a recruiting tool.

Be honest about limits. "This one is a state decision, not a county decision, but it will reshape traffic and land use here for the next fifty years" is the most credible sentence the campaign has published. Never claim authority the office does not have.

Closing block

Every issue ends with these four elements, in order:

1. Bottom Line paragraph tying the week to growth.
2. Countdown: "X days until Election Day." Until October 6, add: "Y until early voting opens on October 6." From October 6 on, say early voting is open now.
3. "Plan the growth. Protect what matters."
4. "Ryan"

Add a P.S. forward ask when the issue has a strong From the County item: "Forward this to a neighbor who lives near that route."

Include the disclaimer at the bottom of the email: Paid for by Friends of Ryan Grissinger (D) for Delaware County Commissioner.

Fundraising

Every issue carries a donate line, even a short one, low in the piece. Tie the ask to a specific expense when possible: postcards, printing, mail. "Every dollar goes to X" beats a bare link. Never mention the Ohio $50 political contribution tax credit; it does not apply to this race.

Data integrity

Every county number must be verified as Delaware County, OHIO before it goes in. Multiple Delaware Counties exist and aggregator sites cross-contaminate. Never cite jail capacity or jail population figures, and never cite specific opioid settlement dollar amounts. See Section 0 of briefing-book-v4.md for the full rules, the retired claims registry, the retired framings, and the domain allowlist.

Attribute county figures to their source when the number is doing real work in the argument.

Pre-send checklist

• One primary ask, stated first in What I Need, and in the subject line if possible.
• The ask names the steps, the time it takes, and what the reader does not have to do.
• One canonical link per action, tracked link on the primary ask.
• A From the County item is present and would make sense to someone who has never volunteered.
• First person throughout. No third-person references to Ryan.
• Section 1 of the voice constitution: zero violations, no em dashes, no banned words.
• Every date includes day of week, date, time, and place.
• Every county number verified as Ohio, and checked against both retired lists in the briefing book.
• Countdown, tagline, signature, disclaimer.
• Word count in range for the date.
• One real photo from this week.

Template

Subject: [concrete, specific, ideally the ask]

[Opening line. Most time-sensitive item.]

## What I Did
[2 to 4 short paragraphs. People and places by name.]

## From the County
[100 to 150 words. One county thing, explained plainly. What it means and who decides it.]

## What's Coming
[Day, date, event, place, time.]
Full calendar: ryangrissinger.com/calendar

## What I Need
[The one ask. Steps, time, what they do not have to do, one link.]

[Secondary asks, one line each with one link.]

[Donate line.]

## Bottom Line
[2 to 3 sentences tying the week to growth.]

X days until Election Day. [Y until early voting opens on October 6. / Early voting is open now.]

Plan the growth. Protect what matters.

Ryan

P.S. [Forward ask, when there is something worth forwarding.]

Paid for by Friends of Ryan Grissinger (D) for Delaware County Commissioner