Communications Plan Template — Examples, Outline & Internal Comms Structure
Most communication problems aren't about what was said — they're about what wasn't planned. The wrong audience, the wrong channel, the wrong timing, or no clear owner. A communications plan fixes all of that before the message goes out rather than after it goes wrong. Preview the template below or use the interactive version in FigJam.
What is a communications plan?
A communications plan is a strategic document that outlines who needs to be communicated with, what they need to know, through which channels, and by when. It's used for projects, organisational changes, product launches, and ongoing internal communications programmes. A good communications plan ensures that the right message reaches the right audience at the right time — reducing the information gaps, repetition, and confusion that make communication feel chaotic in most organisations.
The fundamental problem a communications plan solves is that different audiences need different information. What the engineering team needs to know about a product launch is different from what the customer success team needs to know, which is different from what the whole company needs to know. A plan maps those distinctions before communication happens so that each audience receives what's relevant to them, in the format and channel most likely to reach them.
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 build a communications plan that actually gets used
Start with the objective, not the channels
The most common communications planning mistake is starting with the medium — "we'll send an email and post in Slack" — before clarifying what the communication needs to achieve. The objective comes first: is this communication designed to inform, to align, to change behaviour, or to recognise? The answer determines everything else — who the audience is, what the key message needs to be, which channel is appropriate, and what success looks like.
Map audiences before messages
Different stakeholders need different information, framed differently. A change that affects the whole organisation might require five distinct communications: one for leadership who need strategic context, one for managers who need to know how to communicate it to their teams, one for affected employees who need practical implications, one for the broader team who need enough context to avoid rumours, and one for external stakeholders if relevant. Mapping the audiences before drafting messages prevents the common failure of sending one communication that serves nobody particularly well.
Write the key messages before the copy
A key message is not a paragraph of communication — it's the one thing each audience must take away from the communication if they read or hear nothing else. Writing the key messages first, before drafting any actual copy, forces clarity about what the communication is really for. If you can't summarise the key message for each audience in one sentence, the communication isn't ready to be written yet.
Assign an owner to every communication
A communications plan without owners is a wish list. Every planned communication should have a named person responsible for drafting it, reviewing it, sending it, and following up if it doesn't land. The owner doesn't have to do all of these things alone — but they need to be accountable for each one happening. Shared responsibility without a named owner is how communications get missed.
Include recognition as a planned touchpoint
The communications plans that drive the highest employee engagement are the ones that build recognition in deliberately — not as an afterthought but as a planned communication moment. An organisation-wide update that names the teams and individuals who made something happen, a project close-out communication that specifically recognises the contributions that were invisible during the process, an appreciation week campaign that's planned with the same rigour as a product launch — these are the moments where communication and culture intersect. If your organisation uses Karma for peer recognition, the communications plan is the right place to schedule these moments: recognition campaigns, milestone announcements, and appreciation highlights that amplify what's already happening in Slack into the broader communication rhythm of the organisation.
Build in a feedback loop
A communications plan that doesn't measure whether the communication landed is blind. Build in a simple feedback mechanism for every significant communication: a reply option, a one-question survey, a scheduled follow-up meeting, or simply a check-in conversation with someone in each audience group. The question isn't just "did they receive it?" — it's "did they understand it, and did it change anything?"
40 communications plan examples and content ideas
Use these across internal projects, change management, recognition programmes, and ongoing team communications.
Project and initiative communications
Organisational change communications
Recognition and appreciation communications
Team and internal communications
Stakeholder and cross-functional communications
Why recognition belongs in every communications plan
Most communications plans cover the operational and informational: what's happening, what's changing, what people need to do. Almost none treat recognition as a planned communication moment — and it's the element with the highest impact on engagement and culture.
Recognition isn't something that should happen when there's time for it. It should be scheduled with the same discipline as a product launch announcement or a quarterly all-hands. Employee Appreciation Day, appreciation week, milestone recognition moments, project close-out shoutouts — these are all planned communications that need an audience, a channel, a message, an owner, and a timeline. When they're in the communications plan rather than left to individual managers to remember, they happen consistently. And consistency is what turns appreciation from a nice gesture into a cultural norm.
The teams using Karma for peer recognition have a structural advantage here: the recognition data already exists in Slack or MS Teams. The communications plan decides when and how to amplify it — into the newsletter, the all-hands, the announcement channel — so that what happens between individuals becomes visible to the organisation. The peer kudos sent on a Tuesday afternoon becomes the recognition highlight in the Friday update, the monthly newsletter, and the quarterly team retrospective. That amplification is a communications decision, not a recognition decision. And it belongs in the plan.
Frequently asked questions
What is a communications plan?
A communications plan is a strategic document that outlines who needs to be communicated with, what they need to know, through which channels, and by when. It's used for projects, organisational changes, product launches, and ongoing internal communications programmes. A good communications plan ensures the right message reaches the right audience at the right time — reducing the information gaps and confusion that make communication feel chaotic.
What should a communications plan include?
A communications plan should include: the communication objective, the target audiences and what each group needs to know, the key messages for each audience, the channels through which each message will be delivered, the owner responsible for each communication, the timeline or cadence, and a way to measure whether the communication was received and understood. For internal communications specifically, a recognition component significantly increases the plan's impact on engagement.
What is the difference between a communications plan and a communications strategy?
A communications strategy defines the overall approach — the principles, priorities, and long-term direction of how an organisation communicates. A communications plan is the tactical document that executes against that strategy for a specific initiative, project, or period. The strategy answers "how do we communicate as an organisation?"; the plan answers "what are we communicating, to whom, through which channels, and by when?" for a specific context.
How do you write a communications plan?
Start with the objective — what does this communication need to achieve? Then identify the audiences and what each group specifically needs to know. Define the key messages for each audience — the one thing each group must take away. Choose appropriate channels based on audience and urgency. Assign an owner to each communication. Set a timeline. Build in a way to know whether the communication landed — a response mechanism, a survey, or a follow-up conversation.
How often should you update a communications plan?
For project-based plans, review at each major milestone — priorities shift, audiences change, and messages that were relevant at the start are often different from what matters at delivery. For ongoing internal communications plans, a quarterly review is sufficient to assess whether the cadence, channels, and content are still working. The clearest signal that a plan needs updating is when audiences stop engaging — low open rates, unanswered messages, or repeated questions about things that were already communicated.
How does a communications plan support employee engagement?
A communications plan improves employee engagement by reducing the information asymmetry that makes people feel out of the loop and undervalued. When employees consistently receive timely, relevant, and honest communication about decisions that affect them, trust in leadership improves and engagement follows. The most impactful communications plans also include recognition as a deliberate touchpoint — naming specific contributions and making appreciation visible across the organisation at planned moments rather than leaving it to chance.
Other templates
One-on-one Meeting Template
Run productive one-on-one meetings with a structured agenda for feedback, goal tracking, and employee development.
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.
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:
- Google — Google Analytics 4 and Google Tag Manager, for website traffic analytics (https://policies.google.com/privacy)
- Meta (Facebook) — Meta Pixel, for advertising measurement (https://www.facebook.com/privacy/policy/)
- Ahrefs Web Analytics — privacy-focused website traffic analytics (https://ahrefs.com/legal/privacy-policy)
- ProfitWell (Paddle) — subscription and revenue analytics (https://www.paddle.com/legal/privacy)
- MailerLite — newsletter sign-up forms (https://www.mailerlite.com/legal/privacy-policy)
- Calendly — demo and meeting scheduling (https://calendly.com/legal/privacy-notice)
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:
- Commissioner for Personal Data Protection
- 1 Iasonos Street, 1082 Nicosia, Cyprus
- Email: commissioner@dataprotection.gov.cy
- Web: https://www.dataprotection.gov.cy
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.
Links to other sites
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