Six templates for the messages a small business actually sends: a company announcement email with three worked examples, a structured weekly team update, a pack of twelve short internal emails, a policy change notice with acknowledgment tracking, urgent closure messages, and a tracker workbook. Editable Word and Excel files, no email form.
The worst internal email I ever sent had every fact in it. Correct dates, correct process, three paragraphs of reasoning, and a subject line that said Important update. Two people asked me the same question the following week and one of them had not opened it at all.
What was missing was not information. It was the first sentence carrying the news, an actual subject line, a line saying what was not changing, and one named person to reply to. Those four things are the difference between a message that gets read and a message that gets forwarded to a colleague with the words did you see this.
So there are six templates below rather than one. Five are editable Word documents and one is an Excel workbook, free, with no form in the way. They cover the messages a small business genuinely sends: an announcement, a weekly update, a stack of short everyday emails, a policy change with a record attached, and the ones you write in four minutes on a bad day.
TL;DR
An internal announcement email needs six parts: a subject that states the news, the whole story in sentence one, what is changing with dates, what to do and by when, what is not changing, and a named person to ask. Six free templates below, including a weekly team update document. No signup.
What Every Internal Email Needs
Six parts, and the order is fixed. Most internal messages that fail are not missing facts. They bury the news under the reasoning, leave the obvious worry unaddressed, and end with a shared inbox instead of a person.
A subject that says the news
Not an important update. The change, the date, and whether action is needed, in about eight words. This is the only part most people read.
The whole news in sentence one
If somebody reads one line and stops, they should know what changed and whether it touches them. Everything after is read through that sentence.
What to do, and by when
Numbered, with dates. If there is nothing to do, write that plainly, because silence on the point makes people assume they missed something.
What is not changing
Pay, hours, schedules, who your manager is. Name the fears and close them. The one you leave unnamed is the one that spreads.
A named person to ask
One person with a name, not a shared inbox. Tell them first that they are the name in the message.
Where it lives afterward
The announcement is temporary; the rule it created is not. Point at the handbook section or the folder that now holds the current version.
The two that get dropped most often are what is not changing and the named contact. Both are cheap to write and both remove a week of follow-up questions, which is the actual cost of a message that lands badly.
There is a seventh part that only applies sometimes: an acknowledgment. Routine news does not need one. A policy change does, and asking for it in the same message is far easier than chasing it later.
Which Template Should You Use?
Pick by situation. The announcement email covers most company news, the weekly update is the only one you send on a schedule, and the tracker is what keeps the other five from becoming a folder of things nobody can find.
Company Announcement Email
The default
The structure that works for almost any piece of company news, followed by three worked examples: a policy change, a new tool, and an office move. Ends with a six-line check to run before you press send.
Weekly Team Update
The recurring one
A structured update document in eight sections: headline, the numbers with last week beside them, what got done, what is next, what is stuck, decisions, people, and one ask. Includes a fully filled-in week.
Internal Email Examples Pack
Twelve short messages
Ready to send once the brackets are filled: closure, outage, a new starter, a leaver, a policy update, open enrollment, a moved payday, an all-hands invitation and recap, a training reminder, a schedule change, and a thank you.
Policy Change Notification
When you need a record
The one message where being provable matters more than being memorable. The notice itself, an acknowledgment request, a tracking table with a chase schedule, and a worked expense policy example.
Urgent Notice and Closures
Written in four minutes
Five messages built on the same three-line shape: what happened, what to do now, when the next update comes. Covers same-day closure, an overnight closure, an outage, a site incident, and the holding message.
Weekly Update Tracker
Spreadsheet, three tabs
A rolling log of the weekly updates you have sent, the three to five numbers you repeat every week with their sources and owners, and an announcement log recording who was told what, where it went, and where it was filed.
If You Are Announcing Something This Week
Open the announcement template and read the three worked examples before you fill anything in. They are more useful than the blank structure, because the structure tells you what a section is for and the example shows you how short each one is allowed to be. Then, before you send, do the two things that are not in the document: tell anybody personally affected in a conversation, and give your managers the message a day early so they are answering questions rather than reading it at the same moment as their team.
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
Download all six together as a zip file, or take the one you need. Five are editable Word documents and one is an Excel workbook with three tabs. Fill in the brackets, delete what does not apply, and change anything that does not sound like your business.
Download All 6 Internal Communication Templates
The announcement email, weekly team update, examples pack, policy change notice, and urgent messages as DOCX, plus the tracker as XLSX, in a single zip.
Template 1: Company Announcement Email
The structure that carries almost any piece of company news, then three worked examples: a policy change, a new scheduling tool, and an office move. Ends with a six-line check to run before you press send.
Company Announcement Email Template
COMPANY ANNOUNCEMENT EMAIL
[Company Name]
Announcement:
Audience: [whole company / one team / managers first, then everyone]
Sent by: Send date: [MM/DD/YYYY]
Channel: [email / team chat / printed and posted by the clock]
Acknowledgment required: [yes / no] Replies due by: [MM/DD/YYYY]
THE STRUCTURE
Subject: [Put the actual news in the subject. An important update is not a
subject line. Time off requests move to the app on October 1 is one.]
Hi everyone,
[SENTENCE ONE: the whole news, in one sentence. If somebody reads this line and
nothing else, they should know what changed and whether it touches them.]
What is changing
[Two or three sentences, concrete, with dates. Describe what is different on
Monday morning rather than the reasoning that led there.]
Why
[One or two sentences. A reason people can repeat to each other holds up. A
reason that sounds like a press release gets replaced by whatever they invent.]
What this means for you
[The part they opened the message for. Written from their side of the desk, not
from the company’s.]
What you need to do, and by when
1. [Action] by [date]
2. [Action] by [date]
[If there is genuinely nothing to do, write nothing to do and say it plainly.
Otherwise everyone assumes there is something they missed.]
What is not changing
[Name the fears and close them: pay, hours, schedules, who your manager is. The
fear you do not name is the one that spreads.]
Who to ask
[A named person and how to reach them, not a shared inbox nobody watches.]
Where this lives afterward
[Handbook section, shared drive folder, or pinned message. One place, named.]
Thanks,
[Name]
[Title]
EXAMPLE 1: A POLICY CHANGE
Subject: Time off requests move to the app on October 1
Hi everyone,
From October 1, time off requests go through the app instead of email, and your
manager approves them there.
What is changing: the request form and the approval both live in one place, so
you can see your remaining balance before you ask. Email requests sent after
October 1 will get a reply pointing you back to the app.
Why: we lost two approved requests last quarter because they were buried in an
inbox, and both people found out the week before they traveled.
What this means for you: about a minute per request, and you stop having to
remember how many days you have left.
What you need to do: open the app and check that your balance looks right. If it
does not, tell Priya before September 26 and she will correct it.
What is not changing: how much time off you get, how far ahead you need to ask,
and who approves it.
Questions: Priya, or bring it to Thursday’s huddle.
This replaces the time off section of the handbook, which is updated already.
EXAMPLE 2: A NEW TOOL
Subject: New scheduling app goes live Monday the 6th
Hi everyone,
From Monday the 6th, next week’s shifts are published in the scheduling app and
the printed sheet by the door stops.
What is changing: you will get a notification when the schedule is posted, and
swaps go through the app so two people cannot claim the same shift.
Why: the paper sheet was accurate on the day it was printed and wrong by
Wednesday, and the people it was wrong for were always the same ones.
What this means for you: check the app on Friday for next week instead of the
board. Marcus can set you up in about four minutes if you have not signed in.
What you need to do: sign in once before Friday so we know it works for you.
What is not changing: your hours, your usual shifts, how far ahead the schedule
is published, and who to ask for a swap.
Questions: Marcus, in person or on the team channel.
EXAMPLE 3: AN OFFICE MOVE
Subject: We are moving to the Third Street office on November 3
Hi everyone,
We are moving to 118 Third Street on Monday, November 3. The current office
closes on Friday, October 31.
What is changing: the address, the parking situation, and the room you meet
clients in. The new space has covered parking behind the building and street
parking out front.
Why: our lease ends in December and the new space costs about the same for a
floor we can actually fit into.
What this means for you: the commute changes for everyone, by roughly ten
minutes in either direction depending on where you come from. If that creates a
real problem for you, come talk to me this week rather than in October.
What you need to do: pack your own desk into a labeled box by Thursday the 30th.
Boxes and labels are by the kitchen from Monday.
What is not changing: your hours, your parking allowance, and the hybrid
schedule.
Questions: me, any time, and there is a walkthrough on the 24th for anyone who
wants to see it first.
BEFORE YOU SEND
•[ ] Read the first sentence alone. Does it carry the whole news?
•[ ] Anyone personally affected has already heard it in a conversation
•[ ] Managers heard it before their teams did
•[ ] Every date, figure, and name checked
•[ ] A named person to reply to, and they know they are named
•[ ] Read it once as the most anxious person on the team would
NOTE: This is a sample template for general information only and is not legal
advice. Names, dates, and figures in the examples are illustrative.
Template 2: Weekly Team Update
A structured update document in eight sections, with a fully filled-in week so you can see how short each section should be.
Weekly Team Update Template
WEEKLY TEAM UPDATE
[Company Name]
Week ending: [MM/DD/YYYY] Written by:
Goes to: [whole company / this team] Sent: [same day and time every week]
Eight sections, in this order, every week. The order matters more than the
length: people learn where to look, and the update becomes something they skim
in ninety seconds rather than something they save for later and never open.
1. HEADLINE
[One line. The single thing somebody should remember from this week. If nothing
happened that deserves a headline, write a quiet week and move on. Inventing one
is how people learn to stop reading.]
2. THE NUMBERS
[Three to five figures, the same ones in the same order every week, each with
last week beside it so the trend is visible without doing arithmetic.]
[Metric 1]: [this week] (last week: [ ])
[Metric 2]: [this week] (last week: [ ])
[Metric 3]: [this week] (last week: [ ])
3. WHAT GOT DONE
[Finished things only, with the person named. Three to six lines. In progress
belongs in the next section, not this one.]
•[ ]
•[ ]
•[ ]
4. WHAT IS NEXT
[What the week ahead is for, with an owner and a date on each line. If a line
has no owner, it is a wish rather than a plan.]
•[Thing] ([owner], due [date])
•[Thing] ([owner], due [date])
5. WHAT IS STUCK
[The section that makes the update worth reading. What is blocked, who is
blocked on it, and what would unblock it. An update whose blockers section is
empty every single week is not being written honestly, and everybody knows.]
•[Blocked thing]: waiting on [person or event], needed by [date]
•[Blocked thing]: waiting on [person or event], needed by [date]
6. DECISIONS AND CHANGES
[Anything decided this week that changes what somebody does. One line each, with
where the detail lives. This is the section people search back through, so keep
the wording plain.]
•[Decision], effective [date]. Detail: [where it lives]
7. PEOPLE
Starting: [ ]
Leaving: [ ]
Out next week: [ ]
Worth calling out: [one specific thing one person did, named. Not a general
thank you to everybody, which lands on nobody.]
8. ONE ASK
[One thing you want back from the reader this week: a reply, a number, a check
of something. One. Five asks produce zero.]
A FILLED-IN EXAMPLE
Week ending Friday, March 13. Written by Dana.
HEADLINE
The new intake form is live for every crew, and the double-booking that cost us
two jobs in February has not happened since.
THE NUMBERS
Jobs completed: 41 (last week: 38)
Callbacks: 3 (last week: 7)
Invoices out: 36 (last week: 29)
Open tickets over 5 days: 4 (last week: 9)
WHAT GOT DONE
•Intake form rolled out to all four crews. Marcus trained the last two.
•February invoicing closed on Wednesday, four days earlier than January.
•Two vans back from service, both with the new tablet mounts.
WHAT IS NEXT
•Review the second week of intake data (Dana, due Friday)
•Quotes for the Third Street lease (owner, due Wednesday)
•Book the safety refresher for the whole crew (Priya, due next Monday)
WHAT IS STUCK
•Parts for the two long-running repairs: waiting on the supplier, promised
Thursday, needed before the 20th or we move both jobs.
•Payroll cutoff change: waiting on me to confirm the new Tuesday deadline with
the bookkeeper. My fault, done by Monday.
DECISIONS AND CHANGES
•Callbacks now get logged on the intake form rather than in the group chat,
Worth calling out: Priya rebuilt the parts list from scratch after the supplier
changed their codes, on her own, and did not mention it to anybody.
ONE ASK
If you have a job from February that never got invoiced, tell Dana by Tuesday.
NOTES ON KEEPING IT GOING
•Same day, same time, every week. A predictable update that is a bit dull beats
a good one that arrives whenever there is time.
•Fifteen minutes to write. If it takes an hour you will stop within a month.
•Write it in the message body rather than attaching a document. An attachment
is a decision to open something, and most people decide no.
•Skipping a week is fine as long as you say so. Disappearing without a word
teaches people it was never real.
•Keep the sent copies. Twelve of these is the most honest record of a year that
a small business will ever produce.
NOTE: This is a sample template for general information only and is not legal
advice. Names and figures in the example are illustrative.
Template 3: Internal Email Examples Pack
Twelve short messages for the situations that come round again and again, from a same-day closure to a moved payday to a thank you after a hard week. Each is written to go out as it stands once the brackets are filled.
Internal Email Examples Pack
INTERNAL COMMUNICATION EMAIL EXAMPLES
[Company Name]
Twelve short messages for the situations that come round again and again. Each
one is written to be sent as it stands once the brackets are filled. They are
deliberately short, because the length of an internal message is a signal about
how urgent it is, and a long message about a small thing reads as neither.
1. OFFICE CLOSED TOMORROW
Subject: Office closed tomorrow, [day date]
The office is closed tomorrow, [date], because of [reason]. Nobody should come
in.
[Everyone is paid for the day as normal. / Hourly staff scheduled tomorrow will
be paid for their scheduled hours.] Work from home if you can and if you have
what you need; if you cannot, that is fine.
Next update: [day] by [time], on [channel].
[Name]
2. SYSTEM OR PHONE OUTAGE
Subject: [System] is down, use [workaround] until further notice
[System] has been down since [time]. [Vendor / our provider] is working on it and
has not given a fix time.
Until it is back: [the workaround, in one or two lines].
Do not [the thing that will create a mess when the system returns].
Next update at [time], here.
[Name]
3. NEW HIRE STARTING MONDAY
Subject: [First name] starts Monday as our new [job title]
[First name] [Last name] joins us on [date] as [job title].
[One sentence on their background and one on what they will be working on, with
the names of the people they will work with most.]
Say hello when you get the chance. [First name] is [in the office / working
remotely from [city]] and the best way to reach them from [date] is [channel].
[Name]
4. SOMEONE IS LEAVING
Subject: [First name] is leaving us on [date]
[First name] is leaving [Company Name] on [date] [to take a role at another
company / for personal reasons they are happy for me to share as: [reason]].
[One or two sentences on what they did here, specific enough that it could only
be about them.]
From [date], [what they handled] goes to [name] and [what else] goes to [name].
Send anything in flight to [name] this week rather than after.
There is [a leaving lunch on [date] / a card going round with [name]].
[Name]
5. POLICY UPDATE IN THE HANDBOOK
Subject: [Policy name] has changed, effective [date]
The [policy name] policy changed on [date]. The short version: [the change in one
sentence].
What is different for you: [one or two lines].
What has not changed: [the reassurance, named].
The updated policy is [where], and the previous version is [where]. Questions to
[name].
[Please confirm you have read it by [date]. / Nothing to do beyond reading it.]
[Name]
6. OPEN ENROLLMENT OPENS
Subject: Benefits enrollment is open until [date], action needed
Open enrollment runs from [date] to [date]. [If you do nothing, your current
elections roll over. / If you do nothing, you will have no coverage next year,
so this one genuinely needs your attention.]
What changed this year: [one or two lines, plainly].
Where to enroll: [link or place]. How long it takes: about [ ] minutes.
Drop-in session on [date] at [time] with [name] for anyone who wants to walk
through it with a person.
[Name]
7. PAYDAY FALLS ON A HOLIDAY
Subject: [Month] payday moves to [day date]
Payday normally lands on [usual date], which is [holiday] this month, so pay will
reach accounts on [new date] instead.
Nothing else changes: the amount, the period it covers, and the cutoff for
timesheets are all the same.
If your bank has not shown it by [date], tell [name].
[Name]
8. ALL-HANDS INVITATION
Subject: All-hands on [day date], [time], [place or link]
We are meeting on [date] at [time] in [place or on the link below]. It runs [ ]
minutes and here is what we are covering:
•[Topic]: [who is speaking]
•[Topic]: [who is speaking]
•Questions: [ ] minutes, and you can send them ahead to [name]
[If you are on shift, [name] will run the same thing at [time]. / A written
summary goes out the same afternoon for anyone who cannot make it.]
[Name]
9. ALL-HANDS RECAP
Subject: What we covered at the all-hands on [date]
For anyone who missed it, and for anyone who was there and would rather read it:
•[Decision or news, in one line]
•[Decision or news, in one line]
•[Decision or news, in one line]
Asked and answered: [the question somebody raised, and the answer given].
Asked and not answered yet: [the question], which [name] will come back on by
[date].
[Name]
10. TRAINING DUE DATE REMINDER
Subject: [Training name] is due by [date], about [ ] minutes
[Training name] needs to be completed by [date]. It takes about [ ] minutes and
you can do it on a phone.
[Where to find it.]
[Number] of us have finished it. If you have already done it, ignore this. If
something is blocking you, tell [name] rather than leaving it.
[Name]
11. SCHEDULE OR SHIFT CHANGE
Subject: Schedule change for [team or dates], starting [date]
From [date], [the change in one sentence].
Who this affects: [names or team]. Who it does not: everybody else, and your
hours are unchanged.
[The new pattern, laid out plainly.]
If this creates a genuine problem with childcare, a second job, or travel, come
and talk to [name] this week and we will work it out.
[Name]
12. THANK YOU AFTER A HARD WEEK
Subject: Thank you for last week
Last week was [the specific thing that made it hard], and we got through it
because [the specific thing people did].
[One named example. One. A general thank you to everybody lands on nobody.]
[What happens now, or what you are doing so it is less painful next time.]
Thank you, genuinely.
[Name]
NOTE: This is a sample template for general information only and is not legal
advice. Pay, benefits, and leave wording should be checked against your own
policies and applicable law before you send it.
Template 4: Policy Change Notification
The notice itself, an acknowledgment request that separates having read a policy from agreeing with it, a tracking table with a chase schedule, and a worked expense policy example.
Policy Change Notification Email
POLICY CHANGE NOTIFICATION
[Company Name]
Policy: Version: [ ]
Effective date: [MM/DD/YYYY] Announced on: [MM/DD/YYYY]
Sent by:
Acknowledgment required: [yes / no] Due by: [MM/DD/YYYY]
Replaces: [previous version and date]
A policy change is the one internal message where being memorable matters less
than being provable. You want people to understand it, and you want a record
that they were told, when, and what they were told.
THE MESSAGE
Subject: [Policy name] changes on [date], [please confirm you have read it]
Hi everyone,
The [policy name] policy changes on [date].
What is different
[The change itself, in plain language, before any of the reasoning. Two or three
sentences. If there are several changes, number them, and put the one that
affects the most people first.]
1. [Change]
2. [Change]
What has not changed
[Explicitly. A policy update with no reassurance in it invites people to assume
the worst about the parts you did not mention.]
Why
[One or two sentences. If the honest answer is that the law changed or the
insurer changed it, say that. It is a better answer than a manufactured one.]
What you need to do
[Read it, confirm it, sign it, or nothing. Be specific, and give a date.]
Where to find it
The full policy is at [location]. The version it replaces is at [location], kept
so you can see what changed.
Questions
[Named person], by [date], and I will send round the answers to anything that
comes up more than once.
[Name]
[Title]
ACKNOWLEDGMENT REQUEST
[Use this when the policy is one you would want to prove somebody had seen.]
Please reply to this message with the word acknowledged, or sign the copy at
[location], by [date]. This confirms you have read the policy, not that you
agree with every part of it.
If you have a question that would change whether you can follow it, ask before
you acknowledge rather than after.
TRACKING
Name Sent Acknowledged Method
____ _ _____
____ _ _____
____ _ _____
____ _ _____
Chase list, [date]:
Second chase, [date]:
Anyone still outstanding on [date] gets a conversation, not a third email.
A WORKED EXAMPLE
Subject: Expense policy changes on April 1, please confirm you have read it
Hi everyone,
The expense policy changes on April 1.
What is different:
1. Receipts go in within seven days of the spend rather than at month end.
2. Anything over $250 needs approval before you spend it, not after.
What has not changed: what you can claim for, the mileage rate, and how quickly
you get paid back.
Why: two people ended up out of pocket for six weeks last quarter because their
receipts arrived after the close, and the approval line exists so nobody is told
no after they have already paid.
What you need to do: read it, and reply with acknowledged by April 8.
Where to find it: handbook, section 9. The old version is in the archive folder.
Questions to Priya by April 4.
NOTE: This is a sample template for general information only and is not legal
advice. Some policy changes carry notice requirements or deadlines set by
federal or state law. Confirm your obligations, and have counsel review anything
that changes pay, benefits, or terms of employment.
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
Five messages on the same three-line shape: what has happened, what to do right now, when the next update comes. Covers a same-day closure, an overnight closure, an outage, a site incident, and the holding message for when you do not know yet.
Urgent Notice and Closure Messages
URGENT NOTICE MESSAGES
[Company Name]
For the message you write in four minutes, on a day when something has gone
wrong. Every one of these follows the same three-line shape, because a person
reading on a phone in a hurry can hold three things.
THE THREE-LINE SHAPE
Line 1: what has happened, in plain words.
Line 2: what you want the reader to do, right now.
Line 3: when the next update comes, and where.
That third line is the one that stops the follow-up questions. A message without
it generates a dozen replies asking the same thing.
1. CLOSURE, SAME DAY
Subject: [Location] closed today, [date], do not come in
[Location] is closed today because of [reason]. Do not travel in. If you are
already on your way, turn around and let [name] know.
[Pay: everyone is paid for today as normal. / Hourly staff scheduled today are
paid for their scheduled hours.]
Next update by [time] today on [channel].
2. CLOSURE, ANNOUNCED THE NIGHT BEFORE
Subject: Closed tomorrow, [day date]
We are closed tomorrow, [date], because of [reason]. Nobody comes in.
[What happens to today’s work that will not get finished, and who is telling
customers.]
[Pay position, stated plainly.]
If anything changes overnight I will send an update by [time] on [channel].
Check there before you set off.
3. OUTAGE
Subject: [System] is down since [time], here is the workaround
[System] has been down since [time]. [Who is fixing it] is on it. I do not have a
fix time yet.
Until it is back: [the workaround]. Do not [the thing that creates a mess later].
Next update at [time], here, even if there is nothing new to say.
4. SAFETY INCIDENT ON SITE
Subject: Incident at [location] this morning, everyone is accounted for
There was [a brief factual description] at [location] at about [time]. Everyone
is accounted for. [One person was taken to hospital as a precaution and is being
looked after.]
Do not [enter the area / use the equipment] until [name] says otherwise.
Do not post about this anywhere public, and send any question from outside the
company to [name].
Next update at [time].
[Say only what you know. Never name the person, never describe their injuries or
their condition, and never speculate on the cause while it is being looked into.]
5. THE HOLDING MESSAGE, WHEN YOU DO NOT KNOW YET
Subject: [Thing that happened], what we know so far
You will have heard that [the thing]. Here is what I can confirm: [the two or
three facts you are certain of].
Here is what I do not know yet: [the list, plainly]. I would rather tell you that
than guess.
Nobody needs to do anything right now [except [the one thing]].
I will send the next update at [time], and I will send it then whether or not
there is more news.
BEFORE YOU SEND AN URGENT MESSAGE
•[ ] Every word of it is something you know, not something you assume
•[ ] The pay question is answered, or you have said when it will be
•[ ] It went to the channel people actually read on a bad day, not just email
•[ ] Anyone without a company inbox is covered: text, a call, or a sign on the
door
•[ ] There is a time on the next update, and somebody owns sending it
•[ ] No medical detail, no names attached to anything personal
NOTE: This is a sample template for general information only and is not legal
advice. Closure pay, reporting obligations after a workplace incident, and
notice requirements vary by state and by situation. Confirm yours before you
rely on any wording here.
Template 6: Weekly Update Tracker (Spreadsheet)
Three tabs: a rolling log of the updates you have sent, the numbers you repeat every week with their sources and owners, and an announcement log recording who was told what, on which channel, and where the final version was filed.
Weekly Update Tracker
A
B
C
D
E
F
G
H
1
Week ending
Headline
Done
Next
Stuck
One ask
Sent on
Replies
2
2026-02-27
February invoicing closed four days early
Intake form on two crews; invoicing closed
Roll intake form to remaining crews
Supplier parts, promised Thursday
Flag any February job not invoiced
2026-02-27
6
3
2026-03-06
Callbacks down from seven to three
Two vans back in service
Review first week of intake data
Payroll cutoff still unconfirmed
Confirm your app sign in works
2026-03-06
4
4
2026-03-13
Intake form live for every crew
All four crews trained; 41 jobs done
Third Street lease quotes
Parts still outstanding, needed by the 20th
Send Dana any uninvoiced February job
2026-03-13
9
5
6
7
8
9
Writing a Company Announcement
Write the news as one paragraph before you open the email. What is changing, why, when, what people do differently, and what is not changing. If that paragraph will not come out cleanly, the decision behind it is unfinished and announcing into the gap costs more than waiting a day.
1
Write the paragraph first
Five things in plain language. This is the step people skip, and everything downstream then takes twice as long and produces a week of corrections.
2
Tell the affected people in a conversation
Anyone whose own job changes hears it individually. Nobody should learn something about their own work from a message addressed to a group.
3
Brief the managers a day early
They get asked first. A manager reading the announcement at the same moment as their team has been told nothing useful, and it costs them credibility.
4
Put the news in the subject line
The change, the date, and whether action is needed. Around eight words. If the subject could belong to any message, it gets opened last.
5
Lead with the news, not the reasoning
Sentence one carries the whole story. The why goes underneath it, in one or two sentences, in language people can repeat to each other.
6
Close the fears and name a person
Say what is not changing, by name: pay, hours, schedules, managers. Then give one person to reply to, and tell them first.
Two details make a bigger difference than the wording. The first is the gap between briefing managers and telling everyone: too short and it was pointless, too long and it leaks, and a day is usually about right. The second is the follow-up, which most announcements never get, and which is what turns a change into a routine rather than something that stays permanently in progress.
For the specific announcements that already have their own conventions, use the specific template. A new employee announcement and a promotion announcement both carry expectations that a generic company update does not.
Internal Email Examples, Weak and Strong
A finished message teaches more than a blank structure does. Weak internal emails fail in the same way every time: they announce that news exists instead of delivering it, and the reader has to work out whether any of it applies to them.
Situation
What usually gets sent
What is worth sending
A policy change
Please see the attached updated policy, effective immediately
Time off requests move to the app on October 1. Your balance shows before you ask. Nothing else changes
An office closure
Due to circumstances the office will be closed tomorrow
Office closed tomorrow, March 4. Do not come in. Everyone is paid as normal. Next update by 8am
A new tool
We are excited to announce a new platform to streamline our processes
Shifts are published in the app from Monday the 6th. The printed sheet stops. Sign in once before Friday
Someone leaving
We wish Marcus all the best in his future endeavors
Marcus leaves on the 28th. His open jobs go to Dana, his invoicing to Priya. Send anything in flight to Dana this week
A hard week
Thanks to everyone for their hard work during this period
Last week we ran three crews short and still closed every job. Priya covered two routes on Thursday without being asked
The right-hand column is not better writing. It is a decision to put the specific thing in the message instead of a description of the category the thing belongs to. Every one of those rows got shorter, and every one of them answers the question the reader was going to ask anyway.
The Weekly Team Update
A weekly team update is a short written summary, sent the same day and time each week, covering what happened, what is next, and what is stuck. Fixed sections in a fixed order are what make it skimmable, and skimmable is what makes it survive.
Section
What goes in it
What kills it
Headline
One line: the single thing to remember from this week
Inventing one on a quiet week. Say it was quiet instead
The numbers
Three to five figures, same order, with last week beside them
Changing which numbers appear, so nobody learns to read the trend
What got done
Finished things only, with the person named
Listing work in progress, which makes the section meaningless
What is next
Each line with an owner and a date
Lines with no owner. Those are wishes, not plans
What is stuck
The blocker, who is blocked on it, what would unblock it
An empty blockers section every week. Everyone knows
Decisions and changes
Anything decided that changes what somebody does
Burying a decision in prose so it cannot be found later
People
Starters, leavers, absences, and one specific call-out
A general thank you to everybody, which lands on nobody
One ask
One thing you want back from the reader this week
Five asks, which produce zero replies
Fifteen minutes is the cap that matters. An update that takes forty minutes to write is competing with work that has a customer attached, and it loses by about week six. If it will not fit inside fifteen minutes, cut a section rather than skipping a week.
Why the Rhythm Beats the Polish
Gallup reports that employees whose managers hold regular meetings with them are almost three times as likely to be engaged as employees whose managers do not, and that engagement is highest where there is some form of daily contact, whether face to face, by phone, or digital (Gallup). The written weekly update is the cheapest way a small business gets close to that: predictable, short, and the same shape every time, so people know where to look rather than deciding whether to open it.
The written update does not replace the conversation, and it works best when it is not trying to. Use it to carry information, so the meetings you do hold are spent on the things a document handles badly.
Subject Lines and Send Times
The subject line is the only part of an internal email that everybody reads, so it should contain the news rather than announce that news exists. Around eight words, with the change, the date, and whether action is needed.
Situation
Subject that gets opened last
Subject that works
Policy change
Important update
Expense policy changes April 1, please confirm
Closure
Weather advisory
Office closed tomorrow, March 4, do not come in
New process
Exciting news about our operations
Shifts move to the app Monday the 6th
Benefits
Annual enrollment information
Benefits enrollment closes November 14, action needed
Meeting
Team meeting
All-hands Thursday 3pm, agenda inside
Weekly update
Weekly newsletter, issue 14
Week of March 13: intake form live, callbacks down
Send times matter less than people think, with two exceptions worth holding. Anything that changes what somebody does on Monday should not arrive late on Friday, because the questions will sit unanswered all weekend and arrive as anxiety. And anything urgent goes to the channel people read on a bad day, which for frontline staff is rarely email.
The other rule is repetition. A single send reaches the people who happened to be looking that morning, so anything that changes behavior goes out two or three times, in different places, across a week. That is not nagging. It is the difference between a message being sent and a message being received, and it is what a wider internal communication strategy is mostly built to solve.
Three Lines to Keep Out
Three sentences show up in small business internal emails regularly, and each one creates a problem the writer did not intend. None of them is worth the convenience.
Please Keep This Between Us
A line telling employees not to discuss a change among themselves is a poor bet in a message about pay, hours, or working conditions. Federal law provides that employees shall have the right to self-organization, to form, join, or assist labor organizations, to bargain collectively through representatives of their own choosing, and to engage in other concerted activities for the purpose of collective bargaining or other mutual aid or protection (29 U.S.C. 157). Those protections are not limited to unionized workplaces. If genuine confidentiality is needed, such as customer data or an unannounced acquisition, say what specifically is confidential and why. This is general information, not legal advice.
The second is the medical detail. Announcing that somebody is out is routine; announcing why they are out is not yours to share, however small and close the team is.
Sarah Is Out for Surgery
The ADA requires an employer to treat any medical information obtained from a disability-related inquiry or medical examination, as well as any medical information voluntarily disclosed by an employee, as a confidential medical record, which may be shared only with supervisors, managers, first aid and safety personnel, and government officials investigating ADA compliance (EEOC enforcement guidance). In practice that means the message says who is covering the work and until roughly when, and says nothing about the reason. If the person wants their colleagues to know, they can tell them. This is general information, not legal advice.
The third is silence on pay. A closure message that does not say whether people are being paid produces more anxiety than the closure did, and for salaried exempt staff the answer is usually already settled by law rather than by choice.
We Will Come Back to You on Pay
Under the Department of Labor guidance on furloughs and reductions in hours, deductions may not be made from the employee's predetermined salary for absences occasioned by the employer or by the operating requirements of the business, and if the employee is ready, willing, and able to work, deductions may not be made for time when work is not available (DOL Fact Sheet 70). Hourly staff and full-week shutdowns work differently and several states add their own reporting-time rules, so confirm your own position. Then put the answer in the message rather than leaving it out. This is general information, not legal advice.
Sending These Without an HR Department
Every internal communications playbook assumes somebody whose job this is, a design tool, and an approval chain. At twenty people it is the owner on a Thursday, between two other things, and the same three failures show up every time.
The update starts weekly and is monthly by April
The cause is almost never lack of interest. It is that the first few took forty minutes each, because nobody had decided what goes in them, so week six arrives during a busy stretch and the update loses to something with a customer attached. The fix is structural: fixed sections in a fixed order, three numbers you can pull in two minutes, and a fifteen-minute cap. If it will not fit in fifteen minutes, cut a section rather than skipping the week.
Half the team never saw the announcement
Email reaches the people who sit at a desk. On a mixed team it reaches maybe half, and the half it misses is usually the half the announcement was about. Pick the channel by who you need to reach rather than by what is convenient to send, send anything that changes behavior more than once, and put a printed copy where the people without a company inbox already look. A message sent properly to the wrong channel has not been sent.
Everything sounds urgent, so nothing does
When every message opens with an important update, people learn that the phrase carries no information and start triaging by sender instead of subject. Reserve urgency for things that are actually urgent, keep routine news inside the weekly update rather than sending it separately, and give the truly urgent messages a shape of their own so they are recognizable in a list. Scarcity is what makes a subject line work.
The practical answer is smaller than it looks. One fixed weekly update with a fifteen-minute cap, announcements that lead with the news, and a second send a week later for anything that changes what people do.
If the same question keeps arriving after every message, that is a channel problem rather than a writing problem, and team communication is the wider ground it sits on. Applicant tracking is coming soon to FirstHR.
Send It, Confirm It, File It
The templates work on their own, filled in and sent. What tends not to work is what happens after the send: the acknowledgment nobody collected, the second send nobody scheduled, and the announcement that changed a rule but never reached the document holding that rule.
Tell the affected people first
Anyone whose own job changes hears it in a conversation, then managers, then everybody. Nobody should learn something about their own work from a message addressed to a group.
Ask for an acknowledgment on anything that binds
A read receipt is not agreement and an open rate is not a record. For policies and anything with a deadline, ask for a reply or a signature and chase the gap the next day.
Move the final version into the handbook
The message is temporary; the rule it created is not. If the only copy lives in a channel that scrolls, the answer in six months is a search rather than a lookup.
Send it again in a week
Anything that changes what people do needs sending two or three times. The second send is not nagging, it is the one that reaches the people who were busy on the first.
The filing step is the one people find pointless until they need it. Somebody asks in October what the expense rule is, and the honest answer is that it is in a message from April that three people can still find. Moving the final version into the employee handbook turns that into a lookup.
That is the part FirstHR handles around the messages. The announcement and the policy it changed sit in document management with a version history, acknowledgment comes back e-signed and dated against the right person, the self-service portal means people can find the current version without asking anybody, and the follow-up steps become assigned tasks with owners rather than good intentions. Applicant tracking is coming soon to FirstHR.
To be clear about scope, FirstHR is an onboarding and HR platform, not a messaging tool, not a payroll provider, and not a law firm. It does not run your team channel, decide whether a closure is paid, or write the message for you. It holds the record and the tasks around it, so pair it with the channels your team already uses. Applicant tracking is coming soon to FirstHR.
Key Takeaways
An internal announcement needs six parts: a subject that states the news, the whole story in sentence one, what is changing, what to do by when, what is not changing, and a named person to ask.
Write the news as one paragraph before you open the email. If it will not come out cleanly, the decision behind it is not finished.
Tell anyone personally affected in a conversation, brief managers a day early, then send to everybody.
A weekly team update works when it has fixed sections, a fixed send time, and a fifteen-minute cap. The blockers section is what makes it worth reading.
Anything that changes behavior goes out two or three times, on the channel the people it affects actually read.
Keep three lines out: do not discuss this, the medical reason for an absence, and silence on whether a closure is paid. This is general information, not legal advice.
Frequently Asked Questions
What should be included in an internal communication email?
Six things, in this order. A subject line that states the actual news rather than announcing that news exists. A first sentence carrying the whole story, so a reader who stops there still knows whether it affects them. What is changing, concretely, with dates. What the reader has to do and by when, or a plain statement that there is nothing to do. What is not changing, which is where you name the obvious fears about pay, hours, and schedules and close them. And a named person to ask, plus where the information will live once the message has scrolled away. Most internal emails that fail have all the facts and are missing the fourth and fifth items, which is why they generate a week of the same question.
How do you write a company announcement email?
Write the news in one paragraph before you open the email. What is changing, why, when, what people do differently, and what is not changing. If that paragraph will not come out cleanly, the decision behind it is not finished, and announcing into that gap costs more than waiting a day. Then tell anyone personally affected in a conversation, brief the managers who will be asked first, and only then send to everybody. In the message itself, lead with the news rather than the reasoning, number any actions with dates, name one person to reply to, and say where the final version will live. Read the first sentence on its own before you send: if it does not carry the whole announcement, rewrite it.
What is a weekly team update and what goes in it?
A weekly team update is a short, fixed-format written summary sent on the same day every week, covering what happened, what is next, and what is blocked. Eight sections work well: a one-line headline, three to five numbers with last week beside them, what got done with people named, what is next with owners and dates, what is stuck and who is stuck on it, decisions that change what somebody does, a people section for starters, leavers, and absences, and one specific ask. The blockers section is the one that makes it worth reading, and an update whose blockers are empty every week is not being written honestly. Cap it at fifteen minutes to write, because that is what determines whether it survives past month two.
How often should you send internal updates?
Give it a rhythm rather than a volume target. For most small businesses a weekly written update plus a monthly conversation about how the business is actually doing covers it, with announcements sent separately when there is something to announce. Predictability matters more than frequency: an update that arrives every Friday at four is read, and a better one that arrives whenever there is time is not. Skipping a week is fine as long as you say you are skipping it, because disappearing without a word teaches people the whole thing was optional. Anything that changes what people do is the exception to the rhythm and needs sending two or three times regardless, since a single send reaches only the people who were paying attention that morning.
Should an announcement go by email or team chat?
Choose by who you need to reach and what has to survive. Email reaches desk-based staff reliably, holds detail well, and leaves a record you can point at later, which makes it the right home for policy changes and anything with a deadline. Team chat is faster and better read on a phone, which makes it right for same-day operational news, but it scrolls and it is a poor place for anything you might need to prove was sent. On a mixed team neither one reaches everybody, so frontline and hourly staff usually need a third route: a printed sheet where they already look, a message read out at the shift huddle, or a text. The practical rule is one channel to carry the message and one place to hold the record, and they do not have to be the same.
Do employees have to acknowledge an internal announcement?
Not for routine news, and yes for anything you would want to prove was received. Read receipts and open rates are not records: they tell you a message was displayed, not that a person read or understood it. For policy changes, safety instructions, and anything carrying a deadline, ask for an explicit reply or a signature, make clear that acknowledging means the person has read the policy rather than agreed with every part of it, and track who has responded. Set a date, chase the gap once in writing, and turn the remaining names into a conversation rather than a third email. Acknowledgment captured electronically with a timestamp against the right person is considerably easier to produce later than a folder of paper.
What should you never put in an internal announcement email?
Three things in particular. Anything medical about a named person, because the ADA requires employers to treat medical information as a confidential record shared only in narrow circumstances, so an absence is announced without the reason. Any instruction telling employees not to discuss the change among themselves, since federal law protects the right of employees to engage in concerted activities for mutual aid or protection, and a blanket confidentiality line in a message about pay or working conditions is a poor place to test where the boundary sits. And speculation, whether about a cause, an outcome, or somebody’s future, because an internal message is forwarded more often than people expect. Say what you know, say when you will know more, and leave the rest out. This is general information, not legal advice.
Are these internal communication email templates free to download?
Yes. All six download free with no email form and no account: five as editable Word documents and one as an Excel workbook with three tabs. Taking all six at once gives you a single zip file with each one inside it separately. That is worth mentioning, because many of the most widely linked internal communication template packs sit behind a registration form or open only inside a vendor product. Free does not mean finished, though. Fill in the brackets, delete the sections that do not apply, and change anything that does not sound like you, because a message that reads as though it came from a template is worse than a short one that reads as though it came from a person the team knows.
