Verified against ChatGPT · 2026-08-08
Draft a recurring newsletter issue that doesn't pad out a thin week with filler
Turns a messy list of this week's updates into a structured newsletter issue with a real lead story, honest section-skipping when there's nothing worth saying, and a subject line that matches what's actually inside.
The prompt
Ready to copy — highlighted parts are example details you can swap.
You are drafting this week's issue of a recurring newsletter I send on a fixed schedule, using the raw updates I give you below rather than inventing content to fill out the usual sections. NEWSLETTER PURPOSE AND AUDIENCE Weekly product update for our 4,200 beta users — they read it to decide whether to log back in this week. RAW UPDATES FOR THIS ISSUE - shipped bulk export (been requested since March) - fixed the timezone bug in scheduling - nothing new on mobile app, still in review with Apple - support response time crept up to 14hrs, working on it RECURRING SECTION STRUCTURE Lead story, Shipped this week, Known issues, One thing we're working on, Community shoutout. VOICE TO MATCH "Bulk export shipped. You asked, we built it, here's how to use it in under a minute." RULES FOR THIS ISSUE Read the raw updates first and decide which one is genuinely the lead story based on what would matter most to the audience described above, not just whichever item I listed first. If a recurring section in the structure has nothing worth including this week, say so explicitly and cut it rather than stretching a minor update to fill the space or inventing a generic tip to plug the gap — an issue with four sections and one real story reads better than five padded ones. Write in the voice sample's actual sentence rhythm and vocabulary, not a generic newsletter voice — if the sample is short and clipped, do not write in long marketing sentences. Every section needs one specific, concrete detail (a number, a name, a date) pulled from the raw updates; if a raw update is vague, flag it back to me as needing a specific detail rather than writing around the vagueness with confident-sounding filler. Write three subject line options that each describe what's actually inside this specific issue, not a generic teaser that would fit any issue you could send. WHAT NOT TO DO Do not add a closing inspirational line, a generic "stay tuned" sign-off, or a recap of what past issues covered unless the voice sample shows that's normally part of the format. Do not soften or hedge any specific number or claim from the raw updates. OUTPUT FORMAT 1. Three subject line options. 2. The full issue body in the recurring section structure, with any cut section named and the one-line reason it was cut. 3. A list of any raw update that was too vague to state as a concrete detail, with the specific question I'd need to answer to fix it.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
GPT-5.1 defaults to filling every named slot in a structure you give it, because a recurring template reads as an implicit demand for completeness — without an explicit instruction to cut a section, it will manufacture plausible-sounding content for "Community shoutout" or "One thing we're working on" even when your raw updates contain nothing for that slot, which is exactly how newsletters drift into feeling padded and interchangeable week over week. Naming the lead-story decision as a judgment call based on audience relevance, rather than defaulting to list order, matters because the model otherwise treats the first bullet you typed as the most important one by position alone, which is an accident of how you happened to jot notes down, not a reflection of what the audience cares about. Requiring one concrete detail per section closes GPT-5.1's tendency to smooth a vague input into confident, general-sounding prose — when a raw update is thin, the model's fluency will paper over that thinness with generic phrasing unless it's told that flagging the gap back to you is the correct move, not writing around it. The voice-sample matching works because without a concrete style anchor, GPT-5.1 reverts to a mid-register, slightly promotional newsletter voice that is recognizable across thousands of AI-drafted newsletters; pointing it at your own actual sentence rhythm forces it to pattern-match against your specific cadence instead of its own default. Finally, tying subject lines to what's actually inside this issue rather than a generic teaser formula prevents the common failure where the subject line could be reused verbatim on any week's issue, which is a sign it was generated from the newsletter's category rather than its content.
What you get back
Subject line options: "Bulk export is live (you asked in March)" / "This week: exports, a timezone fix, and a support update" / "Shipped: the export feature you've been waiting on". Lead story: Bulk export ships... Cut section: Community shoutout — no submissions came in this week, cutting rather than reusing an old one.
Verified against
ChatGPT GPT-5.1 · 2026-08-08
Changelog
- 2026-08-08 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — Google Ads management, built and maintained for you — that's Scult's day job.
EXPLORE GOOGLE ADS MANAGEMENT
