You may notice that Word’s AutoCorrect feature sometimes replaces a specific word combination and other times leaves it alone. This inconsistency can be confusing, especially when you rely on AutoCorrect to fix typos, expand abbreviations, or insert special characters. The root cause lies in how Word evaluates context, case sensitivity, and the order of entries in the AutoCorrect list. This article explains the technical reasons behind the inconsistent behavior and shows you how to control when AutoCorrect fires.
Key Takeaways: Why AutoCorrect Skips Certain Word Combinations
- AutoCorrect entry order and duplicates: When two entries share the same trigger text, only the first one in the list runs, causing the second to appear inconsistent.
- Case sensitivity of AutoCorrect entries: An entry defined as “teh” will not match “Teh” or “TEH”, so the same word typed in different cases triggers differently.
- Contextual exceptions and formatted text: AutoCorrect does not run inside hyperlinks, fields, or when the text is part of a larger word, which creates the appearance of skipped corrections.
Why AutoCorrect Applies Inconsistently to Specific Word Combinations
AutoCorrect in Word is a rule-based replacement engine. When you type a space, punctuation, or press Enter, Word checks the word immediately before the cursor against its list of AutoCorrect entries. If it finds a match, it replaces the typed text with the replacement text. However, several factors cause the engine to skip a match or apply a different replacement.
Duplicate AutoCorrect Entries Compete for the Same Trigger
If you add a new AutoCorrect entry that uses the same trigger text as an existing entry, Word keeps both entries in the list. Only the entry that appears first in the alphabetical list runs. The second entry never triggers. For example, if you have an entry that replaces “adn” with “and” and another entry that replaces “adn” with “Adobe”, only the first one in the list fires. The other appears to be ignored entirely.
Case Sensitivity in AutoCorrect Entries
AutoCorrect respects the case of the trigger text exactly as you typed it when you created the entry. An entry with the trigger “teh” matches only lowercase “teh”. If you type “Teh” at the start of a sentence, AutoCorrect does not replace it unless you also have an entry for “Teh”. This case-sensitive matching is the most common reason a word combination triggers only sometimes.
AutoCorrect Exceptions List Blocks Certain Words
Word maintains an internal exceptions list that prevents AutoCorrect from running on specific words. You can add words to this list manually, and Word also adds words automatically when you press Backspace to undo a correction. Once a word is in the exceptions list, AutoCorrect never replaces it again unless you remove it from the list.
Context Where AutoCorrect Does Not Run
AutoCorrect does not run inside hyperlinks, tracked changes, fields, or when the typed text is part of a larger word. For example, if you type “teh” as part of “tehran”, AutoCorrect will not replace it because the text is not a standalone word. Similarly, if you are editing inside a hyperlink display text, AutoCorrect is disabled.
Steps to Diagnose and Fix Inconsistent AutoCorrect Triggers
- Open the AutoCorrect dialog
Go to File > Options > Proofing > AutoCorrect Options. This opens the AutoCorrect dialog where you can see all current entries. - Search for duplicate trigger words
In the Replace column, scroll to find the word combination that triggers inconsistently. If you see two or more rows with the same Replace text, delete all but the one you want to keep. Select the row and click Delete. - Check the case of the trigger word
Note whether the trigger word in the AutoCorrect list is lowercase, uppercase, or title case. Type the word in that exact case to see if AutoCorrect fires. If you need case-insensitive correction, create separate entries for each case variation. - Review the AutoCorrect exceptions list
In the AutoCorrect dialog, click the Exceptions button. In the First Letter and INitial CAps tabs, look for your trigger word. If it appears there, select it and click Delete to remove the exception. - Clear the AutoCorrect exceptions added automatically
Switch to the Other Corrections tab in the Exceptions dialog. This tab lists words that Word added automatically when you pressed Backspace after a correction. Remove any entries that match your inconsistent trigger. - Test the correction in a plain document
Create a new blank document. Type the trigger word in the exact case shown in the AutoCorrect list, followed by a space. If AutoCorrect still does not fire, close Word completely and restart it to refresh the AutoCorrect engine.
If AutoCorrect Still Behaves Inconsistently
AutoCorrect does not run inside a table cell or text box
AutoCorrect works inside tables and text boxes, but it may appear to skip if the cell or text box is part of a linked or locked document section. Check whether the document has sections with different proofing languages. AutoCorrect uses the proofing language of the text. If the language is set to a language that does not have AutoCorrect entries, the correction does not run. Select the text, then go to Review > Language > Set Proofing Language and choose the language that matches your AutoCorrect entries.
AutoCorrect does not fire after a manual undo
When you press Ctrl+Z or Backspace right after AutoCorrect makes a replacement, Word adds the original word to the exceptions list automatically. To restore correction for that word, open the AutoCorrect Exceptions dialog as described above, go to the Other Corrections tab, and delete the word. The next time you type that word, AutoCorrect will run again.
AutoCorrect does not work with keyboard shortcuts or AutoText
AutoCorrect runs only when you type text followed by a space, punctuation, or Enter. It does not run when you insert text via a keyboard shortcut, AutoText, or a macro. If you are using a shortcut to insert a word combination, AutoCorrect never evaluates it. Use the AutoCorrect entry directly instead of a shortcut.
| Item | AutoCorrect Entry | AutoCorrect Exceptions |
|---|---|---|
| Purpose | Replaces typed text with replacement text | Prevents AutoCorrect from replacing specific words |
| Storage location | AutoCorrect list in Normal.dotm | Exceptions list in Normal.dotm |
| Case sensitivity | Exact match of trigger case | Case-insensitive match |
| Duplicate handling | Only the first entry in alphabetical order runs | All matches block the correction |
| Automatic addition | User adds entries manually | Word adds entries when user presses Backspace after a correction |
To keep AutoCorrect consistent, review your AutoCorrect list monthly for duplicates. Delete any entries you no longer need. When you create a new entry, type the trigger word in all lowercase to match the most common typing pattern. If you need case-insensitive behavior, create three entries for the same trigger: lowercase, Capitalized, and ALLCAPS. This ensures AutoCorrect fires regardless of how you type the word.