Why Your Spellchecker Can't Catch Bad Grammar (And What Actually Can)

The Squiggly Line Lied to You

Spellcheck does one job: it checks whether a string of letters matches an entry in a dictionary. That's it. It has no idea what a sentence means, whether the words are in the right order, or whether you meant to write a completely different word that happens to also be spelled correctly.

Take this sentence: "Their coming to the meeting, but we're going to loose the contract if we don't respond." Every single word in there is spelled correctly. Not one red underline. But it should be "they're," not "their," and "lose," not "loose." Spellcheck has nothing to say about either mistake, because both are real words — just the wrong ones.

Grammar checking works on a different layer. It looks at how words relate to each other: does the subject match the verb, does the pronoun point to something clear, does the sentence actually finish the thought it started. That's a harder problem than dictionary lookup, which is why so many writers assume the green checkmark on their spellcheck means the writing is clean. It doesn't. It means the words exist.

Five Errors Spellcheck Will Never Flag

• Homophone swaps — its/it's, affect/effect, then/than — every option is a valid word, so nothing looks wrong to a dictionary
• Subject-verb agreement across a long clause — "the list of requirements, which changes every quarter, are confusing" reads fine at a glance but the verb doesn't match the subject
• Dangling or misplaced modifiers — "walking into the office, the printer was broken" implies the printer walked in
• Comma splices and run-ons — two complete sentences glued together with just a comma, grammatically wrong but spelled perfectly
• Tense drift within a paragraph — starting in past tense and sliding into present halfway through without meaning to

What This Actually Costs You

None of these errors will stop a reader from understanding your point on the first pass. That's exactly why they're dangerous — they don't announce themselves. Instead they chip away at something quieter: the reader's confidence that you're careful. A dangling modifier in a cover letter doesn't confuse the hiring manager, but it does make them wonder what else you didn't check.

In a client email, a comma splice reads as rushed. In a report headed up the chain, a subject-verb mismatch reads as sloppy, even when the underlying analysis is solid. The gap between "technically understandable" and "reads like it was written by someone paying attention" is almost entirely made up of the errors spellcheck can't see.

Four Kinds of Grammar Tools, and When Each One Fits

Matching the Tool to the Moment

The mistake most people make is looking for the one grammar tool to rule them all. There isn't one, because the four categories above solve different problems. A browser extension is built for speed and interruption — it catches a mistake mid-sentence, while the thought is still fresh, which is exactly what you want for email and Slack. A desktop app is built for depth — it's meant to sit with a 4,000-word draft for twenty minutes, not flag you every three seconds.

The built-in check in your word processor is the laziest option in the best sense: it costs nothing to use, so there's no excuse to skip it, even if you plan to run something more thorough afterward. Web-based checkers earn their keep when you're working somewhere unfamiliar — a borrowed laptop, a client's shared drive — where installing an extension isn't an option.

A real editing toolkit isn't about ranking these four and picking a winner. It's about knowing which one to reach for based on where you're writing and how much is riding on the result.

Building Your Own Toolkit in Four Steps

1. 1
   Audit where you actually write

   List the three places you produce the most text — email, a CMS, Slack, Word. Your toolkit should cover those specific spots, not some hypothetical writing setup you don't actually use.

2. 2
   Pick one real-time layer

   Add a browser extension or lean on your built-in editor check for the writing you do fast, in the moment — messages, comments, quick replies.

3. 3
   Add one deep-pass layer

   Choose a web-based checker or desktop app for anything that goes out once and matters — proposals, reports, cover letters. Run it before you hit send, not while you're drafting.

4. 4
   Test it against a planted error

   Write one paragraph on purpose with a comma splice, a dangling modifier, and a homophone swap. See what each tool in your toolkit actually catches. You'll learn its blind spots faster this way than by reading a feature list.

The Toolkit Is the Point, Not the Tool

None of this requires overhauling how you write. It just means accepting that the checkmark from spellcheck was never telling you the whole story, and building a second, deeper layer alongside it. Once you know which category you're missing — real-time or deep-pass, browser-based or offline — filling that gap is a quick fix, not a project.

If you want to see this deeper layer in action on something you've already written, run a paragraph through AI Humanizer Lab's Grammar Checker and compare what it flags against what your current spellcheck missed. It's a fast way to find out exactly where your toolkit has a hole in it.