All-Staff Update Format

What it is

The All-Staff Update Format is a structured approach to communicating company-wide news, achievements, and strategic information to your entire organisation. It ensures your message is clear, accessible, and reaches everyone consistently regardless of their role or location.

This template works because it balances formality with readability, includes context-setting for those unfamiliar with the topic, and creates natural opportunity for questions. It’s designed to be usable across multiple channels: email, intranet, video voiceover, or all-hands meetings.

The structure prioritises what matters most to your audience: why they should care, what’s changing, how it affects them, and what happens next.

When to use it

Use this template when:

• Making major announcements to the entire workforce
• Sharing quarterly business updates or financial performance
• Announcing organisational changes, restructuring, or new initiatives
• Celebrating significant achievements or milestones
• Communicating policy changes or new working arrangements

Don’t use this template for:

• Urgent crisis communication (use crisis protocols instead)
• Departmental or team-specific updates (use manager-cascade-notes)
• Detailed technical explanations requiring specialist knowledge
• Individual performance feedback or one-to-one conversations
• Sensitive personnel matters affecting specific individuals

Inputs needed

Before drafting, gather:

• The core news/update in 1-2 sentences
• 3-4 supporting points or context items
• Any relevant metrics, dates, or timelines
• Who is responsible for implementation
• What action, if any, is needed from staff
• Expected FAQs or concerns
• Distribution channels (email, video, meeting, intranet)

---

The template

Subject line

[Outcome/action + Timeframe]: [Key announcement]

Examples: “Strategic Partnership Launched Today: What This Means for Us” or “New Flexible Working Policy – Effective 1 March”

---

Opening (2-3 sentences)

Hook: Lead with the most important information or the impact that will resonate most. Avoid burying the lead.

“I’m pleased to announce that we’ve secured Series B funding of £12m, which positions us to accelerate product development and expand our market reach.”

---

Context (3-4 sentences)

Background: Help people understand why this matters and what led to this point. Include enough detail for those unfamiliar with the situation.

“Over the past 18 months, we’ve grown from 45 to 120 team members. Our product adoption has increased 340%, but we’ve identified bottlenecks in our infrastructure and customer success capabilities. This investment directly addresses those gaps.”

---

What’s changing (3-5 bullet points)

Clear outline: Describe the specific changes, new initiatives, or implications.

• New roles being created in Engineering and Customer Success
• Investment in three priority projects: Platform Modernisation, API Expansion, and Regional Support
• Team structure changes effective 1 March
• Updated internal tools and systems rolling out next quarter

---

How it affects you (by audience segment)

Personalisation: Acknowledge how this impacts different groups.

• Engineering: You’ll be working on modernisation alongside new feature development
• Customer-facing teams: New support tools and expanded team means faster response times
• Operations/Admin: We’re hiring a dedicated Finance role to reduce administrative burden
• Everyone: We’re hiring. If you know great candidates, refer them via [link]

---

Timeline (if applicable)

Clarity: Show what happens when, so people know what to expect.

Date	Milestone
1 Feb	Announcements to major clients and partners
15 Feb	New team members start
1 March	Team restructure and new roles go live
Q2 2026	Platform modernisation project begins

---

Next steps / How to engage

Action: Tell people what they should do or where to find more information.

• Questions? Join our All-Hands on Friday 3 Feb at 2pm (see calendar invite)
• Interested in one of the new roles? Email [name] with your CV
• Want the detailed strategy deck? Available on [location]
• Feedback? Share via [anonymous survey/open meeting]

---

Closing (1-2 sentences)

Tone: End with optimism and gratitude. Reinforce the core message.

“This is an exciting moment for us all. Thank you for the hard work that’s brought us here. I can’t wait to share more details on Friday.”

---

AI prompt

Base prompt

Write an all-staff update.

What I know so far:
- Organisation: [WHO WE ARE AND ROUGHLY HOW MANY PEOPLE WORK HERE]
- Who it is from: [THE NAME AND ROLE IT WILL BE SENT FROM]
- The news: [WHAT IS NEW OR CHANGING, IN ONE OR TWO SENTENCES]
- Why it is happening: [THE REASON, AS WE CAN SAY IT TO STAFF]
- Who is affected and how: [WHICH TEAMS OR GROUPS, AND WHAT CHANGES FOR EACH]
- Dates: [WHEN THINGS HAPPEN, OR "NO DATES YET"]
- What staff should do next: [ANY ACTION, AND WHERE TO ASK QUESTIONS]
- What staff are likely to worry about: [THE QUESTIONS OR CONCERNS WE EXPECT]
- Channel: [EMAIL, INTRANET, ALL-HANDS OR VIDEO]

