Latest
What’s New at The Writing King: Week of October 25, 2026Challenger Remembrance Day: The Engineer Who Wouldn’t SignJoel Salomon: The Truth About MoneyReddit Is Putting Up a Login Wall. Wikipedia Won’t Be Far Behind.Victoria Chemko: The Body Is the First TechnologySir Patrick Stewart: A TributeA Yale Economist Says We Won’t Be Missed. He Forgot the Bread Line.Walter Koenig: A TributeAI Has Paid Off Outside Tech. Apollo Is Reading the Wrong Scoreboard.I Don’t Post Bad ARC Reviews. I Send the Author a Note.The Little Red Book of Stuff That Works!Your Kids Are Your Own FaultGrow a PairYou’re Broke Because You Want to BeIt’s Called Work for a Reason!No Time for TactShut Up, Stop Whining, and Get a LifeWilliam Bessette: AI Enablement and Child Welfare TechnologyFree Book Planning ToolsWhat’s New at The Writing King: Week of October 18, 2026Ghostwriting by the Numbers: Timelines, Word Counts and the First CallPromising Young Woman (2020) ReviewBillions for AI, Pennies for the Plumbing: AI Companies Should Pay to Keep PHP AlivePHP2Shell: AI Found a 22-Year-Old Crack Under Your Website in Two DaysPetrov Day: The Officer Who Didn’t Believe the ComputerKindle Unlimited Is Now Kindle+. AI Audiobooks Just Joined the BuffetChina Is Using Bots to Fan the Data Center Backlash. The Backlash Is Still Real.The Society of Authors Signed an Ethical AI Charter, Then Ran From It in Eight DaysMo Gawdat Says the AI Dystopia Starts in 2027. Read the List, Skip the DatesWhen to Quit Writing a Book: I’ve Abandoned Dozens, and I’d Do It AgainGetty Images Filed for Bankruptcy. Can You Prove You Licensed Your Book’s Images?Fluff Words: Cut Them From Your Prose, Keep Them in Your DialogueWhere Can Writers Learn Storytelling From Movies? Richard Lowe Publishes 1,226 Film and TV Reviews With Writing Craft NotesWhere Are the Independent Bookstores and Public Libraries Worth Visiting in Tampa Bay? Author Richard Lowe Profiles 44 of ThemWhere Can You Hear Founders and Executives Tell Their Own Stories? Richard Lowe’s Leaders and Their Stories Publishes Every Unscripted Interview With a Full TranscriptWhat Should You Know Before Hiring a Ghostwriter? The Writing King Publishes 57 New Answers, Including What to Do When It Goes WrongAuthor Richard Lowe Publishes Eight Volumes of Enemies of You, a Researched Series on the Forces Working Against Ordinary AmericansThe Jackal (1997) ReviewThe Day of the Jackal (2024) ReviewYour First Novel Is an Apprentice Piece: What Beta Readers and Editors Can’t FixWhen the Cloud Gets Bombed: What the AWS Data Center Strikes Teach About BackupsHuman-Written Book Labels Are Gatekeeping With a FeeThe Enshittification of Microsoft Office: Why I Switched to a Free CloneGlobal Encryption Day: The Padlock Every Writer Depends OnWriting Your Worst Moments in a Memoir: Show the Evidence, Skip the VerdictHow to Register a Copyright for Your Book (and What Doesn’t Count)Your AI Chats Aren’t Private: Deleted ChatGPT Logs in CourtThe Board Seat Scam: A 419 Letter in a Business SuitI Joined the Science Fiction Book Club 30 TimesCitations in a Memoir: Endnotes, Footnotes and Fair Use

What Happens When You Disagree With a Chapter

TL;DR: A draft arrives and something structural is wrong. That moment decides the project. The first draft feels strange because you’re reading yourself described for the first time, the fix is naming what a reader would wrongly conclude from a passage, and rewriting it yourself teaches the writer nothing while giving the book two voices.

A draft arrives and something is wrong with it. Not a typo. Something structural. The chapter says what you said and it doesn’t sound like you, or it emphasizes the wrong part of a story, or it makes an argument you agree with in a way you’d never have made it.

That moment decides more about the project than anything before it. Handled well it produces a better book and a working relationship that survives another six months. Handled badly it produces a client who stops reading drafts, approves everything, and loses interest in a book they’re still paying for. Clients disappear mid-book often, and my contract accounts for it. Thirty days without contact puts a project on hold, and sixty means it’s abandoned. I’d much prefer an argument about chapter three to that silence. The difficulty is that most people have no practice at this. Giving detailed critical feedback on somebody else’s writing about your own life isn’t a skill anybody develops in an ordinary career, and the natural instincts are mostly wrong.

Some people go quiet and hope the next chapter is better. Some rewrite the passage themselves. That solves one chapter and teaches the writer nothing. Some deliver a general verdict, saying it doesn’t feel right. That’s true and unusable.

