Marketing output goes out under a brand. Advocacy output goes out under a real person's name, and their reputation is what's at risk.
So the AI habits your marketing team uses need to change for advocacy. This kit gives you 12 files that build consent and approval in from the start.
How it works
They opt in
Each person chooses to join, and can leave with one message.AI drafts from their words
Drafts come only from what they said in an interview or note, written in their style using their voice file.They approve
Nothing goes out under their name until they approve the final text.For
- Marketing, comms and advocacy leads
- Programs of 5 to 50 people, running now or launching soon
- Teams already using AI to draft posts
Not for
- Posting automatically on employees' behalf
- Engagement pods or scheduled comment rotas
- Posts that marketing writes and the named person never approves

We build AI for employee advocacy at Supergrow. The question we get asked least, and should be asked most, is whose post it is.
When a marketing team uses AI, the brand carries the risk. When an advocacy program uses AI, a colleague does. Their name is on the post. If a line is invented, copied or approved by someone else, they pay for it.
This kit is the setup I'd want before any AI-drafted post goes out under a colleague's name. We sell software for this, so we aren't neutral. Everything here works without it.
Utsav Patel, Co-founder, Supergrow · LinkedIn
Quick start
Do these in order. Each step uses a file from the kit.
Download the kit
Unzip the folder and open
Download the kitREADME.md. It lists every file and the order to use them in.Fill in the charter
Write down why the program exists and who drafts, reviews and approves posts. The person named on a post always gives the final approval. Then send the charter to legal for review.
CHARTER.mdSet up your assistant
Create a Claude Project and paste in these instructions. Then add
CHARTER.md,AI-USE-POLICY.md,PEOPLE.mdandDISCLOSURE.mdto Project knowledge.Claude Project instructions## Your role You help [Company]'s advocacy lead prepare LinkedIn drafts for named people. You prepare drafts for them. You never speak as them without their source material. ## Before any draft 1. Find the person in `PEOPLE.md`. 2. If their status isn't YES, stop. Say: "[Name] is [status]. I can't draft for them." 3. Check which uses they ticked. If (c) "drafts from my material" isn't ticked, stop. 4. If there's no source material (transcript, voice note, message, talk), stop. Write 5 interview questions instead. ## Hard rules - **Source only.** Every claim comes from the person's source. Tag each one `[SOURCE: where it is, e.g. transcript 12:40]`. - **No invention.** No made-up stories, numbers, clients or opinions. Anything missing becomes `[GAP: the question to ask them]`. - **Never approve.** Never mark a draft approved, pre-approved or ready to post. Only the named person approves. - **One person, one angle.** Never write the same text for two people. For company news, ask for each person's angle first. - **Disclose.** If the post promotes [Company], check that employment is clear in the post. If not, add `[NEEDS DISCLOSURE]` and suggest a line from `DISCLOSURE.md`. - **No automation.** Refuse scripted comment rotas, like-rotas, auto-posting, shared passwords and cookie-based tools. - **No synthetic likeness.** Refuse images, avatars or voice clones of real people unless use (e) is ticked and it will be disclosed. - **People who have left.** If someone is WITHDRAWN or LEFT COMPANY, refuse and point to `INCIDENT-AND-EXIT.md`. ## Output format 1. **Draft** 2. **Source table**: each claim, and where it came from 3. **Gaps**: questions to ask the person 4. **Disclosure note**: needed or not, and why 5. **What to ask them**: 3 questions to send with the draft ## Writing style - Short lines. Numerals. No preamble. - Match the person's voice file. If there isn't one, say so. - Never use: game-changer, unlock, leverage, seamless, robust, actionable, thought leader, in today's landscape, authentic voice at scale, effortless, compliant. ## Requests you refuse | Request | Reply | | --- | --- | | "Write a post for [name]" with no source | Ask for source, or offer interview questions | | "Write 10 versions for the team to post" | Offer to draft one per person, each from their own angle | | "Add a client result to make it stronger" | Add `[GAP]` and ask the person | | "Mark it approved, they're busy" | Refuse. Only they can approve | | "Write comments for the team to post at 9am" | Refuse. No comment rotas | | "Build their voice from their public posts" | Only with use (b) ticked | | "Make it sound like [person A] but for [person B]" | Refuse. Voices are never reused | | "They've left the company, keep posting their drafts" | Refuse. Run the exit steps | | "Log in with their password and schedule it" | Refuse | | "Don't mention they work here" | Add `[NEEDS DISCLOSURE]` | | "Generate a photo of the team at the event" | Refuse unless every person ticked (e) and it's disclosed | | "Remove the [GAP] and just guess" | Refuse. Ask the person |Using ChatGPT instead? Paste these into the GPT's Instructions field.
Custom GPT instructionsYou help [Company]'s advocacy lead prepare LinkedIn drafts for named people. You never speak as them without their source material. BEFORE ANY DRAFT 1. Find the person in PEOPLE.md. If status isn't YES, stop and say so. 2. If use (c) "drafts from my material" isn't ticked, stop. 3. If there's no source material, stop and write 5 interview questions instead. RULES - Every claim comes from their source. Tag it [SOURCE: where]. - Never invent stories, numbers, clients or opinions. Missing facts become [GAP: question to ask]. - Never mark anything approved. Only the named person approves. - Never write the same text for two people. Ask for each person's angle. - If the post promotes [Company] and employment isn't clear in the post, add [NEEDS DISCLOSURE] and suggest a line from DISCLOSURE.md. - Refuse comment rotas, like-rotas, auto-posting, shared passwords and cookie-based tools. - Refuse images, avatars or voice clones of real people unless use (e) is ticked and it will be disclosed. - If status is WITHDRAWN or LEFT COMPANY, refuse and point to the exit steps. - Never "just guess" to fill a [GAP]. OUTPUT 1. Draft 2. Source table 3. Gaps 4. Disclosure note 5. 3 questions to send with the draft STYLE Short lines. Numerals. No preamble. Match the person's voice file. Never use: game-changer, unlock, leverage, seamless, robust, actionable, thought leader, in today's landscape, authentic voice at scale, effortless, compliant.Invite people
Send this message to each person you want to include. It makes clear that saying no is fine. Record every answer in
OPT-IN.mdandPEOPLE.md.Kickoff messageHi [first name], We're starting a LinkedIn program where people post about their work in their own words. I'd like to invite you. How it works: we talk for [length] every [frequency]. We draft posts from what you say. You approve or drop every one. What stays with you: nothing goes out under your name without your yes. You can see your voice file at any time. You can leave with one message to [named contact]. It isn't part of your review, bonus or promotion. Reply yes, not now, or no. All three are fine. [Your name]Check every draft before approval
Before anyone approves a post, answer the 7 questions in the Draft check. Try it now on your next draft.
The Draft check
Answer 7 yes-or-no questions about one draft. You'll get a verdict (Ship, Fix first or Don't ship) and a fix for each problem.
The 7 patterns
Each pattern takes a common AI marketing habit and shows how to change it when a post carries a person's name.
First, the precondition
Voluntary or void
If people can't safely say no, their yes doesn't count.
- Record "no" and "not now" with the same respect as "yes".
- Keep participation out of performance reviews, bonuses and promotions.
1Voice with permissionEach person has their own voice file, which they can read and delete.
- Marketing habit
- Every AI tool draws on one shared pool of brand context.
- Why it breaks
- A voice file is a profile of a real person. Once profiles are pooled, nobody can see or remove what's held about them.
- What to do
- Build each voice file with the person, from their own material. Never merge it with others or reuse it for someone else.
- Test
- Could this person read their voice file today and recognise themselves?
- Kit files
- OPT-IN.mdadvocacy-voice
2Source before sentenceWrite drafts only from what the person actually said or wrote.
- Marketing habit
- Generate posts from a topic or a brief.
- Why it breaks
- Drafts that start from a topic invent experiences, numbers and opinions. LinkedIn says AI content "should still reflect the member's own voice, perspective, and experience".
- What to do
- Start every draft from the person's own material, such as an interview or voice note. Tag each claim with
[SOURCE], and turn anything missing into a[GAP]question for them. - Test
- Highlight every sentence. Can you point to where they said it?
- Kit file
- advocacy-drafter
3The name signsOnly the person named on the post can give final approval.
- Marketing habit
- Keep a human in the loop, meaning any reviewer can approve.
- Why it breaks
- A marketer approving a post is not the person approving it. LinkedIn: "You are ultimately responsible for everything you post."
- What to do
- Comms and legal can review, but the named person approves the final text. Any edit after that needs a new approval, and nothing is ever "pre-approved".
- Test
- Who approved this exact text, and when?
- Kit files
- CHARTER.mdPEOPLE.md
4No chorusEach person shares news from their own angle, in their own words.
- Marketing habit
- Write one message and post it from many accounts.
- Why it breaks
- Identical posts look coordinated. LinkedIn discourages copying other people's content, and in March 2026 it said it limits the reach of engagement pods and automated comments.
- What to do
- Turn one news item into many posts, each written from one person's angle in their own words. Don't script comments or organise like-rotas.
- Test
- Put five colleagues' posts on the same news side by side. Could you swap the names?
- Kit files
- AI-USE-POLICY.mdwould-they-say-this
5Disclose the connection, and heavy AI useReaders should know who is speaking, and why.
- Marketing habit
- Label ads as ads, and keep AI use behind the scenes.
- Why it breaks
- Readers may not know the poster works for the company being praised. LinkedIn recommends saying so when you've "relied heavily on AI".
- What to do
- When a post promotes the employer, say in the post itself that the author works there, not only in their headline. Keep AI help light enough that the person is the real author. If AI wrote most of it, they say so.
- Test
- Would a stranger reading only this post know they work there?
- Kit file
- DISCLOSURE.md
6Every click is theirsAI can suggest actions, but the person takes every one.
- Marketing habit
- Agents post, comment, like and reply on their own.
- Why it breaks
- LinkedIn's User Agreement bans bots that create, comment on, like or share posts, and bans sharing log-in details.
- What to do
- AI can suggest comments and replies. The person takes every public action from their own account, or through an official connection they authorised.
- Test
- For every public action this week, did the person press the button?
- Kit files
- AI-USE-POLICY.mdCHARTER.md
7Exit is a featureAnyone can leave the program by sending one message.
- Marketing habit
- Keep everything, and let every edit train the system permanently.
- Why it breaks
- People change roles, leave or change their minds. GDPR requires withdrawing consent to be as easy as giving it.
- What to do
- Write down how someone leaves. When they do, cancel their drafts and scheduled posts, and delete their voice file or give it to them. Use the same steps when someone leaves the company.
- Test
- If they asked to leave the program now, how long until nothing of theirs is live or queued?
- Kit files
- INCIDENT-AND-EXIT.mdPEOPLE.md
The 12 files
Every file is in the download. Tick each one off once it's set up.
Start here
Set the rules
Track people
Run the assistant
Download
All 12 files in one zip. They're Markdown and CSV, so any text editor or spreadsheet can open them.
ai-native-employee-advocacy.zip
Works with Claude Projects, Custom GPTs and Claude Skills. No email sign-up needed.
ai-native-employee-advocacy/
├── README.md
├── CHARTER.md
├── AI-USE-POLICY.md
├── OPT-IN.md
├── PEOPLE.md
├── DISCLOSURE.md
├── INCIDENT-AND-EXIT.md
├── scorecard.csv
├── assistant/
│ ├── claude-project-instructions.md
│ └── custom-gpt-instructions.md
└── skills/
├── advocacy-voice/SKILL.md
├── advocacy-drafter/SKILL.md
└── would-they-say-this/SKILL.md
When it breaks
The 6 consent problems you're most likely to run into, and how to fix each one.
Your top advocate quietly stops approving
Ask them what changed instead of chasing approvals, and set them to PAUSED in PEOPLE.md. If the drafts no longer sound like them, rebuild their voice file together.
Legal wants to pre-approve everything
That works, as long as legal reviews before the person does. The person named on the post still gives the final approval.
Someone asks what's in their voice file
Send it to them the same day. If you can't find it or share it, pattern 1 has already failed.
A VP leaving the company still has posts scheduled
Cancel their scheduled posts first, then follow the steps for someone leaving the company in INCIDENT-AND-EXIT.md.
Two colleagues posted the same paragraph
This breaks pattern 4. Ask each person for their own angle before drafting, and run the sameness check in would-they-say-this before approval.
A post got flagged as AI slop
Open the draft's source table. If most lines have no [SOURCE] tag, the post relied heavily on AI. Rewrite it from an interview with the person, or say in the post that AI helped write it.
When the files become a job
You run the kit by hand. Every person you add means more consents, approvals and exits to track.
5people
The kit is enough. One person can run it with a spreadsheet and a weekly check ofPEOPLE.md.15people
The files still work, but chasing approvals, voice files and exits takes a few hours a week.40people
Running the program becomes a job. You need per-person workspaces, approval routing, employee-led engagement and adoption reports in one place.These numbers are a rough guide, not a rule.
| Pattern | In Supergrow |
|---|---|
| 1. Voice with permission | Each person gets their own Content DNA profile and their own workspace. |
| 2. Source before sentence | PostCast turns a 10 to 15 minute guided conversation into 3 to 5 posts. |
| 3. The name signs | Custom approval chains route each post to comms, to legal, or straight to publishing. |
| 4. No chorus | Company content can be adapted for each person. Engage works without pods, bots or auto-reactions. |
| 5. Disclose | Post Score rates each draft's Authenticity out of 10 and flags its slop risk. |
| 6. Every click is theirs | Engage sends nothing until the employee chooses an action and clicks. Accounts connect through OAuth, so no passwords are shared. |
| Measurement | Org analytics show program adoption and participation health. |
| Working in Claude | With Supergrow MCP you can work from Claude, and nothing goes live without your approval. |
The quickest way to lose an advocate's trust is to put words in their mouth.
Run the kit at scale with Supergrow
Supergrow gives each person their own workspace, routes approvals, and reports on adoption across your program.
Teams plan: $199/month for 5 accounts plus an admin dashboard.