SUNDAY SIGNAL

A field guide for independent newsletter creators

The Signal
System

Turn one week of noise into one useful issue readers save, share, and act on.

A repeatable 90-minute rhythm
01 Find it02 Shape it03 Ship it
Sunday Signal · Field Guide 0101 / 08

The promise

The newsletter problem isn’t ideas. It’s signal.

Your notes app is full. Your tabs multiply. The hard part is deciding what deserves your reader’s attention—and shaping it into something useful before the week gets away from you.

The system at a glance

Raw materialNotes, links, conversations
Your lensOne clear point of view
Reader valueOne useful next move
Choose faster

Score ideas against usefulness instead of chasing novelty.

Write cleaner

Use a familiar issue architecture so every paragraph has a job.

Learn weekly

Read replies, saves, and forwards as signals—not vanity scores.

The Signal System02 / 08
01

Find the signal

Choose the idea with tension.

A signal sits where something changed, something matters, and your reader can do something about it.

Specificity

Can you name the person, moment, behavior, or decision?

123
Stakes

What becomes easier, safer, clearer, or more possible?

123
Usefulness

Can the reader try, decide, save, or share something today?

123
You-ness

Does the idea carry your observation—not a recycled summary?

123
From the fictional Sunday notebook
“Three readers replied to the same sentence: the part where I admitted my weekly process was mostly recovery.”
Signal score · 10 / 12

Issue angle: The hidden cost of rebuilding your newsletter process every week.

Reader move: Adopt one repeatable 90-minute rhythm.

Step 01 · Find03 / 08

02 · Shape the issue

Give every paragraph a job.

A reliable issue shape creates room for personality. The reader knows where they are; you can spend your energy making the idea sharper.

Sunday Signal · Issue 244 min read

Stop rebuilding your newsletter every week

A 90-minute rhythm for moving from scattered notes to one useful send.

1Open with the tension

Name the moment your reader recognizes before offering advice.

2Make one claim

Say what you believe in a sentence that could be disagreed with.

3Show the proof

Use a scene, example, number, or artifact from real work.

4Hand over the tool

End with a checklist, prompt, template, or next move.

Step 02 · Shape04 / 08

03 · Ship on rhythm

The 90-minute newsletter studio.

Use one protected block. Make the decision once, move forward, and leave polishing time for the sentences readers will remember.

00–15

Choose

Score three candidate signals. Pick the strongest—no new research tabs.

Output
one promise
15–35

Outline

Write tension, claim, proof, and reader action as four blunt bullets.

Output
four beats
35–65

Draft

Write forward. Use brackets for missing details instead of breaking momentum.

Output
rough issue
65–80

Sharpen

Strengthen the opening, remove repeats, verify facts, and make the action obvious.

Output
clean draft
80–90

Package

Write three subject lines, check links, preview mobile, schedule the send.

Output
scheduled

Before you schedule

The opening names a real tension.
Every claim has a source or example.
There is one primary reader action.
Links and mobile preview are checked.

A useful issue sent beats a perfect issue stranded in drafts.

Protect the rhythm. Your reader’s trust compounds when the promise arrives on time.

Step 03 · Ship05 / 08

Tear-out worksheet

Build your next issue.

My signal

The observation, reply, moment, or source worth developing.

My point of view

The single sentence I want the reader to remember.

My proof

The scene, artifact, example, or number that earns trust.

Reader action

The smallest useful move they can make after reading.

Three subject lines, three different promises
1.
2.
3.
Workbook · Issue planner06 / 08

Close the loop

Measure resonance, not applause.

The best metric is the one that tells you what to make next. Read behavior as editorial feedback, then return to the notebook.

Replies

Signal: recognition. Readers saw themselves in the tension or want to add nuance.

Saves

Signal: utility. The issue contains a tool worth returning to when the moment arrives.

Forwards

Signal: identity. The idea helps readers say something about what they value.

Actions

Signal: momentum. Readers clicked, downloaded, registered, or tried the next move.

The ten-minute review

Do this before you start the next issue.

01Underline the sentence readers quoted back to you.
02Save the best reply as a future signal—not a testimonial.
03Write one line about what felt slow in the process.
04Choose one small change to test next week.

Open rate tells you who arrived. Resonance tells you what earned a place in their life.

The resonance loop07 / 08

Your next seven days

One useful signal.
One clear issue.
Every week.

MNotice

Capture reader questions and moments with tension.

TCollect

Add proof, links, examples, and your own observation.

WChoose

Score three signals. Commit to one promise.

TShape

Outline tension, claim, proof, and action.

FDraft

Use the 90-minute studio and schedule.

SListen

Read replies and collect resonance signals.

SReset

Review the process and clear the runway.

Make the rhythm visible.

Put this page beside your desk. The goal is not to fill every day with newsletter work—it is to give each day one clear job so the issue never has to begin from zero.

Choose next send date
Block the 90-minute studio
Capture the first signal
Tell one reader what’s coming
SUNDAY SIGNAL
One useful idea for independent creators, every Sunday.
Fictional demonstration content created by EZdoc.
No real creator’s writing is reproduced.
The Signal System · Field Guide 0108 / 08