Newsletter Template — Internal Team Newsletter Examples & Structure | Karma
Sign up

Newsletter Template — Internal Team Newsletter Examples & Structure

Most internal newsletters go unread. The ones that get opened, forwarded, and talked about are the ones that carry something worth knowing — a specific update, a named recognition, a human moment that makes the reader feel like they're part of something rather than being communicated at. Preview the template below or use the interactive version in FigJam.

Get all templates
Use this free template

Updated

July 2026

Ready to Use

Available in FigJam

What is an internal newsletter?

An internal newsletter is a regular communication sent to employees that shares company updates, team news, recognition highlights, and other information relevant to the organisation. It's one of the most consistent tools for keeping distributed, hybrid, or fast-growing teams informed and connected — particularly when what it carries is specific, relevant, and worth reading rather than the kind of generic corporate communication that gets deleted without opening.

The key distinction between an internal newsletter that works and one that doesn't is editorial intent. A newsletter written to communicate — to share things the audience genuinely needs or wants to know — gets read. A newsletter written to demonstrate that internal communications is happening does not. The template below is built around the first intention.

See the Template in Action

Explore the template below to see how it's structured. To use the fully editable version, open it in FigJam, where you can copy, customise, and collaborate with your team.

How to write an internal newsletter people actually read

Lead with what matters most, not what's most formal

The default internal newsletter structure opens with a message from leadership, followed by company updates, followed by the content people actually wanted to read. Reverse it. Lead with the most relevant and engaging content — a recognition highlight, a team win, a specific update that affects people's work — and put the formal leadership message further down if it's needed at all. People open newsletters in the same way they scan a newspaper — headline first, the rest only if the headline earns it.

Keep it short enough to read in three minutes

The internal newsletters with the highest open and engagement rates are consistently the shortest ones. Three minutes is the practical maximum for a voluntary read in a workday. If the content can't fit in three minutes, it's either too much information for a single issue or it's not sufficiently edited. A useful editorial test: if you could cut a section without anyone missing it, cut it.

Name people specifically

The single highest-engagement element in any internal newsletter is a named recognition of a specific person for a specific contribution. Not "the team did a great job on the product launch" — "Yuki rewrote the API documentation over a single weekend so the launch could happen on schedule, and nobody outside the team knew it needed doing." Named, specific, public appreciation gets read, forwarded, and talked about in a way that general updates never do.

Use a consistent format

Readers build habits around reliable structures. When the recognition section is always in the same place, people scroll directly to it. When the company update is always brief and at the top, people trust they're not missing anything if they skim. Consistency also reduces the production time significantly — the editor is filling a known structure rather than redesigning from scratch each month.

Write like a person, not a communications department

The voice of an internal newsletter is the biggest differentiator between the ones people read and the ones they don't. Passive voice, corporate jargon, and third-person references to "the organisation" signal that the newsletter is produced rather than written. Active voice, first-person ownership of the content, and a genuine editorial point of view signal that a person made decisions about what to include and why — which is the experience that builds readership.

Include a recognition digest from Slack

If your team uses Karma for peer recognition, the monthly recognition feed is ready-made newsletter content. The top kudos from the past month — pulled directly from the Karma dashboard — become the recognition section of the newsletter with minimal editorial effort. The peer appreciation that happened in the team channel gets amplified to the whole organisation, and the people who gave and received recognition see their contributions acknowledged at a wider scale.

40 internal newsletter content ideas

Use these to fill any section of the newsletter — organised by content type.

Company and leadership updates

What changed in company strategy, direction, or priorities this month
A decision that leadership made — and the reasoning behind it
Progress on a company-wide goal or OKR — where we are vs where we expected to be
A market or industry development that affects the organisation
A hiring update — who joined, who was promoted, what the team structure looks like now

Team and project highlights

A project that shipped, launched, or reached a milestone
A team that solved a hard problem — with enough specificity that the reader understands what made it hard
A behind-the-scenes look at work that's usually invisible to the rest of the organisation
A cross-functional collaboration that produced something neither team could have done alone
An early result or signal from something the company is experimenting with

Recognition and appreciation

The top peer kudos from the past month — named, specific, pulled from Karma or another recognition source
A milestone recognition: workiversaries, anniversaries, or tenure milestones reached this month
A manager shoutout to a team member for something that deserved more visibility than it got
A customer or client quote that names a specific employee's contribution
A "recognition spotlight" — one person, one paragraph, one specific thing they did that made a difference

People and culture

