[NTTP]

Announcement Writer

Share internal news, a policy change, a new hire, or a team update, clearly and without corporate fluff.

What is happening, why, and when it takes effect if relevant. The more specific, the better the result.

Free to try, no sign-up needed

Your text isn't stored. It's sent to Anthropic to generate your result, then discarded. Privacy

Prefer to write it yourself? Use the free prompt.

What it produces

Real output from this tool, not a mock-up.

What went in

What kind of announcement
A policy or process change
The details
Changing the expenses policy from 1 October. Currently everyone emails receipts to finance and it takes about 3 weeks to reimburse. Moving to Pleo cards: photograph the receipt in the app, no claim forms, no waiting. Limits 500 a month standard, managers 2000, above that needs pre-approval as now. Old process closes 30 September. Cards arrive week of the 22nd, there will be a 20 minute setup session.
Tone
Matter-of-fact

What came back

Subject: Expenses policy is changing to Pleo cards, effective October 1 Starting October 1, we're moving off the email-and-reimburse expenses process and onto Pleo cards. Why: right now everyone submits receipts by email to finance and waits about 3 weeks to get reimbursed. With Pleo, you get a company card, photograph the receipt in the app at the time of purchase, and there's no claim form and no wait, since the charge comes straight off the card instead of your own money. What's changing: - Everyone gets a Pleo card. Cards arrive the week of the 22nd, and there's a 20 minute session to set them up. - Spending limits: 500/month standard, 2000/month for managers. - Anything above your limit still needs pre-approval, same as now. Timeline: - The old email-to-finance process closes September 30. - Any expense from before September 30 still goes through the old process, email your receipts to finance as usual. - From October 1, all new expenses go through Pleo. More details on the setup session will follow. If you don't have a Pleo card by the week of the 22nd, contact [insert contact/team name].

When to use it

Use this for internal news that people need to actually absorb: a policy change, a new hire, a change to how the team is structured. It states what is changing, when, and what it means for the reader, without the corporate padding that makes people skim to the bottom looking for the point.

Common questions

What makes an internal announcement get read?
Leading with what is changing and what the reader has to do, rather than with context and rationale. Most announcements bury the actual instruction in paragraph four, which is why people skim to the end and then ask a question already answered.
Should I explain why?
Briefly, and after the what. A one-line reason helps people accept a change; three paragraphs of justification signal that you expect resistance and often create it. Put the detail in a linked document for the people who want it.
Can I use it for bad news?
Yes, and matter-of-fact is usually the right tone for it. What people react badly to is not bad news but vagueness, so be specific in the details box about what is changing and what is not. The tool is built to be clear about both.
Is it free?
You can run it three times a day with no account. Signing in gives you renewing monthly credits, and this tool costs one credit per run with the one-click refinements included.

Similar tools

All Work & Meetings