Employee Advocacy: Disclosure and Review Before Publishing
A scoped checklist for disclosures, confidential information, employee participation and regulated communications.
An employee advocacy programme needs clear rules about what people may share, how they disclose their relationship and who reviews sensitive material. An AI writer or approval button does not establish legal compliance.
This guide covers a few practical review questions, with US sources where specified. Requirements vary by jurisdiction, industry and the communication itself; have the responsible legal or compliance owner define your programme's rules.
Make the employment relationship clear
The US FTC endorsement guidance explains that endorsements must be honest and that a material relationship should be clearly disclosed when the audience would not expect it. Do not assume a job title on a separate profile will make the relationship apparent to everyone seeing a post.
An illustrative opening is: “I work on the product team at ExampleCo. Here is the approval problem we designed this feature to address.” The disclosure should be easy to notice in the actual context of the post. It does not make an unsupported performance claim acceptable.
Build a review brief for each post
| Question | Evidence or decision to retain |
|---|---|
| Is this the employee's real opinion or experience? | Author confirmation |
| Are product and performance claims supportable? | Approved source and relevant limitations |
| Is a customer identifiable? | Permission for the specific material and use |
| Is the employment relationship apparent? | Disclosure in the publishing context |
| Does this require specialist review? | Named reviewer and decision |
| What version was approved? | Final text, assets and approval record |
Removing a name is not sufficient if the remaining details identify a customer. A fictional example can teach a process, but label it and do not present it as a customer result.
Separate participation from data processing
Make it possible to decline public posting without a performance penalty. Separately, ask the privacy owner to document what employee information the programme collects, why, who can see it and how long it is retained. Do not assume that agreeing to join a programme resolves every data-processing requirement. The EDPB consent guidelines are a starting reference for EU consent questions, not a programme certification.
Escalate regulated communications
For FINRA member firms, Notice 17-18 discusses recordkeeping and supervision of business communications. The content of a communication matters; using a personal device or social account does not automatically remove obligations. Do not reduce the rules to “all posts need preapproval” or “educational posts are exempt.” Have the firm's compliance owner specify the applicable process.
Prepare the correction path
Before launch, name the person who can pause scheduled posts, investigate a disputed claim and coordinate corrections. Test that process with a harmless draft. Retain records according to the applicable policy; do not promise automatic deletion where retention duties may apply.
Related Articles
How to Turn Employee Expertise Into Company-Page Content
An interview-to-publication workflow for useful company posts, with contributor choice and clear ownership.
Employee Advocacy vs Company Posting: How to Allocate Effort
Compare employee and company-page content by purpose, effort and reader response instead of assuming a universal reach multiplier.
Employee Advocacy ROI: A Worksheet That Separates Revenue From Reach
Calculate programme costs and attributed gross profit while keeping influenced pipeline and aggregate impressions separate.