Managing a team? Your emails set the tone for your entire department. Here are templates every manager needs.
Template 1: Monday Kickoff Email
Subject: This Week's Priorities - [Date Range]
Team, Happy Monday! Here's what we're focused on this week:
Top Priorities: 1. [Priority 1] - Owner: [Name] - Due: [Date]. 2. [Priority 2] - Owner: [Name] - Due: [Date]. 3. [Priority 3] - Owner: [Name] - Due: [Date].
Quick Wins from Last Week: [Shoutout to team member] for [accomplishment]. Let's have a great week!
Template 2: Project Status Update
Subject: [Project Name] - Status Update [Date]
Completed: [Task 1], [Task 2]
In Progress: [Task 3] - [Name] - ETA: [Date]
Blocked/Needs Attention: [Issue] - Need [specific action] from [Name/team]
Next Steps: [What's happening next and when]
Template 3: Announcing a Change
Subject: Important Update - [Brief Description]
What's Changing: [Clear, specific description]
Why: [Honest explanation - people handle change better when they understand the reason]
When: [Effective date and transition timeline]
What This Means for You: [Specific impacts and what they need to do differently]
I'm hosting a Q&A on [date/time] and my door is always open.
Internal Email Is a Management Instrument
Externally, email persuades. Internally, it aligns — it tells people what changed, what is expected, and what they should do differently on Monday. Judged that way, most internal email fails not because it is impolite but because the reader finishes it unsure what, if anything, they are supposed to do.
Three Labels That Fix Most of It
Tell people at the top which kind of message this is:
- FYI — no action needed, read when convenient.
- Action needed by [date] — and say exactly what and from whom.
- Decision made — here is what changed and why.
Putting one of these in the subject line eliminates most internal follow-up traffic on its own.
Announcing a Change People Will Not Like
- State the change plainly in the first line. Do not build up to it — people scroll for it and resent the preamble.
- Give the real reason. A sanitized reason invites speculation that is always worse than the truth.
- Say precisely what is different day to day.
- Say what is not changing. This is reassuring and almost always omitted.
- Name where questions go, and answer them for real.
Recognition That Means Something
Generic praise devalues quickly. Name the person, name what they did, and name the effect it had. "Marisol rebuilt the intake sheet last week and the Friday backlog was gone by Tuesday" is worth more than a paragraph about how great everyone is. Send it to the group when the work was visible; send it privately when the person would rather not be singled out.
Performance and Feedback Belong in Conversation
Email is a poor instrument for corrective feedback: it lands without tone, it cannot answer questions, and it becomes a permanent record of a conversation that had not happened yet. Have the conversation, then send a short written summary of what you agreed — expectation, support, date for the next check-in. The summary protects both people.
Recurring Updates That People Read
A weekly team update earns its place if it is short and always the same shape: what shipped, what is blocked and who is unblocking it, what is coming next week, and anything the team needs to know from elsewhere. Same format, same day, ruthlessly short. Predictable beats comprehensive — a long update is skipped, and a skipped update is not communication.
Volume Is a Management Decision
Every message you send sets a norm for how much internal email is acceptable. If people are drowning, the fix is not better subject lines — it is sending less. Ask of each message: does this need to exist, does it need everyone, and does it need to be email rather than a note where the work already lives?