A new employee introduction — with something personal, not just their job title
An employee Q&A — three questions answered by someone the organisation doesn't usually hear from
A values story — a specific example of a company value being lived in practice
A wellbeing resource, reminder, or initiative that's actually relevant to people's lives
A team tradition, ritual, or culture moment worth sharing with the wider organisation

Learning and development

A resource that's genuinely worth reading, watching, or listening to — with one sentence on why
A course, tool, or framework someone on the team has found useful
A lesson learned from something that didn't go as planned — written honestly
An event, conference, or community the team is participating in
A skill or capability the organisation is building — and why it matters

Operational and practical

An upcoming date or deadline that affects the whole organisation
A policy or process change — explained clearly, not just announced
A tool or system update that changes how people work
An FAQ on something people have been asking about
A reminder about a benefit, resource, or programme that exists but goes underused

Engagement and participation

A question the editorial team genuinely wants answered — with a way to respond
A poll or vote on something lightweight and relevant
An invitation to contribute to the next issue — a nomination for recognition, a project highlight, a resource recommendation
A call for volunteers or participants in something specific
A feedback prompt — what do you want more of in this newsletter?

Why recognition is the most important section of any internal newsletter

Most internal newsletters treat recognition as a nice-to-have — a section that gets cut when there's too much to fit, or filled with the same names every month because nobody maintains a systematic record of who did what.

Recognition is consistently the highest-engagement element in internal newsletters, for a straightforward reason: people read to see if they or someone they know has been mentioned. The section that names a specific person for a specific contribution gets forwarded, screenshot, and talked about in a way that no company update ever does.

The practical challenge is that gathering recognition content takes effort. The easy solution is to pull it from where it already lives. If your organisation uses Karma for peer recognition in Slack or MS Teams, the past month's kudos feed is a ready-made recognition digest. The specific, genuine peer appreciations that happened in the team channel become the newsletter's recognition section — amplified to the whole organisation, with minimal editorial overhead.

This is the connection between daily peer recognition and periodic communication: the kudos given in Slack on a Tuesday afternoon becomes visible to the whole company in the monthly newsletter. The person who received it sees their contribution acknowledged twice — once in the moment, once at scale. The organisation sees, repeatedly, what its people value about each other. Over time, this shapes culture more reliably than any values statement.

Frequently asked questions

What is an internal newsletter?

An internal newsletter is a regular communication sent to employees that shares company updates, team news, recognition highlights, and other information relevant to the organisation. It's one of the most effective tools for keeping distributed or hybrid teams informed and connected — particularly when the information it carries is specific, relevant, and worth reading rather than generic corporate communication.

What should an internal newsletter include?

An effective internal newsletter typically includes: a brief company or leadership update, team or project highlights, a recognition section naming specific contributions, upcoming events or dates, a resource or read worth sharing, and a closing human moment. The recognition section is the highest-engagement element in most internal newsletters — it's where people scroll first and spend the most time.

How often should you send an internal newsletter?

Monthly is the most common cadence for internal newsletters — frequent enough to stay relevant, infrequent enough that the content has time to accumulate. Weekly works for smaller, fast-moving teams where there's genuinely enough to report each week. Whatever the cadence, consistency matters more than frequency — a newsletter that arrives reliably on the first Monday of every month builds the habit of being read.

How do you write an internal newsletter people actually read?

The newsletters people read are the ones that feel like they were written for them specifically. Keep it short enough to read in under three minutes, lead with the most relevant information rather than a formal foreword, include named recognition of specific people and contributions, use a consistent format so readers know what to expect, and write in a human voice rather than corporate communication language. The recognition section consistently produces the highest engagement because people read to see if they or someone they know has been mentioned.

What is the difference between an internal newsletter and an employee engagement survey?

An internal newsletter is an outbound communication — sharing news, updates, and recognition. An employee engagement survey is an inbound tool — collecting information from employees about how they feel about their work. They serve complementary purposes — the newsletter communicates and recognises, the survey listens and measures. The most effective internal communications strategies use both.

How does an internal newsletter support employee recognition?

The internal newsletter is one of the highest-reach recognition vehicles available to any organisation — it reaches every employee, in every location, at the same time. A dedicated recognition section that names specific contributions, celebrates milestones, and highlights peer kudos from the past month makes appreciation visible at scale. Teams using Karma can pull directly from their recognition feed for this section — the kudos given in Slack become the recognition highlights in the newsletter, extending peer appreciation beyond the team channel to the whole organisation.

Other templates

One-on-one Meeting Template

Run productive one-on-one meetings with a structured agenda for feedback, goal tracking, and employee development.

MeetingsWorkshopsManagement

