Why the editor never rewrites your sentences

Paste a paragraph of your novel into almost any AI tool, ask what it thinks, and within seconds it will offer to make it better. It won’t ask what you meant. It will hand the paragraph back washed, pressed and folded, faintly smelling of somebody else’s house.

Plenty of writers have tried this once. A good number of them have tried it exactly once.

When we started building RedPencil, the rewrite button was the obvious feature. It is the easiest thing to build, and it demonstrates beautifully, which is a different thing from working. We decided early that our editor would never have one. This post is about why.

First, the plain facts, because they matter more than anything clever I could say around them. RedPencil’s editor is AI. It reads the whole manuscript before it says anything. Every note points to a chapter and page. It never writes a word of your book.

Your voice is made of choices that look like mistakes

Take a sentence out of a novel and put it under a lamp, and it will usually look wrong in some small way. It runs on. It repeats a word. It starts with “And”. A tool that reads one paragraph at a time sees the fault and fixes it, and it is often right about the paragraph.

It is wrong about the book. The sentence may run on because the character speaking it can’t stop talking when she is frightened, and the reader learned that about her in Ch. 3. The word may repeat because the narrator is counting something, the way anxious people do. What looks like a flaw at the level of the sentence is often the voice at the level of the book.Editorial judgmentwhose voice, though?

A rewrite doesn’t know that, so it does exactlyEditorial judgment what rewrites do. It moves every sentence toward the most usual way of saying it. One fix at a time, your prose drifts toward a sort of tasteful magnolia, the colour a landlord paints a flat before showing it, and the book starts to sound like everyone’s.

The sentence is the wrong layer

Developmental editing is about whether the book works. Does the first chapter ask a question the middle remembers? Does the timeline hold between Ch. 7 and Ch. 19? Does the character who wants two things ever have to choose? Those are the problems that make a reader put a book down, and not one of them lives inside a single sentence.

You can polish every line of a chapter that shouldn’t exist. Writers do it all the time: weeks of careful sanding on a chapter that is later cut in an afternoon. A tool that offers sentence fixes pulls your attention to the layer that feels productive, and away from the layer where the trouble usually is.

The book has to be yours, in a way you can say out loud

Some publishers and contests now ask writers whether AI was used in their books, and readers ask too. The honest answer is getting harder to give. When the editor never writes, the answer stays simple. Every word in the manuscript is yours. The editor read it, and asked questions about it, and that is all it did to it.

That rule is the one I care about most. There are late nights, deep in my own revision, when I want the machine to just fix the ugly paragraph. I know it is ugly. I know roughly what is wrong with it. But the fixed version would be a paragraph I didn’t write, sitting in a book with my name on the cover, and I would feel it every time I reread the page.

What the editor does instead

It points. Every note names the chapter and page it rests on, so you can check the claim against your own book. It says whether the note is a fact you can see on the page, an inference drawn from the evidence, or editorial judgment, which is taste with reasons attached. When it can’t tell, it says “I can’t determine this confidently”, and says what would settle it.

It asks. If a character seems to be lying and the book never confirms it, the editor asks whether that is intended, instead of assuming.

It suggests a direction and leaves the sentences to you. Here is the kind of note it writes, about the invented manuscript from our essay on sagging middles:

Sample note, invented manuscript. Editorial judgment: from Ch. 9, p. 121 to Ch. 15, p. 214, no scene returns to the question of what happened to Ansel. Consider whether the festival in Ch. 12 could carry it. Ch. 5, p. 61, where Hesper finds the ticket stub, already shows how you make an ordinary object do that work.

That last move matters more than it looks. When the editor wants to show you a technique, it points to a place in your own manuscript where you already use it. You wrote the answer once. You can write it again.

There is one kind of change the editor can prepare, and it is worth saying plainly: a continuity fix, such as a name spelled two ways. You review it and apply it yourself, or you don’t. That is the whole list. Nothing else it produces is meant to go into your manuscript.

None of this replaces a person. RedPencil is meant as a pass before a human editor, or alongside one, so that when someone spends weeks on your book, their time goes to the questions only a person can answer.

Something to try tonight

Take the paragraph you like least. Before you touch it, write the editor’s note on it yourself: where it is, down to the page, what is wrong with it in one sentence, and one question you would ask its author. Then answer the question.

More often than you would expect, the answer is somewhere other than the paragraph. The scene before it is doing the paragraph’s job, or the paragraph is trying to explain something the chapter never set up. That is a developmental note, and you just wrote it without changing a word.

RedPencil isn’t open yet. Until it is, the sample reports show what its notes look like, on an example manuscript.

The sentences are the part of the book that sounds like you. An editor’s job is to help the rest of the book deserve them.