# Communications Plan

The internal comms calendar and ready-to-adapt messages that explain why Clones are coming, answer the replacement question and keep wins visible.

## What this is for

The first thing most employees hear about AI at work is a rumor. If leadership does not explain the why, the what and the "what about my job" early and plainly, the rumor wins and adoption stalls. This plan sets who says what, to whom and when, and gives you messages you can adapt in minutes. The core message never changes: Clones add capacity to teams, and people stay accountable for decisions.

## When to use it

Build it in Month 2, before Department 1 launches. Add a launch wave for every department. Run the recurring items (win stories, Clone of the Month, Champion spotlights) from first results through Month 12.

## Who's involved

- **Executive sponsor** is the voice of the launch announcement and the "why".
- **Business owners** announce their own department launches.
- **Internal communications lead** owns channels and timing.
- **Champions** supply win stories and nominate Clones of the Month.
- **Change & Enablement Lead** owns the plan.

## How to fill it in

1. Agree the three core messages with the sponsor (section 1). Every later message should trace back to one of them.
2. Map audiences and channels (section 2).
3. Fill in the calendar (section 3), anchored to department go-live dates.
4. Adapt each message template (section 4). Replace bracketed text; keep the structure.
5. Route each message through the approvals in section 5 before it goes out.
6. Track reach and response (section 6) and review at the Champions council.

## The template

### 1. Core messages

| # | Message | Proof point |
|---|---|---|
| 1 | **Why:** We are adding AI teammates so our people spend time on the work that needs them. | _Problem statements from the executive briefing_ |
| 2 | **Capacity, not replacement:** Clones take on repetitive work. People stay accountable for decisions. | _Sponsor commitment in the launch message_ |
| 3 | **Safe by design:** InfoSec helped build the rules. Clones earn more independence only with evidence and sign-off. | _Governance Charter; autonomy ladder_ |

### 2. Audiences and channels

| Audience | What they need to hear | Channel | Messenger |
|---|---|---|---|
| All employees | Why, what's changing, capacity not replacement | _All-hands, intranet, email_ | Executive sponsor |
| Launching department | What their Clone does, training dates, where to get help | _Team meeting, Slack channel_ | Business owner + Champion |
| Managers | How to talk to their teams; how to handle concerns | _Manager briefing_ | Sponsor + Change Lead |
| Adjacent teams | What handoffs change and when | _Email, team leads_ | Business owner |
| Works council / employee reps (if applicable) | Purpose, data use, safeguards | _Formal consultation_ | Sponsor + HR |

### 3. Calendar

| Date / trigger | Message | Audience | Channel | Owner | Status |
|---|---|---|---|---|---|
| _2 weeks before Dept 1 launch_ | Manager briefing pack | Managers | Meeting | Change Lead | |
| _1 week before_ | Sponsor launch announcement | All employees | Email + intranet | Sponsor | |
| _Same day_ | Capacity-not-replacement FAQ published | All employees | Intranet | Comms lead | |
| _Launch day_ | Department launch note | Department | Slack | Business owner | |
| _Launch + 30 days_ | First win story | All employees | Newsletter | Champion | |
| _Monthly_ | Clone of the Month | All employees | Intranet + all-hands | Change Lead | |
| _Monthly_ | Champion spotlight | All employees | Newsletter | Change Lead | |
| _Day 90_ | 90-day results summary | All employees | Sponsor email | Sponsor | |

### 4. Message templates

#### 4.1 Launch announcement from the executive sponsor

> **Subject:** Our new AI teammates, and what they mean for you
>
> Team,
>
> Over the next few months we are bringing AI teammates, which we call Clones, into [Company]. They will start in [Department 1] and [Department 2], then roll out to other teams over the year.
>
> **Why we are doing this.** Too much of our week goes to [top problem from the executive briefing, e.g. retyping data between systems and chasing status]. Clones will take on that kind of repetitive work so our people can spend more time on [customers / judgment calls / the work that needs a person].
>
> **What this is not.** This is not a plan to reduce headcount. Clones add capacity to our teams. People stay accountable for decisions, and every Clone has a named owner in the business.
>
> **How we are keeping it safe.** Our InfoSec team helped design the rules before anything went live. Clones start by drafting and suggesting. They only take on more independence after they have proven themselves, and only with sign-off from InfoSec and the business owner.
>
> **What happens next.** Each department will have a Clone Champion, a colleague who will help you get started. You will get short training before your team goes live. Questions are welcome: [channel / FAQ link].
>
> I will be using my own Clone for [morning briefings / meeting prep], and I will share what I learn.
>
> [Sponsor name, title]

#### 4.2 "Capacity, not replacement" FAQ

