Reader survey results roundup
Summarize top themes from the Q3 subscriber survey for a future issue.
Plan, write, and ship your newsletter on a Kanban Template built for editors
The Newsletter Board Kanban template gives content teams a repeatable workflow for planning a recurring newsletter, from raw idea capture through drafting, review, and send day. Instead of scattering ideas across docs and chat threads, every issue moves through five clear columns on a kanban board so editors always know what's next. Use the MCP server or REST API to create tasks straight from your idea-capture tool, then track progress with columns, keyboard shortcuts, and the command palette to move fast without leaving the keyboard. Whether you're a solo writer or a small marketing team, this template keeps every issue accountable from first pitch to final send.
Template preview
Capture raw newsletter ideas, reader suggestions, and topic pitches before they're scheduled into an issue.
Reader survey results roundup
Summarize top themes from the Q3 subscriber survey for a future issue.
Interview with guest contributor
Pitch: short Q&A with a customer about their onboarding experience.
Product launch teaser angle
Draft angle connecting the upcoming feature release to reader pain points.
Ideas assigned to a specific send date and issue number, ready to move into drafting.
Issue #42 - Fall product roadmap
Scheduled for Oct 3 send; owner assigned, outline due Friday.
Issue #43 - Customer spotlight
Scheduled for Oct 10 send; sourcing quotes from support team.
Issue #44 - Year-end recap teaser
Scheduled for Oct 17 send; needs data pull from analytics.
Active writing and content assembly for the current issue, including subject lines and copy blocks.
Write subject line variants
Draft 3 subject line options for A/B testing on Issue #42.
Assemble body copy sections
Combine intro, feature highlight, and CTA blocks into the draft template.
Source header image
Pick or design a header graphic matching the issue theme.
Editorial and stakeholder review, proofreading, and link checking before the issue is approved.
Editor proofread pass
Check grammar, tone, and brand voice consistency for Issue #42.
Verify all links and UTMs
Click-test every link and confirm UTM parameters are correct.
Legal/compliance sign-off
Get approval on any claims or pricing mentions before send.
Issues that have been sent, archived here with send date for future reference and performance tracking.
Issue #41 - September highlights
Sent Sept 26; log open and click rates once available.
Issue #40 - Back to school edition
Sent Sept 19; archived with final copy and performance notes.
Step 1
Capture every newsletter idea in Idea Backlog as soon as it comes up, tagging the source (reader feedback, team pitch, product update).
Step 2
During planning, move approved ideas into Scheduled and assign an issue number and send date.
Step 3
Move the issue to Drafting once writing begins, breaking the task into subject line, body copy, and image sourcing subtasks.
Step 4
Shift the issue to Review for proofreading, link checks, and any required sign-off before it's approved to send.
Step 5
After the send goes out, move the task to Sent and log performance notes for future reference.
AI agent usage
This playbook lets an AI agent manage a recurring newsletter pipeline end-to-end using the MCP server: capturing ideas, scheduling issues, tracking drafts through review, and archiving sent issues, all by reading and moving tasks across the board's five columns via create_task, move_task, and update_task calls.
## Newsletter Board Agent Instructions
This project uses columns: Idea Backlog, Scheduled, Drafting, Review, Sent.
- New topic pitches go into Idea Backlog via create_task.
- When an issue is assigned a send date, move_task it to Scheduled and update the title with the issue number.
- When writing starts, move_task to Drafting.
- Once proofreading is requested, move_task to Review.
- After the newsletter is sent, move_task to Sent and append performance notes via update_task.
Always use list_tasks to check current board state before creating duplicate tasks.Learn more about the board-centric workflow in Kanban for AI Agents or open the MCP guide.
The free plan supports 1 project with up to 25 tasks total, which is enough for several months of newsletter issues if you archive older Sent tasks periodically.
Yes, the board works for any size team; upgrading to Pro ($12/mo or $96/yr) removes the task cap if your newsletter pipeline grows beyond 25 active tasks.
Yes, use the MCP server or REST API to programmatically create_task entries in Idea Backlog whenever a new pitch comes in from another tool.
You can leave them in the Sent column for reference or use delete_task to clean up older entries if you're approaching the 25-task limit on the free plan.
Yes, you can navigate columns and tasks using keyboard shortcuts and the command palette without needing the mouse, which speeds up daily triage.
Yes, the macOS app supports the same kanban board, columns, and tasks as the web version so you can manage your newsletter pipeline natively.
Ready to create this board?
Sign in and use the template to create a project with columns and sample tasks.