Use these headings, in this order:
1. Subject line: what is happening and when, in 10 words or fewer.
2. Opening: the news itself in the first sentence, then why it matters, in two or three sentences.
3. Context: what led to this, in three or four sentences, written for someone who knows nothing about it.
4. What is changing: three to five bullet points.
5. How it affects you: one short line for each team or group affected.
6. Timeline: a table with the columns Date | What happens. Leave it out if there are no dates.
7. Next steps: what to do, where to find more, and how to ask questions or give feedback.
8. Closing: one or two sentences in the sender's voice.

Write 300 to 400 words, warm and direct, in the sender's voice rather than corporate language. Assume a mixed audience, and explain internal jargon and acronyms.

How to work:
- Use only what I have given you. Where you fill a gap yourself, mark it [Assumed: what you assumed]. Where the draft needs a fact, figure, name, date or quote I have not given you, write [Confirm: what is needed] rather than inventing it.
- Do not estimate numbers such as audience sizes, budgets, targets or results unless I have given you data to base them on.
- Where a whole table or list rests on the same assumption, say so once above it rather than marking every line.
- If I have left a gap in [CAPITALS] unfilled, treat it as unknown. Do not fill it with an example.
- Use UK English and plain language.

Finish with two short sections:
Questions for you: the 3 to 5 answers that would most improve this draft, most important first.
Check before use: the facts, approvals and judgements a person must confirm before this is used.

Variations

Organisational change

Use this when the update is about a restructure, new reporting lines or roles at risk.

This update is about organisational change: [WHAT IS CHANGING IN THE STRUCTURE]. Say clearly what is not changing as well as what is. Do not describe anyone's role as safe or at risk unless I have said so. If roles may be affected, add a line saying how individuals will hear about their own situation and when, and mark that line [Confirm: HR and legal wording]. Add a short "Questions you may have" section with three to five questions and honest answers, using [Confirm: …] where we do not yet know. This section does not count towards the word limit.

Short versions for other channels

Use this when the same news also needs to go out on chat or be said out loud.

After the update, also write: a post of 60 words or fewer for [OUR CHAT CHANNEL, SUCH AS TEAMS OR SLACK] that links to the full update, and a script of about one minute for the sender to say at [THE MEETING OR ALL-HANDS]. Keep all three versions consistent on facts and dates.

---

Human review checklist

• Opening hook delivers the headline: Lead paragraph makes clear what the announcement is about within first sentence
• Context is accessible: Background explanation works for someone unfamiliar with the topic; jargon is minimised or explained
• Impact is personalised: Update addresses how this affects different teams or roles specifically, not just generically
• Timeline is clear: If changes are being implemented, dates and sequence are explicitly stated (avoid vague language like “soon” or “shortly”)
• All action items are obvious: People know what they need to do next, if anything, and where to find information or ask questions
• Tone matches context: Professional but not distant; celebratory for positive news, reassuring for change
• Length is appropriate: 300-400 words; scannability maintained with headers and bullets, not overwhelming
• Distribution channels are appropriate: Message is suitable for the channel(s) it will be shared via (email vs. video vs. all-hands requires different framing)
• Leadership voice is authentic: Update sounds like real communication from leadership, not a corporate template
• Potential concerns are addressed: FAQ section or next steps preempt obvious questions or concerns

---

Tips for success

Lead with impact, not process Start with what matters to your audience – what’s changing for them, what opportunity or risk is being addressed – not with the history of how you arrived at the decision. Save context for the second section.

Assume mixed technical literacy Your audience includes finance staff, developers, operations, support, and leadership. Avoid jargon or explain it immediately. “API integration” means nothing to your People ops team unless you explain it briefly.

Make it scannable Use headers, bullets, and short paragraphs. Many people will skim this during a busy day. Your most important information should survive a 30-second read.

Address different audiences explicitly Rather than hoping various teams will figure out the relevance, tell them directly: “If you work in Engineering…” “For our customer-facing teams…” This personalisation drives engagement and reduces questions later.

Create clear next steps End ambiguity about what happens next. Provide specific dates, specific contact people, and specific actions. “More details to follow” creates uncertainty; “Briefing sessions scheduled for next week; calendar invite Thursday” creates clarity.

---

Common pitfalls

Burying the lead The worst opening is “As you may know, over the past three years, our market has been shifting…” Your team doesn’t care about the history until you’ve told them what’s new. Lead with news, then explain context.

Over-explaining the why without addressing the what You can spend an entire update explaining business drivers without clearly saying what’s actually changing. “We’ve decided to implement a new performance review system because market research shows…” Without clearly stating the changes being made, staff leave confused.

Assuming everyone knows the context New employees, people in remote locations, and people who don’t attend all meetings might be unfamiliar with background information. Build in enough context that someone joining last month understands the update.

Creating information overload with multiple announcements Don’t combine three separate pieces of news in one update. If you have multiple announcements, separate them or clearly delineate each section. Combining 15 different changes in one message causes people to disengage.

Forgetting the human element A perfectly structured update delivered in corporate language feels disconnected. Your update should reflect actual leadership voice, acknowledge effort or concern, and feel warm even when delivering difficult news about change.