Skip to content

borghei/Claude-Skills / tools/linkedin/linkedin-employee-advocacy

linkedin-employee-advocacy

Verified

Designs and runs an employee advocacy programme: who posts what and how often, review rules, and what is never scripted. Use when getting a team posting, writing an advocacy policy, or fixing a programme that has stalled.

references/governance-and-consent.md

View on GitHub
# Governance and Consent

The rules that keep an advocacy programme honest toward readers, fair toward
employees and safe for the company. This file is operational guidance, not
legal advice. Employment, advertising-disclosure and securities rules differ
by country and sector; have counsel confirm the charter wording for every
jurisdiction the team works in.

## Contents

1. Three parties, three duties
2. Consent and voluntariness
3. Account ownership
4. What must never be scripted
5. Disclosure
6. Review by trigger
7. What a reviewer may and may not change
8. Deadlines and escalation
9. Restricted roles
10. Incident pause
11. Drafting tools
12. Leavers
13. Auditing the rules
14. Governance checklist

## 1. Three parties, three duties

| Party | What they are owed |
|-------|--------------------|
| Readers | To know that the author works for the company being discussed, and that the words and opinions are the author's own |
| Employees | A free choice to take part, ownership of their accounts, and no consequence for declining |
| The company | That confidential, inaccurate or unlawful statements are caught before publication |

Most governance failures protect the third party at the expense of the first
two: heavy review, supplied copy, enrolment by default. The design below
protects all three by keeping review narrow and consent explicit.

## 2. Consent and voluntariness

A personal account on a professional network is the employee's own. Taking
part is a favour to the employer, not a duty of the job, unless public
communication is genuinely part of the role (a founder, a spokesperson).

Rules the charter must state:

- Joining is by the employee's own yes, given individually, not by a
  manager's nomination or a team-wide announcement.
- Anyone may pause or leave at any time by telling the owner. No reason is
  required.
- Participation, cadence and reach are **not** inputs to performance reviews,
  bonuses, promotion cases or team targets.
- Declining has no consequence. This must be true in practice: if every team
  lead is on the programme and asks their reports weekly, it is not voluntary.

The planner treats a missing voluntary statement (GV-01) and any link to
performance or pay (GV-02) as blockers.

Recognition is fine. Thanking someone for a post that helped a customer is
normal. A leaderboard is not recognition; it is a ranking, and it converts a
voluntary activity into a competitive one.

## 3. Account ownership

- The company does not hold, request or store an employee's login. Nobody
  posts from another person's account. This is a blocker (GV-03) because it
  removes the employee's control and usually breaches the platform's terms.
- Scheduling on someone's behalf through a delegated tool is a decision for
  the employee alone, and they must be able to revoke it at once. The default
  position is that people publish their own posts.
- The connections, followers and post history built during the programme
  belong to the person and leave with them.

## 4. What must never be scripted

Some things stop being true when a company writes them. These are never
supplied as copy, however the request is phrased.

| Never scripted | Why |
|----------------|-----|
| First-person opinions ("I think", "I believe", "in my experience") | An opinion someone else wrote is not theirs; publishing it under their name misleads the reader |
| Personal stories and anecdotes | An invented or borrowed story presented as lived experience is fabrication |
| Praise for the employer or its products | Praise is only worth anything if it is unprompted and disclosed |
| Reviews, ratings and testimonials | An employee review written to order is a fake review |
| Comments and reactions on colleagues' posts | Coordinated engagement manufactures the appearance of interest. A rota or "please all like this by ten" message is a blocker (GV-06) |
| Replies to criticism of the company | A staged defence by employees reads as astroturfing and usually makes the criticism bigger |
| Statements about competitors | The legal exposure is the company's; the name on the post is the employee's |
| Identical text across several accounts | Duplicate posts are recognisable to readers and are the clearest sign of a script. Blocker GV-05 |

What the company **may** supply: facts and figures cleared for public use,
links, images, event details, a list of possible angles, a reminder of the
disclosure rule, and someone to talk a draft through with.

The line is this: the company can tell people what is true and what is
public. It cannot tell them what they think.

## 5. Disclosure

When an employee writes about their employer, its products, its customers or
its job openings, a reader should be able to tell that the author works there.

Practical rule for the charter:

- The employer is shown as the current position on the profile. This is the
  baseline, not the whole answer.
- When a post promotes something the company sells or is hiring for, the text
  itself makes the relationship plain in ordinary words: "we", "my team",
  "where I work", "I'm on the team that built this".
- If the employee received anything for posting (a gift, a prize, paid time
  beyond normal working hours), the post says so.

Advertising and consumer-protection regulators in many countries treat
employee endorsements as connected to the business. The exact wording
required differs. Have counsel confirm it, and put two or three example
phrasings in the charter so nobody has to guess. Missing guidance is blocker
GV-04.

## 6. Review by trigger

Most posts need no review. A post about how the author approaches their craft,
what they learned from a project in general terms, or what they think about a
trend puts nothing at risk. Sending those through a queue slows everything
and teaches people that their voice needs permission.

Review is therefore by **trigger**: a post is checked only when it contains
one of a short written list of things. Each trigger has a named checker and
one question to answer.

