Hi Reader,
A Forbes headline this week said the quiet part out loud.
AI can write the CEO's message. It can't tell them not to send it.
That's the gap nobody budgets for. Drafting got cheap. A memo that used to take a week of back and forth now takes ten minutes. So more messages get written, faster, with fewer people reading them before they ship.
The draft was never the hard part. The hard part was the person in the room who said, "Wait. Not today." Or "Not to them." Or "Not at all."
That person is still you. But you can give them a sparring partner.
This week's prompt doesn't help you write the message. It helps you decide whether it should exist.
ππ½ Here's the prompt:
π― Expert Mode: The "Send Gate"
Scenario: Your CEO has a message ready to go. A memo, a LinkedIn post, a statement. It reads well. Before it ships, run it through a gate that asks what a good chief of staff would ask: should this go, to whom, and when?
Instructions:
1οΈβ£ Grab the draft exactly as it stands. Don't polish it first. You're judging the decision, not the prose.
2οΈβ£ Write three lines of context: who it's going to, what's happening in the business right now, and anything sensitive in the background (earnings, layoffs, litigation, a news cycle you're already in).
3οΈβ£ Paste both into Claude or ChatGPT with the prompt below. (Use your company's approved AI account. Unreleased exec messages are exactly the kind of thing you don't want in a personal chat history.)
Act as a chief of staff and senior communications counsel with veto power. Your job is not to improve this message. Your job is to decide whether it should be sent at all.
β
Context: [paste your three lines]
β
Draft: [paste the draft]
β
Give me a verdict first: Send, Send with changes, Hold, or Kill.
Then answer five questions, one or two sentences each:
β
Timing: Is anything happening now, or in the next two weeks, that makes this land differently than the author intends?
β
Audience: Who will read this besides the intended audience, and how does it read to them? Think employees, investors, reporters, regulators, and anyone it mentions.
β
Gap: Where does this promise something the business can't back up, or contradict something we've said before?
β
Screenshot: Which single sentence would look worst as a screenshot with no context?
β
Silence: What happens if we don't send it at all? Is that better or worse?
β
Finish with a short list of what would have to change for your verdict to move to Send.
β
Do not rewrite the draft. Do not soften the verdict to be polite.
4οΈβ£ Read the verdict before the reasoning. If it says Hold or Kill, ask yourself honestly whether you already knew.
5οΈβ£ Take the "what would have to change" list to the exec. Present it as options, not objections. "Here's how we get this to Send" is a much easier meeting than "I don't think we should."
Suggested Tool: Claude (it holds context well and is more willing to push back than to polish)
Why You'll Love It
- It separates "is this well written" from "should this go out," two questions AI tools love to blur together.
- It gives you language to push back on an executive without sounding like you're blocking them.
- It catches the second audience: the employee, reporter or investor who wasn't on the distribution list but will see it anyway.
AI made drafting fast. Judgment is still the bottleneck, and that's good news for anyone whose job is judgment. Run the gate before the next one goes out.
Talk soon,
Chris
β‘ The Cowork Version
Same gate, except Claude checks every pending draft against your calendar and your own past statements, then files a verdict memo for each one.
Setup (one time):
- Create a folder called
Send Gate with an Inbox subfolder. Drop any draft that needs a decision in there (.docx, .md or .txt all work).
- Add a
Context.md file to Send Gate listing the dates that matter in the next 30 days: earnings, launches, board meetings, anything sensitive in flight.
- Add a
Past Statements subfolder with your last 90 days of press releases, exec posts and public statements.
- Optional: connect your calendar so Claude can check timing against what's actually scheduled, not just what's in the context file.
Run this Cowork command:
Review every draft in the Send Gate/Inbox folder. For each one, act as a chief of staff and senior communications counsel with veto power. Do not rewrite the drafts. Your job is to decide whether each one should be sent.
β
1οΈβ£ Read Context.md, every file in Past Statements, and my calendar for the next 30 days before you read any draft.
β
2οΈβ£ For each draft, give a verdict: Send, Send with changes, Hold, or Kill.
β
3οΈβ£ Test each draft on five points: timing against the calendar and context file, every audience who will see it beyond the intended one, any gap or contradiction with our past statements (quote the earlier statement exactly), the single sentence that would look worst as a screenshot, and what happens if we stay silent.
β
4οΈβ£ For any draft that isn't a clean Send, list exactly what would have to change to get it there.
β
5οΈβ£ Save one verdict memo per draft in Send Gate/Verdicts, named [draft name] - Verdict.md.
β
6οΈβ£ Save a Send Gate Summary.md in Send Gate that ranks every draft by risk, with the verdict and the one-line reason, so I can brief an executive in two minutes.
What you'll get:
- A verdict on every pending draft, not just the one you remembered to check
- Contradictions with your own past statements, quoted side by side
- The worst-screenshot sentence flagged in each draft
- A risk-ranked summary you can walk an executive through in two minutes
- A dated record showing each message was reviewed before it went out
Want it on autopilot? Ask Claude to schedule this every weekday at 7am. Anything dropped in the Inbox overnight has a verdict waiting before your first meeting.
Here are a few articles from the past week to help keep you up to speed:
1.AI Can Write The CEO's Message, But It Can't Tell Them Not To Send Itβ
Forbes Communications Council
September 30, 2026Hi Reader,
A Forbes headline this week said the quiet part out loud.
AI can write the CEO's message. It can't tell them not to send it.
That's the gap nobody budgets for. Drafting got cheap. A memo that used to take a week of back and forth now takes ten minutes. So more messages get written, faster, with fewer people reading them before they ship.
The draft was never the hard part. The hard part was the person in the room who said, "Wait. Not today." Or "Not to them." Or "Not at all."
That person is still you. But you can give them a sparring partner.
This week's prompt doesn't help you write the message. It helps you decide whether it should exist.
ππ½ Here's the prompt:
π― Expert Mode: The "Send Gate"
Scenario: Your CEO has a message ready to go. A memo, a LinkedIn post, a statement. It reads well. Before it ships, run it through a gate that asks what a good chief of staff would ask: should this go, to whom, and when?
Instructions:
1οΈβ£ Grab the draft exactly as it stands. Don't polish it first. You're judging the decision, not the prose.
2οΈβ£ Write three lines of context: who it's going to, what's happening in the business right now, and anything sensitive in the background (earnings, layoffs, litigation, a news cycle you're already in).
3οΈβ£ Paste both into Claude or ChatGPT with the prompt below. (Use your company's approved AI account. Unreleased exec messages are exactly the kind of thing you don't want in a personal chat history.)
Act as a chief of staff and senior communications counsel with veto power. Your job is not to improve this message. Your job is to decide whether it should be sent at all.
β
Context: [paste your three lines]
β
Draft: [paste the draft]
β
Give me a verdict first: Send, Send with changes, Hold, or Kill.
β
Then answer five questions, one or two sentences each:
β
1. Timing: Is anything happening now, or in the next two weeks, that makes this land differently than the author intends?
2. Audience: Who will read this besides the intended audience, and how does it read to them? Think employees, investors, reporters, regulators, and anyone it mentions.
3. Gap: Where does this promise something the business can't back up, or contradict something we've said before?
4. Screenshot: Which single sentence would look worst as a screenshot with no context?
5. Silence: What happens if we don't send it at all? Is that better or worse?
β
Finish with a short list of what would have to change for your verdict to move to Send.
β
Do not rewrite the draft. Do not soften the verdict to be polite.
4οΈβ£ Read the verdict before the reasoning. If it says Hold or Kill, ask yourself honestly whether you already knew.
5οΈβ£ Take the "what would have to change" list to the exec. Present it as options, not objections. "Here's how we get this to Send" is a much easier meeting than "I don't think we should."
Suggested Tool: Claude (it holds context well and is more willing to push back than to polish)
Why You'll Love It
- It separates "is this well written" from "should this go out," two questions AI tools love to blur together.
- It gives you language to push back on an executive without sounding like you're blocking them.
- It catches the second audience: the employee, reporter or investor who wasn't on the distribution list but will see it anyway.
AI made drafting fast. Judgment is still the bottleneck, and that's good news for anyone whose job is judgment. Run the gate before the next one goes out.
Talk soon,
Chris
β‘ The Cowork Version
Same gate, except Claude checks every pending draft against your calendar and your own past statements, then files a verdict memo for each one.
Setup (one time):
- Create a folder called
Send Gate with an Inbox subfolder. Drop any draft that needs a decision in there (.docx, .md or .txt all work).
- Add a
Context.md file to Send Gate listing the dates that matter in the next 30 days: earnings, launches, board meetings, anything sensitive in flight.
- Add a
Past Statements subfolder with your last 90 days of press releases, exec posts and public statements.
- Optional: connect your calendar so Claude can check timing against what's actually scheduled, not just what's in the context file.
Run this Cowork command:
Review every draft in the Send Gate/Inbox folder. For each one, act as a chief of staff and senior communications counsel with veto power. Do not rewrite the drafts. Your job is to decide whether each one should be sent.
β
1οΈβ£ Read Context.md, every file in Past Statements, and my calendar for the next 30 days before you read any draft.
β
2οΈβ£ For each draft, give a verdict: Send, Send with changes, Hold, or Kill.
β
3οΈβ£ Test each draft on five points: timing against the calendar and context file, every audience who will see it beyond the intended one, any gap or contradiction with our past statements (quote the earlier statement exactly), the single sentence that would look worst as a screenshot, and what happens if we stay silent.
β
4οΈβ£ For any draft that isn't a clean Send, list exactly what would have to change to get it there.
β
5οΈβ£ Save one verdict memo per draft in Send Gate/Verdicts, named [draft name] - Verdict.md.
β
6οΈβ£ Save a Send Gate Summary.md in Send Gate that ranks every draft by risk, with the verdict and the one-line reason, so I can brief an executive in two minutes.
What you'll get:
- A verdict on every pending draft, not just the one you remembered to check
- Contradictions with your own past statements, quoted side by side
- The worst-screenshot sentence flagged in each draft
- A risk-ranked summary you can walk an executive through in two minutes
- A dated record showing each message was reviewed before it went out
Want it on autopilot? Ask Claude to schedule this every weekday at 7am. Anything dropped in the Inbox overnight has a verdict waiting before your first meeting.
Here are a few articles from the past week to help keep you up to speed:
1. AI Can Write The CEO's Message, But It Can't Tell Them Not To Send Itβ
Forbes Communications Council
September 30, 2026
Michele Caselnova looks at how large language models are drafting more and more executive communications, and why none of them have the judgment to stop a message that shouldn't go out. It's the story behind this week's prompt. The faster your drafts get, the more your value shifts to the call on whether to send them.
2. AI and Data Science in Communications: From Reactive to Predictive PRβ
O'Dwyer's
September 30, 2026
Tom Coombes, founder and CEO of Cognito, argues that narratives now take shape in niche forums and social networks well before they reach mainstream media, and that AI makes it possible to catch them early. The stat worth clipping: only 37% of organizations know where negative sentiment about their brand is concentrated. If you can't say where it lives, you can't get ahead of it.
3. PR Newswire Launches AEO & GEO Report for AI Brand Visibility in APAC Regionβ
PR Newswire
September 28, 2026
PR Newswire is building a report into its Amplify platform that tracks how often large language models mention your brand, which sources shape their answers, and what those answers actually say. It runs on Trajaan, the AI search intelligence platform Cision recently acquired. When the biggest wire service bakes AI visibility into the distribution product, it stops being a side project for your team.
4. How publishers are rethinking audience engagement: Five takeaways from the Future of Media Technology Conferenceβ
Nieman Lab
September 30, 2026
Publishers are moving away from chasing clicks and toward habits, newsletters and in-house on-camera talent at outlets like The Economist and The Guardian. They also admit AI search optimization is still guesswork, and they want AI platforms paying for original reporting. If you pitch these outlets, their shift is your shift: a story built for a newsletter or a journalist's on-camera franchise travels further than one built for search.
5. Two 23-year-olds used AI to create a daily audio briefing. It's now the top news app in Argentina.β
Nieman Lab
October 1, 2026
Lisa AI turns dozens of Argentine news outlets into a personalized 10-minute audio briefing, and within weeks of its August launch it was the top news app on Argentina's App Store, with 80% of users coming back daily. That's happening in a country where trust in news has fallen to 26%. More of your coverage is going to reach people through an AI summary of the story, so the first line of the story matters more than ever.
β