How to use AI without losing your voice as a writer

27 September 2026ProseSpun7 min read

To use AI without losing your voice, never let a suggestion change your page before you have seen exactly what it changes. Treat every suggestion as a proposal: compare it with your own sentence, check how much longer it is, and keep only the parts that read better. Your voice survives when your sentences are the starting point and every change is one you chose.

That sounds obvious. It is easy to lose in practice, because most of the ways a voice gets flattened are quiet ones.

How does AI flatten a writer’s voice?

Rarely in one dramatic swap. It happens a word at a time:

The paste-over. You ask for a better version of a paragraph, it looks fine at a glance, and you paste it over yours. Three of your words survive. You can’t say which three.
Length creep. Each suggestion is a little longer than what it replaced. A spare chapter becomes a padded one, and nobody decided that.
The drifting notes. Your character notes get “updated” from the draft, and one day Tom is described as kind when you wrote him as careful. The prose is still yours; the facts underneath it aren’t.

None of these needs a bad suggestion. They only need a change you didn’t see.

How do you review an AI suggestion?

The same way a good editor’s notes are reviewed: against the original, one change at a time. Whatever tool you use, these steps work.

Write your own sentence first. Plain is fine. A flat line is your plan for the moment, and it is the thing every suggestion should be measured against.
Compare, don’t reread. Reading a suggestion fresh makes it sound good, because it is fluent. Put it next to your line and look only at what moved: what was cut, what was added, what stayed.
Count the words before and after. A four-word line that comes back as ninety words is no longer an edit. It is someone else’s paragraph. The number tells you that before your eye does.
Check that your sentence survived. If you asked for detail, your line should still be there, word for word, with the detail around it.
Change the one wrong word yourself. A suggestion that is nearly right is faster to fix than to ask for again, and the fix is in your voice.
Ask again rather than settle. If it’s wrong, discard it and try again. Accepting a weak version because it’s there is how the voice drifts.

What does a good before-and-after look like?

Here is a flat line about Lisa, waiting for her brother on a wet October night in a harbour city:

Before: Lisa looked at her watch and crossed the street.

And a suggestion that adds detail around it:

After: The rain had thinned to a mist that hung under the streetlights. Lisa looked at her watch and crossed the street. Ten past nine. Tom had said nine, and Tom was never late.

Run the checks. The count goes from 9 words to 33, so 24 were added. The middle sentence is the writer’s, untouched. The additions are a mist and a time, and a fact about Tom that the writer already decided: he is never late. Nothing in it contradicts the story. This one is worth keeping.

A suggestion that read “Glancing anxiously at her timepiece, Lisa hurried across the glistening avenue” would fail at step 4. It is the same moment, with every one of the writer’s words replaced by someone else’s.

(For more ways to add detail to a flat line, see how to describe a scene.)

How do you keep character notes from drifting?

A story bible, or a set of character notes, is only useful if you trust it. Trust goes the moment it changes behind your back.

Keep two rules. Every change to a note is a decision. If a tool, a co-writer or your own late-night self proposes that Tom now works days, you say yes or no to that line. Facts belong to a place in the story. If Tom loses his night shift in chapter nine, he still has it in chapter three. A note that simply overwrites the old fact will mislead you the next time you revise an early chapter.

The danger is worst with automated reading. A program that sees “Tom took a beating at the depot meeting” might decide Tom is injured. If that lands in his notes unseen, every later suggestion writes him with bruises. (We go further into how notes stay true across a long book in A novel is bigger than any model’s memory.)

What does reviewing every change cost?

A step. Every suggestion waits for you to look at it, and that is slower than letting it land. Some days you will want to accept everything and move on.

What the step buys is that you always know what changed. You never have to reread your own chapter to find out which sentences are still yours, or audit your notes to find out why Tom suddenly limps. For a writer who has more story than confidence in their sentences, that knowledge is the whole point.

How ProseSpun handles it: nothing applies silently

ProseSpun, a fiction writing app for people with more story than sentences, makes that trade on purpose. Not a sentence, not a card, not a change to a character reaches your story until you say so.

Sentences. You select a line you wrote and pick Describe, Dialogue or Rewrite. The result opens under your passage as a proposal. It shows the changes first: removed words struck through, added words underlined. When a result mostly adds, as Describe does, it marks your kept words instead, under a note that reads “Your words are marked”, so you can see your sentence survived. A switch reads Show changes / Clean copy, and ProseSpun remembers which one you prefer. (Dialogue only adds lines, so it shows the clean copy alone.) At the foot are three choices, Accept, Discard and Try again, and the count, such as 9 → 74 words · 65 added. You can type into the clean copy to fix a word before you accept. If a rewrite would replace a few of your words with many, the warning is on the button itself: Replace 4 words with 90.

Cards. Once a scene saves, ProseSpun reads it in the background and proposes changes to the cards it names. They wait in a deck, one card at a time. Each change is a row (Summary, Traits, Tie or State) marked the same way: the old words struck, the new ones underlined. A change to a character’s state says From this scene on. Earlier scenes keep what was true then. You answer each row with Keep or Skip, and can edit a summary before keeping it.

New names. When your prose names someone or something that has no card, the name waits in the deck with a short drafted card. You answer Add as a character (or whatever ProseSpun guessed), Another kind, Same as… if it’s a card you already have, or Not a card. (There is more on how cards work in how to make a story bible.)

Two things don’t wait, and neither changes a word you wrote: when a name in your prose matches a card, it becomes a link to that card, and Threads shows its guess at where a scene takes place until you answer it.

Frequently asked questions

Does using AI make your writing sound generic?

It can, if suggestions replace your sentences instead of building on them. Start from your own line, compare every suggestion against it, and keep only the changes you would have made yourself on a good day. The voice is in the choices, so make them one at a time.

Should I accept AI suggestions whole or in parts?

In parts, whenever the tool lets you. A suggestion is usually right in one place and wrong in another. Edit the wrong word yourself, or discard it and ask again, rather than taking a paragraph you only half agree with.

How can I tell what an AI tool changed in my text?

Compare the suggestion with your original word by word: removed words, added words, and the word count before and after. If your tool doesn’t show you that, paste both versions into any compare tool before you accept. Never judge a suggestion by reading it on its own.

What should a writing tool never change without asking?

Your sentences, and your notes about the story. Prose that changes unseen stops being yours; character notes that change unseen stop being trustworthy. Both should arrive as proposals you keep or discard.

Bring a flat line and see what changes before anything touches your page.

Next: How to start writing a story (even if you're not a writer)