| Trigger in the draft | Checker | The one question |
|----------------------|---------|------------------|
| A customer, partner or supplier is named or identifiable | Account owner for that relationship | Have they agreed to be mentioned in this way? |
| A figure from internal systems (revenue, usage, pricing, headcount) | Finance or the data owner | Is this figure public, and is it stated correctly? |
| Anything not yet announced (product, hire, funding, partnership) | Programme owner | Is it public yet, or on what date? |
| A named competitor | Programme owner | Is the statement factual, fair and something we would stand behind? |
| A legal, regulatory, safety or medical claim | Legal or the relevant specialist | Is it accurate and are we permitted to say it? |
| A colleague is named or pictured | That colleague | Do they agree? |
| An ongoing incident, dispute or investigation | Programme owner | Should this wait? |

Authors apply the list themselves; that is what makes it fast. The charter
lists the triggers and the checker for each. A programme with no written list
is blocker GV-07; a programme that reviews everything regardless is warning
GV-08.

## 7. What a reviewer may and may not change

A checker answers their one question. They may:

- say yes;
- say no, with the reason;
- ask for a specific fact to be corrected, removed or made less specific;
- ask for the post to wait until a date.

They may not rewrite the opening, change the tone, add a call to action, swap
in brand vocabulary, remove an opinion they disagree with, or adjust the
length. If a checker thinks the writing is weak, that is feedback to offer
when asked, not a condition of approval.

The reason is not delicacy. A person whose posts come back restyled will write
the next one in the company's voice to save time, and then stop.

## 8. Deadlines and escalation

- A checker answers within one working day. The planner warns (GV-13) when
  the stated turnaround is longer than twenty-four hours or missing.
- If the deadline passes, the draft goes to the programme owner, who answers
  the same day. **Silence is not approval.** A post that tripped a trigger does
  not publish because nobody replied; the owner's job is to make sure somebody
  always does.
- The author is told the outcome and the reason every time.
- Size the checker's time to the queue. The planner estimates weekly review
  minutes from planned posts and the share expected to trip a trigger, and
  warns (RS-04) when that exceeds the time available. Tune the share after a
  month of real data.

## 9. Restricted roles

Some people cannot speak freely about the business because of what they know
or what their words imply: finance leaders, anyone with investor-facing
duties, legal staff, clinicians, people in licensed or regulated functions,
and officers of listed companies.

For these members:

- mark `restricted_role: true` on the roster;
- name the specialist who checks any post touching the business before it is
  published, and set `pre_publication_check: true` once that is agreed;
- keep their topics on craft and profession, where no check is needed.

A restricted role with no agreed check is blocker RS-06.

## 10. Incident pause

During an outage, a security event, a press issue or a legal matter, a
well-meant post from an employee can do real damage. The charter needs a pause
rule before it is needed.

| Element | Decision to record |
|---------|--------------------|
| Who can call a pause | Normally the programme owner or the incident lead |
| What it covers | Posts and comments about the company and the incident; personal, unrelated posting is not the company's to pause |
| How people are told | One message, one channel, saying what is paused and until when |
| What employees say if asked publicly | A single agreed line pointing to the official statement |
| Who gives the all-clear | A named role, not "when things calm down" |

A pause restricts speech on the company's behalf. It does not instruct
employees to defend the company, and it never asks them to post supportive
messages.

## 11. Drafting tools

Many people will use a writing assistant. The charter should say plainly what
is expected (warning GV-12 if it says nothing):

- A tool may help draft, edit or shorten.
- The author reads, corrects and owns every sentence, and could explain any of
  it in conversation.
- Nothing confidential goes into a tool the company has not approved for
  confidential material.
- A tool does not turn supplied copy into the author's own words. Section 4
  still applies.

## 12. Leavers

State in advance what happens when someone leaves (warning GV-11 otherwise):

- Their account, connections and past posts remain theirs. The company does
  not ask for posts to be deleted, except where a post disclosed something it
  should not have.
- They are removed from the roster and the weekly note on their last day.
- Programme materials (the note archive, unreleased facts) stay with the
  company.

## 13. Auditing the rules

Once a quarter, the owner checks that the rules are working as written:

1. Read a sample of posts that were published without review. Did any contain
   a trigger? If so, the list is unclear or unknown; fix the wording and
   remind people.
2. Read a sample that went to review. Was each checked only for its trigger,
   and answered on time?
3. Ask three members privately whether they have felt pressure to post, to
   react to colleagues, or to change their voice.
4. Look for near-identical posts across accounts.
5. Re-run the planner on the current roster with `--fail-on blocker`.

## 14. Governance checklist

- [ ] Voluntary participation and the pause-or-leave route are written down
- [ ] No link to performance, pay or targets, in writing or in practice
- [ ] The company holds no credentials and posts from no one's account
- [ ] The never-scripted list is in the charter
- [ ] Disclosure rule and example phrasings confirmed with counsel
- [ ] Triggers listed, each with a named checker and one question
- [ ] Checkers know what they may not change
- [ ] One-working-day answer, escalation to the owner, silence is not approval
- [ ] Restricted roles identified and their check agreed
- [ ] Incident pause rule written
- [ ] Drafting-tool rule written
- [ ] Leaver rule written
- [ ] Quarterly audit scheduled
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 323kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall