Build a newsletter from confirmed updates, not a list of ideas. This template keeps source links and unapproved claims visible until the editor signs off.
Prepare the source before you fill it
Approved update: reporting workshop agenda. Source: agenda page. Owner: product lead. CTA: registration link.
How to use this template
Gather approved updates
Add only current facts, owners and source links.
Draft by reader job
Give every section one reason to exist for the reader.
Check claims and destinations
Confirm facts, URLs, permission and unsubscribe requirements before send.
Copy the template
# Newsletter issue
## Issue record
- Audience:
- Send date:
- Editor:
- Approval owner:
## Approved updates
| Reader need | Update | Source link | Owner | Claim check |
| --- | --- | --- | --- | --- |
| | | | | Not reviewed |
## Draft sections
### Section 1
- Reader question:
- Confirmed answer:
- Approved CTA:
- Required asset and permission:
## Open items
| Missing fact or approval | Owner | Send blocker |
| --- | --- | --- |
| | Not assigned | Yes |
## Send check
- Claims checked against sources:
- Links tested:
- Audience and consent checked:
- Approval recorded:Filled example
Reader question: What is in the reporting workshop? Confirmed answer: the approved agenda lists its sessions. Source: agenda page captured by the product owner. CTA: tested registration link. Asset: approved workshop image. Open item: final date confirmation. Owner: product lead. Send blocker: yes until the date is confirmed. The editor records the approval before the campaign enters scheduling.One workshop section with agenda source, approved CTA and an editor check before send.
Review before you share it
- Each factual statement has a source
- Every CTA has a working destination
- Unapproved claims remain outside the draft
- Audience consent is checked before send
What the template cannot establish
- The template does not establish consent
- A draft does not confirm deliverability or legal compliance