I want clients to tell me when a chapter is wrong. The ones who go quiet worry me far more, because a client who stops objecting is often a client who’s about to stop reading, and a book the author has stopped reading is in trouble. There’s a way to have this conversation that works, and it’s worth settling on before the first draft lands.

Decide how you’ll handle the first chapter you dislike before you receive it, because your instinct in the moment will be to say something vague or nothing at all.

Why does a good first draft still feel wrong to the author?

Because you’re reading yourself described for the first time. Everything you’ve ever said about your career, you said out loud, to somebody, in a conversation you were steering. Reading it back as prose is a different experience and the strangeness isn’t a quality judgment. That reaction is strongest in the first two or three chapters and fades. Plenty of authors dislike a passage on Monday and find it fine on Thursday, having changed nothing. Which is an argument for leaving a draft alone for a day before responding. Not to be polite. Because the first reaction and the considered one are frequently different and only one of them is useful.

What kind of feedback on a ghostwritten chapter is usable?

Specific, located, and about effect instead of preference. This paragraph makes it sound like the decision was obvious, and it wasn’t. That’s usable. It names a place, describes what the text does, and says why it’s wrong. I don’t like this chapter isn’t usable. Neither is make it punchier. That’s a request for an outcome with no information about the problem.

Before and after: Name the passage and what it gets wrong
Before

I don’t like this chapter. Can you make it punchier?

After

This paragraph makes it sound like the decision was obvious, and it wasn’t. A reader would think I never hesitated.

The second note names a place, says what the text does and says why it’s wrong, as the post asks.

Clients often apologize for their writing, or tell me they can’t write at all. I tell them that’s why people hire a ghostwriter, and the same goes for feedback. Nobody expects you to know how to fix the paragraph. Tell me what it gets wrong and let me worry about the repair.

The most useful thing an author can say is what a reader would wrongly conclude from a passage. That points straight at the fix and it uses knowledge only you have.

A desk seen from above and to the side. A man leans over a marked-up printed chapter, pen poised, one paragraph bracketed heavily

What should you not do when you disagree with a ghostwritten chapter?

Rewrite it yourself. It’s the obvious move and it feels efficient. You know what you meant, so you fix the paragraph and send it back, and the chapter is now correct.

The most useful thing an author can say is what a reader would wrongly conclude from a passage.

What has happened is that the writer learned nothing about why it was wrong, so the same error appears in chapter nine. And a book with rewritten passages scattered through it develops two voices. Readers notice without being able to say what’s bothering them. Describe the problem and let the person whose job it is solve it. If they can’t solve it twice in a row, that’s real information about the relationship and it’s better to have it early.

When is the disagreement about something else?

When it keeps happening in the same place. A recurring objection to how a particular period gets written is rarely a writing problem. Usually there’s something about that period you haven’t said, or have said in a way that protects somebody, and every draft of it will feel wrong because the material is incomplete. A good writer notices the pattern and asks. That conversation is uncomfortable and it normally produces the best chapter in the book.

If nobody asks, the section stays slightly false through every revision, and it’s usually the one readers find flat.

How should the conversation with your ghostwriter go?

In writing first, then out loud. Notes in the document are better than a call for the specific objections, because they stay attached to the passage and the writer can work through them without reconstructing what you meant. Nobody remembers a verbal note about paragraph three of chapter six.

I record every call and send the client a summary document after each session, so nothing said out loud gets lost. Even so, I want the specific objections written in the draft itself, pinned to the sentence they’re about, because a recording can’t point at paragraph three. What the call is for is the pattern. Whether the voice is drifting, whether the structure is holding, whether something about the whole approach needs to change. Doing it the other way round, a long call about specific paragraphs, produces a conversation that both parties leave with different notes.

How should author feedback change over a ghostwriting project?

The objections get fewer and more specific.

Early chapters draw a lot of feedback, much of it about voice, and that’s the calibration happening. By the middle of a book it should be down to a handful of points per chapter, mostly factual or about emphasis.

If the volume of objections isn’t falling by chapter six, something is wrong that more feedback won’t fix. Either the voice was never captured, or the two of you have different books in mind, and both of those are worth naming out loud instead of grinding through.

How author feedback should change across a bookA timeline of how an author's objections to ghostwritten chapters should change as a book progresses. Early chapters draw heavy feedback, mostly about voice, as the writer calibrates. By chapter six the volume of objections should be falling, and if it is not, the problem should be named out loud. By the middle of the book feedback should be down to a handful of factual or emphasis points per chapter.How author feedback should change across a bookEarly chaptersHeavy feedback, mostly voiceThe calibration happening, and thedraft feels strangest hereBy chapter sixObjections should be fallingIf not, name the problem out loudinstead of grinding throughMiddle of the bookA handful per chapterMostly factual points or questions ofemphasis
How author feedback should change across a bookA timeline of how an author's objections to ghostwritten chapters should change as a book progresses. Early chapters draw heavy feedback, mostly about voice, as the writer calibrates. By chapter six the volume of objections should be falling, and if it is not, the problem should be named out loud. By the middle of the book feedback should be down to a handful of factual or emphasis points per chapter.How author feedback should changeacross a bookEarly chaptersHeavy feedback, mostly voiceThe calibration happening, and the draft feelsstrangest hereBy chapter sixObjections should be fallingIf not, name the problem out loud instead ofgrinding throughMiddle of the bookA handful per chapterMostly factual points or questions of emphasis

