On this page
- The duty you actually have is narrower than the one you feel
- Two tests settle the yes or no in about a minute
- The Personeur Disclosure Ladder, and how to pick your rung
- What to say when a client or a prospect asks you directly
- What to say when a board member or an investor asks
- What to say when a journalist asks, and the on record rule
- The internal case, when a salaried employee writes the CEO's posts
- The sentences that manufacture an obligation you never had
- What moving up a rung actually buys you
There is no general obligation to announce that an executive uses a writer, and most audiences already assume professional help behind consistent output. The narrower duty is real. Never claim sole composition, answer directly the moment you are asked, and give the same answer to a client, a board member, an employee and a journalist. Inside your own company the calculation reverses, because the fact is already known and the only live question is whether the writer is credited.
The duty you actually have is narrower than the one you feel
No general rule requires an executive to announce that someone helps write their LinkedIn posts. Speeches, letters to shareholders, opinion columns and books have been produced this way for a century, and the convention that the named person is the author of the position rather than the typist of the sentence is older than the platform. What you are feeling is not a legal obligation. It is the discomfort of holding a fact you have never had to say out loud.
Three things do create a real obligation, and only three. The first is a specific claim you made yourself, in public, about how the writing was produced. The second is a contract you signed: some employers, some award submissions, some publications and some paid partnership arrangements require attribution or disclosure as a term. The third is a category where authorship itself is the product being sold, which covers bylined columns in publications, academic credit and anything a reader buys because a named person wrote it rather than because a named person believes it.
of B2B marketers call LinkedIn the most effective channel for thought leadership. An executive feed is now a serious professional instrument rather than a hobby, which is exactly why the question of who writes it starts arriving from people whose opinion has consequences.
Content Marketing Institute, cited 2026The pages that answer this question online almost all stop here. They establish that no rule compels disclosure, then move on. That leaves the executive with the settled principle and none of the equipment, because the difficult moment is never the decision. It is the second when a client leans back and asks, in front of two of their colleagues, whether you write your own stuff.
Two tests settle the yes or no in about a minute
Run the sole composition test and the authorship test, in that order, and the answer for your situation falls out. The sole composition test asks whether you have ever claimed, in a specific sentence, to have personally composed the words. The authorship test asks whether the reader is buying the authorship or the position. If both come back clean, you are in the ordinary case, and the ordinary case requires nothing to be announced.
| The situation | Claimed sole composition? | Is authorship the thing being bought? | What follows |
|---|---|---|---|
| Ordinary executive posts, written from your interviews and positions | No | No | Nothing to announce. Answer honestly if asked, in the words below |
| A post that says you wrote it at five in the morning after a hard week | Yes, explicitly | No | You created the obligation. Correct it quietly and stop writing that sentence |
| A bylined column in a publication that commissions named writers | Implied by the byline | Yes | Disclosure terms belong in the commissioning agreement, agreed before filing |
| An awards entry, a fellowship application or academic credit | Implied by submission | Yes | Follow the body's stated authorship rules, which usually govern this explicitly |
| A paid partnership or sponsored post | Not relevant | No | Different disclosure entirely, and it is about payment rather than about the writer |
| A book, where the writing itself is the product | Implied by the cover | Yes | Settle credit in the contract, whether that is a named collaborator or silence |
The two tests applied to the situations executives actually find themselves in.
Notice which row causes almost all the trouble. It is not the book and it is not the column. It is the ordinary executive who had no obligation at all, wrote one performative sentence about their own writing process, and converted a private arrangement into a public and falsifiable claim.
The Personeur Disclosure Ladder, and how to pick your rung
Disclosure is not binary, which is why the yes or no framing keeps failing people. There are four rungs, each with a different cost and a different thing it buys. Pick the lowest rung that would survive the question you are most likely to be asked in the next twelve months, and then live on that rung consistently rather than moving up and down depending on who is in the room.
Most executives who agonise about this belong on rung one and are unconsciously comparing themselves to rung four. The gap between those two rungs is where the guilt lives, and it is a comparison against a standard that almost nobody in professional communication has ever met.
Rung one in public and rung four in private is fine. Rung one in public while telling selected people you have a writer, and telling others you do not, is the only configuration with no defence. Different answers to different rooms is the thing that turns an ordinary arrangement into an actual credibility problem, and it is almost always caused by not having rehearsed a single answer you are willing to give everyone.
What to say when a client or a prospect asks you directly
Confirm in one sentence, locate the authorship, then offer a way to verify it. Three moves, roughly fifteen seconds, and the reason it works is that the client is not conducting an integrity audit. They are asking whether the person they are about to hire is the person they have been reading, and the fastest way to prove that is to demonstrate the material rather than defend the process.
The three part answer
- Confirm without the hedge. A version that works: yes, I work with a writer. The hedge, which is a version of technically I approve everything, is heard as a no that has been dressed up, and it is the single most damaging response available because it converts a fair question into an evasion the room can feel.
- Locate the authorship precisely. Say what you supply and what the writer supplies. A version that works: the positions and the arguments are mine, we record an interview every fortnight, and the writer turns the arguments into paragraphs. The specificity is what carries it, because vague reassurance sounds exactly like a script.
- Offer verification rather than asking for trust. A version that works: ask me about anything I published this quarter and I will take it further than the post did. This is the move nobody prepares and it settles the question completely, because a person who did not originate a position cannot extend it under questioning.
The third move is the one that matters, and it is also a standard you should be able to meet. If you genuinely cannot go deeper on your own last three posts, the disclosure question is not your real problem. Your input into the engagement is, and that is a production issue that shows up in the drafts long before it shows up in a conversation, which is why it appears among the red flags in month two.
One thing to avoid: do not volunteer this in a pitch. Answering directly when asked reads as confidence. Announcing it unprompted while selling reads as pre-emptive guilt, and it invites a question the buyer had no intention of raising.
- Almost every published answer to this question resolves the yes or no and stops, which leaves the executive holding the only part that is actually difficult, namely the sentence they have to say out loud when a client asks across a table.
- You have no general duty to announce a writer, but you can manufacture one in a single sentence, and the sentence is almost always a post claiming that you personally wrote something at an unusual hour.
- The four people who ask are asking four different questions, so the answer keeps the same facts and changes its emphasis: a client is asking about attention, a board member about risk, an employee about respect, a journalist about a story.
- Inside the company disclosure is not a decision, because the drafts already pass through several inboxes; the decision is whether the person writing them is named, paid for the skill and allowed to reference the work later.
- Choose the lowest rung on the ladder that survives the question you are most likely to be asked, and rehearse the answer before you need it rather than during.
What to say when a board member or an investor asks
A board member asking this is not asking about honesty. They are asking about risk and cost, in that order, and an answer pitched at the honesty question will not land because it answers something they did not ask. Give them the control structure and the spend, and the question closes in under a minute.
A version that works: yes, we use a writer. Nothing publishes without my approval, positions come from a recorded interview with me, anything touching numbers or forward looking statements goes through the same review as any other external communication, and the arrangement costs a defined amount each month against a defined output. That answer contains a control, an input source, a review path and a price, which is the shape of every answer a board is trained to accept.
| Who is asking | What they are actually asking | Lead with | What loses them |
|---|---|---|---|
| A client or prospect | Is the person I am hiring the person I have been reading | The offer to go deeper on any post you published | A hedge, or a process explanation nobody requested |
| A board member or investor | Is this a controlled and costed activity or a personal indulgence | Approval control, review path, monthly cost against output | Talking about voice and craft, which sounds like a hobby |
| An employee | Do you expect me to believe something everyone here already knows | Plain confirmation, then who does it and how it is resourced | Any implication that the arrangement is confidential internally |
| A journalist | Is there a story in the gap between the claim and the fact | The same words you would use with a client, on the record | A denial, an off the record framing, or a spokesperson answering for you |
The same facts, weighted for the person asking.
The facts never change across those four rows. Only the order changes. That is the whole discipline, and it is why a single rehearsed answer that you are willing to give to all four is worth more than four clever ones.
What to say when a journalist asks, and the on record rule
Assume everything is on record and give the same answer you would give a client. A journalist asking whether an executive uses a ghostwriter does not have a story yet, because the practice is ordinary and the answer is boring. The story only exists if the answer is a denial that can later be contradicted, or if someone in the organisation gives a different answer than you did.
The mechanism is worth understanding, because it explains why the instinct to deny is so expensive. A confirmation produces one line in a piece that was about something else. A denial creates a falsifiable claim, and falsifiable claims attract verification: an invoice, a contract, a freelancer's portfolio, a former employee, a scheduling tool with two logins. The denial is the story, not the writer.
A version that works: I work with a writer, as most executives publishing consistently do. The arguments and the positions are mine, I approve everything before it publishes, and I am happy to talk about any position I have taken. Then stop talking. The follow up question is almost always about a position rather than about the arrangement, which is exactly where you want to be.
Communications teams reflexively deflect this question, and a deflection from a spokesperson reads worse than a confirmation from the principal. Anyone who might field it should have the same three sentences you use. This is a five minute conversation that prevents the only version of this that ever becomes an actual problem.
The internal case, when a salaried employee writes the CEO's posts
Inside a company, disclosure is not a decision you get to make, because the fact is already distributed. The moment a draft passes through an inbox, the arrangement is known, and the only live question is whether the person doing the work is named, resourced and allowed to build a career on it. This is the case almost nothing published on this subject addresses, and it is the case that generates most of the actual resentment.
Work the arithmetic on your own assumptions rather than on a survey. Assume the writer, their manager, an executive assistant, one person in marketing and one in legal see drafts in a normal month. That is five people who know with certainty. Assume each of them mentions it once over a year to one person they trust, which is a conservative assumption inside a workplace, and the count doubles. Ten people knowing a thing is not a secret. It is an unmanaged fact, and unmanaged facts get told in the worst possible framing by whoever is most annoyed.
The internal failure is rarely about honesty. It is about credit and career. A communications professional who writes a CEO's feed for two years has produced the best work of their career and can point to none of it. If they leave with no evidence, the organisation has consumed a portable asset and returned nothing, and that is the grievance that eventually leaks.
- Name the work in the job description, using words like executive communications or executive content, so the role is a recognised profession rather than an unspoken favour
- Say it plainly in the room the first time somebody asks, because the alternative is a rumour that carries an implied accusation the plain answer does not
- Agree in writing what the writer may show a future employer, whether that is anonymised drafts, approved samples under a confidentiality agreement, or a written reference describing the scope
- Pay for the skill rather than the seniority band, because an executive voice is a specialist competence and treating it as an admin task is what starts the countdown to their resignation
- Give the writer direct access to the executive rather than routing through a chief of staff, since every intermediary strips out the specifics that make the writing sound like a person
- Decide who holds the account credentials and write it down before anybody leaves, which is a separate question covered in what happens to the account afterwards
One more internal rule, and it is the one that prevents the ugliest version. Never ask an employee to deny it. Putting a salaried person in the position of lying about their own work on your behalf is where an ordinary arrangement becomes something they will describe very differently once they have left.
The sentences that manufacture an obligation you never had
Most disclosure crises are self inflicted, and they are inflicted by a single performative sentence inside a post. You had no duty to announce anything until you made a specific factual claim about your own writing process, and once you have, every reader who later learns otherwise is not discovering a convention. They are discovering that you told them something untrue about a small thing, which they will generalise.
- Any variant of writing this at five in the morning, which is the most common one and the most quoted back. It is also unnecessary, since the reader is there for the argument rather than the hour it was typed.
- No ghostwriter, no AI, just me. This appears most often in posts about authenticity, which is a genre that produces this problem at a higher rate than any other.
- Every word here is mine. Sometimes true, frequently a habit picked up from other feeds, and impossible to walk back if it is not.
- I never let anyone touch my writing. Said as a personality claim rather than a factual one, and read as a factual one.
- Describing your writing routine in specifics you do not actually have, such as the Sunday morning session or the notebook, because a fabricated ritual is a harder thing to be caught in than the arrangement it was invented to conceal.
There are true replacements that do the same emotional work. This took me three attempts to get right is true if it did, and it is about the thinking rather than the typing. I have argued about this internally for a month is usually true and is far more interesting to a reader than the hour of composition. I changed my mind on this since I last wrote about it is the strongest of all, because it is a claim about ownership of the position, which is the thing you genuinely own.
The general rule is simple enough to hold in your head while drafting. Claim the thinking, never claim the typing. A writer can produce your sentences. Nobody can produce your positions, which is why the positions are the only thing worth asserting authorship over.
What moving up a rung actually buys you
Moving from private to askable or stated buys three specific things, and it is worth knowing them because the decision is usually made on feeling rather than on what changes. It removes the story from anyone who might otherwise reveal it, since a fact you have published cannot be used as a revelation. It makes your writer referenceable, which matters if you want them to stay and matters more if they are an employee. And it signals operating scale, because a person with a writer is a person with enough happening to require one.
It costs one thing, and the cost is real. Disclosure invites the follow up question of how much of this is actually you, and that question has to be answered with evidence rather than assurance. The evidence is specificity in the posts themselves: your numbers, your names, the argument you had, the decision that went badly. A disclosed feed full of general industry wisdom is worse than an undisclosed one, because you have told the reader to look for you and then not been there.
Around 3% of members post more than once a week, according to aggregate 2026 LinkedIn statistics reports. Consistent executive output is visibly unusual, and readers are not naive about how it gets produced. That is the quiet reason disclosure costs less than most executives expect, and it is why the arrangement is far more likely to be assumed than discovered.
Whichever rung you choose, put it in writing with your writer, alongside what they may show and to whom. Discretion running in one direction only is not an arrangement, it is an assumption, and the contract is the right place to settle it. Both sides of that question sit in the clauses that actually bite and in who owns published posts.
Questions people ask next
Do I legally have to disclose that I use a ghostwriter on LinkedIn?
What do I say if an employee asks whether I write my own posts?
Does admitting to a ghostwriter damage trust with clients?
Should I name my ghostwriter publicly?
Is it different if my ghostwriter is an employee rather than a freelancer?
What if someone posts publicly that I use a ghostwriter?
Send one old post.
Email any post you have published, with your LinkedIn URL. A rewrite in your voice comes back free, so you can judge the craft on your own words.
Get the free rewrite →