> **Are Clones replacing people?**
> No. Clones add capacity to teams. They take on repetitive work like [examples]. People stay accountable for decisions.
>
> **What will a Clone do in my team?**
> [Department-specific answer from the Clone Design Spec.] At first it drafts and suggests; you decide.
>
> **Can a Clone act without asking anyone?**
> Only after it has earned it. Every Clone starts at Assist or Recommend. Moving up requires evidence on accuracy and overrides, and sign-off from InfoSec and the business owner. Some actions are never allowed, and those are written down in our Governance Charter.
>
> **What data can it see?**
> Only the systems and data approved for its job by InfoSec. Its actions are recorded in an audit log.
>
> **What if it gets something wrong?**
> You correct it, the way you would correct a colleague's draft. Tell your Champion or use [channel]. Corrections help it improve and are reviewed by the team.
>
> **Will my performance be measured against a Clone?**
> No. We measure the Clone's work, such as accuracy and time given back to the team, not yours against it.
>
> **Who do I ask?**
> Your Champion [name], office hours [time], or [channel].

#### 4.3 Win story

> **Headline:** [Team] gives back [X hours] a week on [task]
>
> **The problem:** [One sentence, in the team's words.]
>
> **What changed:** [Clone name] now [what it does], and [person/role] reviews [what they review].
>
> **The result:** [Metric vs. baseline, e.g. invoice intake time down from 3 days to 4 hours over 6 weeks.]
>
> **In their words:** "[Quote from a team member about what they now spend time on.]"
>
> **Want this for your team?** Talk to [Champion] or [CoE intake link].

#### 4.4 Clone of the Month

> **Clone of the Month: [Clone name], [Department]**
>
> **What it does:** [One sentence.]
>
> **This month:** [Tasks completed], [hours given back], Power Rating [score / trend].
>
> **Why it was nominated:** [Champion's reason, e.g. handled the quarter-end surge with zero escalations missed.]
>
> **The people behind it:** Owned by [business owner], coached by [Champion].

#### 4.5 Champion spotlight

> **Champion spotlight: [Name], [Role], [Department]**
>
> [Name] has helped [N] colleagues get started, published [N] workflows to the library, and runs office hours every [day].
>
> **Favorite workflow:** [Short description.]
>
> **Tip for new users:** "[Quote.]"
>
> **Thanks from:** [Business owner or sponsor, one line.]

#### 4.6 Department launch note (from the business owner)

> Starting [date], [Clone name] joins our team in [channel]. It will [what it does] and will always check with us before [actions requiring approval]. [Champion] is our Champion; training is on [date]. Questions go to [channel].

### 5. Approvals

| Message type | Drafted by | Approved by |
|---|---|---|
| Company-wide | Change Lead / Enablement Clone | Sponsor + comms lead (+ HR if job impact is mentioned) |
| Department | Champion / Change Lead | Business owner |
| Anything mentioning data or security | Change Lead | InfoSec lead |

### 6. Measurement

| Measure | Target | Actual |
|---|---|---|
| Launch announcement open / read rate | | |
| FAQ views in first 2 weeks | | |
| Questions raised in channel (and answered within 1 business day) | | |
| Pulse survey: "I understand why we are using Clones" (1–5) | | |
| Pulse survey: "I am worried AI will replace my role" (1–5, lower is better) | | |

## Good looks like

- The sponsor sends the launch message personally and visibly uses a Clone. Sponsor silence reads as doubt.
- The replacement question is answered before anyone asks it, in writing.
- Win stories use real numbers against baseline and quote real people.
- Managers are briefed before their teams hear anything.
- Recognition is regular. Clone of the Month and Champion spotlights keep momentum after launch week.
- Common mistake: promising outcomes in the launch message. Promise the approach; report outcomes once they are measured.

## How Clone helps

The **Enablement Clone** drafts each message from the templates above, the Department Opportunity Brief and the latest Adoption Dashboard numbers, then routes drafts for approval. The **Project Clone** keeps the calendar in the portal and flags any department go-live without a scheduled announcement. Win stories and Clone of the Month data come straight from Power Rating and usage in the portal.

## Sign-off

| Role | Name | Date | Decision |
|---|---|---|---|
| Executive sponsor | | | Approved |
| Internal communications lead | | | Approved |
| HR lead (if applicable) | | | Approved |

## Related

- [Champion Charter](/playbook/templates/champion-charter)
- [Training Curriculum](/playbook/templates/training-curriculum)
- [Go-Live Checklist](/playbook/templates/go-live-checklist)
- [AI Use Policy](/playbook/templates/ai-use-policy)
- [Change Management at Clone Solutions](https://clone.org/solutions/change-management)

---
From the Clone Solutions Playbook: https://solutions.clone.org/playbook/templates/communications-plan