Team Charter Template

Define your team's purpose, roles, values, and working agreements to improve collaboration and accountability.

MeetingsWorkshopsBrainstorming

Icebreaker Template

Kick off meetings and workshops with engaging icebreaker activities that help teams connect and communicate.

MeetingsManagement
View all

Ready to get started?

If you're ready to get started with Karma, sign up now and explore the benefits of the recognition for your team. You can also reach out for a free demo.

Add Karma to Slack
Free demo

Karma bot privacy policy

Effective date: 18 August 2026

This Privacy Policy explains how Sliday LTD ("Sliday", "we", "us", or "our") collects, uses, shares, and protects personal data. It covers both the Karma application (for Microsoft Teams, Slack, Telegram, and the web) and the https://karmabot.chat website.

Who we are and how to contact us

The data controller is Sliday LTD, a private limited company registered in Cyprus under company number HE450506, with its principal place of business at Pavlou Valdaseridi 2A, 1st floor, Larnaka, Cyprus, 6018.

For any privacy-related enquiry, or to exercise your data protection rights, contact us at hi@karmabot.chat.

Privacy matters are overseen by our Legal Advisor / Operational Security Manager, Stas Kulesh. A dedicated Data Protection Officer has not been appointed, as Sliday LTD is not required to appoint one under Article 37 of the GDPR; privacy responsibilities are held by the Legal Advisor.

Personal data we handle and where it comes from

From the Karma application

When your organisation installs and uses Karma, we process the following personal data, obtained from Microsoft Teams / Microsoft Entra ID (Azure AD) and from your use of the application:

  • Display name — from Microsoft Teams / Microsoft Graph
  • Email address — from Microsoft Teams / Microsoft Graph
  • User Principal Name (UPN) — from Microsoft Graph (/me)
  • Microsoft Entra (Azure AD) object ID and tenant ID — from Microsoft authentication
  • Profile photo — from Microsoft Graph (/me/photo)
  • Team and channel names — from Microsoft Teams
  • Karma activity (karma given and received, associated messages) — from your use of the app

Where Karma is used with Slack or Telegram, the equivalent identity and workspace data is obtained from that platform instead.

From this website

  • Contact details you give us — such as your email address and name when you subscribe to updates, request a demo, or contact support
  • Usage and device data — IP address, browser type and version, pages visited, date, time and duration of visit, referring page, and similar diagnostic data
  • Cookies and similar technologies — see "Cookies and website analytics" below

Why we process personal data

We process personal data to:

  • Identify you and link you to your organisation's Karma workspace
  • Operate the core recognition ("karma") features, leaderboards, and adaptive cards
  • Display your name and profile photo within the app
  • Deliver notifications and service communications
  • Administer subscriptions and billing
  • Provide customer support and respond to your enquiries
  • Monitor, secure, maintain, and improve the service, and detect and address technical issues
  • Send newsletters, marketing, or promotional material where you have chosen to receive it — you can opt out at any time via the unsubscribe link in any email, or by contacting us

Lawful basis for processing

We process personal data on the following lawful bases under the GDPR:

  • Performance of a contract — to provide the Karma service to your organisation
  • Legitimate interests — to operate, secure, and improve the service, where not overridden by your rights
  • Consent — for marketing communications and for non-essential cookies and analytics, where consent is required
  • Legal obligation — where we are required by law to retain or disclose data, including for tax and accounting purposes

Where your organisation is the controller and we act as processor, processing is carried out on your organisation's documented instructions.

Who we share personal data with

We share personal data only with the sub-processors listed below, each of which is necessary to deliver the service and is engaged under an appropriate data processing agreement. This is the complete list of sub-processors with access to personal data. We do not sell personal data.

Service sub-processors

  • DigitalOcean — application hosting and managed database
  • Amazon Web Services (AWS) — profile photo storage (S3)
  • Cloudflare — edge delivery and web application firewall
  • Microsoft — authentication, the Teams platform, and Microsoft Graph
  • Stripe — subscription billing and payment processing
  • Sentry — error monitoring
  • MailerLite — notification and marketing email delivery

