You are the person who gives everyone else in the company a voice. You ghostwrite for the CEO, edit the CHRO's all-hands script, draft the crisis holding statement, turn the VP of Product's four bullet points into a narrative announcement, and manage the internal newsletter. You own the company's written tone from board presentations to Slack announcements. The bottleneck is never the ideas — you know what needs to be said. It's the volume. The all-hands is Thursday, the acquisition announcement is Tuesday, the CEO email about the layoffs went out wrong last time and you cannot repeat that, and there are five different VPs who all need communication support this week.
This is the distinct function that owns the company narrative, executive communications, employee-facing broadcasts, crisis and issues comms, town halls, and the CEO's written voice — not marketing campaign work, not content marketing and SEO briefs, and not OCM and change management. Corp comms and internal comms is the function where a single poorly-worded all-hands message triggers a hundred panicked Slack threads, and a good crisis holding statement bought by the right 30 minutes saves a news cycle. Claude doesn't make the decisions. It solves the blank page.
Before the use cases, the hard disclaimer that matters here: Claude cannot access Staffbase, Simpplr, Poppulo, Firstup, Microsoft Viva Engage, Yammer, Slack, Teams, your intranet, or your CMS. It cannot access your media monitoring tools — Meltwater, Cision, Mention — or your press release distribution platforms — PR Newswire, Business Wire, Globe Newswire. It has no access to internal employee data, org charts, listening platform data, or any company system. It cannot send communications, publish to any channel, or research breaking news about your company. Claude is strictly a drafting tool. You bring the facts, the organizational context, the leadership direction, and the judgment about what can and cannot be said. Claude handles structure, tone calibration, and speed.
That boundary matters more in this function than almost anywhere else. An executive message that misrepresents a financial figure is a legal and reputational problem. A crisis statement that speculates about cause before legal has reviewed it is worse. A newsletter that publishes uncleared information from a business unit creates internal controversy. The caveat isn't boilerplate — it's the operating constraint that makes Claude usable in a function where the stakes of every word are unusually high. It is reinforced at every use case below.
What Claude Can Do for Corporate and Internal Comms Professionals
1. CEO / Executive Message or Announcement Narrative
The CEO needs to send an all-company email about a strategic shift, acquisition, restructuring, or major milestone. What you have is four bullet points and a 15-minute verbal brief. What you need is a polished 400-word email that sounds like the executive, lands with employees, and doesn't create a firestorm in the comments. This is the use case that probably takes up the most of your week, and it's the one where the blank page is most reliably painful.
Claude cannot access your internal communications platforms, executive inboxes, or any company data. Paste in the executive's talking points, your notes from the briefing, and any context you have. Claude builds the draft; you and the executive shape it into something that actually sounds like them.
I need to draft an all-company email from [executive name/title] about [topic].
Context: [paste executive brief, talking points, or raw notes from your verbal briefing]
Audience: [all employees / specific function / leadership layer]
Tone: [confident and clear / empathetic and direct / celebratory but grounded]
Length target: [approximately X words]
The message should open with [the reason this matters to employees / the decision itself / acknowledgment of what employees may be feeling].
Please draft the full email, flag any section where I need to supply additional context, and note where the executive's voice may need adjustment based on what you know about their usual communication style (which I'll provide if relevant). Do not fabricate company data, team sizes, or financial figures — use [NEEDS DATA] flags where I haven't provided specifics.
Output you get: Three subject line options. Full email body with clear paragraph structure: opening → context → what's changing → what's not changing → what employees should do next → closing. A shorter Slack/intranet version (3–4 sentences). A note on tone tradeoffs.
The "what's not changing" section is explicitly called out in the output — the same reason it matters in change management work. It is the first thing employees look for when something is shifting, and most executive communications skip it or bury it. The omission is what generates the panicked Slack threads. Ask Claude to make it explicit and it will.
2. All-Hands / Town Hall Script and Run-of-Show
Quarterly or annual all-hands. The exec team has slides. Nobody has a script. You have 48 hours. The CEO ad-libs well in small rooms and struggles in front of 2,000 people on a livestream. The CFO's segment is always five minutes longer than planned. The head of engineering has never used a teleprompter. The run-of-show exists as a spreadsheet cell nobody has opened.
Claude cannot access your presentation decks, calendar systems, or any internal planning tools. Give it the agenda, the speaker list, the business context, and the tone you're after. Claude produces the structure; you get executive approvals on the pieces that matter.
I'm building the script and run-of-show for a [quarterly / annual] all-hands on [date].
Format: [live in-person / virtual / hybrid]
Duration: [X minutes]
Speakers: [list names/titles and their segments]
Key themes: [paste themes or agenda topics]
Business context: [what's been happening this quarter — wins, misses, key announcements]
Audience: [all employees / specific region / specific business unit]
Tone: [energizing and direct / steady and honest / celebratory but grounded]
Please produce:
(1) A full run-of-show table (Segment / Speaker / Time / Key Messages / Handoff Notes)
(2) A speaker intro for each presenter
(3) A scripted opening from the most senior leader that sets the tone
(4) A scripted close that lands on a clear takeaway and call to action
Flag any segment where I need to supply missing data with [NEEDS CONTENT]. Do not invent business results, headcount, or financials.
Output you get: Run-of-show table. Speaker intros. Scripted opening. Scripted close. A one-paragraph facilitator briefing note.
The scripted opening is the hardest part to delegate — it sets the emotional register for the entire event. Get the executive's verbal approval on that section before you run with the full draft. Everything else can iterate; the opening landing wrong is hard to recover from mid-event. For executive assistants managing the logistics and scheduling layer around the same event, Claude for executive assistants covers the operational side of the same calendar.
3. Internal Announcement for Organizational Changes
A leadership change, org restructuring, or senior new hire announcement. HR signed off. Legal cleared it. Legal said "keep it simple." The exec wants it out by 5pm. You have the facts, you've done this a hundred times, and the blank page is still the problem.
The trap here isn't the draft — it's the distribution format. The company-wide email is not the same document as the manager talking points, which is not the same as the Slack post. If you write them separately from scratch, the messages drift. If they drift, the managers sound like they got different information than the company-wide announcement implied. That inconsistency is what generates the follow-up questions you spend the next three days answering.
Claude cannot access your HRIS, org chart, or employee directory. Paste in the facts. Claude produces all three format variants from the same prompt.
I need to draft an internal announcement about [change: new hire / departure / reorg / promotion / leadership transition].
Key facts: [name(s), title(s), effective date, reporting structure change if applicable]
Context for employees: [what this means for how teams are organized / who to contact / what stays the same]
Tone: [warm and welcoming / steady and professional / forward-looking]
Distribution: [a manager cascade email / a company-wide announcement / a Slack post in #company-announcements / all three]
Please draft:
(1) The primary announcement (200–300 words)
(2) A manager talking points version (bullet format, for team leads answering questions)
(3) A short Slack version (3 sentences max)
Flag any section requiring legal or HR review. Do not speculate about the reasons behind any departures or transitions — use only the facts I've provided.
Output you get: Three format variants — full announcement, manager talking points, Slack post. A "FAQ employees will ask" section with 3–5 anticipated questions and suggested responses. A note on what NOT to include.
That last element is where comms professionals get burned. The things not to include: speculation on why someone left, financial terms, org implications not yet announced, anything that reads as if the departure was involuntary when you're not in a position to address that publicly. Claude won't add those things if you don't provide them — but it will call out the absence of information employees are likely to ask about, so you can prepare the manager talking points accordingly. For the OCM side of larger organizational announcements, Claude for change management professionals covers the full transformation communications and stakeholder engagement layer.
4. Crisis and Issues Communications
Something happened. News is breaking, an incident occurred, or a sensitive external story is developing that will affect employees. You need a holding statement and an internal comms response — fast, and in the right order. "Fast" in crisis comms is measured in minutes, and the internal audience almost always needs to hear from the company before they see it externally.
Claude cannot assess legal exposure, regulatory risk, union obligations, or any company-specific context. Every crisis communication requires legal and HR review before distribution. Claude produces the structure; your legal and HR partners clear it before anything goes out. Do not use a Claude-generated holding statement as a final document without review.
We're managing a developing situation: [brief factual description of the issue — what happened, what we know, what we don't know yet].
Affected audiences: [employees / media / specific stakeholder groups]
What we want to communicate right now: [what we can confirm / what we're doing / what we can't say yet]
Constraints: [ongoing investigation / legal hold / regulatory sensitivity / pending board approval]
Tone: [calm and authoritative / empathetic and transparent / brief and factual until more is known]
Please draft:
(1) A 3-sentence internal holding statement for employees — acknowledges the situation, confirms we're taking it seriously, tells them what to expect next and when
(2) A manager cascade note — what managers should say if asked (bullet points only)
(3) A longer internal statement structure to use once we have more facts — placeholder structure with [AWAITING CONFIRMATION] flags throughout
Do not speculate, do not invent facts, do not draft an external press statement unless I ask — these are two different documents with two different legal reviews.
Output you get: Holding statement (3 sentences, legally conservative). Manager cascade notes (bullet format — exactly what to say, nothing more). Longer internal statement skeleton with [AWAITING CONFIRMATION] flags throughout. A brief "what to avoid saying" note: no minimizing language, no speculation on cause, no timeline commitments you can't keep.
The [AWAITING CONFIRMATION] flags are doing real work here. They map exactly to the information you're waiting on — from legal, from the incident investigation, from leadership decisions not yet made. They also force an honest reckoning with what you actually know versus what you're tempted to imply. Treat each flag as an action item with an owner before this document is finalized.
5. Employee Newsletter
The monthly or biweekly internal newsletter. You have twelve submissions from different business units. They are written in twelve different voices. Some are 600 words when the section should be 80. One contains a claim that needs to be verified before it's published company-wide. None of them start with the most important information. Your job is to make this read like a coherent, readable document and not like a committee wrote it — which is, in fact, exactly what happened.
Claude cannot access your intranet, CMS, Staffbase, Simpplr, or Poppulo. It cannot publish anything. You paste in the raw submissions and your tone guidance. Claude structures the output; you validate every item against the submitting team before it publishes.
I'm building the [monthly / biweekly] internal newsletter. Here are the submissions I've received from different teams:
[paste raw submissions — label each by team]
Company tone: [paste a paragraph of company voice guidance or describe the register — e.g. "direct and warm, no corporate jargon, plain language first"]
Audience: [all employees / specific region]
Newsletter sections: [e.g. Company Updates / Team Spotlights / What's Coming / Resources & Reminders]
Length target: [approximately X words total]
Please:
(1) Rewrite each submission in consistent company voice — do not add information I haven't provided
(2) Suggest an order that puts the most important item first, with brief rationale
(3) Write a brief editorial intro (3–4 sentences from the "communications team" or "your name here")
(4) Write transitions between sections if needed
(5) Flag any submission that is unclear, too long, or potentially sensitive
Do not invent employee names, team accomplishments, or metrics I haven't supplied.
Output you get: Full newsletter draft with consistent voice. Suggested order with rationale for why items are sequenced the way they are. Editorial intro. A "flagged items" section noting anything that requires follow-up with the submitting team — the too-long ones, the ones with unverified claims, the ones that sound like they might need legal eyes before publishing.
The flagged items section is the practical value add here. The newsletter submissions you receive are often fine on substance and problematic on form, length, or risk. Claude's job is to surface those issues before they become a published mistake, not to resolve them for you.
6. Exec Ghostwriting
The CHRO needs a 5-minute conference speech on the future of work. The CEO asked for a LinkedIn post about the company's culture relaunch. The CTO needs written responses to a journalist's three questions. All by tomorrow. You write all of it. The challenge isn't the message — it's producing something that sounds authentically like each executive when your only reference material is a verbal brief and maybe one prior piece of their writing.
Claude cannot access LinkedIn, email inboxes, or any executive's prior writing. Paste in the examples you have. The more actual writing you can provide, the better the calibration.
I'm ghostwriting [a speech / LinkedIn post / written interview response / conference remarks] for [executive name/title].
Audience: [external: industry conference / LinkedIn followers / media / investors — or internal: all-hands / leadership offsite]
Length: [X minutes spoken / X words written]
Key messages to land: [paste talking points or brief]
Tone and voice: [paste prior examples of their writing or describe their voice — e.g. "direct and data-driven, no corporate jargon, leads with the question not the answer"]
Context: [what's happening at the company or in the industry that makes this timely]
Please draft the full piece, flag sections where I need to supply an anecdote or specific example with [NEEDS EXAMPLE], and note any claim that requires fact-checking before the executive uses it publicly. Do not invent quotes, statistics, or industry data I haven't provided.
Output you get: Full draft. A "voice notes" section with 2–3 observations about where the draft aligns with or diverges from the voice examples you provided. A list of [NEEDS EXAMPLE] flags with suggestions for what type of anecdote or data point would work. A shorter alternate version if the executive needs a cut.
The most useful thing you can give Claude for exec ghostwriting is a paragraph of the executive's own recent writing — a prior LinkedIn post, a paragraph from an all-hands speech, a recent email to the organization. One real example calibrates register faster than a paragraph of description. For EAs supporting the same executive's communication calendar and scheduling the external commitments that generate these deliverables, Claude for executive assistants covers the operational layer. For the client-facing communication layer that management consultants build for the same leaders, Claude for management consultants covers that output set.
Why Claude Over ChatGPT for Corp Comms and Internal Comms
The core comparison is covered in depth at Claude vs ChatGPT for work. For this function specifically, four things matter.
100K+ context window. Paste the CEO's last six email communications, the most recent all-hands script, the reorg announcement, and the culture memo into a single session. Claude holds the voice across all of them — which is the whole game in exec ghostwriting. When you're maintaining a consistent executive voice across a quarter's worth of communications, the context window is what makes that possible. ChatGPT's shorter context forces you to reconstruct the voice in every session.
Conservative and attribution-honest. Claude will not invent an employee satisfaction score, a financial figure, or a headcount number for your all-hands narrative. It flags the gap with [NEEDS DATA] rather than filling it with a plausible-sounding number — which is exactly the behavior you need before an executive says something publicly that turns out to be wrong. In this function, a fabricated figure in an executive communication is not a minor accuracy problem. It's a credibility crisis.
Projects per executive. Build one Project per leader you support. Load their voice samples, past communications, communication principles, and preferred format once. Every draft you produce from that Project inherits the full context automatically — without reconstructing it from scratch every session. The consistency you get from accumulated context is the difference between ghostwriting that sounds authentic and ghostwriting that sounds like a template with their name on it.
Structured output fidelity. Run-of-show tables stay tables. Holding statements stay concise. Newsletter sections stay separated. When you give Claude a multi-format request — "produce the full email, the Slack version, and the manager talking points" — it produces three distinct documents with the right format for each, not a merged hybrid you have to pull apart manually.
4 Practical Tips for Corporate and Internal Comms Professionals
One Project per executive you ghostwrite for. Load their voice, their communication principles, their preferred length and format, and 3–5 examples of their best writing. Every draft you produce from that Project inherits the context automatically. The third CEO email of the quarter should sound more like them than the first — not less.
For crisis comms, use Claude for structure, not for judgment. It will produce a holding statement skeleton faster than you can open a new document. But you supply what's confirmed, what's not confirmed, and what legally cannot be said yet. Claude does not know what is legally sensitive. You do. The structure is the time-saver; the judgment is yours.
For all-hands scripts, give Claude the run-of-show structure first. Get the architecture right — the segment sequence, the time allocations, the handoffs — before you draft a single word of script. Then draft segment by segment in separate sessions. Trying to produce the entire all-hands script in one prompt produces generic, uniform output. Getting the architecture right first and then building each segment separately gives you something the executive team will actually use.
The three-format-variants technique. Whenever a message needs to cascade through channels — exec email → manager talking points → Slack post — ask Claude for all three in a single prompt. The consistency you get from a single generation is materially better than three separately drafted versions. Message drift between formats is what creates manager confusion and follow-up questions. Produce them together.
The Complete Claude Playbook
Ready to work faster without losing the precision this function demands? The Complete Claude Playbook ($27) has prompt frameworks for executive messaging, all-hands scripts, crisis holding statements, org change announcements, internal newsletters, and exec ghostwriting — built for the corporate and internal comms professional who owns the company's written voice and needs to produce everything on deadline.