Feedback on a ghostwritten book should shrink from heavy voice notes early to a few factual points by the middle.

A project where the author is still rewriting the tone in chapter twelve is a project that should have had a difficult conversation at chapter four.

My take

Describe the problem and let the writer fix it. Your own rewrite teaches them nothing and leaves your book with two voices. Put specific objections in notes on the document, where they stay attached to the words. If the same section keeps feeling wrong, look at what you haven’t said about that period. Expect the conversation to be uncomfortable, and expect a better chapter to come out of it.

What if you are simply wrong about a chapter?

It happens, and a writer who never says so isn’t doing the job. Authors sometimes object to something that’s working. A story that feels self-indulgent to the person who lived it is frequently the most engaging passage in the chapter. An admission that feels exposing is often what makes the whole book credible.

You’re the worst-placed person to judge that, because you’re the only reader who was there.

So the exchange should go both ways. If your writer agrees with every objection you raise, you’ve hired somebody who’s managing you instead of making the book better.

I tell prospects on the first call that a book is a months-long relationship between two adults with honest communication both ways, and a writer who nods along to every note is breaking that deal just as surely as a client who vanishes.

How to handle a ghostwritten chapter you disagree with.
Situation What to do Why
The first draft feels strange Leave it a day before responding The first reaction and the considered one often differ
Giving a note Be specific, located and about effect “Make it punchier” says nothing about the problem
The most useful note Say what a reader would wrongly conclude from a passage It points at the fix and uses knowledge only you have
The urge to rewrite it Describe the problem and let the writer solve it Rewrites teach nothing and give the book two voices
The same section keeps feeling wrong Look at what you have not said about that period The material is usually incomplete
Choosing a format Written notes for specific objections, calls for patterns Notes stay attached to the passage
Objections not falling by chapter six Name the problem out loud The voice was never captured, or you want different books
You might be wrong Expect the writer to push back A writer who agrees with everything is managing you

From the author
The Ghostwriting Advantage by Richard Lowe

The Ghostwriting Advantage
Drafts that describe you for the first time feel strange. The Ghostwriting Advantage covers how to get your book written for you by somebody who has done it 54+ times.

Frequently Asked Questions

Why does a ghostwriter’s first draft feel wrong?
Because you’re reading yourself described for the first time. The reaction is strongest in the first chapters and fades, and plenty of authors dislike a passage on Monday and find it fine on Thursday having changed nothing.
What feedback on a ghostwritten chapter is useful?
Specific, located and about effect. Naming a paragraph and saying what a reader would wrongly conclude from it points straight at the fix and uses knowledge only the author has.
Should I rewrite a ghostwritten passage myself?
No. It feels efficient and it teaches the writer nothing, so the same error reappears later, and scattered rewrites give a book two voices that readers notice without being able to name.
What if I keep objecting to the same section of my ghostwritten book?
That’s usually not a writing problem. There’s normally something about that period you haven’t said, or said in a way that protects somebody, so every draft feels wrong because the material is incomplete.
Should feedback to a ghostwriter be written or spoken?
Written for specific objections, because notes stay attached to the passage. Calls are for patterns, such as whether the voice is drifting or the structure is holding.
How do I know if working with a ghostwriter is going well?
The objections get fewer and more specific. If the volume isn’t falling by chapter six, something is wrong that more feedback won’t fix, and it’s worth naming instead of grinding through.
What if my objection to a ghostwritten chapter is wrong?
It happens. Stories that feel self-indulgent to the person who lived them are frequently the most engaging, and a writer who agrees with every objection is managing you instead of improving the book.
About the Author
Richard Lowe, professional ghostwriter

Richard Lowe is a professional ghostwriter and author with 113+ books authored and 54+ ghostwritten. Before writing full time he spent 33 years in enterprise technology, including 20 years as Director of Computer Operations and Technical Services at Trader Joe's. He writes nonfiction, fiction and memoir, and works with executives and experts on books that build authority.

More about Richard Lowe →

Disclaimer

The views and opinions expressed in this blog post are solely those of Richard Lowe and are based on personal experience and research. This content is for informational purposes only and should not be construed as professional legal, financial, accounting, or business advice. Always consult with qualified professionals before making important business or legal decisions. Richard Lowe is not a lawyer, accountant, or licensed professional advisor, and this content does not establish any professional relationship.

0 comments

No comments yet. Yours can be the first.

Was this useful?

Leave a comment