We do not store or collect your payment card details. That information is provided directly to Stripe, our payment processor, whose use of your personal information is governed by its own privacy policy (https://stripe.com/privacy). Stripe adheres to the standards set by PCI-DSS as managed by the PCI Security Standards Council.

Website analytics and marketing providers

The https://karmabot.chat website additionally uses:

We may also disclose personal data where required to do so by law or in response to a valid request by a public authority, or where necessary to protect our legal rights, prevent or investigate wrongdoing, or protect the safety of users or the public.

Cookies and website analytics

Cookies are small pieces of data stored on your device. We use cookies and similar technologies (including beacons, tags, and scripts) to operate the website, remember your preferences, keep the service secure, and understand how the site is used.

The cookies we use fall into these categories:

  • Essential cookies — required to operate the website and keep it secure
  • Preference cookies — to remember your settings and choices
  • Analytics and marketing cookies — set by the providers listed above to measure traffic and advertising performance

You can instruct your browser to refuse all cookies or to notify you when a cookie is set. If you refuse cookies, some parts of the website may not function correctly.

We do not currently respond to browser "Do Not Track" (DNT) signals.

How long we keep personal data

We retain personal data for the duration of your organisation's active subscription and for six (6) months after subscription cancellation, after which it is deleted. This applies to customer account and identity data, profile photos, and karma transaction records.

  • Database backups operate on a rolling 7-day point-in-time recovery window, so any backup containing erased data is automatically superseded within 7 days.
  • Upon a verified data deletion request, we action it as promptly as reasonably possible and in any event within one month, as required by the GDPR.
  • Billing and accounting records may be retained for longer where required by law.
  • Operational data — error telemetry, security logs, and backups — is disposed of automatically as it ages out of the relevant service's retention window.

Full details are set out in our Data Retention and Disposal Policy.

Your data protection rights

Subject to applicable law, you have the right to:

  • Be informed about how your personal data is used
  • Access the personal data we hold about you
  • Rectification — to have inaccurate or incomplete data corrected
  • Erasure — to have your personal data deleted
  • Restriction — to request that we restrict processing of your personal data
  • Data portability — to receive your data in a structured, commonly used, machine-readable format
  • Object to our processing of your personal data
  • Rights relating to automated decision-making and profiling — Karma does not carry out automated decision-making producing legal or similarly significant effects
  • Withdraw consent at any time, where we rely on your consent

To exercise any of these rights, contact us at hi@karmabot.chat. We may ask you to verify your identity before responding.

Making a Subject Access Request (SAR)

To submit a Subject Access Request, contact us at hi@karmabot.chat. We respond to all SARs within one month, as required by the GDPR, unless the request is complex or numerous, in which case we may extend the response time by a further two months and will tell you if we do. We maintain a data mapping process that lets us locate and retrieve all personal data held about a specific data subject across our systems — principally the production database and the profile photo object storage — so that a SAR can be fulfilled thoroughly.

International transfers and safeguards

Karma production data is hosted in the United States (DigitalOcean SFO region). As Sliday LTD is established in the EU (Cyprus), this involves a transfer of personal data to a third country.

Such transfers — and transfers to other sub-processors located outside the EU/EEA, including Microsoft, AWS, Cloudflare, Stripe, Sentry, and the analytics providers listed above — are protected by appropriate safeguards, principally the Standard Contractual Clauses (SCCs) incorporated into each sub-processor's Data Processing Agreement, supplemented by those providers' certification frameworks, including the EU–US Data Privacy Framework where the provider participates.

Sliday LTD takes all steps reasonably necessary to ensure that your data is treated securely and in accordance with this Privacy Policy.

Your right to complain to a supervisory authority

You have the right to lodge a complaint with a data protection supervisory authority.

Our lead supervisory authority is the Office of the Commissioner for Personal Data Protection of the Republic of Cyprus:

You may also lodge a complaint with the supervisory authority in your own country of residence.

Security of data

The security of your data is important to us. We apply technical and organisational measures appropriate to the risk, including encryption in transit, access controls, vulnerability scanning, and error monitoring. However, no method of transmission over the internet or method of electronic storage is completely secure, and we cannot guarantee absolute security.

Children's privacy

Our service is not directed at anyone under the age of 18. We do not knowingly collect personal data from children. If you are a parent or guardian and believe your child has provided us with personal data, please contact us and we will take steps to remove it.

Our service may contain links to sites we do not operate. We have no control over, and assume no responsibility for, the content or privacy practices of any third-party site. We encourage you to review the privacy policy of every site you visit.

Changes to this Privacy Policy

We may update this Privacy Policy from time to time. We will post the updated policy on this page and update the effective date at the top. Where changes are significant, we will notify you by email and/or a prominent notice on our service before the change takes effect. We encourage you to review this policy periodically.

Contact us

If you have any questions about this Privacy Policy, contact us:

  • By email: hi@karmabot.chat
  • By post: Sliday LTD, Pavlou Valdaseridi 2A, 1st floor, Larnaka, Cyprus, 6018