Here’s a sentence no grammar checker will flag: “Nora pushed her dark hair out of her brown eyes and reached for the phone.” Subject, compound predicate, correct possessives, nothing out of place.
It’s also wrong, if Nora’s eyes were green back in chapter two.
Proofreading software has become very good at what it does. The trouble is that what it does stops at the edge of the sentence, and some of the most embarrassing mistakes in a manuscript live elsewhere.
What grammar software actually checks
Grammar and spelling tools evaluate language at the level of the sentence, occasionally the paragraph. They catch subject-verb agreement errors, dangling modifiers, comma splices, doubled words and every variety of their, there and they’re.
Many also flag wordiness and words repeated too close together. That’s genuinely useful, and if you aren’t running your draft through a checker before anyone else sees it, you should be.
But every one of those checks asks the same question: is this sentence correct as written? None of them asks whether the sentence is true inside your story.
Five errors that are grammatically perfect
Consider the kinds of mistakes that make a reader stop and flip back fifty pages. Each one can be written in flawless English.
- The eye color change. Nora has green eyes in chapter 2 and brown eyes in chapter 19. Both sentences are correct.
- The shifting day. The meeting is set for Tuesday. Two chapters later a character remembers it happening on Thursday, with no time passing in between to explain it.
- The impossible knowledge. Marcus confronts his sister about her affair, but nobody ever told Marcus. The reader found out in a scene he wasn’t in.
- The gun from nowhere. In the climax, the heroine grabs a revolver from the desk drawer. It’s the first time the book has mentioned a revolver, a desk or that drawer.
- The resurrection. Uncle Pete dies in chapter 11. In chapter 16, after a round of revisions shuffled some scenes, he’s pouring drinks at the wedding.
Run any of those through a grammar checker and it will pass without a squiggle. “Uncle Pete poured another round” is a perfectly formed independent clause. The software has no idea he’s supposed to be dead.
Why the software can’t see them
No smarter proofreader will close this gap next year, because it’s built into what grammar checking is. A grammar tool analyzes text in small windows, working out how words relate within a sentence: which noun a verb belongs to, whether a clause is complete, whether a pronoun has a clear antecedent nearby.
That last one is a useful comparison. An unclear antecedent is a problem of reference over a few words. A plot hole is the same kind of problem stretched over two hundred pages, a detail on page 240 that has to agree with a detail on page 31.
To catch Nora’s eyes, a tool would need to remember every physical fact about every character from page one and notice any contradiction. To catch Marcus, it would need to track who was present in every scene and what each person could plausibly know.
That’s a different job entirely. It’s what an editor does on a developmental read, holding the whole story in mind and testing each scene against it. Some manuscript analysis software now attempts whole-book reading, but a standard proofreader was never built for it, and it won’t warn you about what it’s missing.
How to check your story yourself
A simple system catches most story-level errors, and none of it needs special tools. The three habits below are the core of it, and this guide on how to find plot holes in your novel goes further into common types and where they hide.
Keep a continuity sheet
Start a document or spreadsheet with one entry per character. Every time the text states a physical fact, log it: eye color, hair, height, scars, the car they drive, their sister’s name.
Do the same for places, such as which side of the street the café is on, and for knowledge. For each major secret, note who learns it and in which chapter, so when Marcus brings up the affair you can check whether he should know.
Build a timeline
Write out the story’s days in order and pin each chapter’s events to a date, or at least a day of the week. It feels tedious. It’s also the most reliable way to catch a Tuesday that became a Thursday, a pregnancy that lasts eleven months, or a broken wrist that heals over a weekend.
Revisions are where timelines break most often. Moving a scene earlier to fix the pacing can quietly put a character in two places at once, so update the timeline every time you move something.
Read in big blocks
Grammar errors show up in slow, close reading. Story errors show up in the opposite. Read the manuscript in as few sittings as you can manage, ideally a third or half of the book at a time, so chapter 2 is still fresh when you reach chapter 19.
Keep a notepad beside you and resist fixing sentences as you go. You’re reading for facts, not commas, and every time something makes you pause (wasn’t he in the hospital?), jot the page number and keep going.
Use both kinds of checking, in the right order
Do the story check first, while you can still move scenes and cut chapters without wasting effort. Save the grammar pass for last, once the plot is locked, because there’s no point perfecting the commas in a chapter where Uncle Pete shouldn’t be alive
About the Author
